Discussion Locked

NAV Corporate

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
My company upgraded from NAV Corporate 7.65 to 9.0. Now most of our machines are not accepting the new client. They are all still running 7.65. We try and force down version 9.0 from the AV server but it asks us for a domain password (but will not accept and domain admin passwords.) If we install locally on a computer it will install without a problem, but it will not work remotely.

7 replies

by cg it

hope you have the symantec packager installed. if not install symantec packager. then configure the client program and deploy the program to target clients using the packager program. if clients do not accept the package because of a password problem, then open up the symantec system center console, unlock your server group, highlight your primary server under groups, right click, choose all tasks, symantec antivirus, client administrator only options. click the security tab and disable the option lock the ability of users to unload symantec antivirus services. click ok.

close all windows, when prompted to save console settings choose yes. exit symantec system center.

open the symantec packager, then deploy the antivirus program to target clients.

by cgordon

Have your tried using the local admin password?
ie. "computer_name"\"Administrator_account_name" and then the password for that computer

by curlergirl

What OS is installed on your client machines? You do know that the remote install won't work on Win9x machines, only on NT and above, right? The password it is asking for is the Symantec Server Group admin password that you use to unlock the server group in the System Center, not a domain admin password. Or, possibly, if your 7.x clients were configured to require a password to uninstall the application, it might be looking for that password as well.

My experience with SAVCE versions 8.x and above is that it will not install properly with a user logged on unless that user has local administrator permissions. I never give my users local admin rights, so I ask the users to log off first on the machines I'm going to install, and then I run the remote install. It's kind of a pain, 'cause it requires a little coordination and scheduling, but it works very well that way.

Also, if you get the remote install to work, you MUST wait at least 5 minutes or so after the remote download finishes in the Symantec System Center before rebooting the workstation. The install is not actually finished when the System Center download finishes - all it's doing is downloading the files necessary to run the install. The actual install then runs on the local machine after the SSC console remote activity is done. If you reboot the workstation before the rest of the process has completed, your install won't work.

Hope this helps!

by tksolway

they are all 2000, I tried the AV password as well. I just went and installed everything manually, I still am not sure why the rollout did not work for some computers.

This discussion is closed to new replies.