Hi Carlos, How many clients are affected? Are all of the clients having the same issue or just one? It shouldn't take that long to update a client. If the client is connected to the policy manager, the gold shield should have a green dot in the lower-right of the shield. If you right-click the icon, you can click on the "Update Policy" and the client should contact the Policy Manager immediately. To confirm if the client successfully connected to the Policy Manager, click on "View Logs" for the "Client Management" and you should see in the logs if the client successfully connected to the Policy Manager. You should also be able to ping the Policy Manager from the client. I would also check the sylink.xml file on the client to insure that it has the correct ip address and name for the Policy Manager.

Verfiy also if the smc is running on the client computers, did you export the package?

   Networkccna, thanks for answering.

   All clients are affected, they all have the same issue, except one client - by the way, it configuration is exactly the same as others clients - it was "erratic" for 2 days, than simple became "fixed".

   The client seems to be connected to the policy manager, although the gold shield have the "stop" icon in the lower-right of the shield.

   Right-click and "Update Policy" didn't chance anything.

   I will check the logs you wrote and the sylink.xml file on the client.

   Thanks again,
   Carlos Oliveira

Every client which gets installed with all the three features should be restarted once.

Just check the clients for Policy serial nos and same are matching with the SEPM server.

On SEPM console you can find it on  Details  (tab).

Every client which gets installed with all the three features should be restarted once.

Just check the clients for Policy serial nos and same are matching with the SEPM server.

On SEPM console you can find it on  Details  (tab).