Problems with PXE booted PE environment (Network Steve Forum)

Problems with PXE booted PE environment

I'm getting an 0x8009310B error when I use PXE boot to run an OSD TS. The machine can't find it's policies. I've verified that NIC drivers are loading and can ping using "Ping server" and as "Ping server.fqdn.com" to the MP and any other sites on the network or internet. I do NOT get the problem when I boot from a CD built from the same 32bit PE image. Nor do I get the error if I boot from an older version OSD disk that requires that I download a PE to run the TS. Those seem to run just fine. I'm uninstalled my PXE point on the server, and recreated it, and that didn't help. I've also tried modifying the dates on my self signed certificates to try to get the policies to load. I'm stumped. Anyone have any new ideas for me to try?

May 14th, 2010 12:08pm

can you post the failure messages from your SMSTS.log file please ? My step by step SCCM Guides windows-noob on Twitter

Free Windows Admin Tool Kit Click here and download it now

May 14th, 2010 4:25pm

Here you go. It appears to be unable to decrypt the policy. MP Public Certs=308201D830820145A0030201020210E205D71524A65A834C32E637E4CF81A6300906052B0E03021D050030213111300F06035504031308505244534D533031310C300A06035504031303534D533020170D3039303431333233313030355A180F32313039303332313233313030355A30213111300F06035504031308505244534D533031310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D00308189028181008815D0D6E4D13EC9A06CA79B0FF9BA73DAED8E7157DDAFEEA7D98919F3676FA185582109151FA1866C9707EB2A2A847A4B6D79DF8CC97251D243F992D16027EBD39E361E6B7938F0C8C133D1F70C93A16E1374A36A65BCC45BC55A5116FE1AEE1A77959BBA79B5372C16EE4C6209F3B5D193215EB2DD8CFE34586CC96DE886970203010001A317301530130603551D25040C300A06082B06010401823765300906052B0E03021D0500038181004C8DC1446A25C78A7D8B0A563A0873D4C15272E9B4771CB42E4B82167E4EEF4B277D4F9CC44BD8B49C4BC0F1AA846205A4D2EAACECFBB850C276EF1FDF6A64FDDB8C9E74CFA43B2BAEF21C55AA27A7FB7EB42B12FF288BEC7E89E8496C5FAB0C56CE3387A5E6195457A8F6132489CA6CA86F8194EAF4702125079C5DCE0AA5A3 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) MP: server=SMSSERVER.COMPANY.COM, http=80, https=443, default=80 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Root CA Public Certs= TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Missing root CA environment variable from variables file TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Custom hook from X:\\TSConfig.INI is TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) No custom hook found TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) No Need to create Authenticator Info TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Getting MP time information TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Requesting client identity TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Formatted header: TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>21311d85-9d4d-4b54-8ee9-fdba014ea274</SourceID><SourceHost/><TargetAddress>mp:[http]MP_ClientIDManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-05-15T01:07:43Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="306"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>MP_ClientIDManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) CLibSMSMessageWinHttpTransport::Send: URL: SMSSERVER.COMPANY.COM:80 CCM_POST /ccm_system/request TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) The request has succeeded. 200 OK TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Decompressing reply body. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) ::DecompressBuffer(65536) TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Decompression (zlib) succeeded: original size 411, uncompressed size 2436. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Client identity reply: <ClientIDReply RequestReceivedTimeHigh="30077882" RequestReceivedTimeLow="1106176202" ReplySentTimeHigh="30077882" ReplySentTimeLow="1106332664" ReplyServerTimeZoneBias="420" ReplyServerTimezoneStandardTimeHigh="31014192" ReplyServerTimezoneStandardTimeLow="31266000" ReplyServerTimeZoneStandardBias="0" ReplyServerTimezoneDaylightTimeHigh="31014192" ReplyServerTimezoneDaylightTimeLow="31266000" ReplyServerTimeZoneDaylightBias="-60" ReplyServerTimezoneStandardTimeYear="0" ReplyServerTimezoneStandardTimeMonth="11" ReplyServerTimezoneStandardTimeDayOfWeek="0" ReplyServerTimezoneStandardTimeDay="1" ReplyServerTimezoneStandardTimeHour="2" ReplyServerTimezoneStandardTimeMinute="0" ReplyServerTimezoneStandardTimeSecond="0" ReplyServerTimezoneStandardTimeMilliSeconds="0" ReplyServerTimezoneDaylightDateYear="0" ReplyServerTimezoneDaylightDateMonth="3" ReplyServerTimezoneDaylightDateDayOfWeek="0" ReplyServerTimezoneDaylightDateDay="2" ReplyServerTimezoneDaylightDateHour="2" ReplyServerTimezoneDaylightDateMinute="0" ReplyServerTimezoneDaylightDateSecond="0" ReplyServerTimezoneDaylightDateMilliSeconds="0" Unknown="0"><Identification><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) -60 -60 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Server time zone info: 420, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Client Identity: TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Netbios name: TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Current time: 2010-05-15 01:07:43.507 TZ:Pacific Standard Time Bias:0480 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Current time zone info: 480, Pacific Standard Time, [0 0 0 0 0 0 0 0], 0, , [0 0 0 0 0 0 0 0], 0 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Adjusting the system time: -7200.567 seconds TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Time zone info set to: 420, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60 TSPxe 5/14/2010 7:07:43 PM 1184 (0x04A0) New time: 2010-05-14 23:07:42.939 TSPxe 5/14/2010 5:07:42 PM 1184 (0x04A0) Current time: 2010-05-14 23:07:42.939 TZ: Bias:0420 TSPxe 5/14/2010 5:07:42 PM 1184 (0x04A0) Downloading policy from SMSSERVER.COMPANY.COM. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Initializing HTTP transport. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting URL = SMSSERVER.COMPANY.COM. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting Default Port = 80. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting SSL = false. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting CRL = false. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting Server Certificates. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting Media Certificate. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Preparing Client Identity Request. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting transport. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting SourceID = 21311d85-9d4d-4b54-8ee9-fdba014ea274. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting site code = SMS. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting SMBIOS GUID = 0A9E4723-4D82-4E98-9645-E49ECE618EE6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Adding MAC Address 00:03:FF:E9:4D:85. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Executing Client Identity Request. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Requesting client identity TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Formatted header: TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>21311d85-9d4d-4b54-8ee9-fdba014ea274</SourceID><SourceHost/><TargetAddress>mp:[http]MP_ClientIDManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-05-14T23:07:43Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="412"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>MP_ClientIDManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) CLibSMSMessageWinHttpTransport::Send: URL: SMSSERVER.COMPANY.COM:80 CCM_POST /ccm_system/request TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) The request has succeeded. 200 OK TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Decompressing reply body. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) ::DecompressBuffer(65536) TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Decompression (zlib) succeeded: original size 464, uncompressed size 2578. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Client identity reply: <ClientIDReply RequestReceivedTimeHigh="30077882" RequestReceivedTimeLow="1112121758" ReplySentTimeHigh="30077882" ReplySentTimeLow="1112121758" ReplyServerTimeZoneBias="420" ReplyServerTimezoneStandardTimeHigh="31006264" ReplyServerTimezoneStandardTimeLow="31271384" ReplyServerTimeZoneStandardBias="0" ReplyServerTimezoneDaylightTimeHigh="31006264" ReplyServerTimezoneDaylightTimeLow="31271384" ReplyServerTimeZoneDaylightBias="-60" ReplyServerTimezoneStandardTimeYear="0" ReplyServerTimezoneStandardTimeMonth="11" ReplyServerTimezoneStandardTimeDayOfWeek="0" ReplyServerTimezoneStandardTimeDay="1" ReplyServerTimezoneStandardTimeHour="2" ReplyServerTimezoneStandardTimeMinute="0" ReplyServerTimezoneStandardTimeSecond="0" ReplyServerTimezoneStandardTimeMilliSeconds="0" ReplyServerTimezoneDaylightDateYear="0" ReplyServerTimezoneDaylightDateMonth="3" ReplyServerTimezoneDaylightDateDayOfWeek="0" ReplyServerTimezoneDaylightDateDay="2" ReplyServerTimezoneDaylightDateHour="2" ReplyServerTimezoneDaylightDateMinute="0" ReplyServerTimezoneDaylightDateSecond="0" ReplyServerTimezoneDaylightDateMilliSeconds="0" Unknown="1"><Identification><Machine><ClientID>GUID:3a45b82d-9361-482a-ba28-3331846c26e5</ClientID><NetbiosName>Unknown</NetbiosName></Machine></Identification></ClientIDReply> TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) -60 -60 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Server time zone info: 420, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Client Identity: GUID:3a45b82d-9361-482a-ba28-3331846c26e5 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Netbios name: Unknown TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Client GUID = GUID:3a45b82d-9361-482a-ba28-3331846c26e5, Netbios name = Unknown, State = Unknown TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Client is unprovisioned TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Using unknown machine GUID: bb342e15-7f6f-4e84-a388-b1692768f181 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Unknown client identity: GUID:3a45b82d-9361-482a-ba28-3331846c26e5 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Preparing Policy Assignment Request. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting transport. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting site code = SMS. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting client ID = bb342e15-7f6f-4e84-a388-b1692768f181. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Executing Policy Assignment Request. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Sending RequestAssignments TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Formatted header: TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>bb342e15-7f6f-4e84-a388-b1692768f181</SourceID><SourceHost/><TargetAddress>mp:[http]MP_PolicyManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-05-14T23:07:43Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="728"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>MP_PolicyManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) CLibSMSMessageWinHttpTransport::Send: URL: SMSSERVER.COMPANY.COM:80 CCM_POST /ccm_system/request TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) The request has succeeded. 200 OK TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Decompressing reply body. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) ::DecompressBuffer(65536) TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Decompression (zlib) succeeded: original size 11006, uncompressed size 84246. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Retrieving Policy Assignments: TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {8dd45e15-5035-44db-a8cc-e02f86e4b2ef}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {8e057290-c2b7-47bc-97f1-e9232f176cf8}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {32281478-8f4d-42f2-8169-b8198c6b80bf}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {0f92868f-8c14-472a-893e-0a3afa74ceb4}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {373610a4-df6d-4320-ab93-398b09371bb2}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {4d252995-4e6c-418f-9458-8a35e3d3923d}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {c484fd55-9773-4baa-b1fe-530af256458b}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {3b15543b-234a-41dd-bd9b-ab1346dab50e}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {3a52b025-7986-4da6-a3d4-616680b34765}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {6aeacb62-fb50-4141-826f-d8cd305a8113}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {c18894e6-afeb-46fa-bc6b-6dfe007237bb}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {d8587b3b-2efc-4106-a84c-43b9b6c1ee15}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {e116fca0-b47e-440d-a242-d148461bb494}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {ffaf79d4-c2c9-40c3-989e-0c466eb39d46}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {2241fe3b-b4f2-4a75-917f-21f035fce557}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {8f100676-4fff-46e4-87db-9197ac771e4b}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {cc9cc9c5-5939-40f3-ad94-0bd8b02c4ab4}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {42d673d2-e63b-41d6-9fe7-ab410f2d4a7f}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {2ba7ebae-6b11-468a-b9ea-9496298b1465}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {f3e5ebde-ffb4-42ce-bac7-1d98274974da}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {219088eb-d965-447e-934d-fd9b2a252f35}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {9fac66ca-bcec-4466-937c-fe0e3327547c}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {230ce71a-057c-4e58-ac01-dc4bf17363d8}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {d5f3b007-67b1-4a22-a2fc-6de72a15b22e}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment {5981bfbf-2af5-458e-a44a-f05b790bdf8d}. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment SMS2006F-SMS000A3-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment SMS20096-SMS000B8-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment SMS200BD-SMS000D1-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS0000D-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS0004F-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS00053-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS00054-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS00055-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS00062-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS0007B-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS0007D-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS00086-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS000A0-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS000A9-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS00003-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS00004-C547EBB5. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS0005F-1CF0612E. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS00006-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS00071-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS000CC-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS2006F-SMS0006C-AEF036D4. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS00003-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS00004-C547EBB5. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS00006-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS0000D-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS0004F-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS00053-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS00054-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS00055-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS0005F-1CF0612E. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS00062-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS0006C-AEF036D4. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS00071-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS0007D-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS00083-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS00086-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS000A9-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS20096-SMS000B5-C392A31F. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS00003-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS00004-C547EBB5. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS00006-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS0000D-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS0004F-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS00053-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS00054-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS00055-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS0005F-1CF0612E. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS00062-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS0006C-AEF036D4. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS00071-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS0007B-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS0007D-6CC4AEB6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS000A0-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS000CC-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS000D0-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Processing Policy Assignment DEP-SMS200BD-SMS00086-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Successfully read 81 policy assignments. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Downloading policy body SMS2006F-SMS000A3-DBBBC9D6. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Preparing Policy Body Request. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting transport. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting policy location = http://<mp>/SMS_MP/.sms_pol?SMS2006F-SMS000A3-DBBBC9D6.47_00. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Executing Policy Body Request. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) CLibSMSMessageWinHttpTransport::Send: URL: SMSSERVER.COMPANY.COM:80 GET /SMS_MP/.sms_pol?SMS2006F-SMS000A3-DBBBC9D6.47_00 TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) The request has succeeded. 200 OK TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) found a secure policy TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) decoding policy TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) CryptDecryptMessage ( &DecryptParams, pbEncrypted, nEncryptedSize, 0, &nPlainSize, 0 ), HRESULT=8009310b (e:\nts_sms_fre\sms\framework\smscrypt\windes.cpp,359) TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) SMS::Crypto::DES::DecryptBuffer ( hCertStore, (BYTE*) pServerReply, nReplySize, pDecrypteReply, dwDecryptedSize), HRESULT=8009310b (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,4339) TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) oPolicy.RequestPolicy((GetPolicyFlags() & POLICY_SECURE) != 0), HRESULT=8009310b (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1841) TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Failed to download policy SMS2006F-SMS000A3-DBBBC9D6 (Code 0x8009310b). TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) (*iTSPolicyAssignment)->GetObjects(pszClassName, aTSPolicyObjectArray ), HRESULT=8009310b (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1111) TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) 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_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,948) TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Exiting TSMediaWizardControl::GetPolicy. TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=8009310b (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawelcomepage.cpp,280) TSPxe 5/14/2010 5:07:43 PM 1184 (0x04A0) Setting wizard error: An error occurred while retrieving policy for this computer (0x8009310B). For more information, please contact your system administrator or helpdesk operator. TSPxe 5/14/2010 5:07:43 PM 1128 (0x0468) WelcomePage::OnWizardNext() TSPxe 5/14/2010 5:07:43 PM 1128 (0x0468) Skipping Confirmation Page. TSPxe 5/14/2010 5:07:43 PM 1128 (0x0468) Skipping Task Sequence Selection Page. TSPxe 5/14/2010 5:07:43 PM 1128 (0x0468) Skipping Variables Selection Page. TSPxe 5/14/2010 5:07:43 PM 1128 (0x0468) Skipping Resolve Progress Page. TSPxe 5/14/2010 5:07:43 PM 1128 (0x0468) Activating Finish Page. TSPxe 5/14/2010 5:07:43 PM 1128 (0x0468) Initializing the countdown timer. TSPxe 5/14/2010 5:07:43 PM 1128 (0x0468) Loading bitmap TSPxe 5/14/2010 5:07:43 PM 1128 (0x0468) Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 5/14/2010 5:07:44 PM 740 (0x02E4) The command completed successfully. TSBootShell 5/14/2010 5:07:44 PM 740 (0x02E4) Successfully launched command shell. TSBootShell 5/14/2010 5:07:44 PM 740 (0x02E4)

