It is possible to run the ControlUp RealTime DX Console from another server other than the Monitor as long as it meets the requirements outlined in the Knowledge Base article https://support.controlup.com/docs/communication-ports-used-by-controlup-hybrid-cloud-1. Having the Console on the Monitor server is not preferred as it can bog down resources and can lead to corrupted RAM databases which may cause alerts and automation not to fire. It is best practice for users to open the Console on a dedicated machine and to use the DEX platform instead of Solve.
Read the entire article here...
ControlUp Solve
NEW ControlUp Edge DX, RealTime DX Updates!
We have updated our ControlUp Edge DX and RealTime DX solutions and added many great new scripts to help our customers solve problems and create really happy end-users!
Read the entire article here...
Read the entire article here...
Excluding Machines from the On-Prem Console View in ControlUp
The user asked how to exclude machines from the Machines view in an on-premise console. Following a suggestion from another user, they need to remove permissions on hypervisor level for the service account being used. While this can be done at the cluster level, they wanted to suggest a filter in the Console to make it more practical. They will open a feature request for this. As a workaround, unchecking a box can be done. For more details refer to the article: https://support.controlup.com/docs/en/excluding-a-machine-hypervisors-from-the-monitor?highlight=exclude.
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...
Connecting to a SOP Server with Error Message Resolved in ControlUp
A user was trying to connect to a SOP server but was receiving an error message. Permissions were enabled for ControlUp admins, but the user was not able to resolve the problem. Solutions proposed included recreating the JWT and deploying a new appliance, and the latter worked. A detailed explanation on generating a new JWT could be found in the Support documentation.
Read the entire article here...
Read the entire article here...
Troubleshooting Video Latency on Non-Persistent VM with ControlUp
A user asked about troubleshooting video latency on a non-persistent VM, and it was suggested to use User Session Details in Solve as the best starting point. If Remote DX was installed, they can also watch session relevant latency, CPU, RAM and other metrics in a single place. Script Action can be used for advanced data collection. The Network Latency graph may be legit, but there was a known issue with the Linux RDX plugin. A new beta version which fixes this issue will be available soon. After sifting through the data, 3.75GB of RAM usage was found - they will look at adjusting graphics settings with Horizon View.
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...
Tracking Unused Desktop Pools in Solve with ControlUp
A user asked about tracking unused desktop pools in Solve - ControlUp offers a Session Count report which tracks usage over time and allows the user to look back for up to a year. The report provides quick insight into usage of Desktop Pools. An additional option is to setup a trigger to log users off after a set time of inactivity.
Read the entire article here...
Read the entire article here...
Troubleshooting Analyze Logon Duration “Gap” Time with FSLogix Integration
Members discussed troubleshooting Analyze Logon Duration "Gap" time using product version 8.8 and FSLogix integration. It was suggested to use the 'Disk Mount Time' column in the console to look for any patterns among machines and certain file shares. Isolating the user to one server and running procmon with the ALD script could help narrow down 'the needle in the haystack'. This could reduce lines of code to a few 100k.
Read the entire article here...
Read the entire article here...
Error “The target folder does not exist” Under EUC Environment in ControlUp
A user had an issue with setting a trigger for a target folder in a delivery group under the EUC Environment - the EUC was connected and visible, but saving the trigger returned the error that the target folder doesn't exist. After troubleshooting with other members, closing the console and removing the ControlUp profile from Roaming App Data was suggested as a solution.
Read the entire article here...
Read the entire article here...