How do I use Microsoft Intune to configure VNC Connect?

Follow

If you have an Enterprise subscription you can deploy, configure and license VNC Connect using Microsoft Intune. Microsoft Intune can be used as an alternative to Group Policy for Azure AD joined devices. To configure VNC Connect using Microsoft Intune you will need to ingest the VNC Connect ADMX templates into Intune and apply settings by using a Device Configuration Profile.

VNC Server

Create a new device configuration profile

  1. Log in to https://endpoint.microsoft.com/#home
  2. Click Devices on left menu, then Configuration profiles
  3. Click Create profile
  4. Select Platform - Windows 10 and later, Profile - Custom
  5. Click Create
  6. Enter a name (e.g. VNC Server Configuration), click Next
  7. Configuration setting: Leave blank and click Next (we'll edit this later)
  8. Configure Assignments: Configure which group(s) to apply the policy to e.g. All devices, click Next
  9. Applicability Rules: Configure any rules to use when determining whether to apply the policy to a device or leave blank, click Next
  10. Review + create: Click Create

Ingest the ADMX templates for use by the configuration profile

  1. Log in to https://endpoint.microsoft.com/#home
  2. Click Devices on left menu, then Configuration profiles, then click the profile that you want to edit
  3. Click Properties
  4. Click Edit next to Configuration settings
  5. Click Add, then populate the fields as below
    • Name: The name of the row, e.g. VNC Server Licensing ADMX
    • Description: An optional extended description
    • OMA-URI:
      ./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/VNCServer/Policy/VNCServerLicensing
    • Data Type: String
    • Value: The contents of the realvnc_licensing ADMX file (download here)
      Open the realvnc_licensing ADMX template in Notepad and copy and paste the contents
  6. Click Add, then populate the fields as below
    • Name: The name of the row, e.g. VNC Server Config ADMX
    • Description: An optional extended description
    • OMA-URI:
      ./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/VNCServer/Policy/VNCServerConfig
    • Data Type: String
    • Value: The contents of the realvnc_server ADMX file (download here)
    • Open the realvnc_server ADMX template in Notepad and copy and paste the contents
  7. Click Save, then Review+Save to check the OMA-URI you just created. Click Save

Licensing VNC Server

  1. Log in to https://endpoint.microsoft.com/#home
  2. Click Devices on left menu, then Configuration profiles, then click the profile you want to edit
  3. Click Properties
  4. Click Edit next to Configuration settings
  5. Click Add, then populate the fields as below:
    • Name: LicenseKey
    • Description: An optional extended description
    • OMA-URI:
      ./Device/Vendor/MSFT/Policy/Config/VNCServer~Policy~Licensing/RealVNC_vncserver_Machine_vncserverlicense
    • Data Type: String
    • Value:
      <enabled/>
      <data id="Value" Value="LICENSEKEY"/>
  6. Click Save, then Review+Save to check the OMA-URI you just created. Click Save

Configuring VNC Server

Before you can configure a policy setting, please ensure you have ingested the ADMX template via OMA-URI, above.

  1. Log in to https://endpoint.microsoft.com/#home
  2. Click Devices on left menu, then Configuration profiles, then click the profile you want to edit
  3. Click Properties
  4. Click Edit next to Configuration settings
  5. Click Add, then populate the fields as below:
    • Name: The name of the setting, e.g. Permissions
    • Description: An optional extended description
    • OMA-URI:
      ./Device/Vendor/MSFT/Policy/Config/VNCServer~Policy~VNC_Server~vncserver_Machine/RealVNC_vncserver_Machine_Permissions
      • The template format is:
        ./Device/Vendor/MSFT/Policy/Config/VNCServer~Policy~{CategoryPathFromADMX}/{SettingFromADMX}
      • Both {CategoryPathFromADMX} and {SettingFromADMX} are determined from analysing the ADMX template file. The table below shows the values to use for VNC Server.

        CategoryPathFromADMX
        SettingFromADMX
        VNC_Server~vncserver_Machine
        RealVNC_vncserver_Machine_{parametername}

        Replace {parametername} with the VNC Server parameter name

        Note: if a particular parameter is not accepted, please refer to the ADMX file for the correct policy name
    • Data Type: String
    • Value: This depends on the type of parameter you are setting. Please refer to the below table.

      Setting Type
      Value
      True/False <enabled/>
      Text <enabled/>
      <data id="Value" value="{parametervalue}"/>

      Replace {parametervalue} with the text string

      Note: ensure quotes are normal quotes and not smart quotes if copy and pasting!
  6. Click Save, then Review+Save to check the OMA-URI you just created. Click Save
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.