Deploying systemhound Client using Active Directory

From systemhoundwiki

1 How to deploy the systemhound client MSI installer via active directory

How to deploy the systemhound client MSI installer via active directory

The following steps can be followed to configure Microsoft Active Directory Group Policy to deploy the systemhound client to your pc estate. Before starting make sure you are logged in as an administrator.

The client install msi is deployed as a single file as part of the central server installation
into the folder systemhound\utils\LoginscriptInstallation.

[edit]

Creating an MSI administrative install

Create an Administrative Installation of the systemhound client msi by typing the following at the command line:

MSIEXEC.EXE /a "<Path>\systemhound-client.msi" CENTRALSERVERNAME=<systemhound Servername>

Where

<systemHound Servername> represents the name of your systemhound central server
<Path>                   represents the location of the “systemhound client.msi” file

This will launch the Administrative Installation wizard. Be sure to install the systemhound Client installation package to a network share capable of being accessed by all computers you wish to install the software onto. Once the administrative installation point is in place, you can assign or publish the application from Active Directory so that it is made available to your computers or users. The 'systemhound central server name' you provided on the command line will be stored within the administrative install - be sure that the computers that receive the software install will be able to perfrom a TCP/IP 'ping' against the server.

Tip: It is recommended that you create a dns entry for yout systemhound cental server rather than using the hostname in case you change the server name in the future.

[edit]

Configuring a group policy

The systemhound client must be assigned to Computers (and not Users) because it audits the PC and not the user. Using either 'Active Directory Users and Computers', or the 'Group Policy Management Console', edit the Group Policy that affects the computers you wish to make this software available to.

Select 'Computer Configuration' and double click 'Software Settings'
Next, in the console tree, right click Software Installation, and select New Package from the menu.

Select the MSI-package from the Administrative Installation you created earlier. In the Browse Box, enter the UNC path to the MSI file deployed earlier. You must only use UNC paths here, and never paths that include drive letters.

Choose a deployment option of 'assigned'

Exit the GPO management application

[edit]

Deployment

When your users reboot their machines systemhound will be installed whilst they log on. (Install time may vary depending on network speed and traffic).

Once the user has logged on, the client install will complete and the machine will report to the systemhound Server.

[edit]

Administrative Rights

systemhound client installs a windows service and therefore requires administrative rights during the install. If the user performing the install does not have administration rights to their pc the following FAQ may be of assistance to you : How To Allow Users Who Are Not Administrators to Install MSI Packages

[edit]