Downloads of v


Last Update:

30 Aug 2022

Package Maintainer(s):

Software Author(s):

  • VSoft Technologies Pty. Ltd.


automise administration automation IDE cmd CLI admin trial

Automise (Install)

  • 1
  • 2
  • 3 | Updated: 30 Aug 2022



Downloads of v



Software Author(s):

  • VSoft Technologies Pty. Ltd.

  • 1
  • 2
  • 3
Automise (Install)

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Automise (Install), run the following command from the command line or from PowerShell:


To upgrade Automise (Install), run the following command from the command line or from PowerShell:


To uninstall Automise (Install), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade automise -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade automise -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install automise
    name: automise
    version: ''
    state: present

See docs at

chocolatey_package 'automise' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

See docs at

cChocoPackageInstaller automise
    Name     = "automise"
    Version  = ""
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'automise':
  ensure   => '',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 30 Aug 2022.


Automise provides a graphical IDE and command line to create, debug, and run Windows administrative tasks. Automise includes many actions to perform common Windows administration tasks.

The package will download and install Automise with the default settings. A 30 day trail is included for each new installation after which a licence is required from our store.

Built In Actions

Over 350 actions are included for common Windows tasks. Notiable groups of these actions include;

  • Logic - If..Then, Try..Catch..Finally, Switch, While, Iterator, and Async
  • File & directory - Search, Read, Update, and Delete
  • Text file - Search, Replace, Create, Read, Update, and Delete
  • Database - ADO Execute SQL, Stored Procedure, Backup
  • Notification - Email (SMTP), MSN, ICQ, and Telnet
  • Execution - Command line, PowerShell, Remote Execution, and PSTools
  • Software Maintenance - Install, Uninstall, Reinstall, MSI
  • Media - CD/DVD/Bluray
  • Upload & download - Web Deploy, EC2, IIS, FTP, and SFTP
  • Configuration - Active Directory, .Net, HyperV, VWWare, XML, Windows OS, and IIS

Custom Scripting

All actions provide customisation through settings as well as scripting events. These events allow custom scripted behavior to be performed. Supported languages for scripts are JScript, VBScript, PowerShell, and IronPython.

Custom Actions - Action Studio

Custom actions are used for large or complex custom scripting requirements. These custom actions can be backed by scripting logic or C# implementations. Custom action styles that can be written include;

  • Standard Actions - Simple actions that don't call an external tool.
  • Execute Actions - Actions that call an external tool to perform the desired task.
  • Iterator Actions - Tasks that require their repetition to be simplified in builds.

$ErrorActionPreference = 'Stop'; #Stop on all errors

$packageName = 'automise' #Unique name of the package
$installerType = 'EXE' #Installer is an executable. 
$url = '' #URL to download installer for current version. 
$silentArgs = '/SP /VERYSILENT /SUPPRESSMSGBOXES /CLOSEAPPLICATIONS' #Silent install arguments for our installer
$validExitCodes = @(0) #Valid return codes from the installer for success
$checksum = '16ABECE279D7CD1BC101E9D28199BD8293D541F57D3A7E36707F7CF882E5A357'

#Run chocolatey install package commandlet
Install-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" "$url" -validExitCodes $validExitCodes -checksum $checksum -checksumType sha256
$ErrorActionPreference = 'Stop'; #Stop on all errors

$packageName = 'automise' #Unique name of the package
$registryUninstallerKeyName = '{9A60B92A-77EC-44E5-8DC9-4F63798010E8}_is1' #The uninstall registry key for our application. Defined and setup by the installer exe.
$installerType = 'EXE' #Our uninstaller is also an executable
$silentArgs = '/SILENT /VERYSILENT /SUPPRESSMSGBOXES' #Silent arguments to make the uninstaller not show any GUI
$validExitCodes = @(0) #Valid return codes from the uninstaller for success

$shouldUninstall = $true; #We should uninstall if we detect no errors. 
#Keys where our uninstall data is stored in registry
$local_key       = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$local_key6432   = "HKCU:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$machine_key     = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$machine_key6432 = "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"

