Deploying via MSI to remote locations

[netwise]

I'm aware that SystemHound can be pushed out or run from a login script, which works great.  I'm also aware that remote sites can update through the Internet via port 4004.  What I don't have is a simple way to update remote clients with the software in the first place.  It would seem that I have two options, both involve hosting a file on our web server, which is fine:

1) Use WinZip SelfExtractor or similar program to 'package' the "client.exe" file and then transparently run the command "client.exe -install -quiet -host <hostname>".  This method means you need to own said software though.

2) Use an MSI packaging utility to make an MSI package.  This option is mostly free.

The question I have, is that the MSI capturing will find the SystemHound unique ID, and thus package that.  Obviously, this ID can be excluded, but will SystemHound generate it automatically if not found?

We have a number of small outside locations that need to be updated and have VPN's installed and SystemHound would greatly help us determine which sites these are, how out of date their software, etc.

Thanks for your time!

[barrygreen]

systemhound generates a unique GUID for each machine which sends its data back to the systemhound server.

[Dee]

systemhound will regenerate the id so please don't include it within within your package.

To capture the minimum files needed: install the client using the wrong host name using the standard installer (not client.exe). That way the client will never contact the server and download its plugins etc. Then within you're new MSI package change the host name to the correct one and check the unique id has not be created within the registry.

Let us know how you get  on !

D