Before you begin with the SysKit Shell installation, we recommend that you carefully perform all preparation steps by reading the Pre-Installation Requirements article.
Our application just needs to be installed on a single server, which will then be used for monitoring other servers in the farm.
To install the SysKit Shell, proceed with the following steps:
Download the newest release.
Unpack and run the SysKitShellSetup.exe. The wizard will guide you through the installation steps, click Next > to proceed.
Click I Accept the terms of the license agreement to accept the license and then click Next > to proceed.
Select the destination folder for the application installation files, e.g., C:\Program Files\SysKit\Shell. Click Next > to proceed.
You can change the folder name where the application shortcuts will be created and modify the availability option to install the SysKit Shell for All users or Only for the current user. Click Next > to proceed.
In this step you need to enter information about the Service Account that will be used for running the SysKit Shell Service. This account will be used to gather data from your server(s). Enter the custom user account in the following format: DOMAIN\USERNAME.
Click Next > to check and validate the credentials.
The installation wizard will unpack your files and you will be able to run the application from: Start > All Programs > SysKit Shell.
In the installation process, the SysKit Shell Setup will install and configure a new instance of SQL Server Express 2012 LocalDB (free of charge). This is the quickest option. We take care of the configuration.
Once the installation is completed, the SysKit Shell will start. If the application does not start automatically after installation, you can run it manually from: Start > All Programs > SysKit Shell.
Before you can explore the UI and run scripts, there is one more thing to do! You need to change the current user preference for the Windows PowerShell execution policy by running the command below. Note: Start the Windows PowerShell as the SysKit Shell service user.
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted -Force
This will let you load all configuration files and run all scripts. If you run an unsigned script that was downloaded from the Internet, you will be prompted for permission before it runs.
Most problems are related to SysKit Shell Service authentication against the Active Directory or the SQL Server instance. If you are experiencing problems with installation, please contact us. Our team will schedule a support call and help you install the SysKit Shell remotely.