Right now, we realize the PolicyPak Cloud Service is going thru some disruptions in service.  This document shows how to determine if background sync’ing is occurring.

A manual sync with Cloud Client 23.5 might fail to operate and present errors like this:

A manual PPCLOUD /sync pre-23.5 might look like this on a failed manual sync attempt:

We are actively working on the issues as they come up.

We realize that it may appear that a computer isn’t getting any new policies / not sync’ing to the cloud service.However, what is more likely is that these computers are syncing in the background and get updated policies; but you’re unable to see this with PPCLOUD /sync. Tip: PPCLOUD /status will show you the details of the policies ON the machine which occurred from the last sync, without attempting to PERFORM a sync.
 

See below for two sections: one for PolicyPak Cloud 23.5 client and one for pre-23.5 client.

Note: Only when you see the message "...has been proceeded successfully" is an indication of a truly successful sync and policy update.

Checking Background Sync’ing for PolicyPak Cloud 23.5 Client

To verify for yourself that that background syncs are occurring, when using the PolicyPak Cloud 23.5 or client, please turn to the APPLICATION or PolicyPak logs where events will be for PolicyPak Cloud.

Note: Future versions of PolicyPak Cloud client are slated to have its own event log.

Here’s an example of a machine when syncs happen in the background, across a few log events (from earliest to latest event on an automatic, background sync.)

To look at them in order we have…

Note: Only when you see the message "...has been proceeded successfully" is an indication of a truly successful sync and policy update.

Checking Background Sync’ing for clients BEFORE PolicyPak Cloud 23.5

There is less detail in the event logs in previous versions.

On Pre-23.5 machines, you can see similar events like this for success.

And like this for failure during a background sync.

Final Thoughts: PPCLOUD /status

In all cases, using PolicyPak CLOUD /status will NOT perform a sync but will tell you the final result of policies upon the machine. This is helpful so you can know what the machine’s current state actually is. Example with some text removed to save space…