KrisO

OK, so SC Endpoint Protection re installed itself automatically and it broke PXE again. While it was working I was able to image a computer. I've created a Case with Microsoft already. So I'll keep you informed.

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.

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.

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.

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.