If you have a subscription that offers mass deployment, you can deploy, configure and license RealVNC Connect using Microsoft Intune. Microsoft Intune can be used as an alternative to Group Policy for Azure AD joined devices.

Download the RealVNC Connect ADMX templates

The ADMX templates can be download using the links below:

RealVNC Server ADMX templates

RealVNC Viewer ADMX templates

Once downloaded, extract the ADMX and ADML files from the zip archive, making a note of the location.

Import the RealVNC Connect ADMX templates into Intune Endpoint Manager

This is a Microsoft public preview feature. Read more here: https://docs.microsoft.com/en-us/mem/intune/configuration/administrative-templates-import-custom

1. Download the ADMX templates for the RealVNC Connect application(s) that you want to configure with Intune

2. Sign in to the Microsoft Endpoint Manager

3. Navigate to Devices > Configuration > Import ADMX > Import
   
   
   
   

4. Upload your files:

   • ADMX file: Select the ADMX file you want to upload.
   • ADML file for the default language: Select the ADML file you want to upload. Remember, you can add only one language file for each ADMX file you upload.
   • Specify the language of the ADML file: Shows the ADML language of the file you uploaded.

   Note: If you have previously uploaded older versions of the ADMX and ADML files, you must first delete the existing templates and any configuration profiles using the existing templates before uploading the updated files.

5. Click Next

6. In Review + Create, review your changes then click Create to import the files

7. When the import completes, your ADMX templates are shown in the list
   
   

Create a configuration profile to configure and license RealVNC Server and RealVNC Viewer

1. Sign in to the Microsoft Endpoint Manager

2. Navigate to Devices > Configuration > Create > New Policy

3. Enter the following properties:

   • Platform: Select Windows 10 and later.

   • Profile: Select Templates > Imported Administrative templates (Preview):

     

4. Click Create.

5. In Basics, enter the following properties then click Next:

   • Name: Enter a descriptive name for the profile. Name your profiles so you can easily identify them later. For example, a good profile name is ADMX: RealVNC Server for Windows.
   • Description: Enter a description for the profile. This setting is optional, but recommended.
6. In Configuration settings, select and configure the settings you want in your policy. When finished, click Next.

7. In Scope tags (optional), assign a tag to filter the profile to specific IT groups and click Next.
   For more information about scope tags, see Use role-based access control (RBAC) and scope tags for distributed IT.

8. In Assignments, select the user or groups that will receive your profile. For more information on assigning profiles, see Assign user and device profiles in Intune.
   
   If the profile is assigned to user groups, then configured ADMX settings apply to any device that the user enrolls, and signs in to. If the profile is assigned to device groups, then configured ADMX settings apply to any user that signs into that device. This assignment happens if the ADMX setting is a computer configuration (HKEY_LOCAL_MACHINE), or a user configuration (HKEY_CURRENT_USER). RealVNC Server uses device configuration, while RealVNC Viewer uses user configuration.
   
   Click Next when you are done.

9. In Review + create, review your settings. When you click Create, your changes are saved and the profile is assigned and started to be deployed to the targeted devices.
   
   You can check the progress of the deployment on the configuration overview page of the profile: