Contributor
Contributor

End Point Agent issue - Insufficient privileges.

Jump to solution

I have been creating a small lab to test some things before we deploy vROps 6.6 into our Live environment.

I have installed the EPOps agent to some of our windows servers but i am reciving an issue that i can not pin down.

When the agent start it goes though the connection test and tries to register with vROps but comes up with "Unable to complete automatic agent setup. Insufficient privileges."

The account that i am using to install the agent is local admin

The account that i am using to authenticate to vROps is admin

SSL thumbprint is correct, tested by changing a character

Service is using Local system

DNS to vRops

I cannot work out what is causing a Insufficient privileges message. i have googled and searched the support site but cannot see anything that highlights what the issue is or how to remediate it

any ideas?

-- command prompt output --

C:\ep-agent\bin>ep-agent.bat start

Logs can be found at: C:\ep-agent\bin\..\log\agent.operations.log

wrapper  | Starting the End Point Operations Management Agent service...

wrapper  | End Point Operations Management Agent started.

[ Running agent setup ]

- The agent loaded an existing token

    1498820874491-2927026359934563913-4601639992058902881

Enter the server hostname or IP address: vrops.lab

Enter the server SSL port [default=443]: 443

- Testing secure connection ...

- Connection successful.

Enter your server username: admin

Enter your server password: **Not echoing value**

- Registering the agent with server.

Unable to complete automatic agent setup. Insufficient privileges.

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
Leadership
Leadership

That's because admin account do not have properly permissions, since that the Manage Agents permission is not assigned to any other role, including the Administrator role. So, if you want use the "admin" user, assign the Manage Agents permission, or create a new user just for End Point operations and assign the AgentManager role.

See the following VMware KB article for additional information: Configuring the End Point Agent for Operating System Monitoring (EPAgent, End Point Operations Manag...

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto

View solution in original post

0 Kudos
1 Reply
Leadership
Leadership

That's because admin account do not have properly permissions, since that the Manage Agents permission is not assigned to any other role, including the Administrator role. So, if you want use the "admin" user, assign the Manage Agents permission, or create a new user just for End Point operations and assign the AgentManager role.

See the following VMware KB article for additional information: Configuring the End Point Agent for Operating System Monitoring (EPAgent, End Point Operations Manag...

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto

View solution in original post

0 Kudos