May 14th, 2010 7:17pm

Hi, This looks like a cerficate problem, when looking at the error code. SMS::Crypto::DES::DecryptBuffer ( hCertStore, (BYTE*) pServerReply, nReplySize, pDecrypteReply, dwDecryptedSize), HRESULT=8009310b 1. Are you running x64 2008 OS? 2. Are you using a self signed PXE certificate? I was having the exact same problem at another customer, where the only thing that worked for me was: 1. Uninstall PXE Service Point 2. Uninstall MP 3. Reboot 4. Re-install MP 5. Re-install PXE (Create a new self signed PXE certificate) Regards, Bess, Kenneth - http://www.systemcenterblog.net - http://www.systemcenterforum.net

Free Windows Admin Tool Kit Click here and download it now

May 15th, 2010 6:58am

1) No not yet. I'm running 2003 server on the SCCM server. I will be migrating shortly, but don't have the server up yet. Why do you ask? (just curious, as Im actually going to migrate very soon if I can) 2) I am using a self signed cert. And I was thinking the same as you, so I changed dates multiple times on the expiration of my cert, thinking that would force the server to regenerate the cert and solve the problem. But alas, no dice. I've not tried yanking the MP from the server. I have pulled PXE and WDS and reinstalled them twice. I can try yanking the MP out of the process for a bit later today and see if that solves things. But I'm curious why would that make a difference? Isn't the cert tied to PXE? Or does it link up with a cert in the MP? (just trying to learn how a process works that I'm not familiar with)

