Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Manager does not show green dot

Updated: 23 May 2010 | 5 comments
Visu310's picture
0 0 Votes
Login to vote

Hi all,

I was using Symantec Endpoint Protection MR4 and recently I upgraded to their latest version MR4 MP2.. I just ran the setup file and upgraded the manager, after upgrading.. I used "Upgrade group with packages" to upgrade all my clients... Now here is my problem..

1) After upgrading, client shows green dot but manager doesnt. However, its receiving all updates and policies... Help & Trouble shooting says its reporting to my custom group... But I can't see a green dot in my manager uder my custom group...

2) I deleted the client entry from manager console and its not showing up again.. But still the client says its reporting to manager uder custom group..

3) I tried a Sylink replace, it dint help... No change..

4) I tried pushing new package with "Reset client-server comm.." settings.. Here is my new problem... After pushing new package, green dot appears on client for 2-3 secs and disappear... And manager still doesn't have an entry..

I don't know what went wrong... Can someone please help me???

P.S: Problem is not with all clients though, but 70% of them... in diff groups..

Regards,
Visu.

Comments

pete_4u2002's picture
26
May
2009
0 Votes 0
Login to vote

hi, for the new problem, run

hi,
for the new problem,
run sylinkreplacer and see if it helps, if it does not run sylinkmonitor to know the connection...

from the client machine
http://SERVER IP/secars/secars?hello,secars

it should read 200 ok.

Pete!

Abhishek Pradhan's picture
26
May
2009
0 Votes 0
Login to vote

Try the following > Go to

Try the following >

Go to Admin > Servers. On the left bottom side, look for a link that says Administer Domain. (I'm not too sure abt the location, but it's somewhere in Admin ). If you see 2 domain ID's given threr, tryto click on the "Administer domain" link below the other one and see what happens after you switch the internal SEPM domain. In case even that doesnt help, you may want to reconfigure the SEPM. This may seem a bit weird, but works in most cases.

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

Visu310's picture
26
May
2009
0 Votes 0
Login to vote

Thanks for your

Thanks for your response.

@Pete

I have tried that secars test, its fine. I get that "200, ok" message. And also, I have tried Sylink replace... I even checked the Sylink contents, group name and server ip are correct but still, i have this problem.

@Abishek

I have checked in the admin tab, I see only one domain which is "default". And I have no problem in reconfiguring the Manager, But I have about 160 clients reporting to 7 different groups with distinct policies. I don't want to lose the settings. Is there a way to fix this problem without losing my configuration? And also, let me know what has happened in this case... I'm totally confused!!

Cheers,
Visu.

I came, I saw, I err ;)

Abhishek Pradhan's picture
27
May
2009
0 Votes 0
Login to vote

Well, the Manager

Well, the Manager reconfiguration wont make you lose your policies and settings. It's more or less like you are filling petrol in your vehicle...hehe

All it's going to do is make sure the reporting and other stuff are reconfigured, w/o touching your policies and settings.

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

Ghent's picture
25
Sep
2009
0 Votes 0
Login to vote

Start with the Sylink log file.

Hi,
The first thing I would do is take a look at the Sylink Log file. Here is a support link:
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/c5fbee13489b48a58025734e0039509a?OpenDocument

While your monitoring the Sylink log file, click the "Update Policy" button and see what happens when the client tries to register or request an index file.

If you can't make heads or tails out of it, try posting it here and seeing if someone else can tell what's happening..