It was actually via a bat file (was trying to replicate the setup). It also does same thing on my windows 7 laptop. Get the 'XDClientName has stopped working' box with options to check online for solution or to close the program. After I close that box, the expected error shows in the cmd window. But regardless...just my observations. There has got to be a better way to get this info from the server via kix alone. Im not familiar with xen, but would the old wtsmanager work in that environment?

http://kixhelp.com/wr/files/kixtart/wtsmanager.zip