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

            
  • Migrating to a New Operating System                
  • Changing Hardware on Endpoints                
  • Moving Endpoints to New Subnets                
  • Communicating Through Firewalls                
            

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. For more information, 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 Endpoints

            

If you install a new hard drive in an endpoint and reinstall SecureAnywhere on it, it will display 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. For more information, see Deactivating Endpoints.

            

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

            

Moving Endpoints to New Subnets

            

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

            

*.webroot.com

            

*.s3.amazonaws.com

            

WSAWebFilteringPortal.elasticbeanstalk.com

            

*.webrootanywhere.com

            

Communicating Through Firewalls

            

If a firewall is in place, please allow Webroot’s path masks through the firewall, as described in the following table. 

            

For more information on firewalls, see Preparing for Setup.

                                                                                                                                                                                                                                                                            

PATH

INFORMATION

*.webrootcloudav.com

Agent communication and updates.

                            

Note: Some firewalls do not support double dotted subdomain names with a single wildcard mask, for example, g1.p4.webrootcloudav.com being represented by *.webrootcloudav.com, so some environments might require either *.p4.webrootcloudav.com or *.*.webrootcloudav.com.

*.webroot.comAgent messaging.
*.s3.amazonaws.comAgent file downloading and uploading.
WSAWebFilteringPortal.elasticbeanstalk.comRequired for agent Web Filtering, elasticbeanstalk is an amazon AWS domain.
*.webrootanywhere.comManagement portal and support ticket logs upload.