bkay

SCCM 2012 R2 upgrade broken WDS/PXE



37 posts in this topic

Hello Everyone,

This website has been a great resource to learn about SCCM and walks you through the entire process - thanks to all who have contributed!

 

I can normally find the answers I need in this forum, but this one has me stumped.

 

My setup is a Single Site server, Windows 2012, SCCM 2012 R2 upgraded from SP1

 

The upgrade seemed to go well, with the exception of the inability to PXE boot devices. After doing much digging and troubleshooting, the problem is with the WDS service.

 

I have turned off the PXE setttings in Server and Site System Roles, removed all Boot Images from the software library, renamed the RemoteInstall folder.

 

Confirmed that the WDS services is uninstalled, restarted.

 

Enabled the PXE settings, let SCCM do the WDS install, added back the ADK 8.1 boot images.

 

If the server is restarted after the boot images are added, the WDS server crashes. If the boot images are distributed the WDS server crashes.

 

post-21866-0-47089700-1382653899_thumb.jpg

post-21866-0-77689700-1382653896_thumb.jpg

post-21866-0-11595900-1382653898_thumb.jpg

post-21866-0-80667900-1382653894_thumb.jpg

distmgr_log.txt

 

The WDS server will stay running if no boot images are added or distributed. I have tried different boot image files (not just the ADK 8.1 ones), and have the same result. The server object itself is part of the administrators group on the server. The server has not moved OU's.

 

Any ideas other than a complete re-install?

 

Thanks!

Bryce

 

 

 

Share this post


Link to post
Share on other sites


After upgrading to R2 on two sites. One site has 10 remote PXE enabled DPs, none of them would PXE boot initially after the upgrade, but a simple restart of the WDS server from within the WDS console got them all working again.

 

Did you at least try this before you went about removing roles etc?

Share this post


Link to post
Share on other sites

I never went into the WDS console to try restarting the service there, but did multiple machine restarts and tried restarting through the services management console.

Share this post


Link to post
Share on other sites

I have exactly the same issue.

 

This issue has something to do with the WINPE.WIM / BOOT.WIM files that are created from the ADK 8.1 images.

 

Trying to manually create the boot.wim files by following the TechNet article "How to Customize Windows PE Boot Images to Use in Configuration Manager" http://technet.microsoft.com/en-us/library/dn387582.aspx fails. The DISM command fails when adding any of the optional components required by Config Manager.

 

Rocket Man, are your sites running on Server 2012?

Share this post


Link to post
Share on other sites

Yes all remote DPs are running server 2012. After doing 3 more WDS service restarts today at the other remote DPs and imaging is working again via PXE at these 3 again also.

Share this post


Link to post
Share on other sites

I have the exact same error, have tried uninstalling PXE, WDS, ADK 8.1 installed all over again, if i look at the crash logg it seems to crash when WIMGAPI.DLL is loaded, the system32 one is version 6.3.9600.16412 and the wimgapi from ADK 8.1 released after okt 17 is 6.3.9600.16411, dont know if this matters but i read an old post about different versions of wimgapi.

 

i tried installing the old version of ADK 8.1, same error so wimgapi is probobly not the reason, does anyone have a valid solution for this becouse at the moment our deployment is not working.

I have opened a ticket with Microsoft and i hope i have a solution soon.

Share this post


Link to post
Share on other sites

just got an IM from the support guy at Microsoft, they apperently have alot of cases regarding this issue and need to Contact the Product team

Share this post


Link to post
Share on other sites

Hi Tjindarr,

 

I've not got any resolution yet. Also have a case logged, but waiting for updates. Thanks for the info re Microsoft having a lot of reported cases. Hopefully there will be a resolution soon.

Share this post


Link to post
Share on other sites

Somehow this seems to have autoresolved itself on my ConfigMgr server. i had added 2 boot images from the installation ISO downloaded from VLSC, but the service still crashed. This morning i added a MDT x64 boot image to create a bootable USB as PXE was not working.

A couple of hours later the support guy from Microsoft sent me an IM that he wanted to take a screen of the distmg.log while he started the WDS service. i then saw that the service was started so i tested a PXE boot and it worked..?!?

 

So my setup now is 3 bootimages on PXE, 2 from installation media both x86 and x64 and one MDT x64. the once from installation media has no drivers while the one from MDT has a bunch of drives added to it. i wont be doing anything with these until i get an answer from Microsoft support about a more stable solution as i have a feeling that if i restart the server it could crash again.

 

I had also installed reporting services and restarted the server but i dont Think it is related, had Before restarted the SCCM server about 20 times.

Share this post


Link to post
Share on other sites

I'm having the exact same issue. I just upgraded to R2, PXe stopped responding but under Site Status and Compenent Status everything is happy. I've tried these few steps below a couple of times now to see if I can trigger a fresh install of wds and pxe. and I ran into the same issues you have where it looks to do something but for me they never started to work. Has anyone else had any luck, or recommend anything?

 

  • untick the enable PXE checkbox on the distribution point. Answer yes that you want to remove the Windows Deployment service.
  • remove your boot images from your distribution point
  • After 5 minutes. Delete %windir%\temp
  • check with server manager if you can add/remove roles on the server. If WDS is done uninstalling there is a pending boot.Reboot!!!
  • check if the remoteinstall folder is located on your system. If it is delete it.
  • reboot
  • Add the PXE point again by checking the box on the distribution point properties. Check the distrmgr.log and see if the remoteinstall folder reappers..
  • Send the boot images to the distribution points again.

Share this post


Link to post
Share on other sites

After all the frustration I tried uninstalling and re-installing one last time..... and it is working!

 

Here are the steps I took (almost with a restart with each step)

  • Uninstalled ADK 8.1
  • Removed boot images from Distribution points
  • Removed Boot Images from SCCM
  • Unchecked PXE deployment from Server and Site System Roles (Let SCCM uninstall WDS)
  • Removed RemoteInstall Directory
  • Re-downloaded and installed ADK 8.1
  • Turn on PXE deployment - check Distmgr.log file to see when it finishes
  • Add Boot Image from ADK to SCCM. Turned on the PXE deployment for these images
  • Distributed Boot Images

The last step is where WDS has stopped working in the past, but today the WDS service stayed up and I was able to deploy one of my Windows 7 task sequences successfully.

 

I was at the point where re-installing on Windows Server 2012R2 seemed like the only option.

 

Good luck to anyone else with the same problems. Patience is definitely needed!

Share this post


Link to post
Share on other sites

After getting a call logged with Microsoft the resolution I was given (although still under investigation at MS) was to re-install wimgapi.msi from the WIM folder within the folder where config mgr was installed too. This has worked for me. This appears to be a problem that has previously happened in config mgr 2007, I found a TechNet article for it. I cannot paste anything into this topic for some reason, but search TechNet for BB932179, it describes re-installing wimgapi among other things.

Share this post


Link to post
Share on other sites

After all the frustration I tried uninstalling and re-installing one last time..... and it is working!

 

Here are the steps I took (almost with a restart with each step)

  • Uninstalled ADK 8.1
  • Removed boot images from Distribution points
  • Removed Boot Images from SCCM
  • Unchecked PXE deployment from Server and Site System Roles (Let SCCM uninstall WDS)
  • Removed RemoteInstall Directory
  • Re-downloaded and installed ADK 8.1
  • Turn on PXE deployment - check Distmgr.log file to see when it finishes
  • Add Boot Image from ADK to SCCM. Turned on the PXE deployment for these images
  • Distributed Boot Images

The last step is where WDS has stopped working in the past, but today the WDS service stayed up and I was able to deploy one of my Windows 7 task sequences successfully.

 

I was at the point where re-installing on Windows Server 2012R2 seemed like the only option.

 

Good luck to anyone else with the same problems. Patience is definitely needed!

 

 

I took the above advice but had to do it a bit different. When I checked the pxe box it would end up failing in the log becasue WDS would require a reboot. Here's what I did to solve my scenario:

 

What did I do:

Upgraded from ConfigMgr 212 SP1 CU2 to R2

 

What was the issue:

PXE hung at 0% loading "RemoteInstall\Boot\boot.sdi" (something like that)

restarted WDS and it failed to start

 

Environment:

CAS with two Primaries (only one of the two Primary servers had the issue)

Windows Server 2012

SQL 2012 SP1

VMWare 5.1 (VMXNET3 nic)

 

Fix:

Uncheck "deploy this boot image from the pxe-enabled dist point" on each boot image

Uncheck PXE

Check distmgr.log for uninstall success

