Still having WinXP problems...

[rbanse]

I am still running into problems with installing the SH client over the network to XP users.  Forunately we only have 40 clients with XP, but I still need to get this figured out.  The problem I am having is in my previous post, just a couple posts below this one.  Thanks for any help.  

(We are purchasing SH for 750 clients, so I am looking forward to using this product.  From using the demo the past month, this product looks very cool.)

[Nish]

The problem is Firewall related. Can you get to the remote registry on the XP client? Open up regedit on the SH server (Start/Run/regedit), then File/Connect Network Registry, enter  in the machine name and hit enter.

Windows should now connect to the machine's registry.

It probably can't and hence systemhound is also failing to make a connection as well. You need to double-check you really haven't got the SP2 Firewall enabled, and double check that port 139 in the Firewall Exceptions tab, in File & Printer Sharing, is enabled.

[rbanse]

Well it must be something else besides the two things you mentioned, because I have checked that again, and the firewall is turned off, and the Port 139 is in the exception list.

[Nish]

if you cannot access the machine's registry remotely, then that is the problem. Can you see if the Remote Registry service is enabled on the machine in question (check in the Services in Contrl Panel)

[rbanse]

Yes, the remote registry service is started (set to start automatically as well)

[Nish]

Well, we've checked that the Firewall isn't running, and that the reg service hasn't been disabled - but the issue still remains that you cannot access the machine's registry remotely via regedit. This failure is what is preventing the remote installation of systemhound clients.

The only option is to install the client using systemhound.exe, manually at the machine. Choose the 'user machine' option.

Alternatively you can call client.exe (in the systemhound/utils folder on the systemhound server - you can put it on a network share) on the client machines: client.exe -install -host [systemhoundserver]

Both methods are manual installation.

[rbanse]

That's too bad I would have to do it manually, but thanks.

[Chriss]

Alternatively you can call client.exe (in the systemhound/utils folder on the systemhound server - you can put it on a network share) on the client machines: client.exe -install -host [systemhoundserver]

Both methods are manual installation.

We put this in our login scripts for our 40 domains, not much manual work anymore.