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:
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.
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.
Your 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.
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 = 184.108.40.206
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.
Here are standard steps to publishing System Mechanic via Group Policy using your newly created .zap file:
After following the steps above, System Mechanic should be displayed as a published application.