XenApp Add-On and shared vDisk

[afinn]

I have the latest version of the XenApp application and the TA-XA65 add-on (server and broker) installed and working. I am able to collect data related to the XenApp Controllers without issue. I also have Session Hosts deployed via PVS which leverage a shared vDisk to host virtualized applications. There are three VM's that network boot to the same vDisk. I am able to collect data on the first server that boots up, however, the logs on the other two state that Splunk thinks they are the same servers as the initial one that boots. When I look at the Splunk console, I only see one session host listed and the Splunkd logs on all three session host have an computername entry for the first one that boots instead of the session host's actual name.

Are multiple session hosts booting from the same vDisk supported or will I need to wait for the PVS application to be released in order to collect performance data on those hosts?

Thanks in advance.

[jconger · Accepted solution]

You need change the Splunk services on the PVS XenApp servers to start manually instead of automatically. Then, you will need to use a startup script to set the Splunk universal forwarder host name to the XenApp server's hostname. The startup script runs after PVS has assigned the hostname and GUIDs, so each XenApp server will report its correct information to the Splunk indexer.

These steps are documented here:
http://docs.splunk.com/Documentation/XenApp/latest/DeployXenApp/Installtheuniversalforwarder#Using_a...

[afinn]

Awesome! I obviously did not RTFM close enough when going through the documentation. Thanks again!