An error occurred while retrieving policy for this computer (0x8009310b) – SCCM 2012

2017-12-01T11:34:23+00:00 October 10th, 2013|Windows|

One of our clients recently had the following error when trying to deploy an image using boot media via OSD:

An error occurred while retrieving policy for this computer (0x8009310b)

We checked the smsts.log file for more info (you can find this on the client – press F8 on the error screen and type “cmtrace” from there open X:WindowsTempSMSTSsmsts.log).

Here is the excerpt:

<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: <MPNAME>:80  GET /SMS_MP/.sms_pol?0012006E-001000C2-6F6BCC28.1_00]LOG]!><time=”12:12:10.047+240″ date=”10-07-2013″ component=”TSMBootstrap” context=”” type=”1″ thread=”692″ file=”libsmsmessaging.cpp:8621″>
<![LOG[Error. Status code 404 returned]LOG]!><time=”12:12:10.062+240″ date=”10-07-2013″ component=”TSMBootstrap” context=”” type=”0″ thread=”692″ file=”libsmsmessaging.cpp:8984″>
<![LOG[Found a secure policy.]LOG]!><time=”12:12:10.062+240″ date=”10-07-2013″ component=”TSMBootstrap” context=”” type=”1″ thread=”692″ file=”libsmsmessaging.cpp:4563″>
<![LOG[Trying to decode policy.]LOG]!><time=”12:12:10.078+240″ date=”10-07-2013″ component=”TSMBootstrap” context=”” type=”1″ thread=”692″ file=”libsmsmessaging.cpp:4567″>
<![LOG[CryptDecryptMessage ( &DecryptParams, pbEncrypted, nEncryptedSize, 0, &nPlainSize, 0 ), HRESULT=8009310b (e:nts_sccm_releasesmsframeworksmscryptwindes.cpp,339)]LOG]!><time=”12:12:10.078+240″ date=”10-07-2013″ component=”TSMBootstrap” context=”” type=”0″ thread=”692″ file=”windes.cpp:339″>
<![LOG[Decoding in non ssl mode failed. Checking if decoding was really needed.]LOG]!><time=”12:12:10.078+240″ date=”10-07-2013″ component=”TSMBootstrap” context=”” type=”1″ thread=”692″ file=”libsmsmessaging.cpp:4587″>
<![LOG[Failed to verify a properly formed XML.]LOG]!><time=”12:12:10.078+240″ date=”10-07-2013″ component=”TSMBootstrap” context=”” type=”1″ thread=”692″ file=”libsmsmessaging.cpp:4592″>
<![LOG[oPolicy.RequestPolicy((GetPolicyFlags() & POLICY_SECURE) != 0, (GetPolicyFlags() & POLICY_COMPRESS) != 0), HRESULT=8009310b (e:nts_sccm_releasesmsframeworktscoretspolicy.cpp,2067)]LOG]!><time=”12:12:10.078+240″ date=”10-07-2013″ component=”TSMBootstrap” context=”” type=”0″ thread=”692″ file=”tspolicy.cpp:2067″>
<![LOG[Failed to download policy 0012006E-001000C2-6F6BCC28 (Code 0x8009310b).

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.  Following this everything worked as expected!