A new user asked if there was a way to limit the number of connections in the ControlUp Real Time Console that a given user can have to the client machines. The suggestion was to use the Solve console, which the user said might not offer the same ‘Incidents view’. However, the Audit Log from the Solve console can show all the triggers that were fired and actions ran, as well as limit the ‘Connect to Windows Machine’ permission. It was suggested to explain the resource constraints to the help desk team and rely on their own principles of self-control. There is no way to detect if too many connections are open, and the Security Policy is all or nothing.
Read the entire ‘Limiting the Number of Connections in ControlUp Real Time Console’ thread below:
Hello everyone! I’m new to ControlUp and wondering if there is a way to limit the number of connections in the Real Time Console a given user can have to the client machines? I’m concerned that if more than a couple of my help desk team opens up dozens of connections to the remote clients it will swamp my RDS server the console will be run from.
Just have them use the Solve console.
I was going to do that but want them to have access to the Incidents view. Is there a way to give them something like Incidents in Solve?
I’m not sure what you’re after in the incidents view but you can use the solve audit log for a lot of that.
I’m sorry, I’m lost since I’m new, can you explain how the Audit Log might replace Incidents?
You should be able to see all the triggers that were fired as well as all the actions that have been ran from the audit log.
taking a look in Solve now, I hope this fits the bill.
It’s just limited and our techs are solid.
If they are solid and you explain to them that they can’t connect to everything at once from the console due to resource constraints then hope they will understand and show a little self-control. 😉
But back to your question, no, nothing can limit what they connect to other than the security policy.
I was thinking the same thing. 🙂
And the security policy is all or nothing, right? There’s no way to limit.
Well, what I meant was the "Connect to Windows Machine" right. Without tat you can’t connect to the machine to gather data. No connections, no load from the console.
Gotcha. yeah, I was thinking I could disable connections if they leave a bunch of connections open and cause performance issues.
No way to detect that. You could do something like kill idle sessions or kill the ControlUpConsole.exe process if memory > X.
Thanks Landon this helped a great deal
If you create folders in console and put the servers in the folders, you can limit via Security Policy what the „helpdesk“-role can see and connect to, but I think that’s not helpful here?
I thought of that as well, but yeah correct. It’s not helpful here because we want them to connect to any of the work stations, just not more than a one or two help desk team members at once and then leave connections open.
Continue reading and comment on the thread ‘Limiting the Number of Connections in ControlUp Real Time Console’. Not a member? Join Here!
Categories: All Archives, ControlUp Real-Time DX, ControlUp Scripts & Triggers