#Try each key. The first to return a valid path, and key get the UninstallString value from it. 
$file = @($local_key, $local_key6432, $machine_key, $machine_key6432) `
    | ?{ Test-Path $_ } `
    | Get-ItemProperty `
    | Select-Object -ExpandProperty UninstallString

#If we don't have a valid uninstall executable, then error and don't run uninstall. 
if ($file -eq $null -or $file -eq '') {
    Write-Host "$packageName has already been uninstalled by other means."
    $shouldUninstall = $false
#If we are still uninstalling then call chocolatey uninstall package commandlet to run our uninstaller
if ($shouldUninstall) {
 Uninstall-ChocolateyPackage -PackageName $packageName -FileType $installerType -SilentArgs $silentArgs -validExitCodes $validExitCodes -File $file

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Automise (Install) 47 Tuesday, May 3, 2022 Approved
Automise (Install) 71 Monday, January 24, 2022 Approved
Automise (Install) 54 Tuesday, November 23, 2021 Approved
Automise (Install) 57 Thursday, September 9, 2021 Approved
Automise (Install) 67 Monday, July 5, 2021 Approved
Automise (Install) 77 Monday, April 12, 2021 Approved
Automise (Install) 92 Friday, January 29, 2021 Approved
Automise (Install) 104 Monday, December 7, 2020 Approved
Automise (Install) 75 Wednesday, November 4, 2020 Approved
Automise (Install) 98 Wednesday, September 30, 2020 Approved
Automise (Install) 111 Thursday, August 27, 2020 Approved
Automise (Install) 119 Tuesday, August 25, 2020 Approved
Automise (Install) 121 Tuesday, July 21, 2020 Approved
Automise (Install) 80 Tuesday, July 14, 2020 Approved
Automise (Install) 109 Wednesday, May 27, 2020 Approved
Automise (Install) 140 Wednesday, April 29, 2020 Approved
Automise (Install) 209 Tuesday, February 4, 2020 Approved
Automise (Install) 164 Friday, November 29, 2019 Approved
Automise (Install) 109 Friday, November 15, 2019 Approved
Automise (Install) 133 Tuesday, October 15, 2019 Approved
Automise (Install) 129 Tuesday, October 1, 2019 Approved
Automise (Install) 117 Tuesday, October 1, 2019 Approved
Automise (Install) 228 Monday, March 18, 2019 Approved
Automise (Install) 158 Thursday, February 28, 2019 Approved
Automise (Install) 154 Thursday, February 28, 2019 Approved
Automise (Install) 226 Tuesday, September 18, 2018 Approved
Automise (Install) 216 Wednesday, July 25, 2018 Approved
Automise (Install) 264 Thursday, May 17, 2018 Approved
Automise (Install) 388 Tuesday, November 21, 2017 Approved
Automise (Install) 373 Tuesday, September 5, 2017 Approved
Automise (Install) 331 Thursday, August 24, 2017 Approved
Automise (Install) 402 Monday, March 27, 2017 Approved
Automise (Install) 373 Thursday, March 23, 2017 Approved
Automise (Install) 354 Friday, March 3, 2017 Approved
Automise (Install) 364 Tuesday, February 14, 2017 Approved
Automise (Install) 415 Tuesday, September 13, 2016 Approved
Automise (Install) 417 Friday, August 19, 2016 Approved
Automise (Install) 427 Friday, July 29, 2016 Approved
Automise (Install) 378 Tuesday, March 29, 2016 Approved
Automise (Install) 330 Tuesday, March 29, 2016 Approved
Automise (Install) 394 Tuesday, March 29, 2016 Approved
Automise (Install) 369 Wednesday, February 3, 2016 Approved
Automise (Install) 378 Friday, January 29, 2016 Exempted
Automise (Install) 401 Friday, January 29, 2016 Approved

Release notes are located at Automise Version History

This package has no dependencies.

Discussion for the Automise (Install) Package

Ground Rules:

  • This discussion is only about Automise (Install) and the Automise (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Automise (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus