How to easily deploy DisplayLink drivers

Some quick notes on how we deploy DisplayLink drivers internally here at DisplayLink. Due to our unique requirements, we don’t deploy our software via GPSI, as our Developers need to use bleeding-edge drivers, rather than the publicly released ones!

Instead we deploy them manually when setting up a PC. DisplayLink IT uses the publicly available Corporare Install files, which are distributed as MSIs. This allows you to do silent, automated installs of our software without having to accept a EULA each time. For ease, I  use AutoIT to do the actual installation as it’s nice and flexible, and we tend to buy laptops on an ad-hoc/purpose specific basis, so Drive Imaging would consume more time than it would save!

  1. Get the DisplayLink Corporate Install files from here: http://www.displaylink.com/corporateinstall/ (You’ll need to register, but it’s a one-time thing)
  2. Extract the both the 32-bit and 64-bit MSIs in the zip file to somewhere useful. If you want to deploy them via GPSI, check out the PDF (I wrote it, and welcome any comments/suggestions, as I have a lot to learn about GPSI!)
  3. For silent installations, I put the MSIs all in one directory and just rename the files as appropriate for each architecture (see below for the naming I use)

The main command lines you need are:

32-bit:

msiexec /i \\server\share\DisplayLinkCore-32bit.msi /norestart /passive

msiexec /i \\server\share\DisplayLinkSetup-32bit.msi /norestart /passive

64-bit:

msiexec /i \\server\share\DisplayLinkCore-64bit.msi /norestart /passive

msiexec /i \\server\share\DisplayLinkSetup-64bit.msi /norestart /passive

Here’s the AutoIT code, should you need it:

Trying to automate creation of VPN connections under Win7

I’m currently playing with Connection Manager Administration Kit for Server 2008.

Why? Because with the advent of Windows 7 (and Vista, to a certain extent), it’s a complete pain in the butt to programme a tool like AutoIT to script and automate the configuration of a VPN connection for our end users. The key issue, is that Microsoft don’t seem to provide any “command line” shortcuts through things like DLLs or Shell extensions to quickly bring up the “Set up a new connection or network” wizard. Sad face.

http://www.windowsecurity.com/articles/Windows-Server-2008-Connection-Manager-Administration-Kit.html