Good morning,
I recently had to re-create my SSC server. The clients appear managed when I push out the new GRC.DAT and cert files to the client. However, they don't show in the console until a reboot (which restarts the service presumably). Can't I force the client to update the console sooner somehow? I sort of inherited this and it seems like they populated on the old server without a reboot. Some of our users leave their machines on for a month (until we force a reboot). I can't wait a month for them to show up ;-) Plus I'd like confirmation that they are communicating on a regular basis. Thanks for any help.
how do you push the grc file?
using the makedrop tool from symantec; this tool replaces the file and restarts the services too.that should fix the issue without reboot
you need to call support to get the tool
I copy the file from the parent server and distribute with our patch management tools (SCCM, Patchlink, etc.). Does the client only check in when the service is restarted? Going forward then how do I get around the issue of users who don't reboot for a month. Will my data always be a month out of date for those people? I guess I'm wondering how often the client checks in with the server? All documentation says you can force the check-in by restarting the service or just wait until the client checks in with the server for it to show up. I had a machine on all night and it did not show up until a reboot. Doesn't it check in predetermined intervals?
There is a tool for that Called "MakeDrop Utility"
Call Symantec and get this tool it will replace root cert,put grc.dat in 7.5 folder and restart the service remotely
Create a logon script to restart the service and deploy
Or if possible access the client services remotely (MMC) and restart the service.....