While most of our Customers are relying on commercial tools such as Microsoft System Center to automate VDM installation or replicate their “golden images” within virtualized environments, there is definitely space for a self contained approach that should work with physical as well as virtual machines:
Remote software installation:
- Assuming here that you have a single license file “LICENSE.VDL” for all computers that need VDM.
- Install VDM on a test computer and import that license file. It is placed next to
VDM.exe
and read on VDM start. - Configure VDM settings for your test user and confirm VDM is working properly. In case troubleshooting of this install is needed, check troubleshooting steps here: LINK.
- Copy the VDM folder to your target machines. Default directory on a 64-bit system is “
C:\Program Files (x86)\VDM
” and “C:\Program Files\VDM
” on a 32-bit system. License file is expected to be part of this copy process, as it is inside the VDM folder. - Execute
VdmSetup.exe
from the “..\VDM\System32
” folder on the target machine with the “-i
” switch to install VDM on the target system. Use “-u
” command line switch to uninstall; reboot is required right after, so VDM files can be removed. Note that remote execution of either option, “VdmSetup -i
” or “VdmSetup -u
“, requires elevation of privileges, which is automatic with local installation and requires some additional scripting when executed remotely, as there will be no elevation prompt. - VDM configuration is done per user and is located at “
HKEY_CURRENT_USER\SOFTWARE\Teknica Software, Inc.
” key within Windows Registry. You can either use user profiles to propagate these same settings to your users configured on your test system, or export that Registry key to “*.reg
” file and imported it to individual users as needed. No administrative privileges required.
Remote software update is very similar:
- Run “
VdmSetup -u
” on the target system and reboot - While preserving
LICENSE.VDL
, delete the contents of the original VDM folder and replace it with new binaries. - Run “
VdmSetup -i
” on the target system. At this point VDM is ready. All VDM settings per user are preserved.
While there are several options to accomplish remote execution, PowerShell’s “
Invoke-Command
” is probably best suited for this task.