Forum Discussion
NimbostratusAPM v13.0.0 Snat pool not getting set in the Vmware connection server for desktop
F5 APM v13.0.0 using VMWARE connection servers and virtual desktop. Using APM vmware IAPP.
Using SNAT pools also.
It seems in virtual desktop if you open up regedit ++ View_Client_remote_ipaddress isn't using the ip from the snat pool but the Self IP. The load balancing piece to the pool members is working correctly but not this piece. So is there a way we can control this on the F5 APM?
Brandon_12607This is pic from regedit fron the VDI. We are trying to control this from the APM. Currently it's using the Self IP and not the snat pool, liked we hoped. We would like this
- Brandon_12607
We followed I APP for APM V13.0 Code F5 engineer said if you want to use the snat pools and Route Domains to add snat before vmware view policy. That way it want add the Vmware View Servers won't use the Self IP instead of the Snat pool.
What do you think? we tried doesn't seem to be working.
- Brandon_12607
VDI environment is working however we can't control what IP is Vmware View server is putting on the Desktop for View Client Broker Remote IP Address
On the VDI DESKTOP run type regedit HKEY_Current_user Volatile environment Look for ViewClientBrokerRemoteIPAddress (Currently it is the Self IP and not the SNAT Address)
Anybody have any thoughts on this?