win08r2 pxe help
sccm 2007 r3 site server and 50 secondaries running pxe
I updated the 32 bit boot PE and distributed all locations just fine but now I discover that non of my secondaries rinning windows 2008 "R2" will start WDs anymore, Womdows 2008 server are just fine. Any ideas?
October 1st, 2012 9:18am
The WDS service don't start? Or do they not replay on PXE?
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2012 9:57am
wds will not start, I just applied the hotfix and that did not help.
http://support.microsoft.com/kb/976073
error: 1067: The process termiinated unexpectedly
Faulting application name: svchost.exe_WDSServer, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: wimgapi.dll, version: 6.1.7600.16385, time stamp: 0x4a5be09a
Exception code: 0xc0000005
Fault offset: 0x0000000000032a8e
Faulting process id: 0x13d8
Faulting application start time: 0x01cd9fdde5452993
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\system32\wimgapi.dll
Report Id: 26664f4b-0bd1-11e2-a3c8-00155d01b21b
--------------------------------------------------------------------------------------------
Version=1
EventType=APPCRASH
EventTime=129935739705627081
ReportType=2
Consent=1
ReportIdentifier=26664f4c-0bd1-11e2-a3c8-00155d01b21b
IntegratorReportIdentifier=26664f4b-0bd1-11e2-a3c8-00155d01b21b
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=svchost.exe_WDSServer
Sig[1].Name=Application Version
Sig[1].Value=6.1.7600.16385
Sig[2].Name=Application Timestamp
Sig[2].Value=4a5bc3c1
Sig[3].Name=Fault Module Name
Sig[3].Value=wimgapi.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7600.16385
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4a5be09a
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000032a8e
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.272.7
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=450a
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=450ac654cb038860a990ded797bd9a11
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=cbe5
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=cbe58757f13d951c7697bff411e99aca
UI[2]=C:\Windows\system32\svchost.exe
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=Windows Deployment Services Server stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\Windows\system32\svchost.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\msvcrt.dll
LoadedModule[5]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[6]=C:\Windows\system32\RPCRT4.dll
LoadedModule[7]=c:\windows\system32\wdssrv.dll
LoadedModule[8]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[9]=C:\Windows\system32\WS2_32.dll
LoadedModule[10]=C:\Windows\system32\NSI.dll
LoadedModule[11]=c:\windows\system32\IPHLPAPI.DLL
LoadedModule[12]=c:\windows\system32\WINNSI.DLL
LoadedModule[13]=C:\Windows\system32\ole32.dll
LoadedModule[14]=C:\Windows\system32\GDI32.dll
LoadedModule[15]=C:\Windows\system32\USER32.dll
LoadedModule[16]=C:\Windows\system32\LPK.dll
LoadedModule[17]=C:\Windows\system32\USP10.dll
LoadedModule[18]=c:\windows\system32\NTDSAPI.dll
LoadedModule[19]=c:\windows\system32\dhcpcsvc.DLL
LoadedModule[20]=c:\windows\system32\VSSAPI.DLL
LoadedModule[21]=c:\windows\system32\ATL.DLL
LoadedModule[22]=c:\windows\system32\VssTrace.DLL
LoadedModule[23]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[24]=c:\windows\system32\WdsDiag.dll
LoadedModule[25]=c:\windows\system32\rtutils.dll
LoadedModule[26]=C:\Windows\system32\IMM32.DLL
LoadedModule[27]=C:\Windows\system32\MSCTF.dll
LoadedModule[28]=C:\Windows\system32\mswsock.dll
LoadedModule[29]=C:\Windows\System32\wshtcpip.dll
LoadedModule[30]=C:\Windows\System32\wship6.dll
LoadedModule[31]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[32]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[33]=C:\Windows\system32\secur32.dll
LoadedModule[34]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[35]=C:\Windows\system32\credssp.dll
LoadedModule[36]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[37]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[38]=C:\Windows\System32\wdsmgmt.dll
LoadedModule[39]=C:\Windows\System32\NETAPI32.dll
LoadedModule[40]=C:\Windows\System32\netutils.dll
LoadedModule[41]=C:\Windows\System32\srvcli.dll
LoadedModule[42]=C:\Windows\System32\wkscli.dll
LoadedModule[43]=C:\Windows\system32\LOGONCLI.DLL
LoadedModule[44]=C:\Windows\system32\SAMCLI.DLL
LoadedModule[45]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[46]=C:\Windows\system32\WLDAP32.dll
LoadedModule[47]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[48]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[49]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[50]=C:\Windows\System32\DNSAPI.dll
LoadedModule[51]=C:\Windows\System32\VERSION.dll
LoadedModule[52]=C:\Windows\system32\WINTRUST.dll
LoadedModule[53]=C:\Windows\system32\CRYPT32.dll
LoadedModule[54]=C:\Windows\system32\MSASN1.dll
LoadedModule[55]=C:\Windows\System32\WDSCSL.dll
LoadedModule[56]=C:\Windows\System32\WdsImage.dll
LoadedModule[57]=C:\Windows\System32\drvstore.dll
LoadedModule[58]=C:\Windows\system32\DSROLE.DLL
LoadedModule[59]=C:\Windows\system32\rasadhlp.dll
LoadedModule[60]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[61]=C:\Windows\system32\kerberos.DLL
LoadedModule[62]=C:\Windows\system32\cryptdll.dll
LoadedModule[63]=C:\Windows\system32\bcrypt.dll
LoadedModule[64]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[65]=C:\Windows\system32\DHCPSAPI.DLL
LoadedModule[66]=C:\Windows\system32\DSAUTH.dll
LoadedModule[67]=C:\Windows\system32\adsldpc.dll
LoadedModule[68]=C:\Windows\System32\wdstptmgmt.dll
LoadedModule[69]=C:\Windows\system32\cscapi.dll
LoadedModule[70]=C:\Windows\system32\binlsvc.dll
LoadedModule[71]=C:\Windows\system32\WDSBP.dll
LoadedModule[72]=C:\Windows\system32\WDSPXE.dll
LoadedModule[73]=C:\Windows\system32\ESENT.dll
LoadedModule[74]=C:\Windows\system32\psapi.dll
LoadedModule[75]=C:\Windows\system32\wdsddps.dll
LoadedModule[76]=C:\Windows\system32\WdsImgSrv.dll
LoadedModule[77]=C:\Windows\system32\wdsmc.dll
LoadedModule[78]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[79]=C:\Windows\system32\rsaenh.dll
LoadedModule[80]=C:\Windows\system32\SHELL32.dll
LoadedModule[81]=C:\Windows\system32\profapi.dll
LoadedModule[82]=C:\Windows\system32\wdscp.dll
LoadedModule[83]=C:\Windows\system32\wdsbcp.dll
LoadedModule[84]=E:\SMS_CCM\x64\smspxe.dll
LoadedModule[85]=C:\Windows\system32\msvcp60.dll
LoadedModule[86]=E:\SMS_CCM\x64\ccmcore.dll
LoadedModule[87]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[88]=E:\SMS_CCM\x64\xprslib.dll
LoadedModule[89]=E:\SMS_CCM\x64\CCMUtilLib.dll
LoadedModule[90]=E:\SMS_CCM\x64\TSMessaging.dll
LoadedModule[91]=C:\Windows\system32\WINHTTP.dll
LoadedModule[92]=C:\Windows\system32\webio.dll
LoadedModule[93]=E:\SMS_CCM\x64\tscore.dll
LoadedModule[94]=C:\Windows\system32\MPR.dll
LoadedModule[95]=E:\SMS_CCM\x64\ccmperf.dll
LoadedModule[96]=E:\SMS_CCM\x64\mpdb.dll
LoadedModule[97]=E:\SMS_CCM\x64\smscore.dll
LoadedModule[98]=C:\Program Files\Common Files\System\Ole DB\oledb32.dll
LoadedModule[99]=C:\Windows\system32\MSDART.DLL
LoadedModule[100]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac\Comctl32.dll
LoadedModule[101]=C:\Program Files\Common Files\System\Ole DB\OLEDB32R.DLL
LoadedModule[102]=C:\Windows\system32\comsvcs.dll
LoadedModule[103]=C:\Program Files\Common Files\System\Ole DB\sqloledb.dll
LoadedModule[104]=C:\Program Files\Common Files\System\Ole DB\MSDATL3.dll
LoadedModule[105]=C:\Windows\system32\DBNETLIB.DLL
LoadedModule[106]=C:\Windows\system32\security.dll
LoadedModule[107]=C:\Windows\system32\msv1_0.DLL
LoadedModule[108]=C:\Windows\system32\schannel.DLL
LoadedModule[109]=C:\Windows\system32\ncrypt.dll
LoadedModule[110]=C:\Windows\system32\wimgapi.dll
LoadedModule[111]=C:\Windows\System32\msxml6.dll
LoadedModule[112]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[113]=C:\Windows\system32\wbemcomn.dll
LoadedModule[114]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[115]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[116]=C:\Windows\system32\ntmarta.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Windows Deployment Services Server
AppPath=C:\Windows\system32\svchost.exe
specifically what I did was add the following boot critical driver to the 32 bit PE
Intel(R) ESB2 SATA AHCI Controller
Intel(R) ESB2 SATA RAID Controller
Again, only R2 secondarys are affected.
October 1st, 2012 10:06am
Have you reviewed any log files on one of these systems? Like smspxe.log?Jason | http://blog.configmgrftw.com
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2012 10:58am
Failed to read PXE settings.
The system cannot find the file specified. (Error: 80070002; Source: Windows)
Failed to read PXE settings.
The system cannot find the file specified. (Error: 80070002; Source: Windows)
Failed to read PXE settings.
The system cannot find the file specified. (Error: 80070002; Source: Windows)
here is another clue. If i remove the 32 boot image WDS will start, if I copy it back it will not start.
October 1st, 2012 11:05am
Those errors above are normal.
Have you tried updating the DP?
How about pulling the driver and updating the DP?
Are you sure you actually need the driver in the boot image?Jason | http://blog.configmgrftw.com
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2012 12:20pm
I'm pretty sure that if I pull the 2 drivers and redeploy everything wil be fine however they are boot critical for this customer.
October 1st, 2012 12:21pm
Have you tried without the drivers in the boot image though? Just to state (the hopefully) obvious, the default boot images have many drivers built in and you should only add drivers to them if the built in drivers are not sufficient.
And, for a sanity check, if the default boot images don't work without the drivers, which drivers did you add?
Also, there's nothing else in smspxe.log? How about distmgr.log on the site server where the content originated?Jason | http://blog.configmgrftw.com
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2012 12:31pm
yes it will work without the drivers I just added (boot critical) for my customer.
October 1st, 2012 12:37pm
OK, then why add them to the boot images at all?Jason | http://blog.configmgrftw.com
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2012 12:39pm
because they were boot critical fro that customers requirements.
I stand corrected, I removed the drivers and now I can't get it to distribute, getting a disk full message which is erroneous, tons of space all servers.
SMS Despooler failed to merge delta to the compressed package "XYZ0013E". The operating system reported error 1: Incorrect function.
Possible cause: The destination drive is full.
Solution: Make more space available on that drive. SMS Despooler will attempt to merge the delta again during its next retry interval
The good news is if I manually copy it to an R2 system at least the WDS starts now. Boy what a waste of time.
trying this fix
http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/a6bb710c-91d6-4d34-b132-9c948e7c9d2b/
that didn't work. I'm dead in the water, anyone help?
October 2nd, 2012 7:10am
Just because they are boot critical doesn't mean that the default images don't have them already though. Those are two different things. Thus my (hopefully obvious) statement above that you should only add drivers to boot images if you've proven that they
are needed and not already included in the boot images.
Disable BDR on the boot images and redistribute. Also, check the amount of available disk space and the desppol.log on the destination systems.
Jason | http://blog.configmgrftw.com
Free Windows Admin Tool Kit Click here and download it now
October 2nd, 2012 11:37am
Thanks Jason, I agree and "had" the perfect PE until I screwed it up so I'm just trying to get back to square one.
I already tried disabling BDR and redistribute but I'm happy to try again.
Opening despool.log with trace32 all white, no red or yellow
317 GB free space and yet site server says:
SMS Despooler failed to merge delta to the compressed package "XYZ0013E". The operating system reported error 1: Incorrect function.
Possible cause: The destination drive is full.
Solution: Make more space available on that drive. SMS Despooler will attempt to merge the delta again during its next retry interval
October 2nd, 2012 2:29pm
This is what I had to do.
Go into SQL and remove the package entry for each location, delete the folder and re-distribute the boot image.
Free Windows Admin Tool Kit Click here and download it now
October 15th, 2012 8:40am
This is what I had to do.
Go into SQL and remove the package entry for each location, delete the folder and re-distribute the boot image.
October 15th, 2012 8:40am