New ERAS / Upgrade Client and Replace Config?

[AStaley]

I've recently updated my existing ERAS to v5. But in my on-going attempt to consolidate servers I've also installed a new instance using SQL Express 2012.

My client PC's currently use NOD32v4 and I'm starting to test a limited deployment of v5 which I would like to connect and use the new ERAS. I originally thought this would be a simple case of building a new install package with the new config and then through the old ERAS deploy the package.

What I've found is that the upgrade goes through fine and the PC then needs to be rebooted. But it's still using the old config for the original ERAS. If I then import my new config it simply merges with the old.

What is the best way to deploy the new package and have it's config replace the original loaded on to the PC?

Thanks, AStaley

[dwomack]

Especially when changing policy settings, it might be easier to push an uninstall of v4 before installing v5 to avoid the issues you're experiencing now. So for now, uninstalling the current config and then installing v5 and putting in the new policy settings you want is probably the easiest road.

How do I push uninstall to client workstations using ESET Remote Administrator? (5.x)