May 17th, 2010 10:39am

Nope, removing PXE and MP and re-adding didn't solve it. Same issues. At least I'm feeling better. I thought initially it was something obvious that I should have noticed. :)

Free Windows Admin Tool Kit Click here and download it now

May 17th, 2010 3:10pm

Hi, Have you deployed the SLP? Regards, Bess, Kenneth - http://www.systemcenterblog.net - http://www.systemcenterforum.net

May 17th, 2010 3:46pm

If your site works in native mode, you should use PXE certificate issued by your CA, not self-signed one. Also you need to import root certificate into ConfigMgr. Look at http://scug.be/blogs/sccm/archive/2008/10/30/sccm-osd-pxe-issues-in-native-mode.aspx. , .

Free Windows Admin Tool Kit Click here and download it now

May 18th, 2010 12:00am

Yes SLP is in place. Again, it works fine for any deployment EXCEPT the PXE boot. I can burn a CD and I'm able to connect and get policies without a problem. Even an old out of data CD. We're not in native mode. We don't have an internal CA that we can use for this yet. As a result, I have to use the self signed certs. Good idea though. :)

May 18th, 2010 12:34pm

Well, now this looks like problem with cryptographic subsystem on the site server. Or you have really big difference between server local time and client one :) , .

Free Windows Admin Tool Kit Click here and download it now

