administrative rights needed to run an application?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Upon executing the HP Install Network Print Wizard 3.04 software, my client
receives an informative message prompt stating the following:

Error. You must have operating system administrative rights to run this
application. Contact your system administrator for assistance.

I have confirmed that the end client does indeed have administrative rights
on the respective machine. The issue can be replicated on any machine he logs
onto. Alternate users with admin rights can log onto the same machines and
the software executes fine. The only workaround that I have found is to
upgrade to the 5.0 version of the software. No related information can be
found within the eventlogs. By the way, we are not enforcing software
restriction policy within our 2003 Domain or on the local group policy level.

Any idea what is causing this issue?
 
I had used procexp while logged on as the user and the access token handle
fails to initiate. If I logon with any other account with similar access
rights the access token handle is initiated for the respective application
process under the logged-on user context and the software launches
successfully. I have checked the ACLs for the computer and user object
within Active Directory and they seem fine. Also, I looked at the ACLs for
the main application directory for the respective software and the access
rights seem sufficient as well. Am I missing and ACL somehere? Thoughts?
 
I had used procexp while logged on as the user and the access token handle
fails to initiate.
Click to expand...

Do you mean that when you perform the steps, Process Explorer gives you
an error message, saying that it fails to initiate?
I have checked the ACLs for the computer and user object
within Active Directory and they seem fine.
Click to expand...

Have you put the user account in Domain Admins group (very dangerous
btw), or Administrators group in local workstations?
Am I missing and ACL somehere? Thoughts?
Click to expand...

It seems it has something to do with the account itself.
 
Small Potato said:
Do you mean that when you perform the steps, Process Explorer gives you
an error message, saying that it fails to initiate?


Have you put the user account in Domain Admins group (very dangerous
btw), or Administrators group in local workstations?


It seems it has something to do with the account itself.
Click to expand...
 
Procexp does not provide an error message. When I hightlight the respective
application process within procexp I do not see an access token handle entry
in the bottom window pane. For some reason the access token fails to get
created. Possibly an LSASS issue? Any idea how I can test the integrity of
the security sub-system to ensure that it is creating access tokens correctly?

I do not see the relevance of placing the user account in the Domain Admins
security group. The user account is part of the built-in local
administrators group on the machines at hand. I have confirmed that the user
account has admin privileges, thus why this issue is so confusing. The only
solution I have found is to upgrade the software.
 
Back
Top