20 January, 2010 at 5:15 pm
by Phil Wiffen · Filed under Miscellaneous
Here’s a sample of the UK rules we use at DisplayLink for our MDT 2010 Deployment Shares:
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
;Skips Welcome Screen
SkipBDDWelcome=YES
; VISTA LOCALE SETTINGS
KeyboardLocale=0809:00000809
UserLocale=en-GB
InputLocale=0809:00000809
SystemLocale=en-GB
UILanguage=en-US
;BitLocker
OSDBitLockerWaitForEncryption = "FALSE"
BdeRecoveryKey=AD
BDEInstall=TPMPin
BdeInstallSupress=NO
OSDBitLockerMode=TPMKey
OSDBitLockerCreateRecoveryPassword=AD
;SkipTimeZone=YES
TimeZone=85
TimeZoneName=GMT Standard Time
UserDataLocation=AUTO
SkipComputerBackup=YES
Permalink
20 January, 2010 at 5:11 pm
by Phil Wiffen · Filed under Miscellaneous
Here’s a sample BOOTSTRAP.INI that we use at DisplayLink for MDT deployments.
This will pre-fill a number of options throughout the MDT WinPE Deployment Wizard.
Share and enjoy
[Settings]
Priority=Default
[Default]
DeployRoot=\\MDTSERVER\Distribution$
SkipBDDWelcome=YES
KeyboardLocale=0809:00000809
UserLocale=en-GB
InputLocale=0809:00000809
SystemLocale=en-GB
UILanguage=en-US
UserDomain=YOURDOMAIN
Permalink
19 January, 2010 at 2:24 pm
by Phil Wiffen · Filed under Miscellaneous
Need to hot-add RAM to a Linux Guest OS in VMware vShpere 4? Some good instructions are provided here
Permalink
11 January, 2010 at 10:01 am
by Phil Wiffen · Filed under Miscellaneous
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!
- 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)
- 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!)
- 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:
If @OSArch = "X86" Then
$PID = Run('msiexec /i \\server\share\DisplayLinkCore-32bit.msi /norestart /passive')
ProcessWaitClose($PID)
$PID = Run('msiexec /i \\server\share\DisplayLinkSetup-32bit.msi /norestart /passive')
ProcessWaitClose($PID)
ElseIf @OSArch = "X64" Then
$PID = Run('msiexec /i \\server\share\DisplayLinkCore-64bit.msi /norestart /passive')
ProcessWaitClose($PID)
$PID = Run('msiexec /i \\server\share\DisplayLinkSetup-64bit.msi /norestart /passive')
ProcessWaitClose($PID)
EndIf
Permalink