Guidance on performing an inventory of your current devices, as well as identifying policies and exclusions throughout your site.

Part of the process of implementing VIPRE is to determine which systems within the target environment need to be protected. Generally speaking, VIPRE recommends that you protect any and all systems that are on any sort of network, but (a) all protected systems must be running an operating system that is certified as compatible with existing VIPRE agents (b) there may be exceptions for systems that are protected in some other way.

Endpoint Systems

Many environments also have a legacy antivirus solution in place and you can leverage that implementation to come up with a candidate list of systems to which VIPRE should be deployed. This is a starting point, however, and the candidate list should be reviewed for any omissions or incompatible systems.

Display existing endpoint devices

Using the resources available with your current endpoint security solution, pull a list of your current device inventory. You can then use this list to help plan your migration to Endpoint Cloud. Consider the following things when creating your plan:

• Order in which devices should have their protection moved to Endpoint Cloud
• Timing of moving the groups of device - is off-hours better for some devices but perhaps not necessary for others in your environment
• Span of time for migration - all in one day or spread across several days or weeks

Policies and exclusions

In addition to the list of systems to be protected, you need to consider your existing policy settings and migrating those from any existing antivirus solutions into Endpoint Cloud. This could include things as simple as what time of day regular scanning should be performed, to detailed exclusions to avoid incompatibilities with local custom apps. Each source antivirus system will have its own set of configuration settings, and in many cases, there won't be a one-to-one match, so you will have to review the old settings carefully to determine which ones make sense to migrate to Endpoint Cloud.

Consider the following policy areas when creating your plan:

• Removing incompatible software during agent install
• Scan schedules and type of scans
• Exclusions
  • Device control exclusion names and/or Friendly names are not migrated; migrated exclusion names are based on the policy name
    2. Removable device exclusions configured to all "Hard drives" or "Non-hard drives" only will be converted using both drive types
    3. Floppy drive device class settings, or floppy exclusions, are not migrated if previously blocked will be allowed after the migration
    4. Exclusions configured to block all access are not migrated
• Become familiar with other policy areas - refer to Related Articles to learn about policies if you are new to VIPRE

View Endpoint Cloud policy details

Refer to Related Articles for details that explain how to display policy settings and exclusions in Endpoint Cloud.

If you are migrating from a non-VIPRE solution, review the Endpoint Cloud default policies and create custom policies and settings as appropriate for your specific environment.

If you are migrating from a VIPRE Server solution, the Endpoint Migrator will migrate your current policies to Endpoint Cloud.