Reboot (before the reboot the wds service will be started) DONT SKIP THIS REBOOT OR IT WILL FAIL

After reboot wds service will be gone

Add wds, choose auto reboot

Wait for wds to complete installation after reboot

Check to make sure wds is set to manual and not started

Rename or delete remoteinstall folder

Check pxe box on the DP

Check distmgr.log (filter to 'contains' wds) for success

WDS service should be started and automatic

Add new 8.1 boot images using copype.cmd process.

Uncheck "deploy this boot image from the pxe-enabled dist point" on each OLD boot image

Check "deploy this boot image from the pxe-enabled dist point" on each NEW boot image

Distribute NEW boot images

Wait for NEW boot images to be distributed

RemoteInstall\SMSImages should contain 2 boot images

Test PXE

 

and as was said previously "Patience is definitely needed!"

 

Thanks

Share this post


Link to post
Share on other sites

I tried all of the above methods and nothing is working so far....

 

My lab was upgraded from CU3 to R2 and I did not experience this issue.

 

We set up a new production site from scratch however and this has been an issue from the start.

 

edit:

 

Hadn't seen mniccum's post yet. I'll give that a shot and see what happens...

Share this post


Link to post
Share on other sites

That worked!

 

Appears the main difference is using copype.cmd, as I had already done all of the other steps in that order, except for that one.

 

Awesome! Thank you.

 

Well, that didn't last long. It's back to WDS refusing to start. It was running ok with just the x86 boot.wim, as soon as I added the x64 boot.wim WDS crashed. I removed the x64 boot.wim and WDS still won't start...

Edited by D3w4yne

Share this post


Link to post
Share on other sites

ugh, no luck so far for me. I tried Bkay method and smorris fix so far, I'll try mniccum method to see if that works. If that doesn't work I guess I'll be calling MS. Thanks for all the help.

Share this post


Link to post
Share on other sites

If ADK 8.1 is not installed then WDS boots without problem and it loads the wimgapi.dll from the system32 folder but if ADK is installed then WDS fails to start because it loads the wimgapi.dll from the ADK but if you overwrite the wimgapi.dll from the system32 folder WDS also fails to start.

Share this post


Link to post
Share on other sites
ADK 8.1 installed

MDT 2013

SCCM 2012 R2 single site, single server.


Uncheck "deploy this boot image from the pxe-enabled dist point" on each boot image

I deleted the existing Boot Images also.

Uncheck PXE

done


Check distmgr.log for uninstall success

SCCM thinks it wasn't installed....

ConfigurePXE SMS_DISTRIBUTION_MANAGER 10/30/2013 5:35:03 PM 9112 (0x2398)

PXE provider is not installed. SMS_DISTRIBUTION_MANAGER 10/30/2013 5:35:03 PM 9112 (0x2398)

No need to initialize monitoring task on SCCM2012 SMS_DISTRIBUTION_MANAGER 10/30/2013 5:35:04 PM 9112 (0x2398)

I rebooted at this point.


Reboot (before the reboot the wds service will be started) DONT SKIP THIS REBOOT OR IT WILL FAIL

Rebooted


After reboot wds service will be gone

WDS was not gone, guessing because SCCM didn't think it was installed... So I'm removing WDS letting it auto-reboot

one back online I also deleted the existing RemoteinstallFolder


Add wds, choose auto reboot

Wait for wds to complete installation after reboot

installed.


Check to make sure wds is set to manual and not started

yes


Rename or delete remoteinstall folder

folder does not exist.


Check pxe box on the DP

Done


Check distmgr.log (filter to 'contains' wds) for success

Created the DP mutex key for WDS. SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:17 PM 9208 (0x23F8)

WDS is INSTALLED SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:17 PM 9208 (0x23F8)

WDS service is already installed. SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:17 PM 9208 (0x23F8)

WDS is INSTALLED SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:17 PM 9208 (0x23F8)

Setting TFTP config key as: System\CurrentControlSet\Services\WDSSERVER\Providers\WDSTFTP SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:17 PM 9208 (0x23F8)

REMINST not set in WDS SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:17 PM 9208 (0x23F8)

WDS is NOT Configured SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:17 PM 9208 (0x23F8)

Registering WDS provider: SourceDir: C:\Program Files\Microsoft Configuration Manager\bin\x64 SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

