Managing Endpoint Upgrades and Other Changes



Hello. You have arrived at an outdated topic. Please click this link to be redirected to the updated Endpoint Protection Admin Guide.

This section describes some special circumstances you may encounter when you change hardware and operating systems on endpoints.

Migrating to a New Operating System
 

If you install a new operating system on an endpoint, the change will create duplicate endpoint entries in the Management Portal. Before you install a new operating system, you should deactivate the endpoint. See Deactivating endpoints.

If you have already performed the OS installation, you can simply deactivate the oldest entry in the Management Portal. The extra license is then removed and the duplicate endpoint is placed in the Deactivated Endpoints group.

Note: In most cases, a simple upgrade to an operating system will not create duplicate entries.
Changing Hardware on an Endpoint
 

If you install a new hard drive in an endpoint and reinstall SecureAnywhere on it, it will appear as a new entry in the Management Portal. Before you switch out a hard drive, you should first deactivate the endpoint from the Management Portal so you do not use an extra license. See Deactivating Endpoints.

If you change other types of hardware on an endpoint, for example, you install a new motherboard, processor, or network adaptor, that upgraded computer will not appear as a new entry in the Management Portal. You do not need to deactivate the endpoint first.

Moving Endpoints to a New Subnet
 

If you move endpoints to a new subnet, make sure the same communication lines are open as on the previous subnet. These domains should be allowed through the firewall:

*.webrootcloudav.com
*.*.webrootcloudav.com
*.p4.webrootcloudav.com
*.compute.amazonaws.com
*.webroot.com
*.webrootanywhere.com
*.prevx.com

Communicating Through a Firewall
 
If a firewall is in place, please allow Webroot’s path masks through the firewall, listed below:
 
PATHINFORMATION

*.prevxinfo.com

 --

 

*.prevx.com

 --
 

*.amazonaws.com

 --
 

*.cloudfront.net

 --
 

*.webrootcloudav.com  

 

Covers the g-url’s as well as several other target addresses.

*.*.webrootcloudav.com

Some devices don’t like a single * for urls that contain dots in the value of *.

*.p4.webrootcloudav.com

For devices that don't like multiple *’s.

*.compute.amazonaws.com

Covers inbound communication from the Amazon cloud servers.

*.webroot.com

To be used for future communications

*.webrootanywhere.com

To be used for future communications
 
For more information on firewalls, see Preparing for Setup.