"Invalid account/password" when installi

[rbanse]

I downloaded the demo version of systemhound, installed the program on a Win2003 server, and now would like to install the program remotely on a client for testing purposes.  When I use the Install Wizard, I see the client name but when I have to logon to start the install it does not accept the domain admin account/pwd that I type in.  I have full admin rights on both machines.  Client machine is WinXP SP2 (firewall disabled).  The exact message I get on the server is as follows:

"Invalid account/password - No network provider accepted the given network path. (0x4b3) "

Any ideas? Thanks
Ryan

[Nish]

Assuming the machine is actually switched on, and you are logged in as domain admin, then try this below:

Installing clients using the Install Wizard will fail if the machine cannot be accessed remotely. This is usually to do with permissions issues in the registry.

You will need to do the following:

Go to the problem machine, open regedit and select following keys:

If the following keys don't exist please see http://support.microsoft.com/d­efault.aspx?kbid=314837  

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers

Ensure that the following groups have inherited permissions by right-click
the key and selecting permissions.  If the check boxes are not selectable
and are grayed out then the permissions are inherited.  If they are white
and selectable the click the advanced button and check the 'Inherit from
parent...' box.

(Machine Name)\Administrators - Full Control
CREATOR OWNER - Special Permissions = Full Control which applies to 'Subkeys
only'
Power Users - Read
SYSTEM - Full Control
(Machine Name)\Users - Read

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

Ensure the following groups do NOT have inherited permissions by
right-clicking the key and selecting permissions then click on the advanced
button and if checked uncheck the 'Inherit from parent...' box.  The
following permissions are granted on this key.

(Machine Name)\Administrators - Full Control
(Machine Name)\Backup Operators - Special Permissions = Read which applies to 'This key only'
LOCAL SERVICE - Read  

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
\AllowedPaths

Ensure the allowedpaths key is inheriting permissions by clicking the
'Inherit from parent...' box

Once the permissions are set, you should be able to install using the Install Wizard.

[rbanse]

I will try this, thanks.  So this probably means every single machine's registry permissions will need to be changed in order for this product to install the client.  That's not a good thing for us since we have 600+ machines on the network.  Is there anyway else you can install the client without using the Install Wizard?  We have used Microsoft SMS in the past and you can enter some commands in the logon script to install their client, is that possible with this product?

[rbanse]

I checked over those permissions on the client's registry, and everything was the way it should be. But it still doesn't work.  I guess I have a question... When you use the install wizard and you need to enter logon credentials for installing the client remotely, a box appears that says "Server: \\clientname\ipc$"    What I am wondering is what exactly is ipc$?  Shouldn't it be c$

[rbanse]

I tried a different machine, and it worked fine.  The machine it isn't working on is XP SP2, so that explains it.  It's weird but I do have the firewall turned off on this XP SP2 machine, but it still won't communicate with SH server.  We are thinking of purchasing this product so if you could answer my question from above when you got time that would be great.  The questions is, what other methods can I use to install the client? Can I insert commands into a logon script? Or what other ways are available?  Thanks for your time.

Ryan

[Nish]

Are you logged in to the domain you are installing to? Because if you are, then you should not be seeing a username/password pop-up. If you're installing to domain A, please ensure you're logged in as domain admin to domain A.

You should be using the format \\domain\hostname, if the pop-up appears.

[Nish]

re XP SP2: could you check something for me - even though the Firewall is off, can you go to the Exceptions tab in the Firewall, and see if File & Printer Sharing is checked? It should be, and also check that port 139 is checked (inside this setting)

You can use logon scripts, but that will require your end users to have admin privileges, if the script will be called to Win NT/2000/XP/2003 machines. There are other ways too, like manually installing using the systemhound.exe (choose 'user machine' option)

But the Install Wizard should work

[rbanse]

Yes, with Firewall turned off, File and Print sharing is still turned on in the exceptions tab, along with the port 139.  Just like you said they should be.  

As for installing clients, here's my problem with using the Install Wizard.  How am I going to know when a new PC gets placed on our network?  By using logon scripts, it will be automatic when someone signs onto the PC for the first time.  We won't have to worry about remembering to install system hound client, instead it will all get taken care of automatically through the logon script.

I have two more questions for you regarding this product.  What is the database based on? SQL?  Also, does the system do a purge every so often? Lets say a PC gets removed from the network, and placed somewhere else.  Will SH remove or update the settings/information it has on that PC?  Thanks for the help!

Ryan

[Nish]

You can certainly use the login script option, but your users would need admin privileges. The next version will include MSI capability so you won't have this issue any more.

Otherwise its a case of periodically installing new clients using the Install Wizard.

systemhound doesn't use a database like SQL - its a custom db using HTML and Javascript

Regarding purge, you use the Website Maintenance tool to delete machines. If a machine is ismply moving somewhere else on the network, you do not need to delete it; the machine still exists so no changes are required.

[rbanse]

Ok thanks, that helps make the decision to buy easier.  Any idea how I can install the client on WinXP SP2? That's the only thing holding us up making the purchase.

[Nish]

What happens if you try a manual install on this XP SP2 client? That is, using systemhound.exe and choosing the user machine option.

[rbanse]

If I install the client manually on the PC, it works just fine.