bkay Posted October 30, 2013 Report post Posted October 30, 2013 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! Quote Share this post Link to post Share on other sites More sharing options...
Clientmgmt.de Posted October 30, 2013 Report post Posted October 30, 2013 I had the same problem. Uninstall SCEP and other antivirus-software from the server. Check here: http://www.clientmgmt.de/it/sccm-2012-r2-wds-service-kann-nicht-gestartet-werden/ Quote Share this post Link to post Share on other sites More sharing options...
smorris Posted October 30, 2013 Report post Posted October 30, 2013 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. Quote Share this post Link to post Share on other sites More sharing options...
mniccum Posted October 30, 2013 Report post Posted October 30, 2013 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 Quote Share this post Link to post Share on other sites More sharing options...
D3w4yne Posted October 30, 2013 Report post Posted October 30, 2013 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... Quote Share this post Link to post Share on other sites More sharing options...
D3w4yne Posted October 30, 2013 Report post Posted October 30, 2013 (edited) 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 October 30, 2013 by D3w4yne Quote Share this post Link to post Share on other sites More sharing options...
KrisO Posted October 30, 2013 Report post Posted October 30, 2013 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. Quote Share this post Link to post Share on other sites More sharing options...
hitman47 Posted October 30, 2013 Report post Posted October 30, 2013 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. Quote Share this post Link to post Share on other sites More sharing options...
mniccum Posted October 30, 2013 Report post Posted October 30, 2013 I was told if the console was removed from the server the WDS service would start. Quote Share this post Link to post Share on other sites More sharing options...
KrisO Posted October 31, 2013 Report post Posted October 31, 2013 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 http://www.systemcentercentral.com/how-to-create-a-new-boot-wim-image-from-adk-with-sccm-2012-sp1-r2-sccm-sysctr/%C2'> 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. Quote Share this post Link to post Share on other sites More sharing options...
