Create a SASE client image

Updated at:

Package a Windows system image with the SASE App pre-installed for rapid, consistent deployment across multiple devices.

Overview

A Windows system image bundles the OS, applications, and configurations into a reusable file. You can use it to restore failed devices quickly, minimize downtime, and provision new client instances on demand.

Prerequisites

Secure Access Service Edge is activated. If you have not activated Secure Access Service Edge, Purchase Service or Apply for a Free Trial (7-day free trial available).

Notes

  • Image distribution security: Image files may contain sensitive data. Distribute them through secure channels to prevent data leaks.

  • SASE system configuration: SASE configurations persist after image deployment. For example, if an endpoint anti-uninstallation policy is configured, employees must request and receive administrator approval before uninstalling the SASE app.

  • SASE App configuration persistence: SASE App settings such as proxy mode and traffic-steering DNS are retained after image deployment.

Procedure

Step 1: Download and install the SASE App

Install all required applications on the source device before you create the image.

  1. Log on to the SASE console.

  2. In the left-side navigation pane, click Settings.

  3. On the Download Client tab, download the appropriate Windows client for your operating system version.

  4. Install the downloaded client using either manual installation or silent installation.

    • Manual installation: Double-click the installer and follow the wizard.

    • Silent installation: Open Command Prompt in the download directory and run the command for your package type:

      • .exe file: <package_name> /S. For example: sase.exe /S.

      • .msi file: msiexec /i <package_name> /quiet /norestart. For example: msiexec /i sase.msi /quiet /norestart.

        Important

        To silently install an .msi package from the command line, you must run the Command Prompt as an administrator.

Step 2: Package the system image

Package the Windows system into an image file. Clear temporary files and logs beforehand to reduce the image size.

  1. In the search box in Windows, search for and open Registry Editor.

  2. Delete HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AliSASE, the registry key related to SASE.

  3. Create the system image using one of the following methods:

    Built-in tool

    1. Open the Control Panel.

    2. In the Control Panel, click Backup and Restore.

    3. In the left navigation bar, click Create a System Image.

    4. In the Create System Image dialog box, follow the wizard to complete image creation.

    Third-party tool

    1. Download and install a third-party image creation tool, such as Acronis True Image.

    2. Start the tool and select Backup Disk or Create Image.

    3. Select the disk partition you want to back up and specify a destination path for the image file.

    4. Start the backup and wait for it to complete.

Step 3: Install image and verify applications

Deploy the image to a target device and verify that the pre-installed applications work correctly.

  1. Restore a target device using the image file you created.

    Important

    If a devTag conflict occurs after you install the image, submit a ticket from the upper-right corner of the console to request a devTag clearing script.

  2. Log on to the Windows system and check the network connection.

  3. Open the SASE App and log on using your enterprise or custom identity source.

    If your administrator enabled network access and CA certificate verification, you are prompted to install a CA certificate after logon.

    Note

    The Windows operating system installs the certificate automatically.

  4. In the lower-right corner of the client, click image, select the appropriate POP cluster, and then click Connect to verify access to your internal enterprise network.

    Note

    If you cannot connect to the internal network, verify that saml-csas.aliyuncs.com resolves correctly. A resolution failure typically indicates a DNS or external network issue.