Hi, please look at the following article I found on this forum: Problem When an OSD (bare metal build) has completed on a brand new machine, the SCCM client does not receive assigned advertisements or policies targeted to that machine, even if left connected on the network for several days. This issue only occurs in the Perth office, which is a Secondary Site with OSD capabilities. This issue is not observed on the Sydney, Melbourne or Brisbane Secondary Sites. Cause This problem is caused by the first Discovery DDR from the client is discarded due to the time difference. When an OSD deployment finishes, there would be one .UDR file sent to the Assigned MP(primary site), which stamps the heartbeat discovery time with the primary site’s time (GMT+10). Later, when the client sends the “real” heartbeat discovery data from the agent side, the heartbeat would be sent to the Proxy MP(secondary site MP) as the client belongs to the secondary site’s boundaries. Due to the Proxy MP being in the time zone GMT+8, it would generate the .DDR with its local time, which then forwards the .DDR file to its parent site. Due to the time zone difference, the .DDR file may be “older” than the original .UDR file time, this would cause the .DDR file to be discarded. Under this situation, the SCCM agent would show up as “Assigned=No” in the console, which causes this issue. Current Solution Change the heartbeat discovery cycle from 1 week to 1 day. When the next scheduled heartbeat discovery is due, the client would become assigned and begin receiving policies successfully. Or, manually trigger a Data Discovery Cycle on the machine 2 hours after the OSD completes. I am currently having this issue. I have put my heartbeat down to 1 hour, but doesn't seem to help. I am going to be testing building the computer in the EST (I'm in Boston, machines are in California). Is there a permanent fix for this by MS?