What are your experiences in upgrade RAS/RAC for mixing 2.7 and 4.0?

I notice some changes in RAS for the LAN update mirrors...appears to run on different ports.

I'm wanting to slowly roll out V4 on some clients with networks running on 2.7.

2.7 defaults ports to 8081, which because I have many SBS setups out there, I often change it to 8088.

From what I've seen on the latest RAS/RAC, it appears it runs the mirror on totally different ports again..and you have the option of including updates for 2.7 which it puts in a subfolder on the mirror, I think something like Version2 or V2updates.

If that's the case, do I have to change the update pass for 2.7 clients to http://mainserver/mirror/v2:8088 or whatever the new port is?

 

Hi! Like v2 , in v3 and v4 you can change the ports used .
By default v4 uses port TCP 2221 for update (Mirror) , port TCP 2222 to connect to ESET RA Server and port TCP 2223 for the Console to connect to the ERA Server .

The new ERA (e.g. v3.0.105) makes updates for v3/v4 only and places them in a folder you have pointed to (or if you don't change it , it will put them in a folder "mirror" in its settings - Documents and Settings\All users\Application data\ESET\ESET Remote Administrator\server\mirror\) .

If you want it also make updates for NOD32 v2 , you should enable the option . In this case , it will create a subfolder called nod32v2, which will be located in the folder where the mirror files for v3/v4 are located .

Do you mean the "update path" ? If not , what pass are you talking about ?

If you mean path , YES , you'll need to reconfigure the workstations with NOD32 v2 to update from http://<mirror_server_name_or_IP>:<desired port>/nod32v2/

The nod32v2 subfolder must be pointed out. E.g. http://192.168.123.7:8088/nod32v2

For v3/v4 , it will simply remain http://192.168.123.7:8088

 

Ugh...yuck...yeah, that's the part I'm talking about.

Actually..I wonder it it would be possible for the new RAS/RAC to be able to support 2x separate mirrors.

Mirror 1 for the new clients, at port 2221
Mirror 2 for the legacy 2.7 clients..at port 8088.
Might be able to change that folder name on one of them.

 

The easiest way is to first create a cfg for the NOD32 v2 clients . It shall change their current settings and make them update from http://<mirror_server_name_or_IP>:<desired port>/nod32v2/

When some time has passed and you are sure they have applied the new cfg , upgrade the ESET RA Server . Your workstations will be ready and will now seek http://<mirror_server_name_or_IP>:<desired port>/nod32v2/ instead of the previously known http://<mirror_server_name_or_IP>:<desired port>

 

Yah..I figured that was the only approach...problem is, it's majorly time consuming to do that for so many clients out there. Normally product renewals like this I don't bill for, I just remote in and update their servers licensing.