Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SAV 10.1.5 - cannot unlock Server group

Status
Not open for further replies.

wimvh

IS-IT--Management
Feb 22, 2006
58
BE
Hi,

I have just installed a brand new HP Proliant ML370 with Windows 2003 R2 and Exchange 2003 SP2 + all Microsoft updates.

After that I installed Symantec System Center and rebooted. Then I installed Symantec AV 10.1.5, creating a new server group with username admin and password symantec.

After reboot, Symantec system center won't let me unlock the server group (account "admin" does not have sufficient permissions to configure SAV).

When I launch the Symantec Client security, and provide the correct username & password, I get the same message (account has got no permission to configure SAV). If I deliberately provide a wrong password, I get another message (wrong username/password).

I even tried to reset the password with the iFORGOT utility, but this does not help.

I have checked the registry, and I do find the entries user-admin-r and user-admin-p under HKLM\Software\Intel\LANDesk\Virusprotect6\Currentversion\Accounts. So the account does exist, but obviously it does not get the correct role assigned.

Finally, I removed all Symantec AV software, rebooted and started over again. The same problem happens again.

Is there any way I can force the admin account into the correct role ? Are there any known issues with Windows 2003 R2 are other recent MS updates? Any other suggestion?

Thank you,
Wim
 
I found a workaround. In case anyone is interested:

I installed SSC and SAV server on an XP workstation. This way the server group was created, and it could be unlocked with the admin account specified during setup. This XP workstations was then made primary server. In other words: a default installation.

After that, I installed SSC and SAV server on the W2003 R2 SP2, joining the existing server group. Finally I transferred the Primary server role to the W2003 R2 SP2 server and uninstalled SSC/SAV from the XP PC.

Now the W2003 R2 SP2 runs SAV as intended. Phew.

Wim
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top