Migrate an Existing SCP Policy to the Skyhigh Client Policy

Prerequisites

• Skyhigh Client 5.0.0.x
• Existing SCP Policy

The policy migration takes place in three steps: 

• Upgrade Skyhigh Client
• Migrate an Existing Policy and Configuration
• Apply Policy to the Skyhigh Client

Perform the following steps to successfully migrate the policy and its configuration.

Upgrade Skyhigh Client

Skyhigh Client upgrade refers to updating the Skyhigh Client Proxy versions below 5.x to the new Skyhigh Client 5.0.0.x, ensuring compatibility with the Skyhigh Client.

To upgrade Skyhigh Client:

1. Log in to the SSE UI.
2. Navigate to Policy > Skyhigh Client > Policy.
   The Skyhigh Client page opens.
3. Click Migrate Existing Deployment.
4. Under the Upgrade Skyhigh Client section, click Download.
   
   
   The latest version of the Skyhigh Client is downloaded.
   
   To install the Skyhigh Client, use one of the following applicable methods:
   • Trellix ePO
   • Intune

Migrate an Existing SCP Policy and Configuration

Policy migration involves migrating the existing SCP policy and its configuration to the new Skyhigh Client policy.

To migrate an existing SCP policy and its configuration: 

1. Log in to the SSE UI.
2. Navigate to Policy > Skyhigh Client > Policy.
3. On the SC Policy dashboard, under the Getting Started window, click New Policy.
   The Select a method to add a policy window opens.
4. Click the Migrate an Existing SCP Policy tab.
5. Perform the applicable action:

► Case 1: If you have an existing SCP policy

Under the Select an Existing SCP Policy tab:

1. From the Select Policy drop-down, select an applicable policy.
2. In the Policy Name field, enter a name. (A default name is auto-populated.) 

NOTE: The Policy name, Client Profile, Gateway List, and Lists (from List Catalog) contain a common identifier. This is unique for every migration attempt to ensure that repeated migration of the same policy works seamlessly.

3. Click Migrate Policy.
   
   
   
   A progress bar with migration status displays.
   
   (Optional) If an error message displays during the migration, click Try Again.
   
   

NOTE:  If the issue continues, contact Skyhigh Support. 

        Upon migration, You have successfully migrated the Skyhigh Client Proxy policy message displays.

      

4. Click Done.
   The policy is migrated.

OR

► Case 2: If you have an OPG file of the existing SCP Policy

Click the Import an Existing SCP Policy tab:

1. Click Browse.
2. Select an applicable OPG file.
   The OPG file is uploaded.
3. In the Policy Name field, enter a name (A default name is auto-populated).

NOTE: The Policy name, Client Profile, Gateway List, and Lists (from List Catalog) contain a common identifier. This is unique for every migration attempt to ensure that repeated migration of the same policy works seamlessly.

4. Click Migrate Policy.
   
   

   A progress bar with migration status displays. 

   (Optional) If an error message displays during the migration, click Try Again.
   
   

NOTE: If the issue continues, contact Skyhigh Support.

     Upon migration, You have successfully migrated the Skyhigh Client Proxy policy message displays.

    

5. Click Done.

The migrated policy appears under the policy tree of the SC Policy dashboard. This policy is automatically linked to a default profile, a gateway, and lists based on the existing SCP policy configurations. To modify these settings, see Configure Skyhigh Client Settings.

NOTE: The Web policy lists used in the existing SCP policy are not migrated as the new Skyhigh Client policy has pre-defined lists. If required, you can add the lists to the selective redirection custom rule in the new Skyhigh Client policy. For more details about adding a list, see List Catalog.

Additionally, you can modify the migrated policy to meet specific requirements. For more details, see Configure the Skyhigh Client Policy.

Apply Policy to the Skyhigh Client

1. After configuring the policy, you must publish and download it.
   The file is saved in the OPG format. 
2. Deploy the Client policy to the endpoints using the applicable deployment methods.