Hey SCCM Users,

i'm running SCCM 2012 R2 SP1 and having big trouble getting my OSD running again. I started with non-SP CU4 some months ago and everything was working fine. Then suddenly OSD stops working randomly always with following log entry (smsts.log client-side):

CLibSMSMessageWinHttpTransport::Send: URL: sccm.server.local:80  CCM_POST /ccm_system/requestError. 
Status code 503 returned

I googled my way around and often found answers about Date/Time Bug. I tried many things and sometimes it really seams to be Date/Time related. Well, now with SP1 i guess the logging was expanded and i get the following error:

CLibSMSMessageWinHttpTransport::Send: URL: sccm.server.local:80  CCM_POST /ccm_system/requestError. 
Status code 503 returned
pNext != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,2054)
reply has no message header marker
...
...
failed to request for client
SyncTimeWithMP() failed. 80004005.
Failed to get time information from MP: http://sccm.server..local.

Well, it's obviously a time/date problem. But i don't get how to handle it. My client's BIOS time is correct. My SCCM Server's Windows-Time is correct. The smsts.log file (client-side) has a wrong timestamp. It's round about 10minutes in the future. When i boot up WinPE after the abort happened and copy the smsts.log to a smb share, the timestamp on the fileshare is many hours off real-time. 

Besides this i am often using HyperV-VMs to test deployment. In Hyper-V you dont have a BIOS to set up the time. The HyperV-Hosts time is syncing with the same ntp as the SCCM Server so they are the same. But i also get this error using Hyper-V VM. When i boot PXE many times then sometime it's working. Could be after 3 reboots or after 8 reboots...

Where can the client time be affected besides BIOS? Is there a setting somewhere regarding WinPE timezone or something?

Thanks in advance!

Edit: I just booted up the not-working client to OS and checked the log-file.

Created: 07/29/2015 00:20PM

Modified: 07/29/2015 00:27PM

Accessed: 07/28/2015 02:41PM

Okay...created and modified timestamp are tomorrow(?!). Inly the Accessed timestamp seems to be okay.

• Edited by Alexander Dmann Tuesday, July 28, 2015 12:44 PM

Any way you could reboot the management point that is having issue in the log  please.

After start a new TS and if it fails can you upload the entire smsts.log please

• Edited by Frederick Dicaire Tuesday, July 28, 2015 4:00 PM
• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator Friday, August 07, 2015 7:17 AM
• Marked as answer by Joyce LMicrosoft contingent staff, Moderator Monday, August 10, 2015 6:43 AM

It seems like i had several problems.

The worst was that i got a bunch of computers having the same GUID (the one which is displayed during PXE boot) I talked to the manufacter's support and received a tool to reandomly change the GUID.

After changing the GUIDs everything seems to work.

Thank you guys!

• Marked as answer by Alexander Dmann 1 hour 34 minutes ago