Service Manager

Installing a Gateway from the Command Line

The Service Manager gateway can be installed on Windows 7 and later operating systems. See Working with Gateways and Standard Gateway System Prerequisites for other requirements for the gateway computer.

You can specify a default organizational unit to associate with your gateway. Ensure that you have this information before you begin the installation. Once the gateway is installed and deployed any clients deployed by the gateway are associated with that organizational unit by default, although this can be changed later.

When you specify a default organizational unit during installation, ensure that the computer you are using to install the gateway does not already have a configuration item record in Service Manager.

After installation, the gateway runs the Discovery client to generate a unique client ID. A registration message is then sent to the Service Manager server.

When the registration message has been received and processed by the server, the gateway computer appears in the Gateway workspace.

Once the gateway is listed you can configure it and begin to audit machines, create records and upload the data. For information about configuration and setting up the gateway, see Gateway Workspace Settings.

You must have domain administrator credentials to access Active Directory and to administer remote computers.

Installing the Standard Gateway

Do one of the following:

•Open the command prompt window and enter the following command:

msiexec/iTenant_URL/IM/GatewayInstaller/SaaSgateway_1.9.msi FRS_ACCESSKEY=Client_authentication_key FRS_SERVERBASE=Cloud_IM_web_service_base_address FRS_OUDefault_organizational_unit_name

•Download the MSI locally and install it by entering the following:

msiexec /i <\windows\temporary internet files>SaaSGateway_1.9.msi FRS_ACCESSKEY=Client_authentication_key FRS_SERVERBASE=Cloud_IM_web_service_base_addressFRS_OUDefault_organizational_unit_name

The ClientInstallation.msi and ClientInstallation.cmd files are downloaded by default to the HEAT Software > SaaSIM > ClientShare folder.

Installing the Data Center Gateway

Do one of the following:

•Open the command prompt window and enter the following command:

msiexec/iTenant_URL/IM/GatewayInstaller/SaaSgatewayDC_1.9.msi FRS_ACCESSKEY=Client_authentication_key FRS_SERVERBASE=HEAT_IM_web_service_base_address FRS_OUDefault_organizational_unit_name

•Download the MSI locally and install it by entering the following:

msiexec /i <\windows\temporary internet files>SaaSGatewayDC_1.9.msi FRS_ACCESSKEY=Client_authentication_key FRS_SERVERBASE=Cloud_IM_web_service_base_address FRS_OUDefault_organizational_unit_name

where:

•Tenant_URL is the URL for the Service Manager instance.

•Client_authentication_key is the unique key for every tenant; obtain this key from your Service Manager Administrator.

•Cloud_IM_web_service_base_address and SaaS_IM_web_service_base_address are the base portion of the address for the web service endpoint.

•Default_organizational_unit_name is the organizational unit to which the gateway is associated.

The ClientInstallation.msi and ClientInstallation.cmd files are downloaded by default to the HEAT Software > SaaSIM > ClientShare folder.

Installing the Client from a Command Line

When you install the gateway, the ClientInstallation.msi and ClientInstallation.cmd files containing the command line parameters are downloaded by default to the HEAT Software > SaaSIM > ClientShare folder.

To deploy the client agent to communicate with the Service Manager data center, run the following command:

MsiExec.exe /i "%temp%\ClientInstallation.msi" /qn /norestart CLNTCFGBASEURL="https://HEAT_IM_server" CLNTCFGCAK="Client_access_key" CLNTCFGDEFOU="Default_organizational_unit_name".

To deploy the client agent to communicate with another proxy server, modify and run the following command:

MsiExec.exe /i "%temp%\ClientInstallation.msi" /qn /norestart CLNTCFGBASEURL="http://Gateway_proxy_server:Port_number" CLNTCFGCAK="Client_access_key" CLNTCFGDEFOU="Default_organizational_unit_name"

To use a third-party proxy to install the client, you must point to this base address for connecting to the gateway data center edition and include the port number.

The protocol for the Discovery server is HTTPS, but the protocol for the local gateway proxy is HTTP.