Arthur Posted February 15, 2017 Posted February 15, 2017 Website / Download / Forum What is the PowerShell App Deployment Toolkit? The PowerShell App Deployment Toolkit provides a set of functions to perform common application deployment tasks and to interact with the user during a deployment. It simplifies the complex scripting challenges of deploying applications in the enterprise, provides a consistent deployment experience and improves installation success rates. The PowerShell App Deployment Toolkit can be used to replace your WiseScript, VBScript and Batch wrapper scripts with one versatile, re-usable and extensible tool. What are the main features of the PowerShell App Deployment Toolkit? Easy To Use - Any PowerShell beginner can use the template and the functions provided with the Toolkit to perform application deployments. Consistent - Provides a consistent look and feel for all application deployments, regardless of complexity. Powerful - Provides a set of functions to perform common deployment tasks, such as installing or uninstalling multiple applications, prompting users to close apps, setting registry keys, copying files, etc. User Interface - Provides user interaction through customizable user interface dialogs boxes, progress dialogs and balloon tip notifications. Localized - The UI is localized in several languages and more can easily be added using the XML configuration file. Integration - Integrates well with SCCM 2007/2012; provides installation and uninstallation deployment types with options on how to handle exit codes, such as supressing reboots or returning a fast retry code. Updatable - The logic engine and functions are separated from per-application scripts, so that you can update the toolkit when a new version is released and maintain backwards compatibility with your deployment scripts. Extensible - The Toolkit can be easily extended to add custom scripts and functions. Helpful - The Toolkit provides detailed logging of all actions performed and even includes a graphical console to browse the help documentation for the Toolkit functions. Version 3.6.9 [12/02/2017] Added SecureParameters parameter to additional section of Execute-ProcessAsUser Added SecureParameters parameter to Execute-ProcessAsUser Added -RegEx parameter to Get-InstalledApplication and modified the help text for the -Name parameter Added DoNotExpandEnvironmentNames parameter to Get-RegistryKey to enable retrieving of unexpanded REG_EXPAND_SZ values Added expandstring functionality to the MSI_InstallParams, MSI_SilentParams, and MSI_UninstallParams XML properties Added support for Windows 10 to the function Set-PinnedApplication to enable pinning and unpinning to the Start Menu Added IncludeUpdatesAndHotfixes Parameter to Execute-MSI and Remove-MSI functions BREAKING CHANGE, Changed variable envCommonPrograms to envCommonStartMenuPrograms Changed behavior of Remove-Folder function to continue deleting files recursively when an error is encountered when $ContinueOnError is used Changed severity of failure messages created in the Set-PinnedApplication to warning (2) from error (3) Changed .ps1 script files so that they are UTF-8 BOM encoded so that you can digitally sign files on non-unicode language systems Fixed issue in Exit-Script where the system tray icon was not being removed at the end of the script Fixed issue in Remove-MSIApplication which caused the function to fail in the case of multiple filtered or excluded applications Fixed issue in Get-PendingReboot where detection of a pending SCCM reboot would cause a fatal error for some clients Fixed issue in Test-MSUpdates giving preference to the Get-Hotfix cmdlet for detecting updates Fixed issue where variable envOSVersion was inconsistent in Windows 8 and 8.1 workstations Fixed issue in Execute-ProcessAsUser with Powershell script execution Fixed issue in Test-MSUpdate which returned a false positive when searching for an installed update Fixed typo in Get-HardwarePlatform function Fixed issue in Set-RegistryKey where registry keys with forward slashes were treated like backslashes and broken up into subkeys Fixed issue in Remove-RegistryKey function where it failed to delete the (Default) value when specified due to limitation of Remove-ChildItem cmdlet Fixed issue in New-Shortcut to use Rename-Item parameter name that is compatible with PS 2.0 Fixed issue in Get-RegistryKey function which caused it to ignore the (Default) value 2
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now