FriendsOfMDT / PSD

PowerShell Deployment
MIT License
526 stars 83 forks source link

Task Sequence Failed, Return Code -2147467259 #121

Closed ewrightmdy closed 9 months ago

ewrightmdy commented 10 months ago

Hi! I'm configuring PSD/MDT for the first time and I'm encountering the above error when the task sequence reaches the driver injection stage over PXE boot. I'm using the total control method as recommended, have already generated the driver package WIMs, and the task sequence I'm using is just the default PSD template with a factory Windows 11 image. If anyone has any recommendations on potential solutions or how to further troubleshoot this error, it would be much appreciated.

ewrightmdy commented 10 months ago

I managed to resolve the above issue by cleaning the disk beforehand with diskpart, however am now encountering a different error when it reaches the install OS phase: 'Unable to continue, could not access the WIM'.

GeoSimos commented 10 months ago

Any logs to share? Redacted for sensitive info please...

ewrightmdy commented 10 months ago

Here is the actual error message:

20240115_104720

Here are the relevant portions of the smsts.log file:

Capture

The relevant portion of PSDStart.log:

Capture1

Furthermore, after the failed task sequence, if I cd into the mounted S: drive, the specified 'MININT/Cache/Operating Systems' directory does not exist.

GeoSimos commented 10 months ago

If you could attach the files (check for any sensitive info and redact accordingly) it would be much more helpful to check it out.

ewrightmdy commented 10 months ago

smsts.log PSDStart.log

GeoSimos commented 10 months ago

From what I see in the logs, you use UNC paths for the PSDDeployRoots property in your BootStrap.ini file, please read the documentation because you have to setup your environment for http/https deployment shares. Can you confirm that this is the case? Because it is evident in the log files. As I've stated in other issues, the documentation consuming will save time from you and will help us support you better (when the installation is done as expected and supported).

ewrightmdy commented 9 months ago

Hi! You were absolutely correct in that we were using UNC paths, we were unaware that they were unsupported. We've configured it over https and while we're still having issues with our configuration, it seems we're on the right track. Thanks you for all the help!

GeoSimos commented 9 months ago

Glad to hear that! Please read the documentation, it will save you a lot of time and hair pulling :-)