Install LiteSpeed on Remote Server Instances
You can install LiteSpeed on multiple remote server instances using the Remote Deploy Configuration wizard.
NOTES:
- Before you run the Remote Deploy Configuration wizard, you must run Complete installation on the machine from which you wish to run the remote deploy.
- Make sure you have a Windows domain user account with Administrator rights for the server instances you want to install LiteSpeed on. The machines must be part of the same domain.
To create and deploy installation files
-
Click the Application Button and select Remote Deploy...
-
On the Remote Deploy Task page, select one of the following tasks:
- Generate Remote Deploy configuration file—To create the installation files and optionally deploy them. If you select the Complete or Core Components Only installation and deploy the files, this will also configure remote server instances.
- Edit existing Remote Deploy configuration files—To edit configuration files generated by the Generate Remote Deploy configuration file task. Use to deploy to many servers that all use the same parameters without having to input all the information every time.
- Deploy existing Remote Deploy configuration files—To deploy the installation and configuration files generated by the Generate Remote Deploy configuration file task.
- Configure LiteSpeed using existing Remote Deploy configuration files—To configure remote server instances. You can use this task to complete installation after you deployed LiteSpeed using a deployment tool such as SCCM or LANDesk.
- Validate existing Remote Deploy configuration files—To see if the configuration files are valid for installation and review installation options and expected actions.
NOTE: To deploy or validate existing Remote Deploy configuration files, you only need to select the main configuration file (usually, LiteSpeedRemoteDeploy_Configuration.xml). The wizard will automatically validate all remaining server-specific configuration files.
-
If you selected the Generate Remote Deploy configuration file task, review the following for additional information:
-
Select one of the following installation types:
- Complete—Installs LiteSpeed for SQL Server, LiteSpeed UI Console, and statistics agent (if you configured LiteSpeed to collect statistics).
- Core Components Only—Installs LiteSpeed for SQL Server and statistics agent (if you configured LiteSpeed to collect statistics), but not the LiteSpeed UI Console
- Client Only—Installs the LiteSpeed UI Console only.
- Statistic Agent Only—Installs/updates the service that transfers information between local and central repositories.
- If the current user account has Windows administrative rights but does not have access to the server instances, select Use a different account for installation to specify an additional account.
-
Select the SQL Server instances on which to install LiteSpeed. Start by clicking the Refresh button to see all the machines found on the network. Select servers in the Servers drop-down list, confirm selection and click Add. If you prefer to add servers manually, enter server names separated by commas in the Servers field and click Add. Alternately, you can import servers from a text file (one server name or IP address per line).
Use the following information to help guide you through instance configuration:
Page Description
Service Account Specify login information for the LiteSpeed Activity Manager service. This service runs on each server and merges statistics from the LiteSpeed local repositories to the central repository database. Typically the account is a Windows domain account. It must have permissions to update the central repository database using Windows authentication (for a cluster configuration, the Windows account must have permissions on all nodes). For more information, see Privilege and Grant Requirements.
NOTE:
- You should select Local system when the central repository is on the same server as the local repository. If the central repository is on another server, the Activity Service will not be able to use Windows authentication to access it. You will need to provide SQL Server login and password on the Central Repository screen.
SQL Servers Select the SQL Server instances on which to install LiteSpeed.
The State column indicates the state of SQL Server instances. To check the state of selected instances click Check Instance State. To update the state, right click on the instance and click Update State.
For all selected instances not in the running state, on clicking Next LiteSpeed will issue a warning as installation on a stopped instance will result in failure.
Installation Directory
Select the installation directory for each SQL Server that LiteSpeed will be installed on.
LiteSpeed will validate the install path for each server before proceeding further.
Install Path State More information The specified path is invalid. This warning may mean any of the following:
- Cannot check folder state.
- Not enough free disk space is available.
- The disk type is not valid for installation.
- The specified path is too long.
- The specified path is not available.
- Disk does not exist.
- Folder does not exist.
Local Repository LiteSpeed uses the login details you specify to connect to the server instance, create the database, and add objects to it. This account must have the appropriate permissions.
Native Backup Activity Select whether you want to update the local repository with information about native SQL Server backup activity and view it in the LiteSpeed UI Console. Click Schedule to modify the default schedule.
Central Repository Point to the server instance and database.
Create and upgrade a Central Repository database. LiteSpeed creates the database if it does not already exist. It checks the version and upgrades if necessary.
Repository Update Indicate when you want the central repository to be updated with backup and job statistics. You can have LiteSpeed update the central repository:
- Automatically after any LiteSpeed activity, such as after every backup/restore operation (best for real time statistics).
- Via a scheduled SQL Server job (best for minimal network traffic).
- Manually.
NOTE: Quest Software recommends that you select Automatically after any LiteSpeed activity for both selections.
Repository Cleanup Select to set repository maintenance, including when to delete old data from repositories, and how much of that data to delete. Old data can be deleted from the local repository, central repository, or both. The repositories are individually selected to remove activity older than a user-selectable number of days, weeks, months, or years. Additionally, Edit Schedule launches a screen where schedule information can be changed.
Tip: Further repository cleanup can be accomplished by using the Purge Repository Data procedure.
Proxy settings Select Use proxy settings for cloud connections. When selected, you can add the proxy address and port. Optionally, you can select to use authentication and then enter username and password.
License I you select Register later, the installed LiteSpeed version will operate as a trial on all instances, until you register it or the trial period expires.
Summary Displays a summary of instance configuration selections.
- On the License page, if you select Register later, the installed LiteSpeed version will operate as a trial on all instances, until you register it or the trial period expires.
-
-
On the Deploy LiteSpeed page, select whether you want to deploy the files immediately or run the wizard later and select the appropriate option.
TIP: On the Deploy Status tab you can check for errors during deployment. If errors are found you are given the opportunity on this tab to select to save the list of failed servers to a configuration file.
Caution: The Remote Configuration wizard does not prevent you from deploying the files if they are not valid.
NOTE: The Simultaneous installs field determines how many servers to install simultaneously. For example, if you select to install LiteSpeed on 50 servers and specify 10 simultaneous installs, then the wizard would install LiteSpeed on 10 servers at a time until it has installed all 50 servers.
- Complete the wizard.
