[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 275
  • Last Modified:

Nav corporate 10.1 overinstall of 7.6 - post install problems, remainders of previous install

We recently upgraded from Nav 7.6 corporate to 10.1 corporate on a Windows 2000 SBS running  Terminal Services.  We used Symantec's documentation to do this. Their procedure is to:
 uninstall legacy Quarantine Console
 uninstall legacy System Center Console
 run a special .exe from their CD that relates to 'rolling' up the version - they clearly state
 not  to use the standard setup.exe in the root
 do various post-install routines in particular unlocking the server group
 Here's a record of our experience and the problems we now have:
 1) Our first step - uninstalling the Quarantine Console snap-in  Add/Remove programs didn't  work.  The uninstall seemed to be looking for the file in the wrong place. We located the file and tried  running it manually  - it told us that the program was already uninstalled. We decided to leave it as is.   Uninstall of System Center from Add/Remove programs went through smoothly.
 2) Continued with the install using special 'rollup' version of .exe as per documentation which  seemed to go smoothly.  After finishing we went into System Centre and noticed that the server  listed there was a server that had been decommissioned years earlier - it was not the name of  the  current server.  After a lot of hacking around we managed to delete the old server and then the old  group and created a new group and had the new server name recognized.
3) Still continued to have various problems - deploying to clients, etc. - so we did a repair  installation with the CD with the CD's autorun menu. First Installed System Center then Symantec Server  ,finally tried to install Quarantine, the last item didn't install.
 4) Repair seemed to go fine and all the major functions seem ok - liveupdate, scheduling
 scanning,  deploying to clients, etc. -  but we are left with the following problems:
a) in  System Center the status of the server seems to randomly fluctuate between being
activated  and deactivated. For example, we go into System Center and unlock the group, the server icon is 'blue' active. We  click on it - it goes 'red' inactive. Sometimes shutting down the console and restarting it gets  the System Centre activated; sometimes it takes several times of going in and going out before  it  becomes active. Have rebooted the server, cleared the System Center cache, run the discovery,  etc.  Nothing seems to change the basic random deactivation situation.
 b) Quarantine Console - we tried installing from CD but message comes up it is already installed  -  yet it's not present as far as we can tell.
  • 4
  • 3
3 Solutions

Looks like you´ll have to clean up, had this problem with Backup Exec once.

Microsoft Cleanup Tool

The tool cleans registry not folders and files.

Robert Lundqvist
Small Business Specialist
i had a similar problem with my installation and i had to use their tool nonav.exe and run it manually on my new nav server also i had to do the same for my clients for some reason they still were pointing to the old server even after updating the clients from 8.1 to 10.1. the tool did the trick for 99% of my clients i had to manually remove the registry entries from 1 or 2 pc. have you try using the nonav from symantec if you dont have it you will have to call their tech support and they will email you a link to download the tool.
lineonecorpAuthor Commented:
Thanks for the info.  Did you run nonav to uninstall NAV completely and then reinstall the new version or did it somhow manage to  uninstall just all version 8 components leaving the new install intact?
When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

lineonecorpAuthor Commented:
I would like to close this as I have not had a reply to my last query in 3 weeks.
Apologies i have i didnt see you posted a comment

Here is what happened

The previous install worked fine version 10.1 but for some reason my users reported several issues the scan would crash unexpectedly when i contacted symantec i was adviced to install 10.1.5 since i created a groups it was really hard to managed all this at the same time i made sure before removing sav 10.1.5 corp editon that all my clients had the latest virus definitions. Then i ran the no nav tool and completely uninstalled sav. afterwards i was able to push the installation to all my network users, but i still had remote locations to install so i ran the nonav tool at the remote locations and set up a webserver to install the software over the internet. the whole process took about 1 week. that included local installation (pushed installation) and remote installation (setting up a webserver)

Let me know if you need more info.

Also sav 10.1 can manage earlier versions on symantec anti virus
lineonecorpAuthor Commented:
Yes, I agree some useful information, thanks. However, I had a little trouble understanding what actually was done so perhaps a recap and I will close this and award points.  

Recap: (Please correct if wrong)  
1)NAV uninstalled completely with Nonav

2) new version freshly  installed  

And this is the jimmymcp02 and Vee Mod preferred/recommended method for installing new versions of Symantec Corporate NAV product as opposed to doing an 'overinstall' where the old product is left in place and it's left to the installation program for the new product to do all the work of properly uninstalling the unnecessary parts of the old install and at the same time keeping the parts that might be desired e.g. exclusions.
lineonecorpAuthor Commented:
If jimmymcp02 can offer a final comment I will close the question.
well the problem with using the add remove feature in my humble opinion is that in the past it has left some registry settings and then i had to end up unistalling it manually removing registry keys, which it could take forever i learned from my first try the  remove programs would to its job but a key or 2 were left in the registry.

You could try simply using the add/remove but the nonav will do a heck of a better job.

Also before running the nonav tool on your nav server make sure you write down what you are currently what folder you are currently excluding ie exchange folder  you might want to look at the following link

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now