PSInstallApplication

KO | EN

gitlite — search

#python #java #python3 #arduino #golang #machine-learning #rust #html #flask #javascript #seismology #nodejs

PSInstallApplication

★ 12 Open GitHub ↗

Powershell script designed to install an application using xml

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Install-Application.ps1

I used to use the AppDeployToolkit from https://psappdeploytoolkit.com/, but I have had alot of people wanting to install software and log it but not have the all the files from the AppDeployToolkit. Over time, I have developed a small powershell sript to install msi files, then one that installed executables, and one that installed another executable with patches and it kept growing. So I decided to combined alot of that into one powershell script with an xml file for the installation answers (if needed)

This script is not perfect, but it does a pretty good job of detecting and installing applications just like the appdeploytoolkit.

The xml is broken into two parts: 
 - The details
 - The Application(s)
	
## The Details
This covers the information for the overall application. 
 - InstallName = is a non-spaced name that is mainly used for logging
 - Name = is the friendly name
 - Version = As of now its just a version for the application installer. I thought of into making it the overall validated version of
 the app that being installed
   
## The Application(s)
This can be multiple applications. The script will loop through each one in order
	
Application Configurations:
 - Name: Name of specific task to run (Used for logging and if DetectionRule has value of [Name])
 - Installer: path to installer. Defaults to source directory, but name MUST be specified
      - AUTO will search for the first file in source folder (if extension is specified, it will seeach for the first file with that
	extension)
	
 - InstallerType: Identifies how script will process the installer
      - Allowed Values (case insensitive): AUTO,EXE,MSI,MSP,MSU,CMD,BAT,VBS
      - AUTO will detect file extension of Installer
	
 - InstallSwitches: Are used for the arguments the application may need. Spaces are allowed
      - If [SourcePath] is provided, it will replace it with the directory the install is located
	<code>eg. Adobe installer requires a Transform file. the full path is required. Instead of hardcoding the full path, use
	TRANSFORMS=[SourcePath]\AcrobatReaderDC.mst"</code>
      - If [RootPath] is provided, it will replace it with the directory the script is located
      - If [TSEnv-\<MDTSCCM\>] is provided, it will replace it with the path or variable the Tasksequence
	<code>eg. Adobe installer requires a Transform file. the full path is required. If the path for the mst file is in the MDT
	Scripts folder, use TRANSFORMS=[TSEnv-ScriptRoot]\AcrobatReaderDC.mst"</code>
      - If special characters are used such as <code>",',[,],(,)</code> use the tick mark to declare key <code>`</code> them as strings
      <code>eg. <InstallSwitches>/adminfile `"[RootPath]\Configs\X86_O16FULL_NOONEDRIVE.MSP`"</InstallSwitches></code>
	
 - SupportedArc: Architecture to compare software with Operating System. If not a match this application will not run
      - Allowed Values (case insensitive): Both, x64, x86
	<code>NOTE: If Both is specified, script will loop through both architictures if OS has it.</code>
	
 - DetectionType: Specifies how the software will detect if application was installed already
      - Allowed Values (case insensitive): File,Reg,GUID
      - GUID will scan system for installed products and compare it to DetectionRule is set {some-guid}. This process takes longer based
      on products already installed

- DetectionRule: Depending on DetectionType, this will be the path, name and value to check
      - Value Requirements for REG Type: Registry path, Registry Key Name, Registry value (optional)
              - If version is not provided it will detect if registry key name exists only
              - If [version] is provided, it will compare it to the version specified in main details
		<code>eg. HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Mobile Client,ProductVersion,[Version]</code>
      - Value Requirements for FILE Type: Folder path, File Name, Version (optional)
              - If version is not provided it will detect if file exists only
              - If [version] is provided, it will compare it to the version specified in main details
		<code>eg. C:\Program Files (x86)\Java\jre1.8.0_181\bin,java.exe,[Version]</code>
      - Value Requirements for GUID Type: {some-guid}, Version (optional)
              - If version is not provided it will detect if GUID exists only
              - If [version] is provided, it will compare it to the version specified in details
		<code>eg. {A68173CF-C68F-4878-A1A1-3AD0A286D38A},[Version]</code>

- IgnoreErrorCodes: Ignores any exit codes in the list. Useful is installer requires a reboot (eg. 3010)	
	
 - ValidateInstall: Used as an extra validation check. Run the detection Rule a second time. 
 	      - Allowed Values (case insensitive): True or False
 	      - If set to true and application is already installed, this will not run
	      - If set to true and detection rule is null, this will not run

## Dynamic values
 - [\<num\>-Version] =  trims the version's first digits in front by <num>
 - [Version-\<num\>] =  trims the version's last digits by <num>
 - [\<num\>-Version-\<num\>] =  Allow to trim the version in front or behind
 
 <code>eg: Adobe Acrobat DC msp file version is [2019.010.20064], but the detection needs to find [19.010.20064], so [2-Version] is used in the DetectionRule (see example xml)</code>

## Additional arguments 
Call by the Intall-Application.ps1 directly. This allow dynamic arguments to be passed using SCCM/MDT properties or other external sources:
 - [InstallArgument] --> Use switch [-InstallerArg <value>] 
 	If specified in the <Installer> section will replace with value passed by the script
	This can be helpful if multple installers exist, but only one to be installed. 
				 e.g. <code>Install-Application.ps1 -InstallerArg %CCTKInstallerVersion%</code>
 - [SwitchArgument] --> Use switch [-SwitchArg <value>] 
	If specified in the <InstallSwitches> section will replace with value passed by the script
				 e.g. <code>Install-Application.ps1 -SwitchArg %siteserver%</code>
 - [DetectArgument] --> Use switch [-DetectionArg <value>] 
	If specified in the <DetectionRule> section will replace with value passed by the script
				 e.g. <code>Install-Application.ps1 -DetectionArg %version%</code>
				
## Examples
 - Typical Example: <code>powershell.exe -ExecutionPolicy Bypass -File ".\Install-Application.ps1"</code>
 - CCTK Example: <code>powershell.exe -ExecutionPolicy Bypass -File ".\Install-Application.ps1" -InstallArg 2.2.1</code>
 - CCM Example: <code>powershell.exe -ExecutionPolicy Bypass -File ".\Install-Application.ps1" -SwitchArg mpserver.doamin.com</code>
 - CCM Example: <code>powershell.exe -ExecutionPolicy Bypass -File ".\Install-Application.ps1" -DetectionArg %version%</code>
 - Verbose Example: <code>powershell.exe -ExecutionPolicy Bypass -File ".\Install-Application.ps1" -Verbose</code>
 
## In Development
 - Support for PS1,PSD1,NUPKG extensions

PSInstallApplication

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README