FriendsOfMDT
Task Sequence breaks at "Install Operating System"
The smsts.log file stated, that there is a CCM folder missing
I am using an HTTPS Deployment, authentication and access from an normal Windows Client in a Workgroup to the WebDAV share is functional with net use, file explorer, FF and Edge
I had a lot of trouble in my hardened GPO controlled environment, because the need of NTLM for authentication. -> Error 403 (http) -> Error 500 (https) -> net use "User has not been authenticated" all caused by denied NTLM.
Is it possible to run "%SCRIPTROOT%\PSDApplyOS.ps1" seperatly, just to check, if the install.wim can be applied manually from the share?
this looks like a formatting issue or a corrupted wim trying to write to the disk drive. Can you try to re-import the wim and see if that resolves it. also make sure disk can be written to.
This is the output, from a newly imported WIM, after I downloaded the Windows 11, 24H2 yesterday from mediacreation. I removed it, copied the OS from a running MDT share via Deployment Workbench, same result. I did a diskpart - clean manually a few times.
I think the download of the file is broken or will not start. What are the depending services for downloadng the file? UNC/SMB doesnt work, I tried already all different kind of Share (http, https, unc)
After a lot of testing and confusing result since yesterday, it seems, that it was caused by a misconfigured SLSHARE in CustomSettings.ini.
Actual, reproducable problem:
- when Re-Installing a system, the disk needs to be wiped manually, reboot into PE and start the TS
That is interesting; I'm not sure how that is connected...I guess the resolution is don't misconfigure your SLSHARE settings. :grin:
On the other hand, did the Wipe Disks button work in the prestart menu or did you run a diskpart clean?
this looks like a formatting issue or a corrupted wim trying to write to the disk drive. Can you try to re-import the wim and see if that resolves it. also make sure disk can be written to.
We are still seeing this issue intermittently but don't have logging turned on, so that's not it. It's not a custom WIM, just straight OS files. It's so random because you can image 4 times correctly then 2 in a row will fail at this exact same spot.
