This article provides a PowerShell scripting template for SCCM and MDT packages. This template can also be used for stand-alone installations (without using SCCM or MDT)!

An SCCM package is basically a container with source files. I recommend using a wrapper (a script) to execute the installation files and for any configuration you may need. And that is exactly what the PowerShell template below offers!
Even better, the template in this article uses my PowerShell Function Library, which effectively turns it into a complete deployment framework.

Scripting Template

The scripting template below is an example that you can use for your installations and configurations. The functions in the template are imported from a PowerShell module for the Dennis Span PowerShell Function Library. The library offers more functions than included in the template (the template is only an example).

Please see the article PowerShell Function Library for detailed information how to install and use the library.

For a complete overview of all PowerShell functions included in the library, see the following articles on this website:

• Windows functions: PowerShell functions for Windows
• Citrix functions: PowerShell functions for Citrix

How to use this template

First, copy the above code in your preferred editor (e.g. notepad) and save the file as a PowerShell script (*.PS1), for example MyAppInstaller.ps1. You can choose any file name you want of course.

You have to modify a couple of lines in the script to match your specific requirements. Enter your preferred log directory and package name in lines 43 and 44, for example:

• $BaseLogDir = "C:\Logs"
• $PackageName = "Adobe Acrobat Reader"

Or

• $BaseLogDir = "C:\Script\Logs"
• $PackageName = "Environment_Config"

When the log directory is created, spaces are automatically replaced with an underscore ("_"), for example: C:\Logs\Adobe_Acrobat_Reader.

The section How to use the library in a PowerShell script in the article PowerShell Function Library describes how to use the library in a PowerShell script. In line 60, make sure to enter the correct path to the library.

In the script sections "Pre-launch commands", "Installation" and "Post-launch commands" make sure to enter the functions you require.

Optional: software (un)installation

In case you are installing or uninstalling software, add your source file(s) to a subfolder relative to the root folder (e.g. Files). The subfolder is the relative path to your package source directory. For example, if this is your package source folder:

\\FileServer1\PackageSource\Adobe\Acrobat Reader\11.0.18_01

Than the subfolder for your installation source files is:

• \\FileServer1\PackageSource\Adobe\Acrobat Reader\11.0.18_01\Files
  or
  \\FileServer1\PackageSource\Adobe\Acrobat Reader\11.0.18_01\MSI
  or
• \\FileServer1\PackageSource\Adobe\Acrobat Reader\11.0.18_01\SETUP

In the PowerShell script, enter the name of your installation file, arguments and sub folder (again, relative to the root folder).

For example:

• Line 83: $FileName = "AcrobatReader.msi"
• Line 85/87: $Arguments =
  • "Transforms=""AcrobatReader.mst"" LANG_LIST=""en_US,de_DE"""
    or
  • "/silent /uninstall"
    or
  • "/QN" (for setup.exe files only)
• Line 89: $FileSubFolder = "Files"

In the previous example, the folder Files is used for the variable $FileSubFolder, This is the default value, but you can use any folder name you want (e.g. "MSI", or "SETUP"). Just make sure that the folder exists relative to the root of the path.

Please note that for MSI packages the following parameters are added by default:

• For uninstallations: "/x ""$File"" /qn /norestart /l*v ""$LogFileAPP"""
• For installations: "/i ""$File"" /qn /norestart /l*v ""$LogFileAPP"""

When you have prepared your PowerShell file copy it in the root of your package source directory. For example:

\\FileServer1\PackageSource\Adobe\Acrobat Reader\11.0.18_01\AppInstaller.ps1

The PowerShell script is executed as follows:

• For installations:
  powershell -file "\\FileServer1\PackageSource\Adobe\Acrobat Reader\11.0.18_01\AppInstaller.ps1" Install
• For uninstallations:
  powershell -file "\\FileServer1\PackageSource\Adobe\Acrobat Reader\11.0.18_01\AppInstaller.ps1" Uninstall

Happy scripting!

Dennis Span

Dennis Span works as a Senior Citrix Architect for a large insurance company in Vienna, Austria. He holds multiple certifications such as CCE-V, CCIA and CCEA. In 2017, Dennis became a Citrix Technology Advocate (CTA). In 2019, he became a Citrix Technology Professional (CTP). Besides his interest in virtualization technologies and blogging, he loves spending time with his family as well as snowboarding, playing basketball and rowing. He is fluent in Dutch, English, German and Slovak and speaks some Spanish.