Skip to main content

Customising deployments

Aside from customizing the Deploy-Application.ps1 script to deploy your application, no configuration is necessary out of the box. The following components can be configured as required:

AppDeployToolkitConfig.xml​

Configure the default UI messages, MSI parameters, log file location, whether Admin rights should be required, whether log files should be compressed, log style (CMTrace or Legacy), max log size, whether debug messages should be logged, whether log entries should be written to the console, whether toolkit should re-launch as elevated logged-on console user when in SYSTEM context, whether toolkit should fall back to SYSTEM context if failure to launch toolkit as user, and whether toolkit should attempt to launch as a non-console logged on user (e.g. user logged on via terminal services) when in SYSTEM context.

AppDeployToolkitLogo.ico​

To brand the balloon notifications and UI window title bars with your own custom/corporate logo, replace the AppDeployToolkitLogo.ico file with your own .ico file (retaining the file name)

AppDeployToolkitBanner.png​

To brand the PSAppDeployToolkit UI prompts with your own custom/corporate banner, replace the AppDeployToolkitBanner.png file with your own .png file (retaining the file name). The file must be in PNG format and must be 450 x 50 in size.

Logging​

The PSAppDeployToolkit generates extensive logging for all toolkit and MSI operations.

The default log folder for the PSAppDeployToolkit and MSI log files can be specified in the XML configuration file. The default folder is C:\Windows\Logs\Software.

The PSAppDeployToolkit log file is named after the application with _PSAppDeployToolkit appended to the end, e.g.

  • Oracle_JavaRuntime_1.7.0.17_EN_01_PSAppDeployToolkit.log

All MSI actions are logged and the log file is named according to the MSI file used on the command line, with the action appended to the log file name. For uninstallations, the MSI product code is resolved to the MSI application name and version to keep the same log file format, e.g.

  • Oracle_JavaRuntimeEnvironmentx86_1.7.0.17_EN_01_Install.log
  • Oracle_JavaRuntimeEnvironmentx86_1.7.0.17_EN_01_Repair.log
  • Oracle_JavaRuntimeEnvironmentx86_1.7.0.17_EN_01_Patch.log
  • Oracle_JavaRuntimeEnvironmentx86_1.7.0.17_EN_01_Uninstall.log

Log Compression​

One of the PSAppDeployToolkit Options in the AppDeployToolkitConfig.xml file is CompressLogs. Enabling this option will create a temporary logging folder where you can save all of the log files you want to include in the single ZIP file that will be created from this folder.

To enable the CompressLogs feature, set the follow option in AppDeployToolkitConfig.xml to True:

<Toolkit_CompressLogs>True</Toolkit_CompressLogs>

When set to True, the following happens:

  • Both toolkit and MSI logs are temporally placed in $envTemp$installName which gets cleaned up at the end of the install.
  • At the end of the install / uninstall, the logs are compressed into a new zip file which is placed in the LogFolder location in the config file.
  • The Zip file name indicates whether it is an Install / Uninstall and has the timestamp in the filename so previous logs do not get overwritten.
  • If your package creates other log files, you can send them to the temporary logging folder at $envTemp$installName.