Multiple members had a discussion on how to create a workflow that would synchronize devices from an Entra ID dynamic group into ControlUp using tags. The matching issue is caused by Entra ID and ControlUp having different device identifiers. Various solutions were presented, such as using a custom query or the Split String node, and eventually a solution was found using the Get Custom Data node. Further details and a visual example can be seen in the discussion.
Read the entire article here...
DNS Related Training & Support Archives
DNS training and support-related archives from inside the ControlUp Community on Slack.
How to View CVAD Delivery Controller Information in ControlUp Real Time Console
A discussion took place about how to see what CVAD delivery controller a machine is registered to within the Real Time Console 9.2.0.622 - the "CVAD Broker Name" column can show the DNS hostname of the controller a machine is registered to, but this may be empty if the machine's registration state is Unregistered or Unknown. The column should show data when connected to the EUC environment where the machine is hosted, and the auto connect feature can also be used to see CVAD data and ControlUp data together. The discussion can be found on the ControlUp Slack channel.
Read the entire article here...
Read the entire article here...
Troubleshooting ControlUp Academy Registration Issues
A user had trouble registering for ControlUp Academy and reached out for support. Another user suggested lowering browser security settings or disabling DNS-ad blockers may help. It was also mentioned that using a personal computer outside of the corporate network allowed for successful registration. The Academy provides valuable webinars and training for potential use cases. General information can be found at https://cuacademy.controlup.com/
Read the entire article here...
Read the entire article here...
IGEL thin clients using port 44484 for trace routes in Edge DX
According to the source code, Edge DX uses traceroute or tracepath to perform trace routes, depending on which one exists. For IGEL devices, only tracepath seems to be available. The port used is random, but usually starts at 44444 and adds a varying modifier based on the version. It is possible that IGEL or the underlying OS uses a static offset. On 12/31, the security team noticed traffic on port 44484 from our IGEL thin clients, which may be caused by additional Network Latency targets set in Edge DX settings. To confirm, they will disable the targets and monitor the traffic.
Read the entire article here...
Read the entire article here...
Understanding the “Public DNS Name” Setting in ControlUp Monitor
A user asked for clarification on the purpose of "Public DNS Name" in the monitor settings. Another user explained that this parameter is used for deploying a monitor using powershell, particularly for monitors in Azure or AWS. A ControlUp support documentation link was provided for more information. This setting is used to specify the address on which the monitor exposes port 443 for outbound agent connections.
Read the entire article here...
Read the entire article here...
Issues with Two Monitors Cycling after Upgrading to 9.0.5
A user opened a ticket but also asked for help in the Slack channel. They are having issues with two monitors cycling through connecting, logging in, and disconnecting after upgrading to 9.0.5. They have tried to run a network test and send a log, but did not find any issues. A link to the support article on creating monitor logs with Log4net was provided. The log file path for version 9.0.5 was also shared.
Read the entire article here...
Read the entire article here...
Troubleshooting a New ControlUp Installation
Several ControlUp users discussed a new installation of ControlUp at a customer's location, specifically running into issues with Insights and containers not being started. Suggestions were made to try a manual install and to open a support ticket. Another user shared their positive experience with a different version of ControlUp. The issues were eventually resolved.
Read the entire article here...
Read the entire article here...
Pinging Google and its potential effects on network latency.
The group discusses pinging Google and other options for avoiding latency issues. Some are concerned about Google blacklisting companies for pinging too much, while others defend using ping as a useful feature but acknowledge the need to disable it in certain security situations. OpenDNS and Cloudflare are suggested as alternative options to avoid pinging Google. The group has a meeting with Cloudflare scheduled.
Read the entire article here...
Read the entire article here...
Troubleshooting the Built-In Synchronization Feature in ControlUp
A user encountered difficulties using the new Built-In Synchronization feature for ControlUp, specifically with custom mappings and instructions lacking examples. Other users provided helpful tips and guidance on how to properly use the feature, including the use of wildcards and setting the sync to a shorter interval. The discussion ended with the confirmation that the desired actions were accurately assigned.
Read the entire article here...
Read the entire article here...
ControlUp for Multiple Customers Without AD Trusts
A user is asking for help with setting up ControlUp for multiple customers without AD trusts. They have read an article about installing the ControlUP Monitor in the customer's domain and opening port 40706. The discussion includes clarification on DNS resolution and port 40706. The upcoming release of Real-Time DX v9 is mentioned as a solution for easier installation in the future, with the ability to deploy the Monitor in a DMZ and access it remotely. The user is advised to open a ticket for more instructions on assigning monitor templates. The discussion also mentions using extensions for vCenter, XenDesktop, Horizon, NetScalers, etc.
Read the entire article here...
Read the entire article here...