A user asked if it was possible to specify the user security context when upgrading agents in ControlUpConsole, as they couldn’t use Domain Admins in their environment. It was suggested to add admin accounts to AD Connections and specify one per domain, and the credentials were stored in the user profile and used only for agent deployment and "agent control". This solution worked for the user.
Read the entire ‘Specifying User Security Context in ControlUpConsole’ thread below:
Is there a way specify the user security context when upgrading agents from the ControlUpConsole? In my environment static local admins are a thing of the past, including domain admins. There are specific accounts that always have local admin rights. The ControlUp service account is one of those. As it stands I can either manually elevate my admin permissions on every server to complete an agent upgrade or beg the security team to give me temporary domain-wide local admin access.
Add an admin account in AD connections and the console will use that account for agent deployment and monitor deployment.
If you have multiple domains you can actually specify one per domain.
My console has this field empty. What else does this touch? Can other users make use of these stored credentials?
Its stored in your profile and only used for agent deployment and “agent control”.
Thank you
This worked. Everyone is happy now. Thanks again!
It’s empty by default which means it takes the user account which is starting the Console if Iam not mistaken…
Continue reading and comment on the thread ‘How to specify the user security context when upgrading agents from the ControlUp Console? ‘. Not a member? Join Here!
Categories: All Archives