Registering WDS provider: ProviderPath: C:\Program Files\Microsoft Configuration Manager\bin\x64\smspxe.dll SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

PxeLoadWdsPxe SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

Loading wdspxe.dll from C:\Windows\system32\wdspxe.dll SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

wdspxe.dll is loaded SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

Disabling WDS/RIS functionality SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

RegOpenKeyExW failed for System\CurrentControlSet\Services\WDSServer\Providers\BINLSVC SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

Found privilege otifyPrivilege on service WDSServer SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

Found privilege SeRestorePrivilege on service WDSServer SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

Found privilege SeBackupPrivilege on service WDSServer SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

Found privilege SeSecurityPrivilege on service WDSServer SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

Privilege SeTakeOwnershipPrivilege NOT found service WDSServer SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

ChangeServiceConfig2 succeeded for WDSServer. Added privilege SeTakeOwnershipPrivilege SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

ChangeServiceConfig succeeded for WDSServer. StartType: 0x2 SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:18 PM 9208 (0x23F8)

WDSServer status is 1 SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:19 PM 9208 (0x23F8)

WDSServer is NOT STARTED SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:19 PM 9208 (0x23F8)

Failed to restart WDS service SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:19 PM 9208 (0x23F8)

Running: WDSUTIL.exe /Initialize-Server /REMINST:"E:\RemoteInstall" SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:19 PM 9208 (0x23F8)

Waiting for the completion of: WDSUTIL.exe /Initialize-Server /REMINST:"E:\RemoteInstall" SMS_DISTRIBUTION_MANAGER 10/30/2013 7: 29:19 PM 9208 (0x23F8)

Run completed for: WDSUTIL.exe /Initialize-Server /REMINST:"E:\RemoteInstall" SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:28 PM 9208 (0x23F8)

CcmInstallPXE: Deleting the DP mutex key for WDS. SMS_DISTRIBUTION_MANAGER 10/30/2013 7:29:28 PM 9208 (0x23F8)

WDS service should be started and automatic

yes


Add new 8.1 boot images using copype.cmd process.

Followed those steps



Uncheck "deploy this boot image from the pxe-enabled dist point" on each OLD boot image

didn't need to as they were deleted.


Check "deploy this boot image from the pxe-enabled dist point" on each NEW boot image

done.


Distribute NEW boot images

done


Wait for NEW boot images to be distributed

done


RemoteInstall\SMSImages should contain 2 boot images

done


Test PXE

Received a PXE-E32 TFTP open Timeout


WDS service was stopped. received two erros in the event log.

Faulting application name: svchost.exe_WDSServer, version: 6.2.9200.16420, time stamp: 0x505a9a4e

Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a

Exception code: 0xc0000005

Fault offset: 0x000000000005870b

Faulting process id: 0x2430

Faulting application start time: 0x01ced5c7dcb65ea0

Faulting application path: C:\Windows\system32\svchost.exe

Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll


Faulting application name: svchost.exe_WDSServer, version: 6.2.9200.16420, time stamp: 0x505a9a4e

Faulting module name: ntdll.dll, version: 6.2.9200.16579, time stamp: 0x51637f77

Exception code: 0xc0000005

Fault offset: 0x000000000001af08

Faulting process id: 0x1860

Faulting application start time: 0x01ced5caa633c64b

Faulting application path: C:\Windows\system32\svchost.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll


Restarted Server.

WDS service will not start.

Share this post


Link to post
Share on other sites

Same problem here. Nothing works. Uninstall Forefront ist not an option or a solution.

 

Do you have a virus scanner enabled on the site server? If I were you, I would try it out.

Share this post


Link to post
Share on other sites

I had the same WDS crash but installing wimgapi.msi from the Installfolder\Microsoft Configuration Manager\wim\ (NOT from the install media for R2 which didn't work) solved it for me.

One reboot later and it's all on and working again.

 

Running it on Server 2012.

Share this post


Link to post
Share on other sites

yeah I tried C:\Program Files\Microsoft Configuration Manager\wim\wimgapi.msi and that didn't work for me.

 

I also tried uninstalling System Center Endpoint Protection and that did work... I'm getting " Configuration Manager is looking for Policy" then it "PXE Boot Aborted. Booting to Next Device..." Which is alot better which means it's responding and I can work.

My with this solution is that Endpoint will probably install it self again and PXE will stop working. But I'll follow up on how it goes.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now