Issue 65 in cassia: feature request or just info

[cas...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 65 by GrungeB...@gmail.com: feature request or just info
http://code.google.com/p/cassia/issues/detail?id=65

What steps will reproduce the problem?
1. VmWare View Environment
2. Install Client, Connect to Windows7 Session
3. Run Cassia, read value ITerminalServicesSession.ClientIPAddress

ITerminalServicesSession.ClientIPAddress is null.
of course this will work with windows RDP, but not with WmWare View.

To be honest i expected that result and i think vmware is probably not
handling the WTSClientAddress proper.

There isn't much info, but what i found was this:
http://communities.vmware.com/thread/201130

Thank you for all the wunderful work that has been done in cassia
Greets
Philipp

[cas...@googlecode.com]

Comment #1 on issue 65 by danports: feature request or just info
http://code.google.com/p/cassia/issues/detail?id=65

I'm not familiar with VMware, so I don't have a test setup I could use to
try to reproduce this issue. If you could step into the code with a
debugger and provide more details, like the return code and data provided
by WTSQuerySessionInformation, that would help.

[cas...@googlecode.com]

Comment #2 on issue 65 by GrungeB...@gmail.com: feature request or just info
http://code.google.com/p/cassia/issues/detail?id=65

Hi

I don't have any knowledge about VmWare View. We are working at a school
and plan to use VmWare View as replacement for fat clients (personal
computers). I coded a Client/Server App that is registering logins and
logouts of all users in a DB. I'm using Cassia to read the session values
in the client service.

I tried to get some information together, but I don't think this is much
help.
I believe the problem is, that VmWare View isn't setting the WTS values in
windows.

-value of clientAddress in GetClientIPAddress()::GetClientIPAddress():
clientAddress {Cassia.Impl.WTS_CLIENT_ADDRESS}
Cassia.Impl.WTS_CLIENT_ADDRESS
- AddressFamily 0 int
- Address {byte[20]} byte[]
[0] 0 byte
[1] 7 byte
[2] 0 byte
[3] 0 byte
[4] 1 byte
[5] 0 byte
[6] 0 byte
[7] 0 byte
[8] 0 byte
[9] 0 byte
[10] 0 byte
[11] 0 byte
[12] 0 byte
[13] 4 byte
[14] 0 byte
[15] 0 byte
[16] 0 byte
[17] 0 byte
[18] 0 byte
[19] 0 byte
forced into IPAddress: {0.0.1.0}

- registry entries from VmWare View.
i think the best way, to detect that we are on a vmware view machine, is to
check the registry for this keys:
[HKEY_CURRENT_USER\Volatile Environment]
"ViewClient_MAC_Address"="00-AF-09-66-E6-05"
"ViewClient_Machine_Name"="CP-PR-01"
"ViewClient_Type"="Windows"
"ViewClient_Broker_Remote_IP_Address"="192.168.1.151"
"ViewClient_Machine_Domain"="domain"
"ViewClient_TZID"="Europe/Italy"
"ViewClient_IP_Address"="192.168.1.151"
"ViewClient_Broker_DNS_Name"="viewconnection.domain"
"ViewClient_Windows_Timezone"="W. Europe Standard Time"
"ViewClient_LoggedOn_Username"="pr"
"ViewClient_Broker_Tunneled"="false"
"ViewClient_Broker_URL"="https://viewconnection.domain:443"
"ViewClient_LoggedOn_Domainname"="domain"
"ViewClient_Broker_UserName"="pr"
"ViewClient_Broker_DomainName"="domain"
"ViewClient_Protocol"="PCOIP"
-(address/names have been changed for security reason)-

All the best & Thanks
Philipp

[cas...@googlecode.com]

Updates:
Status: Invalid

Comment #3 on issue 65 by danports: feature request or just info
http://code.google.com/p/cassia/issues/detail?id=65

Yes, based on that info, it sounds like your diagnosis that this issue is a
VMware one is correct. Glad you were able to find another way to get the
information you needed.