Hi,
I have to check this in our environment.
But what I could see that the "ViewClient_Broker_Remote_IP_Address" is not our thinclient anymore. It's not always the load balancer IP.
I don't need at the moment a smart DEM policy to check internal/external access.
But everyone who is using VMware vIDM/Workspace should have trouble if they can't decide between internal an external access.
Maybe I will try to contact our VMware TAM. It's funny that VMware will not fix it and blames F5 for fixing the issue.
