Symantec AV CE 9 - Can't Unlock Group

[Neily]

The server we used to use for SAV was in need of replacing, so I built a new one on a new machine. I put this server into a new server group as the old one didn't reflect our naming for our network.

I moved all the clients from the old group to the new one successfully. Everything seemed to work ok.

Coming back to work Monday morning, I checked to see if it was funcitoning and noticed that the definitions were 10 days old, and weren't being updated. Having checked every setting and googled for answers a colleague of mine said that in his experience of SAV you had to manually download and update the definitions first time then it would work. I didn't think this was the case, but tried anyway. The definitions didn't update, so I restarted the machine and now I get an error when trying to unlock the new server group.

The error message reads:

Can't communicate with server group, verify network connectivity and that machines are operating within group.

I can unlock the old group from the new machine, but have never been able to unlock the new group from the old machine getting this error! I've tried several solutions including:

1) deleting old defs and re-updating.
2) re-installing SAV CE (well as a repair!)

but nothing has worked!

Can some one shed some light!!?

THANKS TO ALL THOSE WHO REPLY!

 

[darksasami]

Well, if your definitions aren't updating, and you can't communicate with the server group (read: you can't communicate with the server) then the service probably isn't starting. See if you can stop and restart the SAV service. It's entirely possible that the defs are broken, especially if trying to start the service gives error 10, "The environment is incorrect," which can be tricky to deal with even if you've deleted the old ones and reinstalled.

If you do get that, see if someone has a copy of Nonav posted somewhere, which will clean everything out and let you start fresh.

Hanlon's Razor: Never attribute to malice that which is adequately explained by stupidity.

 

[Stiddy]

darksasami,

I would be interested in hearing more about this "Nonav posted" because I have that problem alot. I have found a workaround but would still like you to tell more if possible.

Neily,

Did you ever promote this new server "Make this server a primary server". From what I read this sounds like your problem. What I would have done is. Build new server. Install AV server on it. Make it a prt of the old server group. WHat until it recieves the new defs from the old server. Promote it to the primary. Take old server off line. Delete it from group. Rename new server to old servers hostname. All is well. Maybe someone else has a better way.

 

[Neily]

There is one drawback to this. Nobody knows the password for the old group (its saved so will unlock!!) and the person who set it up doesn't work here anymore!

This nonav app sounds interesting! I'll look out for it!

I've taken the plunge and reinstalled the entire server. I initially tried to remove symantec AV CE9 but then Win Server 2k3 wouldn't restart! Its working now anyway, but we'll see what happens when it goes to update defs.

Thanks

 

[darksasami]

If you can unlock the server, you should be able to create a new server group and drag the server out of it, thereby changing the password. Looks like it's a bit late for that suggestion though...good luck with the reinstall!

Hanlon's Razor: Never attribute to malice that which is adequately explained by stupidity.