This user asked for advice on the issue of VM's becoming unreachable due to Horizon Agent issues, experiencing freezing applications and an inability to console or access the machine once it has reached this state. Causes such as port exhaustion and DNS issues were discussed, as well as suggestions on how to access the system and application log files, and to generate an OS crash dump. It was also suggested to review reassess the configuration and consult other Horizon tech communities. ControlUp historical data and the support article https://support.controlup.com/ docs/controlup-agent-temporary-mode-and-how-to-change-it?highlight=IsTemporary#what-is-the-fix-for-this-problem were also included.
Read the entire article here...
DNS Related Training & Support Archives
DNS training and support-related archives from inside the ControlUp Community on Slack.
Implementation Questions for ControlUp in Corporate and Isolated Environments
A user asked questions about implementing ControlUp in a corporate and isolated environment. The answers explained that Monitors and Data Collectors don't need to be in the same domain, credentials can be used even without trust relationship, and port 40705 needs to be added. Professional Services from ControlUp can be sought for resolving automation issues in an environment with extensive security policies.
Read the entire article here...
Read the entire article here...
Solving DNS Issues for Horizon View/VMware Horizon and Controlup Agents
This discussion focuses on a DNS issue experienced with Controlup agents communicating with the console and monitor. Possible solutions include using a logoff script to release the IP address, solving the DHCP scavenging issue, flushing the DNS, and setting permissions to only allow the DHCP server to update DNS records. VMware Horizon (previously Horizon View) was also mentioned.
Read the entire article here...
Read the entire article here...