(imported topic written by E86C_Faraz_Mirza)
Hello Guys,
Can anyone tell me is there a need to use Administrator account to install TEM agent or any account with Administrator rights? Because I am not able to install agent using e.g Test Account with Administrator rights.
Thanks,
Faraz Mirza
(imported comment written by SystemAdmin)
I routinely install the TEM Agent using my account. I’m a member of a Domain Group that is a member of the Local Administrators group.
(imported comment written by jfschafer)
Yes. You would need to install with admin rights. Can you explain which agent (OS) you are installing and what errors you get?
(imported comment written by E86C_Faraz_Mirza)
Hello,
I am trying to install agent on Windows 7 Professional.
Attached is the screenshot of the error and how I am giving admin rights to user to install agent using that user.
Thanks,
Faraz Mirza
(imported comment written by E86C_Faraz_Mirza)
before it was giving the error in mentioned in last message and after I restarted services, now it gives error of “Access is Denied”. See attached screenshot.
Thanks,
Faraz Mirza
(imported comment written by jfschafer)
When I’ve seen this error, it means the credentials you supplied in the GUI were not of a sufficient level to install software (administrative rights).
Is this machine in the domain or workgroup?
(imported comment written by jfschafer)
One more thing. Is the windows firewall on (try disabling) and deploy again? How About remote registry service running? (try starting that too if it isn’t and try again). I’ve had many remote software deployments not work if remote registry service is not running. (Don’t know if it’s required to deploy the BES agent remotely though, but it’s worth a shot to try)
Also I think maybe it requires a domain user account to deploy the client across network. The instructions on the GUI tool where you enter the username and password specifically says “Please enter a username and password for a DOMAIN account to be used for the installation”. Username would be domainname\faraz if faraz is part of a domain.
You could try computername\faraz as well if this workstation is not part of domain. Maybe that would work?
In the end if you can install the client manually on the system logged onto that account, then it’s got to be a problem with how you are authenticating across the network. I’m betting it’s the lack of computername\ or domainname\ before your username.
(imported comment written by jfschafer)
Wanted to add something about the errors:
The access denied error is soley due to not authenticating properly (ie, wrong password or not specifying domainname\username in the user name field
The no network provider error means it can’t even communicate with machine (ie it’s off or firewall is blocking)
(imported comment written by E86C_Faraz_Mirza)
Hello,
I was testing client deployment on windows 7 with following settings and was getting error of “Access is denied”:
Machine is in workgroup
Firewall is already disabled
Remote registry service is running
Tested computername\username but it does not work
Then I tested installing agent on Windows 2003 Server machine with test user and it works.
I am still not able to identify why it behaves differently on different OS.
I have one more question if you can help:
I was installing TEM agents but client machines do not appear in TEM console after agent is installed. When I update client machine’s host file with server’s IP and FQDN, then it appears in console.
I need to know what is the right method of setting up host file or DNS entry so that client appears in console.
Thanks,
Faraz Mirza
(imported comment written by SystemAdmin)
As for needing to place the TEM Server in the local hosts file, it sounds like your TEM Server is not registered properly in your DNS environment.
From a workstation (without TEM Server being defined in the Local Hosts file) can you resolve the server name using NSLOOKUP from a CMD session? (I’m betting you can’t)
HOW to do this is a well beyond the scope of this forum, but you need to ensure that your TEM Server is registered with your networks DNS server.