Update 2016-08-02: Someone asked, could it not be possible to run external vbs and ps1 scripts as well. Well hat has now been fixed and the new version is available for download.
Current versions support the following installertypes, EXE/MSI/MSP/VBS/PS1. Happy deploying!
My good friend “The Deployment Bunny” did a while back a nice script to install Internet Explorer 11 into a ref image. I now needed a nice way to deploy other applications using the same principle and way to deliver this to customers.
The problem now is most don’t want to edit the script every time a new application should be used. To sort this out the script uses a settings.xml file to specify the needed parameters.
The XML in itself is a short simple one as can be seen below.
<Name>Oracle Java <InstallerName>jre-8u40-windows-i586.exe</InstallerName>
Now all that has to be changed for this to work with other applications is the Name, the file to run and the install switches. If you change to run a MSI instead just change installertype to MSI.
The folder structure for it to work needs to look like this and the install files is then place inside the Source folder.
This can then either be run by simply running the PowerShell script from the folder or by calling on it from inside SCCM or MDT. The Install command from MDT and SCCM is then “cmd /c PowerShell.exe –ExecutionPolicy ByPass –File install-applications.ps1”
If you run this inside of MDT or SCCM and in a Task sequence the logging will be done to the relevant logfolders used by MDT and SCCM.
The script can and a sample settings.xml can be downloaded from here http://bit.ly/1TAdgEh