Windows Deployment Services PXE install hangs at Solution Accelerators screen

Graham Hirst
Graham Hirst used Ask the Experts™
on
I have successfully deployed WDS 2012 R2 Litetouch Windows 8.1 images to Dell XPS 13 and Inspiron 7537 laptops, but having difficulty with a Dell OptiPlex 990 desktop.  Have injected the OptiPlex 990 x64 network drivers to the WinPE image and boot images, but when I deploy an image via PXE to the OptiPlex 990, it hangs on the screen after I select which boot image to boot from.

WDS PXE Boot Hang Screen
Cant see any meaningful information in the logs of the WDS server either.

On my first attempt, it did get passed the above screen and let me select the operating system, but it hung after clicking Next with Windows 8.1 selected.  However, not is always hangs as per the screenshot enclosed.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Most Valuable Expert 2012
Top Expert 2014

Commented:
While it has hung, can you press F8 to bring up the command prompt?  From there, can you navigate to C:\Minint\SMSOSD\OSDLogs and see anything in the BDD.log that it hangs on?

If it won't let you press F8, can you boot it using another boot disk, and read the files?

Rob.
Does this happen on multiple machines? If so then try re-creating the lite-touch image.
Graham HirstIT Engineer

Author

Commented:
This only happens on a Dell OptiPlex 990 desktop.  I don't have the desktop anymore as I had to manually build it, but I wasn't aware that I could get to some logs on the client, so I will check the local logs next time.

I have re-created the lite-touch image, but this failed as well.  I have been toying with presenting only specific drivers instead of letting Windows determine which ones it needs from the mix I've deployed, but so for, it only presents drivers if I present them all!
Introduction to Web Design

Develop a strong foundation and understanding of web design by learning HTML, CSS, and additional tools to help you develop your own website.

Most Valuable Expert 2012
Top Expert 2014

Commented:
Ok. So I guess you'll have to wait until you get another 990, I can have a look at which drivers I'm using if you need.
Graham HirstIT Engineer

Author

Commented:
@RobSampson:  If you're saying you have managed to get this to work with an OptiPlex 990, knowing what drivers you have used would be great.  Otherwise, you're right, I'll have to wait until I get my hands on another one.
Most Valuable Expert 2012
Top Expert 2014

Commented:
Here are the drivers I used from the Dell website when I added them to my OOB drivers in MDT.
Chipset - A04 R304291
Network - A02 R313802
Device - A09 R307994
USB - A01 R292027
Audio - A05 R289789
DVD - Firmware R304505
Intel Unified AMT 7 Management Interface Driver

Hopefully that helps you.

Regards,

Rob.
Most Valuable Expert 2012
Top Expert 2014

Commented:
Actually, looking at my drivers, I also notice I have added Dell WinPE Drivers A06.   That package includes device drivers for use during WinPE booting, which is where your setup is hanging.

Rob.
IT Engineer
Commented:
Getting my hands on one of these in a few days, so I should be able to run some tests.
Graham HirstIT Engineer

Author

Commented:
I injected the drivers from Dell WinPe Drivers A09 and it initially got passed the screen as per the screenshot and continued to the OS deployment...,but then it failed, with the following error.

FAILURE ( 5624 ): 2: Run ImageX: /apply \\SERVER\DEPLOYMENTSHARE$\Operating Systems\YOURIMAGE.wim
Litetouch deployment failed. Return Code = -2147467259 0×80004005
Failed to run the action: Install Operating System
Unknown error (Error: 000015F8; Source: Unknown)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operating aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015F8; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0×80004005

 I Googled and found a link with the same issue, but this didn't help as then it wouldn't even get to he screen that it hung on initially.

After rolling back the changes made from the link, I tried deploying it again... and it worked!

Wondering if a reboot on the server fixed it, or due to the fact that another deployment was in progress, but it worked all the same.  8-)
Graham HirstIT Engineer

Author

Commented:
Injecting the Dell WinPE drivers into the Windows Deployment Service Boot image solved the issue.
Most Valuable Expert 2012
Top Expert 2014

Commented:
Ok great to hear you got it working.
I don't like how cryptic the deployment error messages are, but hopefully we can get there.

Rob.
Graham HirstIT Engineer

Author

Commented:
Don't know why the points didn't go to you mate.  Maybe because it so long for me to get my hands on one of these PCs and it went to a Neglected state.
Thanks for your advice.  Do find WDS a little flaky at times, but was well pleased it worked.
Most Valuable Expert 2012
Top Expert 2014

Commented:
OK, are you able to cancel the close request?  If not, if you let me know which comments you want to select as the answer (because an irrelevant one was chosen), I can close it for you.

Rob.
Graham HirstIT Engineer

Author

Commented:
Injecting the Dell WinPE drivers into the Windows Deployment Service Boot image solved the issue.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial