A user asked for help on creating credentials for ControlUp to run scripts. They questioned if they were in the right place and what would happen if their profile was deleted. Someone suggested creating shared credentials in the Monitor settings and checking the permissions in the Security Policy.
Read the entire ‘How to Set Up Credentials for ControlUp Scripts’ thread below:
Good day everyone.
For the following article:
I’m at the part where I need to assign a service account that can query the ControlUp objects and run the script action. This is the first time I’d be creating credentials for ControlUp to do things by itself. Am I right to assume I have to create an AD user that has rights to the servers in my VDA pool, and that has something like help desk rights in ControlUp?
I’m also wondering if I am in the right place (Credentials Store) cause in the Add New credentials window it states the creds will be encrypted and saved in my Windows profile. What happens when I log off? Will ControlUp still process the users? What happens if my profile gets deleted from the machine where this was created?
Thank you.
So after more reading on your site, it seems it would be best if I create the shared credential in the Monitors settings? That way the credential information would be stored in the Monitor’s user’s profile?
Hey @member can you assist
Yup! Credentials need to be created in the Monitor settings and set as shared so the cmdlets can use them
To add further, you do need the credentials to be able to do the “logoff” action. Whatever group you assign the credentials to, you can verify they have the right permissions in the Security Policy at the bottom of the ControlUp Management Console or launch ControlUp under that account to verify
Continue reading and comment on the thread ‘How to Set Up Credentials for ControlUp Scripts’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers