How to change the source UNC path in a GPSI GPO

Some brief notes on how to change the source UNC path in a GPSI GPO

Instructions are for Server 2008.

Backup the GPO…

  1. Open up “Group Policy Management” console
  2. Find the GPO with the GPSI source UNC you’d like to change
  3. Right click it, choose “Backup”
  4. Back up the GPO a directory, eg C:\GPOs\

Now we need to edit the GPO and change the UNC…

  1. In the GPMC left-hand pane, click on Domains
  2. In the GPMC toolbar, click on Actions, then Open Migration Table Editor
  3. In the Migration Table Editor, click on “Tools” then “populate from Backup”
  4. Choose the backup you want to change
  5. In the Table Editor, change the Destination name to the new UNC path
  6. Now we need to save the migration table.
  7. Click File, Save.
  8. Save the file as something meaningful, preferably in C:\GPOs\

Now we need to apply the new settings…

  1. Go back to the Group Policy Management Console
  2. Find the GPO you need to change and Right-click on it
  3. Choose “Import Settings…”
  4. Click Next twice.
  5. Browse to your backup folder (C:\GPOs)
  6. Confirm the GPO backup whose settings you want to import, then click next.
  7. After the scan is complete, click Next
  8. Now we need to apply the Migration Table mapping:
    1. Choose “Using this migration table…”
    2. Browse to your migration table settings that you saved earlier.
    3. Now click Next, and then Finish
    4. That’s it! 🙂

How to enable Remote Desktop via Group Policy

This one had me stumped, but it’ll teach me to search the internet properly before blundering through. Even if you allow the Windows Firewall to accept Remote Desktop Connections you still need to enable Terminal Services elsewhere in the GP hierarchy. D’oh!

Here’s what you need to enable Remote Desktop remotely:

Computer Configuration > Administrative Templates > Network > Network Connections > Windows Firewall > Domain Profile > Windows Firewall: Allow Remote Desktop Exception

Computer Configuration > Administrative Templates > Windows Components > Terminal Services > Allow users to connect remotely using Terminal Services

Enable both of those options and you’ll be Remote Desktop-ing into PCs by the next day 🙂 (or rather, until your Domain clients refresh their Group Policy settings ;))

DisplayLink MSI Installer is coming…

The cat’s out of the bag 🙂 If you’re geeky enough to read release notes, you may have spotted this in our 4.6 release notes:

Support for corporate deployment of DisplayLink software
It is now possible to obtain a DisplayLink software installation solution that supports automated and remote installation scenarios. This kind of installation requires specific installation steps, detailed in the User Guide that is part of the Corporate Installer.

Yup, it’s true: we’re releasing an MSI installer very soon.

I’m excited about this news on two fronts. Firstly, this is the first time that I’ve contributed directly to a software release; I wrote the Deployment User Guide, gave advice on what IT Administrators want from a corporate installer, and helped steer testing scenarios. Secondly, this feature will allow IT Administrators to deploy DisplayLink’s software onto thousands of PCs simply and easily, further strengthening our ease-of-use message. And I don’t need to tell you how awesome GPSI+MSI is for us IT admins! 🙂

The “Corporate Install” package is different to the standard software release and will require you to register with DisplayLink in order to obtain the MSI files and sign the EULA. Once obtained, you can then deploy DisplayLink software to all the computers in your network via Group Policy Software Installation. Of course, you can perform silent/unattended installs manually via msiexec if you wish as well.

It’s worth mentioning again that the MSI installer has not been released yet, but it is coming. 

Stay tuned for more info! 🙂