66945 Posted March 29, 2018 Report post Posted March 29, 2018 I think I found the issue - timezones. My Primary server (which I connect to, and create deployments) is located in GMT+3 timezone. The 'affected' office is in GMT-7 timezone; difference of 10 hours. Offices that are not affected are in GMT+8 timezone (i.e. ahead of Primary server) When I create a deployment and select 'required + 'ASAP' (without selecting UTC checkbox) - the deployment is made available at at the current time of the primary server. However, since UTC option is not selected, if deployment was made available at 9am on the Primary server, clients will wait till 9am local time before treating deployment as available. Since the affected office is 10 hours behind the primary server, I had to wait 10 hours before the 'ASAP' deployment will begin on those clients. PEBKAC! Quote Share this post Link to post Share on other sites More sharing options...
Diaz Posted March 29, 2018 Report post Posted March 29, 2018 LOL Having never ever set up my system to ignore the timezones(UTC), it wasn't even something that I thought of, well caught! Quote Share this post Link to post Share on other sites More sharing options...
