Can I Package the SH Client into an MSI?

[ERA]

Hi,

I would like to package the system hound client into an MSI file. Using Wise Studio I did do this successfully. However the capture pick up the the "machine_id" and "machine_id2" registry keys. Therefore every PC that has the MSI installed has the same "machine_id" and "machine_id2" registry keys which I believe would be a problem???. Is there a way round this or can you recommend any other way of deploying the clients via Group Policy.

Thanks,

Josche

[Dee]

You are correct regarding the machine_id(s) entries - these must not be duplicated between PCs.

I assume you are snapshoting the "Client install" part of the systemhound InstallShield installer? If you are then repeat the process with the pc not connected to the network - this will enable your install to be as small as possible. The machine id entries are created whenever the pc connects to the systemhound server - so they should not be included in your snapshot if the client couldn't connect to the server.

Let us know how it goes...

Dee

PS. To make sure you snapshot includes everything needed unistall systemhound and ensure the directory program files\systemhound is empty and the registry key HKEY_LOCAL_MACHINE\Software\systemhound is empty too.

[ERA]

Hi,

I am snapshoting the "client install" part of the systemhound installshield installer.

Instead of running another snapshot can I instead excluded the machineID registry entries from the existing capture to obtain the same results?

Thanks,

Josche

[ERA]

Never mind. I removed the entires from the original snapshot. Inturn new keys were created when the MSI was installed onto a new PC.

Thanks for your help.

[Dee]

That is fine too. You should make sure there is no "upload.dat" file within you snapshot also as this contains audit details to be sent to the server. The file is found under "program files\systemhound\logs" but has probably already been sent to the server by the time you finished the snapshot.

Regards,

D

[ERA]

Thanks I did already remove all the files in the log folder.

I also notice in the Program Files\systemhound folder the capture also captured the file "unutil.dll". However when I look at any of the systemhound client that were installed via the console this file does not exist. Can I safely remove this file from the capture?

[Dee]

No don't delete unutil.dll as it is used by the Installshield uninstall part of the software.

Cheers

D

[ERA]

However if I am packaging the software into an MSI file windows installer will be used to uninstall this software as opposed to install shield. So I would think this file is not required?

[Dee]

It really depends...

The unistall dll handles the stopping of the systemhound service on Windows 9x and also ensures the systemhound directory is deleted on uninstall (all OS's). If your snapshot understands the installation of a Windows service (and subsequent uninstall) then you don't need to worry about the Installshield uninstall we provide.

I guess just try it out. If the unstall for the installer you've written works for the operating systems you require then use it....

Dee

[Dee]

UPDATE: systemhound client MSI is now available for download