Since deployment in this method doesn't allow for command line arguments, you'll either need to create a Transform file (.mst) or modify the installer file to include the Access Key.įollow these steps to deploy the installer: One limitation of this method is the requirement to include your Automox organization's Access Key to be included as a parameter. With a minor modification, the Automox Installer MSI can be deployed via Software Installation GPO. If it's already there, it will not take any further action. If it's not present it will download, install, and start the service. On startup, the script will check for the agent. Now that these values are set, you can assign the GPO to your target audience.Enter this into the "Script Parameters" box: -AccessKey your-access-key-goes-here Your Automox Access Key is needed in the script as a parameter.Browse to the script file and click Open.In the dialog box, click the PowerShell Scripts tab then click Add.From the right pane, double-click Startup.Create a new Group Policy Object (GPO) and add the script to your GPO under:Ĭomputer Configuration > Policies > Windows Settings > Scripts (StartupShutdown).You can use the SYSVOL directory or a network share that is accessible to your device. Store the script file in a location that is accessible to your target devices.Click here to download a copy of the script: Download Script.
You can use the following script to check for, download, and install the Automox Agent. Group Policy can be used deploy the Automox agent in two different ways: by deploying a PowerShell Startup Script, or by deploying the latest Automox MSI installer.
#INSTALL SPICEWORKS AGENT VIA GPO HOW TO#
These instructions describe how to bulk deploy the Automox agent using Windows Group Policy.