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
Tuesday, September 24, 2013 8:59 PM
Hi,
I have started receiving this message when building a machine from PXE. It originally happened only to known computers 2-3 weeks ago and the workaround was to delete them from CM2012 and I could build. This week it has started happening to both known and unknown computers. If I push F8 I can ping Primary and Central Servers no problems and have previously built machines so it rules out drivers.
here is a snippet from the smsts.log where I think the problem occurs.
Processing Policy Assignment DEP-CAS2002B-CAS00001-6F6BCC28. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Processing Policy Assignment DEP-CAS2002B-CAS00002-6F6BCC28. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Processing Policy Assignment DEP-CAS2002B-CAS0002B-6F6BCC28. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Processing Policy Assignment DEP-CAS2002B-CAS000DC-6F6BCC28. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Processing Policy Assignment DEP-CAS2002B-CAS000DD-6F6BCC28. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Processing Policy Assignment DEP-CAS2002B-CAS000E4-6F6BCC28. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Successfully read 153 policy assignments. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Downloading policy body CAS2000B-CAS00026-6F6BCC28. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Preparing Policy Body Request. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Setting transport. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Setting policy location = http://<mp>/SMS_MP/.sms_pol?CAS2000B-CAS00026-6F6BCC28.58_00. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Executing Policy Body Request. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
CLibSMSMessageWinHttpTransport::Send: URL: pr1-lab-svr.testdom.internal:80 GET /SMS_MP/.sms_pol?CAS2000B-CAS00026-6F6BCC28.58_00 TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Error. Status code 404 returned TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Found a secure policy. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Trying to decode policy. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
CryptDecryptMessage ( &DecryptParams, pbEncrypted, nEncryptedSize, 0, &nPlainSize, 0 ), HRESULT=8009310b (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,339) TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Decoding in non ssl mode failed. Checking if decoding was really needed. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Failed to verify a properly formed XML. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
oPolicy.RequestPolicy((GetPolicyFlags() & POLICY_SECURE) != 0, (GetPolicyFlags() & POLICY_COMPRESS) != 0), HRESULT=8009310b (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,2067) TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Failed to download policy CAS2000B-CAS00026-6F6BCC28 (Code 0x8009310b). TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
(*iTSPolicyAssignment)->GetObjects(pszClassName, aTSPolicyObjectArray ), HRESULT=8009310b (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,1224) TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
m_pPolicyManager->GetObjects( TS::Policy::TaskSequence::GetClassNameW(), TS::Policy::TaskSequence::GetPolicyCategory(), TS::Policy::TSPolicyAssignment::POLICY_TS_FOR_CD_AND_PXE, aTSPolicyObjectArray ), HRESULT=8009310b (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1205) TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Exiting TSMediaWizardControl::GetPolicy. TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=8009310b (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawelcomepage.cpp,303) TSMBootstrap 17/09/2013 9:20:44 AM 1372 (0x055C)
Setting wizard error: An error occurred while retrieving policy for this computer (0x8009310B). For more information, contact your system administrator or helpdesk operator. TSMBootstrap 17/09/2013 9:20:44 AM 1344 (0x0540)
WelcomePage::OnWizardNext() TSMBootstrap 17/09/2013 9:20:44 AM 1344 (0x0540)
Skipping Confirmation Page. TSMBootstrap 17/09/2013 9:20:44 AM 1344 (0x0540)
Skipping Task Sequence Selection Page. TSMBootstrap 17/09/2013 9:20:44 AM 1344 (0x0540)
Skipping Variables Selection Page. TSMBootstrap 17/09/2013 9:20:44 AM 1344 (0x0540)
Skipping Resolve Progress Page. TSMBootstrap 17/09/2013 9:20:44 AM 1344 (0x0540)
Activating Finish Page. TSMBootstrap 17/09/2013 9:20:44 AM 1344 (0x0540)
Loading bitmap TSMBootstrap 17/09/2013 9:20:44 AM 1344 (0x0540)
Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 17/09/2013 9:21:19 AM 852 (0x0354)
The command completed successfully. TSBootShell 17/09/2013 9:21:19 AM 852 (0x0354)
Successfully launched command shell. TSBootShell 17/09/2013 9:21:19 AM 852 (0x0354)
Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 17/09/2013 9:44:52 AM 852 (0x0354)
The command completed successfully. TSBootShell 17/09/2013 9:44:52 AM 852 (0x0354)
Successfully launched command shell. TSBootShell 17/09/2013 9:44:52 AM 852 (0x0354)
I have also reviewed the MP_GetPolicy.log on the Management Point and can see a similar error.
MP IP: Policy ID=CAS2000B-CAS00026-6F6BCC28 Version=58.00 not found or authorized for B7552EE5-1851-447D-AF79-5E1283D5032B client MP_GetPolicy_ISAPI 25/09/2013 9:24:02 AM 8952 (0x22F8)
I have done a bit of research on PolicySpy but couldn't seem to get anything useful out of it.
I have tested this on numerous machines that were all building fine and none of them work now. Also it might be worth noting that none of our Task Sequences appear in Software Center anymore when previously the did.
I have also checked the deployments for the Task Sequences to ensure they haven't changed and they are configured correctly to be available to clients, media and PXE.
Also tried Clear Required PXE Deployments on All Systems and All Unknown Computers.
Any ideas?
Mike
All replies (9)
Sunday, October 13, 2013 10:54 PM ✅Answered | 1 vote
I ended up fixing the problem by removing all Task Sequences and creating new deployments. I'm not sure what happened as these deployments were established months ago and working fine.
Mike
Wednesday, September 25, 2013 1:52 PM
Hi,
Seems a PXE certificate issue.
I suggest you disable PXE on the DP, remove the boot image=>Wait for hours, then enable it again. Please report back after doing the step above.
Juke Chou
TechNet Community Support
Thursday, September 26, 2013 1:48 AM
Hi Juke,
I Pulled back the Boot Images and Unchecked Enable PXE Support for clients. Confirmed WDS Uninstalled in the distmgr.log and once everything was complete restarted the server. I then waited a couple of hours as suggested and check this option again and after 10mins restarted the server (Required when looking in Server Manager). I then pushed the boot image to site and once they were available I attempted another build but got the same error.
I also tried recreating the Task Sequence Boot Media for a USB Device but am still getting the same error.
I noticed in the distmgr.log when I pushed the boot image to site a whole bunch on RemoveFile failed; 0x80070005 messages. see below. Not sure if this is related.
I checked my Network Access Account is set to use the computer account of the Configuration Manager Client and the local computer account is in the administrators group on the server.
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=pr1-lab-svr.testdom.internal SITE=PR1 PID=2708 TID=4280 GMTDATE=Thu Sep 26 01:28:10.223 2013 ISTR0="Boot image (x64)" ISTR1="["Display=\\pr1-lab-svr.testdom.internal\"]MSWNET:["SMS_SITE=PR1"]\\pr1-lab-svr.testdom.internal\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="CAS00005" AID1=404 AVAL1="["Display=\\pr1-lab-svr.testdom.internal\"]MSWNET:["SMS_SITE=PR1"]\\pr1-lab-svr.testdom.internal\" SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
Successfully found RDC signature for package CAS00005 version 10. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
The current user context will be used for connecting to ["Display=\\pr1-lab-svr.testdom.internal\"]MSWNET:["SMS_SITE=PR1"]\\pr1-lab-svr.testdom.internal\. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
No network connection is needed to ["Display=\\pr1-lab-svr.testdom.internal\"]MSWNET:["SMS_SITE=PR1"]\\pr1-lab-svr.testdom.internal\ as this is the local machine. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
CreateSignatureShare, connecting to DP SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
Signature share exists on distribution point path \\pr1-lab-svr.testdom.internal\SMSSIG$ SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
Set share security on share \\pr1-lab-svr.testdom.internal\SMSSIG$ SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
Share SMSPKGD$ exists on distribution point \\pr1-lab-svr.testdom.internal\SMSPKGD$ SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
Set share security on share \\pr1-lab-svr.testdom.internal\SMSPKGD$ SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
Set share security on share \\pr1-lab-svr.testdom.internal\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:10 AM 4280 (0x10B8)
Set share security on share \\pr1-lab-svr.testdom.internal\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RDC:Successfully created package signature file from \\?\D:\SMSPKGSIG\CAS00005.10 to \\pr1-lab-svr.testdom.internal\SMSSIG$\CAS00005.10.tar SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
Setting permissions on file MSWNET:["SMS_SITE=PR1"]\\pr1-lab-svr.testdom.internal\SMSSIG$\CAS00005.10.tar. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SMSDP_ExpandPXEImage: CAS00005, 1024 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
Library path mismatch: \\?\D:\SCCMContentLib, D:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
Expanding D:\SCCMContentLib\FileLib\8F28\8F28DF76A85229465D922646DBDFC01A07407BEA79BD091CFDD6DB89D5A1C17A from package CAS00005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows\Boot SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CAS00005\Windows SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CAS00005 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
Expanding CAS00005 to D:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:11 AM 4280 (0x10B8)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=pr1-lab-svr.testdom.internal SITE=PR1 PID=2708 TID=4280 GMTDATE=Thu Sep 26 01:28:13.722 2013 ISTR0="CAS00005" ISTR1="["Display=\\pr1-lab-svr.testdom.internal\"]MSWNET:["SMS_SITE=PR1"]\\pr1-lab-svr.testdom.internal\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="CAS00005" AID1=404 AVAL1="["Display=\\pr1-lab-svr.testdom.internal\"]MSWNET:["SMS_SITE=PR1"]\\pr1-lab-svr.testdom.internal\" SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:13 AM 4280 (0x10B8)
StateTable::CState::Handle - (2330:1 2013-09-26 01:28:13.722+00:00) >> (2331:1 2013-09-26 01:08:09.847+00:00) SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:13 AM 4280 (0x10B8)
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='7F6041B0-3EE2-427F-AB72-B89610A6331C' SID=2330 MUF=0 PCNT=2, P1='PR1' P2='2013-09-26 01:28:13.722+00:00' P3='' P4='' P5='' SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:13 AM 4280 (0x10B8)
CStateMsgReporter::DeliverMessages - Created state message file: D:\SCCM\inboxes\auth\statesys.box\incoming\1dsfwfd5.SMX SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:13 AM 4280 (0x10B8)
Successfully send state change notification 7F6041B0-3EE2-427F-AB72-B89610A6331C SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:13 AM 4280 (0x10B8)
Successfully created/updated the package server in the data source SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:13 AM 4280 (0x10B8)
Performing cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:13 AM 4280 (0x10B8)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:13 AM 6136 (0x17F8)
DP thread with thread handle 00000000000024C0 and thread ID 4280 ended. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:13 AM 6136 (0x17F8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:14 AM 6904 (0x1AF8)
Package CAS00005 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:14 AM 6136 (0x17F8)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=CAS00005, Version=10, Status=2301 SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:14 AM 6136 (0x17F8)
StoredPkgVersion (10) of package CAS00005. StoredPkgVersion in database is 10. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:14 AM 6136 (0x17F8)
SourceVersion (10) of package CAS00005. SourceVersion in database is 10. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:14 AM 6136 (0x17F8)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=pr1-lab-svr.testdom.internal SITE=PR1 PID=2708 TID=6136 GMTDATE=Thu Sep 26 01:28:14.525 2013 ISTR0="Boot image (x64)" ISTR1="CAS00005" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CAS00005" SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:14 AM 6136 (0x17F8)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:14 AM 6136 (0x17F8)
Used 0 out of 5 allowed processing threads. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:14 AM 6428 (0x191C)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:14 AM 6428 (0x191C)
Used 0 out of 5 allowed processing threads. SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:19 AM 6428 (0x191C)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 26/09/2013 11:28:19 AM 6428 (0x191C)
Mike
Thursday, September 26, 2013 10:09 AM
Hi,
You need to set a Network Access Account. This should be the issue.
Juke Chou
TechNet Community Support
Thursday, September 26, 2013 10:29 AM
You need to set a Network Access Account. This should be the issue.
Could you please add technical details about the usage of the network access account when it comes to downloading policies?
Torsten Meringer | http://www.mssccmfaq.de
Thursday, September 26, 2013 9:58 PM
I tried setting the Network Access Account to an account that has full administrative rights on servers and enabled PXE again from the CAS. Monitoring the distmgr.log it installs WDS but continues to log that WDS is not installed. Cannot configure PXE server to use WDS.
Again in Server Manager it is requiring a restart. When I originally setup PXE I do not recall the server requiring a restart after SCCM Initiates the WDS Install.
Could this be part of the problem, WDS is installing correctly but cannot be configured or started until a reboot. After Rebooting, SCCM does not go back and reconfigure WDS and therefore WDS remains Unconfigured?
Mike
Wednesday, March 1, 2017 5:09 PM
I didn't really see a good resolution here........... removing all TS's and deployments would be all fine and dandy if I didn't have a ton of them. Has anyone found the root cause? I'm seeing the same behavior currently.
tconners
Wednesday, March 1, 2017 5:34 PM
Tried this so far but no luck:
After a bit of research one of our consultants advised we can pinpoint the problematic policy using the first 8 characters of the policy code:
0012006E
From the SCCM server navigate to Monitoring > Deployments from the “Add Criteria” button choose “Deployment ID” and type in the above code. That will lead you straight to your troublesome policy.
For us the fix was to remove/re-add the policy from the collection (in our case All Unknown Computers”) choose the collection from Assests and Compliance > Device Collections and click the Deployments tab. Right click and delete the problematic Task Sequence then reassign it to the deployment
tconners
Wednesday, March 1, 2017 7:26 PM
Ok strange issue....... I searched SCCM with my query for the offending systems MAC and did not find it.
I searched the smstslog for NetBIOS name, found it, deleted it in the console and all is well now. Strange....... never ran into this where my MAC query did not find a MAC but the object/name was still there.
tconners