You have a network running a distributed setup of Norman Virus Control 5.99. Now you want to upgrade/migrate this network to run Norman Endpoint Protection. This article will guide you through the necessary migration steps.
illustration of network setup – your network does not have to match
There are several ways to migrate existing NVC clients over to NPRO.
The administrators guide to Norman Endpoint Protection describes, in detail, some of the ways this migration can be done. The methods described in the administrators guide are manual methods of migration, which means that they require some manual copying of configuration files.
Because some users want a more automated migration method, Norman has developed a tool called PushMig. This tool is designed to automate some of the manual copying and distribution necessary for the migration of NVC clients to Endpoint Protection.
Note: If the network contains more the one NVC distribution server, it is necessary to first migrate the distribution servers and then migrate the clients under each distribution server. This will be explained at a later point in this article.
Note: The notation “~Norman…” used in this article indicates the Norman folder that contains the NVC application, configuration- and update-files. This folder is normally found at “C:Norman” or “C:Program FilesNorman”, but can be at other locations depending on what was chosen during the initial installation of NVC.
These steps will be explained in more detail later in the article.
The first step in the process is to acquire all the necessary installation files. The files needed are:
These files can be found on Norman’s website.
After downloading the necessary files you are ready to start the migration process.
1.1 - The simplest way to remove the NVC Distribution server is to run the removal tool called “Delnvc5”. This executable file can either be called by running the command “delnvc5” or by running the executable file found in the “~Norman vcinDelnvc5.exe”.
Note: You can also remove NVC by using “Add/Remove programs” in the Control Panel.
Note: If you don’t find “Delnvc5” on your computer or it does not work, you can download the latest version from Norman’s website. But it is recommended that your local “Delnvc5” be used to uninstall.
1.2 - After “Delnvc5” has started you should be presented with 2 choices, “Repair” and “Remove”. Choose “Remove” and press next. After the removal process has been completed, you will have to restart the computer.
1.3 - When the computer has restarted, you will no longer see the N-icon on the taskbar. At this point you will have to delete the “~Norman” folder. Open Windows Explorer, navigate to where the “~Norman” folder is located and delete the entire “Norman” folder.
Note: If you get a message saying that some files could not be deleted because they are being used by a running application, you should check to see if a process with the name “Zanda.exe” is running. If “Zanda.exe” is running, kill the process and re-attempt to delete the Norman folder. If this does not work, you will have to start windows in “Safe Mode” and then attempt to remove the Norman folder.
2.1 - At this point there will be no Norman Antivirus running on the server. You can now install “Norman Endpoint Protection” (NPRO) and “Norman Endpoint Manager” (NEM).
If you are not logged on the server using the Domain Administrator, do so now.
2.2 - Start the installation of Norman Endpoint Protection (with the setup file downloaded earlier). Go through the installation until you are presented with “Setup Type” options page. Here is where you choose whether you wish to perform a “Complete” installation, “Only Antivirus” installation or if you wish to perform custom installation.
If your server has lots of free storage space (>20GB), you can simply select “Complete” for installation of Antivirus and Distribution server.
If not, you can select custom and deselect some of the languages you do not need.
Note: Remember that the server will only download updates for the languages chosen, but this setting can be altered later.
2.3 – Reboot the server if prompted.
2.4 - After the setup, run “Internet Update”. You can do so by right clicking on the Norman tray icon and pressing “Internet Update”.
2.5 – When this is done you will have to setup your “Norman Endpoint Manager”.
This guide will not go through the setup of NEM. For this you should consult the Administrator’s Guide for Norman Endpoint Protection.
After performing the steps stated above, you will have a fully functional Norman Endpoint Manager running on your server.
Now, it’s time to use the tool PushMig to migrate the NVC5 clients to Norman Endpoint Protection. To run PushMig correctly, log in to the server where you installed Norman Endpoint Manager, using the Domain Administrator account.
3.1 - Run the PushMig executable you downloaded earlier. You should now be presented with a console saying that you should check that the correct language(s) and platforms are selected.
This is because PushMig will not migrate any NVC client that the NEM does not support, ie. download updates for. For example if your NEM is set up to only download updates for “English” NVC5 clients, no “Norwegian” NVC5 clients will be migrated by PushMig.
Note: The “English” and “Norwegian” references above refer to the language of the NVC5 application, not the Operating System the application is running on.
This is also valid for Operating Systems. If you have set up NEM to only download updates for XP, no Vista or Windows 7 clients will be migrated.
Consult the Administrator’s Guide if you wish to change these setting.
In PushMig, you will be asked to press “Enter to review the settings”.
This will take you to the Norman Endpoint Manager’s web interface where you can change the settings for supported languages and operating systems.
3.2 - If you select new languages or operating systems, you will be asked to run Internet Update. Press enter after running “Internet Update”.
3.3 - Now you will now be asked to launch the “Migration” page in the NEM web interface by pressing “Enter”.
As the PushMig console states, you have to choose “C:PushMigDistrib” as the migration path and then press “Migrate”. When you see the status “Migration was successful” on the “Migration” page, you can close the NEM web interface and go back to the PushMig console.
3.4 - PushMig will now ask you what the most common installation path is for NVC5 on your client machines. This is not something that you have to know, but it might help if you can see whether or not most clients are installed to “C:Norman” or “C:Program FilesNorman”.
3.5 - After pressing enter, you will be presented with a series of choices. Choose the appropriate choice depending on what your network layout is. If all the clients are in the same domain/workgroup as the NEM server, it would be easiest to select #3 – “Migrate all suitable workstations within the domain/workgroup”. This option will find all the suitable NVC clients and attempt to migrate them to NPRO.
You will be notified with information about the migration status of each client found, from “not supported” to “Successfully migrated”.
Note: Remember that only computers that are turned on and logged in will be migrated.
If there are machines in your network that are unavailable, for example turned off or not logged in, you can re-run PushMig to migrate them at a later time.
Note: Remember that the NVC clients will only be “converted” to NPRO after they have downloaded update and upgrade files from the NEM server. If you have a large network with many clients, it might take some time before all the clients have the necessary files.
The users will be asked to restart the computer to finish the migration.
It is also possible that you only want to upgrade some of your clients to NPRO while others are to still run NVC. This can be done by simply setting up a new NEM server instead of migrating the existing one, and then either migrating computers individually by individual IP addresses or by an IP address range.
(illustration of network setup – your network does not have to match)
(illustration of network setup – your network does not have to match)
If your network contains more than one NVC Distribution server, it is best to migrate each distribution server starting with the lowest ones. The process is the same as when migrating a an entire network with only one distribution server, but you should not choose option #3 – “Migrate all suitable workstations within the domain/workgroup” as this will setup all the clients in the network to get updates from a single NEM Distribution server.
The best choice when you want to migrate only clients under a NVC5 distribution server is to choose to migrate clients by IP addresses, one by one.
Or, if each NVC5 Distribution server is responsible for an IP range, migrate only that IP range when going through the migration process.
PushMig - Software Published: 01.07.2010
Norman is not liable for any form of loss or damage arising from use of this software or from errors or deficiencies therein, including but not limited to loss of earnings.
This supersedes any other warranties, expressed or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.
In particular, and without any limitations, Norman will in no event be liable for loss of profits or other commercial damage including but not limited to incidental or consequential damages.