Why has System Shield blocked a virus that I cannot find in the Threat Database?
The Antivirus Threat Detection Center is laser-focused 24/7 on the reception, processing and categorization of incoming new malware threats from around the globe. As novel malware threats arrive, sometimes by the dozens daily, new threat definitions are created and pushed out continuously to maintain maximum AV threat protection on customer PCs.
This critical process is iolo’s priority, and ensures that the very latest threat definitions are deployed to keep System Mechanic Pro and System Shield customers’ machines safe and free from new malware.
Secondary to this process is the updating of the Threat Database we provide for informational purposes. As such, a search of the Threat Database will not always result in as up-to-date a result as the threat definitions deployed to update the System Mechanic Pro product itself."
Installing additional System Mechanic Professional components after the initial installation
When you first install System Mechanic Professional, you can select one or more of its components to include in the installation. For any components that you did not initially include, you can install them at any time by running the installation wizard again.
· Obtain the latest version of System Mechanic Professional by clicking here.
· Start the System Mechanic Professional installation wizard by running the smpro_dm.exe download manager.
· On the first screen of the installation wizard, click Install System Mechanic Professional.
· Accept the license agreement and set the installation location.
· On the Select Components screen, select the check box next to each of the components you want to install:
· Search and Recover: Recovers deleted files, e-mail, music, photos, and more.
· DriveScrubber: Securely erases data from hard drives.
· System Shield: Protects against viruses, spyware, and other Internet threats.
· Note: Before installing the System Shield component, first uninstall any other antivirus software. Installing two different antivirus products can result in an inaccessible system.
· Continue to follow the on-screen instructions. The last screen of the installation wizard will indicate whether you need to restart your computer to complete the installation.
Using System Mechanic Business Distribution Builder
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.
· /Silent
· Renders the installation silent, excluding Progress and Messaging
· /VerySilent
· Used in conjuction with “/Silent”, hides Progress
· Generally used in conjunction with “/Silent” and “/VerySilent”, suppresses Messaging to the user
· Determines the name of the Start Menu group
· Defines a non-default Install Path
· /ACTIVATIONKEY=”<activationkey>”
· Append the activation key after the “=” exactly as it is received
· /ACTIVATIONEMAIL=”<activationemail>”
· Append the email address associated with your activation key
· /SkipGadget
· Skips installing the gadget file
· /DELAYGADGET
· Delays gadget install until after reboot
· /DELAYJUMPLIST
· Delays jump list creation until after reboot
· /InstallDesktopIconSilent
· If Silent/VerySilent arguments are used, this argument will bypass them in ensuring that the desktop icon is forced to create
· AltConnType=
· 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" /ACTIVATIONEMAIL=licensedemail@yourdomain.com
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
Template
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:
[Application]
FriendlyName = "System Mechanic SMB"
SetupCommand = "\\server\share\SystemMechanic.exe" /Silent /VerySilent /SUPPRESSMSGBOXES /ACTIVATIONKEY="activationkeygoeshere" /ACTIVATIONEMAIL="licensedemail@yourdomain.com"
DisplayVersion = 14.6.2.8
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, licensedemail@yourdomain.com, 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 Applications
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.
