When the delivery group is in another datacenter, it may have its own ControlUp monitor which the EUC view only allows one site per EUC site. RT shows information but Solve does not. It is verified that the monitor is connected and available, but the user needs "cross site association" -- a setting to allow the monitors to share data between each other. Enabling this feature increases network utilization and has to be done manually. For more information, the user can see the Multi-Site Association Feature at https://support.controlup.com/docs/multi-site-association-feature.
Read the entire article here...
ControlUp Monitor Related Training & Support Archives
ControlUp Monitor training and support-related archives from inside the ControlUp Community on Slack.
Solving Issues with the ControlUp Monitors Role
A user was experiencing issues with their security policy graying out the ControlUp Monitors role, preventing access to agents. KB article on security best practises was suggested, along with adding the service account to an appropriate role. It was noted that 8.8 On-Prem was released, containing the bugfix, and that the user would be sent a download link. Release notes were also provided.
Read the entire article here...
Read the entire article here...
Admin Rights Required for Upgrading the ControlUp Monitor?
The user asked if administrative privileges were required to upgrade the monitor from the console on another VM, and if they were needed for the one-time upgrade from 8.6 to 8.7. It was clarified that the organization owner MUST be the first user to upgrade the Real-Time Console to version 8.8, but after that any user can upgrade to 8.8 with any admin rights; and the organization owner is only required for the initial upgrade from 8.6 to 8.7. A user can be added in "AD Connections" with admin rights to override the user used to upgrade the monitors.
Read the entire article here...
Read the entire article here...
Troubleshooting Monthly Trigger Scheduling with ControlUp Monitor Service Time Outs
A user was having trouble scheduling a trigger to run once a month, with the script running correctly when executed manually. After checking backend data and determining a support ticket was required, the team provided a Monitor log4net file and instructions for creating the log file. It was suggested to look into the trigger timings being in different time zones, and instructions were given for setting the Monitor service time outs. In the end it was discovered that the infrastructure servers had incorrect time zones, which caused the problem. ControlUp Monitor service time out was also optimized. The Monitor service should transition from 'started' to 'running' over time. The issue is now resolved.
Read the entire article here...
Read the entire article here...
Adding Computers from Different AD Forests with ControlUp Monitor
A user asked how to add a computer in a different AD forest using the ControlUp Monitor. The EUC-Sync script, which can add machines is available, but the DNS records must be recognized. Additionally, the AD Connection needs to be configured in ControlUp Monitor settings in the Domain Identities section, which is not tied to the user logged in to the console.
Read the entire article here...
Read the entire article here...
Investigating Logic Monitor Hack Fallout with ControlUp Endpoints Isolated
In response to the Logic Monitor Hack in a development Org, the endpoints NICs have been disconnected to isolate them from each other and the internet, which may last for a total of 5 days. To investigate potential fallout, the new DEX console has been accessed and some Scoutbees have been disabled. ControlUp Monitors will not be collecting data as all endpoints have been isolated. For edge dx devices, these will keep collecting data while offline, and will ship that out once they have connection.
Read the entire article here...
Read the entire article here...
Where are the Log File Located in ControlUp
To find the log files for one or more errors, users can install Script Based Actions (SBA) and run it against the cumonitor.exe process in the console, or deploy the monitor with the revised cumonitor.exe.log4net file. For more details, see https://www.controlup.com/script-library-posts/deploy-log4net-for-controlup-processes/ and https://support.controlup.com/docs/how-to-create-monitor-logs-with-log4net. For further assistance, users can contact ControlUp support.
Read the entire article here...
Read the entire article here...
Creating Scripts to Start or Stop Windows Services
A user asked about creating scripts to start or stop Windows Services. It wasn't working in SolVe and the user wanted to see if any examples can be shared. It was suggested to add an event log and see why it's failing in the ControlUp Monitor. A reference link (https://www.controlup.com/script-library-posts/start-stopped-services/) was provided.
Read the entire article here...
Read the entire article here...
Can the ControlUp Monitor Upload Time Be Adjusted?
The user asked if it was possible to adjust the monitor upload time, which was answered as being hard coded to 30 minutes with a delay of up to two hours. On-Premise versions are written to disk every 10 minutes while the cloud version is every 30 minutes. No possibility was available to adjust the interval.
Read the entire article here...
Read the entire article here...
Troubleshooting “Send Message To Horizon User” Script Error
The user was trying to run the “Send message to Horizon user” from the community script using a trigger but received an UAC error. Solutions such as disabling UAC from the Control Panel and making sure the Horizon pod was in the same ControlUp site as the agent machines were suggested. Additionally, the user had to generate Horizon creds on each Monitor server individually. The issue was eventually resolved.
Read the entire article here...
Read the entire article here...