From time to time, PolicyPak Cloud could become unavailable or “goes down”. This is rare, but it can happen.

First, to verify and ensure the problem is with the PolicyPak Cloud service, and not something on your end, please see the following article FIRST https://kb.policypak.com/kb/article/277-how-can-i-troubleshoot-communication-from-the-ppc-client-and-ppc-service/ (and the sub-KB articles at the end.)

However, if the PolicyPak Cloud service itself is down, you might see the following behavior:

1. Computers cannot be joined / re-joined to PolicyPak Cloud

   

2. PolicyPak Cloud /sync might show the following message…

   Syncing with the cloud...

   Could not sync with the cloud.

   1. A network error occurred during sending Sync to https://cloudsvc.policypak.com/Services/Synchronization: The request channel timed out while waiting for a reply after 00:00:29.9686167. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
   2. A network error occurred during sending Sync to https://cloudsvc.policypak.com/Services/Synchronization: The request channel timed out while waiting for a reply after 00:00:29.9530410. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
   3. A security error occurred during sending Sync to http://cloudsvc.policypak.com/Services/Synchronization: The token provider cannot get tokens for target 'http://cloudsvc.policypak.com/Services/Synchronization'.

   Elapsed time: 00:01:00.7012049

This indicates that NEW policies aren’t able to sync from the PolicyPak Cloud server.

However, existing clients will maintain their already-delivered Policy settings.

Additionally, clients will not disconnect or become un-joined from the PolicyPak Cloud server.