XP SP2 - Remote Deployment (push)

[Nish]

With XP SP2 as the systemhound central server, the following applies:

If the Firewall is turned on (which by default it is) then port 4004 needs to be opened up on the SH server in order for systemhound clients to be able to report to it. If you upgrade to 4.0.5.0 (or latest systemhound download), it will automatically configure the port to be added to the Exceptions list. This will appear as 'systemhound collector' in the Exceptions list of the Firewall.

For systemhound clients on Win XP SP2: with a default install of SP2 with Firewall, install the clients normally using the Install Wizard as you do not need to change the firewall settings on client machines.

[Webmaster]

   1. When deploying within a Windows WORKGROUP rather than a DOMAIN network environment you must ensure that the target machines do not enforce Guest access from the network. This is enabled as a default on Windows XP PRO and Windows VISTA. http://support.microsoft.com/kb/290403
   2. The remote installation tool will need to access the remote machines file-system and remote management interface. Firewalls should be configured appropriately. http://support.microsoft.com/kb/840634
   3. The remote installation tool attempts to access the machine using the file share ADMIN$. This is not available on some 'home' operating systems such as Windows XP Home / Windows VISTA Home and an alternative deployment option should be used.