CLIENT.EXE Problem

[Dannymagic]

Just wondered if anybody could help me

The company I work for has had Systemhound for over 3 years (we have a support contract and are on the latest version) and we have been installing the Systemhound client on machines utilising the CLIENT.EXE file from Login Scripts. 

Everything has been working fine until very recently when I've noticed that the CLIENT.EXE keeps reporting:-

Unable to install systemhound! You must be logged in with Administration rights to install the software.

Systemhound is consequently not installing on machines.  I've run the file manually and still get the same error.

Users are logging into a Domain, they are Admins of their machines, I've logged into machines with full Domain Admin Permissions and I get the same message. This occurs on 2000 and XP machines

The funny thing is, if i log into machines as Local Administrator and run the CLIENT.EXE file it works fine both via login script and manually, without the Administration rights error.

To compound matters, in XP, if i run CLIENT.EXE in Compatibility mode for Win95 / Win98 then it seems to work fine too.

I haven't a clue what the problem could be as nothing has changed on our network, the machines have all the correct admin permissions and for the life of me i can't understand why all of a sudden these problems should have started happening.

If i use the Remote Deployment tool from the Systemhound Server then it installs fine on machines, the problem is purely and simply the CLIENT.EXE file 

I'm tearing my hair out as to what the problem could be so if anybody has any ideas then it would be greatly appreciated!!!

Many Thanks!!!
Danny

[mohamoha]

I have experienced the exact same problem. And i believe I've found out where the problem lies.

I install using a login script in a Win2003 domain.

A user was to have a new Stationary Computer as well as a Laptop for home use.

A couple of days later I suddenly noticed that none of the 2 had reported in to the Systemhound server.

First I couldn't see a system in when client.exe installed and when it failed.


I tried to run the Client.exe from the command line with the user (local administrator) logged in.

It didn't work - I became the message:

"Unable to install systemhound! You must be logged in with Administration rights to install the software."


I then tried the same using my own account (domain admin) and the result was the same.

I then asked a user (local administrator) sitting in the same office to log on the computer (knowing her computer had reported in).

This did the trick - the login script installed client.exe.


I then went back to my office and comparred the 2 domain users. I then noticed that the one user who couldn't run Client.exe was member of twice as many Security Groups and Distribution Lists.

Then I started removing the user from Security Groups/Distribution Groups one by one - thinking something was wrong with one of them (don't know what).

When I removed the user from a distribution list it suddenly worked.

I checked to see if this particular distribution group in some way had something to do with the problem.

It hadn't.... Not directly anyway


But what I found out was that users that are member of too many Security Groups/Distribution Groups get the:

"Unable to install systemhound! You must be logged in with Administration rights to install the software."

It seems to me that there is some kind of memory problem with the Client.exe that causes the user rights not to be read.

[Webmaster]

systemhound support have a new version of the client.exe which fixes this problem.

email support@systemhound.com requesting a copy of the client.exe that fixes the 'not a administrator' error

Regards

Dee