Diaz

LOL Having never ever set up my system to ignore the timezones(UTC), it wasn't even something that I thought of, well caught!

Hi 66945 It doesn't matter what is being delivered by SCCM, content is content. You will ned to check the following: The remote site Y IP ranges are in a boundary & boundary group and assigned to the DP. You state "The very same packages, if I deploy to a different office (A with local site server on the same LAN), works flawlessly" this would seem to suggest that there is something stopping the content being delivered across the VPN connection to site Y" in my experience, this is either because the clients on site Y have IP addresses that are not in your boundaries etc. I have seen this where LAN connected clients have different IP's to the clients that only use Wi-Fi, so you will need to double check your IP ranges. It may also be the status messages from your DP not being sent to the site server, this would mean that the content is not "registered" as being available to the clients in the DP boundaries associated with site X/Y, so check that the content is available on the DP. It may also be that your settings do not allow for low priority messages during business hours, so it would take a long Tim for SCCM "to know" that the content is on the DP for the clients at site Y If you can zip up the logs from the CCM folder on the client, that would help immensely. I can take a look for you. Also check and ensure that there are no errors on in the console Problem Office C + Secondary Site (2) + Boundary Group (Office is of different subnet than the Secondary Site servicing this office) 10.20.0.0/16 \ You can use the content explorer tool in the toolkit to check what content is on each DP, check the DP first, clients second. Hope that helps