Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

OpenSSH 3.7.1p1-1 install

DJB_1
Occasional Contributor

OpenSSH 3.7.1p1-1 install

I hope someone can help with a SPECIFIC solution.

I keep getting "The supplied logon credentials are invalid"

What I've done/tried so far:
System is server 2003 SP2 with all recent updates (Dec 2008).
The system is NOT a domain controller.
The system is NOT a member of any domain.
I've downloaded the cp005309.exe to a local folder on the system.
I've created a seperate user account for SIM admin = HPSIMADM. Password is 9 charecters (all lower, no numbers)
Made the HPSIMADM account a member of the administrators group.
loged in as HPSIMADM.
- install fails with above error (credentials invalid)
Logged in as Administrator and tried installing with HPSIMADM as the credentials
- install fails with above error (credentials invalid)
Logged in as administrator and used administrator as the credentials
- install fails with above error (credentials invalid)
reduced the HPSIMADM password to 8 characters
- install fails with above error (credentials invalid)
Logged on as HPSIMADM (with shorer password) and used HPSIMADM as the credentials
- install fails with above error (credentials invalid)
Reduced the administrator password to 8 characters and logged on as administrator, used administrator as the credientials
- install fails with above error (credentials invalid)
Deleted the HPSIMADM user profile (folders) and tried installing logged on as administrator using HPSIMADM credentials
- install fails with above error (credentials invalid)
tried entering server-name\HPSIMADM as the userid
- install fails with above error (credentials invalid)
Tried blanking the domain name out (using HPSIMADM)
- install fails with above error (credentials invalid)

Searched through the forum. several entries over 2 years old suggest password length, /domain switch (not valid here), loging on as the user, but no real solutions or diagnosis.
Is there a debug or verbose log switch to help identify the error location during the install?
Better still, is there a manual install process that avoids using the installer? (copy files, register dll's, create service, grant account privs. etc...)


Many thanks
Dave