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...
Physical Desktops Related Training & Support Archives
Physical Desktops training and support-related archives from inside the ControlUp Community on Slack.
Accessing Alerts in Edge DX
A member from ControlUp asked about role permission for accessing alerts within Edge DX. Another member replied with a helpful suggestion.
Read the entire article here...
Read the entire article here...
Troubleshooting Device Location Updates in Edge DX
A user reported that their device location does not always update in Edge DX, giving an example of their device showing work location after working from home for 18 hours. A suggestion was made to check if device's public IP is changing when switching locations and checking the status of location services on the device's OS. A link to documentation on device geolocation was also shared.
Read the entire article here...
Read the entire article here...
Using Enrich with VDI and DaaS: Edge DX licensing still required?
A user asked if Enrich is still connected to Edge DX licensing. They want to use Enrich 2.0 with their Jira instance to show machine information for their helpdesk, but they are using VDI and DaaS. Another user suggested reaching out to an Account Executive for assistance. The data being used is from physical endpoints.
Read the entire article here...
Read the entire article here...
Deploying EdgeDX Agent on Virtual Desktops and Checking Licensing – Tips from ControlUp Users
A user asked about deploying the EdgeDX agent to virtual desktops. Others confirmed that it is possible and shared tips for installation, including adding extra settings and checking licensing. The agent can also be installed on non-persistent machines. The licensing system for EdgeDX is per device, and current usage can be seen on the overview dashboard or in the maintenance section of the EdgeDX configuration settings. Links to helpful resources from ControlUp were also shared.
Read the entire article here...
Read the entire article here...
Creating Triggers in ControlUp for Outlook Inbox Monitoring
A user inquired about creating a trigger for Outlook Inbox on a server, and received a response suggesting the use of ControlUp to run a script using PowerShell and the Outlook COM Object. The script would then check and report the number of items in the Inbox. An example code was also provided. This solution was provided by Yoni and can be implemented through ControlUp.
Read the entire article here...
Read the entire article here...
High CPU Usage on macOS Sequoia from CoreAgent – ControlUp Community Discussion and Support
Multiple users reported experiencing high CPU usage on macOS Sequoia from /usr/local/com.controlup.edgedx.agent/Bin/CoreAgent. The issue has been observed on a variety of macOS versions, and restarting the device only temporarily resolves it. A ticket has been opened with CU support, and users are discussing the issue in the community. Some have seen similar issues with earlier agent versions, but it has since been fixed.
Read the entire article here...
Read the entire article here...
How to Disable Remote Shadow/Control in Edge DX?
A discussion on disabling remote shadow/control in Edge DX took place, with a user finding the necessary setting and another suggesting that device groups can be assigned. It was stated that only tags should be necessary for setting the limitation but the user found they must also use groups.
Read the entire article here...
Read the entire article here...
How to Remove Devices from EdgeDX Before Maintenance Fall Off Takes Effect
A user asked about removing devices from EdgeDX before the maintenance fall off, due to a hardware refresh causing devices to be listed twice. Others suggested using the register with name flag or selecting and removing the device, and an API endpoint for deleting devices was shared. Someone offered their powershell module and potential ways to track old device names. It was recommended to match on serial numbers.
Read the entire article here...
Read the entire article here...
Translating Trigger Values in ControlUp Scripts
A user asked about a key to translate the "trigger" values for scripts returned via the edgeDX API. Another user mentioned they have the information and will share it. The answer is found through the use of Github Copilot and AI.
Read the entire article here...
Read the entire article here...