May 19th, 2010 1:22am

nope, the time was identical. Checked that one too. Course, if it had been a time issue, then it wouldn't have worked with a boot CD because the failure would have been the same. I found a solution late last night. If you go into Site Settings - Certificates, you'll see an option for PXE. THis is where SCCM keeps the certs for PXE, Boot Media, etc. I looked in PXE, and I had 13 certs. most of them had been blocked. I suspect that the new certs were created everytime I either recreated the PXE service point, or modified the date/time the certs expired. I couldn't figure out which cert was the one that was failing, so I unblocked them all. And Voila, the PXE started working. Unfortunately, I can't seem to delete the older certs. All i can do is block a cert, or unblock it. This is why other boot media worked, because they use a different cert. I wish I had a bit more control over things, but at least now I know where to look. Anyone know how this cert function works, and what can or can't be done to help manage them? Seems to me to be pretty much a back ground process that you can't do much with.

May 19th, 2010 5:42pm

We are suddenly having the same issue. I'm finding very little in teh way of info about this on-line. Has anyone solved this yet? None of my certs are blocked. There is still a good one that hasn't expired.

Free Windows Admin Tool Kit Click here and download it now

January 23rd, 2012 8:27am

Please read below. It solved my problems... ConfigMgr 2007: OSD Task Sequence Fails with the error "An error occurred while retrieving policy for this computer (0x80004005)" J.C. Hornbeck 23 Oct 2008 6:23 PM 2 Here's another ConfigMgr 2007 OSD tip from Frank Rojas out in Charlotte, North Carolina. If you have a Task Sequence that fails almost immediately after it boots into WinPE with an 0x80004005 error then you'll want to check this one out: ======== Issue: When attempting to deploy a Task Sequence via SCCM 2007 OSD, the Task Sequence fails almost immediately after it boots into WinPE with the following error message: An error occurred while retrieving policy for this computer (0x80004005). For more information, please contact your system administrator or helpdesk operator. Examining the SMSTS.log shows the following error message: No cert available for policy decoding Failed to download policy (Policy_ID> (Code 0x80004005). Cause: This error message can be caused by missing, expired, or blocked Certificates for either the Boot Media or the PXE Service Point. Resolution: To determine if the Certificate is missing, expired, or blocked follow the steps below: In the Configuration Manager Admin Console, expand Site Database --> Site Management --> <Site_Code> --> Site Settings --> Certificates. Click on either Boot Media or PXE, depending on the method that the PC is being booted when trying to run the OSD Task Sequence. On the right hand pane, locate the Certificate being used and see if it is blocked, expired, or missing. To resolve the issue for missing or expired certificates on Boot Media, a new certificate needs to be created: Recreate the Boot Media by going in the Configuration Manager Admin Console to Site Database --> Computer Management --> Operating System Deployment. Right clicking on Task Sequences and choosing Create Task Sequence Media. Step through the Task Sequence Media Wizard to create the appropriate media. In the Security screen, locate the Create self-signed media certificate option. Make sure that the Set start date is set to either today or some date in the past. Make sure that the Set expiration date is set to some date in the future. Finish stepping through the Task Sequence Media Wizard to finish creating the ISO or USB Flash Drive. Go to Site Database --> Site Management --> <Site_Code> --> Site Settings --> Certificates --> Boot Media and verify that there is now a valid non-expired non-blocked Certificate. If using CDs/DVDs, once the ISO is created, create a CD/DVD from the ISO and dispose any previous OSD CDs or DVDs. If using a USB Flash Drive, make sure to recreate all USB Flash Drives be redoing steps 1-8 above. To resolve the issue for missing or expired certificates on a PXE Service Point, a new Certificate needs to be created: Go to Site Database --> Site Management --> <Site_Code> --> Site Settings --> Site Systems and choose the server where the PXE Service Point is located. In the right pane, right click on the ConfigMgr PXE service point and choose Properties. Click on the Database tab and locate the Create self-signed PXE certificate option. Under Create self-signed PXE certificate, set the Set expiration date option to some time in the future. Click OK. Go to Site Database --> Site Management --> <Site_Code> --> Site Settings --> Certificates --> PXE and verify that there is now a valid non-expired non-blocked Certificate. Update the Boot Images by going to Site Database --> Computer Management --> Operating System Deployment --> Boot Images. Expand both the Boot image (x64) and Boot image (x86) nodes (and any custom Boot Images if present). For each Boot Image, right click on Distribution Points and choose Update Distribution Points. Step through the Manage Distribution Points wizard until it has completed rebuilding the Boot Images. Restart the Windows Deployment Services (WDS) Server service. To resolve the issue if the certificate is blocked, follow these steps: Go to Site Database --> Site Management --> <Site_Code> --> Site Settings --> Certificates. Choose either Boot Media (if the deployment is being done via a boot media) or PXE (if the deployment is being done via PXE). You will be able to see all of the certificates associated with either the Boot Media or the PXE point. Check to see if the applicable certificate is set to "Blocked" under the Status column. If the certificate is blocked, unblock it. To unblock a certificate, right click on it and choose "Unblock". If you are not certain which certificate is the applicable one, you may have to unblock the certificates one at a time, retry the deployment again, and then see if the error goes away. Once you have determined the applicable certificate, you may want to go back and re-block the certificates that were not applicable and were unblocked during the testing.

February 8th, 2012 10:01pm

I was having the same issue, i removed and reinstalled PXE numerous time but it wasnt until i added the uninstallation of the MP to this process that i managed to get it working. Thank you so much

Free Windows Admin Tool Kit Click here and download it now

May 29th, 2012 11:52am

This topic is archived. No further replies will be accepted.