Instructions for changing ESET RA Servers

Enough customers have asked for help migrating from one ESET Remote Administration (RA) Server to another that I thought these instructions would be in order.

First Configure the New ESET RA Server:

1.    Go to www.eset.com/download#, click on “Take me to my Download” and then on the Business Tab. Using your licensed user name and password, download the following new installers:

a.    RA Server

b.    RA Console

c.    Client Installers (32\64 bit as needed)

2.    Install the new RA Server then the Console on the new machine. Take all the defaults and enter the User name and Password in the RA Server update section. Do not set any other passwords at this time.

3.    Build the applicable update mirrors including the Program Component mirrors for each client installer (32\64 bit) type. Then fire the event to configure the new NOD32 RA Server.

4.    Install the ESET antivirus client on the new Server for local protection. Be sure to follow the Best Practices for server configuration setup.

5.    Point the server’s local ESET “client” to the new ESET NOD32 RA Server for Remote Administration and Updates. To see it quickly show up in the console change the time to 0 minutes, don’t forget to change it back to the default of 10 minutes once shows up.

6.    Confirm the server shows up as a client of itself and is updating properly from the ESET RA Server. This step confirms that the new server is properly configured and ready to manage the clients coming from the old server.

Then change the configuration on the Old ESET RA Server to point clients to the new RA Server:

1.    Open the RA Console on the Old NOD32 RA Server

2.    Go to Tools > Policy Manager

3.    For each applicable policy, change the Remote Administration configuration under the Kernel Setup so the clients will now check in with the new Server with their status and signature levels.

4.    For clients getting updates locally from the old RA Server (instead of the from the Internet), change the update server settings to point to the new NOD32 RA Server.

5.    Save both changes in the Policy Manager. Remember the ESET clients check in for remote administration and update as 2 separate functions.

6.    Over time the clients will start to check in with the new NOD32 RA Server and drop off the old one.

7.    Once you are comfortable that all machines have migrated it is safe to take the old ESET RA Server down.

If you need help confirming this is properly set up and that the migration will go smooth, please let us know!

 

Leave a Reply