Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, May 7, 2015 12:08 PM
Good morning all,
Im working on implementing OS Deployment through SCCM and Ive run into a problem that I cant seem to find a fix for.
Through countless blog posts Ive finally gotten WDS to install properly and to have the service running. The only configuration done to WDS is I pointed it to the Remoteinstall directory and enabled PXE. In SCCM Ive enabled PXE support as well for the DP, configured the boot images (PXE enabled/copy to local server) and successfully distributed them to the DP.
After these steps are completed my remoteinstall\SMSBoot\ contains a few folders; x86, x64, and Fonts. x86 and x64 are both empty. If I go up a folder to remoteinstall, the SMSImages folder has both CRP0000X image folders with the WIM inside. If I go to the SMSTempBootFiles I have both CRP0000X folders with an empty sms folder and a Windows folder that contains a boot folder which has what looks to be the PXE boot files (EFI, Fonts, and PXE folders)
I don't know what im missing and why nothing is copying to the appropriate SMSboot folder, I cant diagnose anything because I don't have a SMSPXE.log either.
What do I need to do to get the files to copy correctly and why do I not have a log?
All replies (5)
Thursday, May 7, 2015 12:12 PM
Edit: just found the PXE log in a different folder. Nothing I can see appears abnormal.
Thursday, May 7, 2015 12:39 PM | 1 vote
Redistribute the boot images to the PXE-enabled DP and watch smspxe.log and distmgr.log.
There is usually no need to open WDS console at all. ConfigMgr does handle everything automatically. Also examine the eventlog.
Torsten Meringer | http://www.mssccmfaq.de
Thursday, May 7, 2015 3:10 PM
Only error I see is in distmgr.log and its ~Package CRP00002 does not have a preferred sender
In the error log I have
The Open Procedure for service "WDSMC" in DLL "C:\Windows\system32\wdsmc.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
The Windows Deployment Services Server service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.
I just noticed that the WDS server service wont start or stay started now, this was never an issue:
The Windows Deployment Services Server service terminated unexpectedly EID: 7034
Thursday, May 7, 2015 5:06 PM
The only configuration done to WDS is I pointed it to the Remoteinstall directory and enabled PXE.
I don't think you have any choice but to start this again. Disable PXE on the DP and uninstall WDS (which should uninstall automatically BTW). Reboot the server to finish the uninstall. Delete any residual folders.Then re-enable PXE again on the DP. It should install WDS automatically - do not configure anything. ConfigMgr does that for you. Restart the server to finish the WDS installation.
I have seen on a few occasions that WDS is not automatically installed. In those cases I have installed it manually (but not configured it) and then enabled PXE.
Edit: don't forget to empty your C:\Windows\Temp folder before trying again.
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
Friday, May 8, 2015 11:17 AM
The only configuration done to WDS is I pointed it to the Remoteinstall directory and enabled PXE.
I don't think you have any choice but to start this again. Disable PXE on the DP and uninstall WDS (which should uninstall automatically BTW). Reboot the server to finish the uninstall. Delete any residual folders.Then re-enable PXE again on the DP. It should install WDS automatically - do not configure anything. ConfigMgr does that for you. Restart the server to finish the WDS installation.
I have seen on a few occasions that WDS is not automatically installed. In those cases I have installed it manually (but not configured it) and then enabled PXE.
Edit: don't forget to empty your C:\Windows\Temp folder before trying again.
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
Just did everything you said to a T, restarted WDS server is running properly. Added the two boot images and they went into the proper folders. Not sure what happened, maybe the second restart was the issue.
After the two boot images were added, the WDS Service will not start:
Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.17415, time stamp: 0x54504177
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
Exception code: 0xc0000005
Fault offset: 0x000000000005f61a
Faulting process id: 0x1718
Faulting application start time: 0x01d089806a1e23dc
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll
Report Id: a9a03547-f573-11e4-80cb-005056802b96
Faulting package full name:
Faulting package-relative application ID: