It's also a shortcut in the server start menu, but this batch file is available on most Horizon machines. The aforementioned support.bat batch file can also generate a log bundle on your connection server. When you investigate problems with Horizon not creating virtual machines, such messages can help you find the root cause of the problem. The Horizon Connection Server LogsĪ debug message outlined in red in Figure 5 refers to a data store that is 36.25% full. You can modify this logging level with a menu option in the start menu on the connection server (Figure 3). By default, the connection servers only log informational messages. VMware Horizon connection server logsĮach connection server's log files live at C:\ProgramData\VMware\VDM\logs. VMware Horizon log files are available on each of the machines in the environment, including clients, agents and servers. VMware administrators have a useful central resource that allows you to find all log files for VMware products and services. However, log files are sometimes in unexpected locations, and it may be hard to find them. For Linux, in /var/log it lives either directly in that folder or a subdirectory for your application. For Windows, that is in c:\programdata in a folder for your application. You can find log files in the most common locations for the given operating system. VMware log file locationsĪll VMware products store log files on the individual machines and without centralized logging, you can always access them in those locations. While this is not feasible for all VMware admins due to various factors such as licensing, it's certainly worth considering this automation.
If you use VMware vRealize Log Insight, you can set the environment to trigger an alert when Horizon receives certain log entries. In this example, the log entry would not contain information about the root case, but that's the benefit of the more detailed troubleshooting logs.Ī benefit of accessing the logs over the event database records is that you can send those logs to a centralized logging server. Therefore, the machine couldn't contact the domain controller. In this case, the reason for the customization error is that the machine was not able to obtain an IP address.
0 kommentar(er)
