Client computer migration in ESET Remote Administrator 6.x

Issue

End of support for version 6.4 and 6.5 of ESET Remote Administrator / MDM

ESET Remote Administrator version 6.5 is currently in Limited Support status and will soon be in Basic Support status. It is expected to reach End of Life status in December 2020.

ESET Remote Administrator version 6.4 is currently in basic support status and is expected to reach End of Life status in December 2019.

The MDM functionality in ESET Remote Administrator version 6 is in Basic Support status as of April 11, 2019. After this date, MDM version 6 will no longer be available for download.

  • ESET Remote Administrator (ERA) 6.x client computer migration to new server

Solution

ERA 6.5 User Permissions

This article assumes that your ERA user has the correct access rights and permissions to perform the tasks below.

If you are still using the default Administrator user, or you are unable to perform the tasks below (the option is grayed out), see the following article to create a second administrator user with all access rights (you only need to do this once):

View permissions needed for least privilege user access

A user must have the following permissions for the group that contains the modified object:

Functionality Read Use Write
Certificates  
Policies

A user must have the following permissions for their home group:

Functionality Read Use Write
Server Settings

A user must have the following permissions for each affected object:

Functionality Read Use Write
Groups & Computers

Once these permissions are in place, follow the steps below.

Complete certificate migration first

Follow the steps in this article only after you have completed the steps in Certificate migration in ESET Remote Administrator 6.x.

Migrate Client computers from the existing server, Server One, to the new ERA server, Server Two, using an agent policy. It is recommended to migrate only one client computer to test. After a successful migration of the test client computer, complete the migration with the rest of the client computers you would like to migrate to the new ERA Server.

I. Create a new Agent Policy on your existing server, Server One in this example.

  1. Open ESET Remote Administrator Web Console (ERA Web Console) in your web browser and log in.

  2. Click Admin  → Policies.
     
  3. Click Policies → New.

Figure 1-1
Click the image to view larger in new window

  1. Type a Name and optional Description for the policy in the appropriate fields.

Figure 1-2
Click the image to view larger in new window

  1. Expand Settings and select ESET Remote Administrator Agent from the drop-down menu.
     
  2. Click Edit server list.

Figure 1-3
Click the image to view larger in new window

  1. Click Add. Type the FQDN / IP address of the new server, Server Two this example, in the Host field and click Ok.

Figure 1-4
Click the image to view larger in new window

  1. Verify the FQDN / IP address for Server Two is correct and click Save.

Figure 1-5
Click the image to view larger in new window

  1. Expand Assign and click Assign. Select a client computer to migrate to Server Two. Only select one client computer to start. Click OK.
     
  2. Click Finish.

    Figure 1-6

II. Apply the Agent Certificate in a new Agent Policy on your new ERA server, Server Two in this example.

  1. Open ESET Remote Administrator Web Console (ERA Web Console) in your web browser and log in.

  2. Click Admin  → Policies.
     
  3. Click Policies → New.

Figure 2-1

  1. Type a Name and optional Description for the policy in the appropriate fields.

Figure 2-2

  1. Expand Settings and select ESET Remote Administrator Agent from the drop-down menu.
     
  2. Click Change certificate.

Figure 2-3

  1. Click Open certificate list.

Figure 2-4
 

  1. Select the Agent certificate and click OK.

Figure 2-5

  1. The Agent certificate is in the policy.

Figure 2-6

  1. Expand Assign and click Assign. Select the test client computer for the policy to target. Click OK.
     
  2. Click Finish.

Figure 2-7

  1. The test client computer is now connected to the second ERA Server and the Agent policy has the correct certificate.

Follow the steps in our Knowledgebase article to complete the ERA Server Migration process.

 

Additional resources