The new feature for Live Remote Management, File Browser, is discussed in a Slack post. It is helping the user to collect logs and pass files between systems. However, the default deployment settings only allow restricted permissions for Admin accounts. To fully utilize the feature, a custom role with necessary permissions must be created. A link to a blog post discussing the future of DEX management and asking for feedback on the new addition is also shared.
Read the entire article here...
ControlUp Community Training & Support Archives
All training and support-related archives from inside the ControlUp Community on Slack.
Troubleshooting the Management Option for File and Registry Browsing on ControlUp Live Features
A user encountered an issue with the new live features on ControlUp, specifically with the management option for file and registry browsing. After troubleshooting, it appears to be a permissions issue and potentially a global feature flag. The user was advised to log with support for further assistance.
Read the entire article here...
Read the entire article here...
Finding Little to No Usage in ControlUp’s Delivery Groups
A user asked for suggestions on how to find groups with little or no usage in ControlUp. Another user suggested using Citrix monitor's list of unused applications as inspiration, and another suggested checking each group individually or finding a way to see trends for multiple groups at once. No solution was determined.
Read the entire article here...
Read the entire article here...
Understanding Permissions for ControlUp File Browser’s Admin Role
A team member asked about the permissions for the Admin role in the newly launched File Browser. The ControlUp team clarified that this is by design and is meant to protect customers from unauthorized access to sensitive files. They suggested creating a separate "Super Admin" role with all the necessary permissions for RRM. More information can be found at https://support.controlup.com/docs/file-browser#permissions
Read the entire article here...
Read the entire article here...
Issues with Dashboard Permissions
There is an issue with Dashboard permissions - Editor role functions as intended, but Viewer role lacks necessary permissions to view data in dashboards. No unexpected permissions in either role. Support ticket may need to be opened to investigate further and collect a HAR file for DEX login process.
Read the entire article here...
Read the entire article here...
Troubleshooting Device Details Error in ControlUp Endpoints
There was a discussion about an error message popping up when opening details for a specific device in Physical Endpoints/Dex portal. Support was contacted and a workaround for this issue has been found. A status update was provided and it was suggested to contact support. The maintenance was completed, but some users are still experiencing the error. The fix should be applied shortly, and logging out of SAML and logging back in is suggested to resolve the issue.
Read the entire article here...
Read the entire article here...
Assigning Multiple Triggers for a Script in ControlUp
A question was asked about assigning multiple triggers to one script. The solution was found to use Workflows or admin can directly do it in Devices.
Read the entire article here...
Read the entire article here...
Using Workflows to Improve WIFI Monitoring on ControlUp
A member asked if it was possible to use the number of samples as a filter when monitoring WIFI signal strength. Another member suggested using a NOT filter on the Wifi Name or using an AND filter to only show desired WiFi information. The issue was that there were over 2000 WIFI AP's and the member wanted to track which ones were delivering subpar performance to endpoints. It was suggested to use workflows to achieve this, and an offer was made to help set it up.
Read the entire article here...
Read the entire article here...
ControlUp Edge DX – SIP Agent Installation and Upgrades
Users discuss if it is okay to install the 'ControlUp Edge DX - SIP Agent' on the monitor servers to see the same type of data as endpoints. It is recommended to have the cu4vdi agent installed on the monitor servers for a fuller picture of the environment. Also, it is possible to upgrade existing clients to a newer version using the PowerShell module. The two different agents, sipagent and cuagent, are discussed and it is noted that detailed metrics can be found in the VDI tab. A call can be set up to answer any further questions.
Read the entire article here...
Read the entire article here...
Security concerns regarding ControlUp for Compliance
A user encountered an issue where C:\Program Files\ControlUp\Cu4Compliance\cu4csvc.exe was being blocked by an ASR rule. They suggested that this be added to the documentation on the support site and a discussion about this update will happen internally. Two key locations for CU4C functionality are C:\Program Files\ControlUp\CU4C and C:\ProgramData\ControlUp\CU4C. To further address security concerns, a user is referred to a relevant Knowledge Base article.
Read the entire article here...
Read the entire article here...
