Deployment Details for System Mechanic 14.6 for Small and Medium Businesses
Domain administrators, here are the deployment details for distributing System Mechanic for Small and Medium Businesses (SMB) version 14.6 on your business’s domain.
This article is divided into three sections:
- Command Line Interface (CLI) Arguments
- Recommended CLI Argument
- Sample ZAP Deployment
1. CLI Arguments
A number of CLI arguments exist for the installation of System Mechanic. These may be used with whatever manner of deployment you elect for your environment. The recommended arguments appear highlighted.
- Renders the installation silent, excluding Progress and Messaging
- Used in conjuction with “/Silent”, hides Progress
- Generally used in conjunction with “/Silent” and “/VerySilent”, suppresses Messaging to the user
- /GROUP="<folder name>"
- Determines the name of the Start Menu group
- Defines a non-default Install Path
- Append the activation key after the “=” exactly as it is received
- Append the email address associated with your activation key
- Skips installing the gadget file
- Delays gadget install until after reboot
- Delays jump list creation until after reboot
- If Silent/VerySilent arguments are used, this argument will bypass them in ensuring that the desktop icon is forced to create
- Overrides the default connection type (e.g. PPOE, Broadband, Dialup)
- 0 = Broadband
- 1 = PPOE
- 2 = Dial Up
2. Recommended CLI Argument
Sample (recommended) usage:
SystemMechanic.exe /Silent /VerySilent /SUPPRESSMSGBOXES /ACTIVATIONKEY="activationkeygoeshere" /ACTIVATIONEMAILfirstname.lastname@example.org
3. Sample ZAP Deployment
The following general procedure may be used for ZAP installation of a non-Microsoft Installer package.
In order to successfully deploy an installation, first ensure that you have set up Group Policy to distribute to any eligible users from a known share location on your deployment server.
Group Policy recognizes .zap files, and will distribute System Mechanic via this method.
Note: This is a general instruction set that would have to be customized to conform to your active directory Group Policy setup.
For more information on .zap publishing see: https://support.microsoft.com/en-us/kb/231747.
a. Creating the .zap File
The .zap file is a text file with a renamed extension so that it will be recognized by Group Policy.
FriendlyName and SetupCommand are the only two required entries; all else are optional.
FriendlyName is the name of the program
SetupCommand is the command line used to run SystemMechanic.exe setup with required switches
Here is a template for your use. Copy and paste this into a text file, renaming to a .zap file (with a name of your choice). Make sure that its file extension changes, rather than creating a “.zap.txt” file.
The highlighted areas should be modified in your final .zap file to suit your environment:
FriendlyName = "System Mechanic SMB"
SetupCommand = "\\server\share\SystemMechanic.exe" /Silent /VerySilent /SUPPRESSMSGBOXES /ACTIVATIONKEY="activationkeygoeshere" /ACTIVATIONEMAIL="email@example.com"
DisplayVersion = 18.104.22.168
Publisher = iolo Technologies, LLC
Modifying the Highlighted Areas
As noted, there are three highlighted text regions in SetupCommand that should be substituted in your install environment:
The first, \\server\share\ in the template above, should be the fully qualified path to where you’ve stored SystemMechanic.exe on your deployment server.
The second, activationkeygoeshere, should contain your System Mechanic license for SMB.
The third, firstname.lastname@example.org, should be replaced with the email associated with your System Mechanic license.
Once you’ve saved your .zap file, you should be ready to proceed to publishing.
b. Publishing SMB via Group Policy
Here are standard steps to publishing System Mechanic via Group Policy using your newly created .zap file:
- Start the Group Policy editor and open a Group Policy
- Select the User Configuration branch
- Expand Software Settings
- Right-click on Software installation and select New – Package
- Select the File type “ZAW Down-level application packages (*.zap)” and selected the .zap file created previously in this deployment. Click Open
- Select Published from the deployment method and click OK
After following the steps above, System Mechanic should be displayed as a published application.
c. Installing Published ApplicationsYour users can install applications distributed via publication by accessing Add or Remove Programs from the Microsoft Control Panel. Within, they should select the option to Add Programs (or Install a program from the network). System Mechanic should appear in the list of available software to install.