How do I configure mixed-version deployments of RealVNC Server on Windows computers using Group Policy?


If you have a subscription which includes mass deployment, you can configure RealVNC Server running on computers you want to control in bulk or remotely using Group Policy.

If you have different versions of RealVNC Server deployed on the Windows computers in your organization, you can use Group Policy WMI Filters to ensure the correct policies are applied. To do this:

  1. Follow these instructions to download policy template files from RealVNC and edit parameters appropriately.
  2. Create one Group Policy Object (GPO) for each version of RealVNC Server you want to configure.
  3. Obtain the exact product name of each version of RealVNC Server.

    To do this, run the following PowerShell command on one remote computer hosting each version of RealVNC Server:

    Get-WmiObject -Query 'Select * from CIM_DataFile Where Name="C:\\Program Files\\RealVNC\\VNC Server\\vncserver.exe"'

    An example result is shown below; the important information is highlighted in red:
    Compressed : False
    Encrypted  : False
    Size       :
    Hidden     : False
    Name       : c:\program files\realvnc\vnc server\vncserver.exe
    Readable   : True
    System     : False
    Version    :
    Writeable  : True
  4. In Group Policy Management Editor, select WMI Filters from the left-hand pane.
  5. Add a new filter for each version of RealVNC Server.

    Give the filter an appropriate Name, leave the Namespace as the default root\CIMv2, and enter the following as the Query, where the name at the end matches the value obtained in step 3:

    Select * from CIM_DataFile Where Name="C:\\Program Files\\RealVNC\\VNC Server\\vncserver.exe" AND Version LIKE "7.5%"

    For example:


  6. For each GPO, select the appropriate filter from the WMI Filtering dropdown. In the example below, this GPO will only be applied to remote computers running RealVNC Server version 7.5:

Was this article helpful?
11 out of 18 found this helpful



Article is closed for comments.