Hi, You can schedule a report through SEPM with the following options

In the SEPM console, click on the Reports tile. Then click on the Scheduled reports tab. Click the Add option and choose the following report.

Report Type : Computer status report
Report name : Computers not checked into server 

You may specify your e-mail address so that you get the report as per your schedule.

Following article tells about the various types of reports you can run from the SEPM console

I hope this helps :-)

Thanks.

On the SEPM you can check the last check in time of your clients & see wheich clients have not checked in from long time to understand the connection issue.

You can create a computer status logs From SEPM > Monitors > Logs & view logs. & export this log.

You can alos create a report fro the computer not checked in for more than 1 week

By going into the SEPM > Reports > computer status reports & select the option for computer not checked into. & you can select the time range to 1 week.

You can also schedule this report so that you will get this reports from the SEPM through E-mail

To get an idea about schedule report you can check the page 181 of the administrator Guide. in CD1 documentation folder.

Does your client change some settings like host name?if so, the client will no longer connected to sepm even if you able to ping it.

Creating report is a good idea. After generating the report needed you can now specify clients that are not updating and do the necessary troubleshooting.

You need to check what is happening on the client itself, Please generate System Logs from the SEP client gui and post it here.

Thank you all for your help.  

Here is my problem and maybe I'm not understanding what benefit the report would get me....but if I generate that report wouldn't it also show all of the computers that are off for long periods of time in our environment?  The trouble we are facing right now is we have people on leave, taking long vacations etc....so at anytime I could run that report and show 100+ computers that have not checked in for the week.   So then I have to go through every single computer to determine which one is just off and which one has lost communication?  I really don't want a computer that has lost communication to not be updating because it lost it's connection, yet its on and I have no idea because I'm not going through that report every day.   Does this make sense?   With our old Virus protection software even if it lost connection to the server it would still go out to the internet to get updates and then show me a report that it was doing that.  Should I put in an alternate update policy in for all my machines?  And if I were to do this is there a report I can run to determine which computers are using different (internet) update sources? 

Any other suggestions are greatly appreciated. 

I know exactly what you are talking about - I've had random systems drop communications with SEPM. I can tell by going to "Help and Support" > "Troubleshooting" and the server sometimes says "Offline" when the server definitely isn't offline.

I haven't managed to sort out what causes it and it's so intermittent that it's difficult to get a system when I have time, that has it.

It would be a very good thing to have some sort of report that generates a "client is pingable but not updating" sort of thing.

Regards,

Chris B 

HI I would like to know the exact clients that are trying to connect to SEPM server everyday. Maybe I can relate and share What I experience and how to resolve your concern.

there are different reasons for the problem

Client is communicating with SEPM or is OFFLINE

HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\SYLINK\SyLink

PolicyMode 1 – means communicating 0- means offline.

How does that reg help?  I still have to look through all my computers to determine if the computers are on and have a 0 in the registry.  Shouldn't the Symantec software be able to tell me this is the case?? 

You can add a location specfic setting in the SEPM
By adding a location for you group.
By this you can set an condition for the clients if they are not connecting to the SEPM then they can run the liveupdate themselfs. Atleast this will make sure that all your clients are updated.

Check this document

http://service1.symantec.com/SUPPORT/ent-security....