We have hourly employees that we would like to place on View. However, due to labor laws / regulations we can not offer offsite access. (Home) We could get sued for hours they worked at home b...
See more...
We have hourly employees that we would like to place on View. However, due to labor laws / regulations we can not offer offsite access. (Home) We could get sued for hours they worked at home but were not paid. So I created a case with VMware and they told me the only way to do this was to use the tagging functionality to limit pools to certain connection servers. This wasn't what I wanted to hear since it causes a lot of problems elsewhere. Wish there was a nice on/off switch somewhere controlling external access. But anyway, I created a third connection server and labeled it and my second replica as "INTERNAL". I added my third connection server to the Microsoft NLB cluster also so I would have LB and redundancy. I then created a seperate pool just for hourly employees and tagged it as INTERNAL also. The problem I am now facing is when I login to the MSFT NLB cluster IP it sometimes uses non "INTERNAL" connection servers (my first one). When it does this then the "Internal" desktop pool doesn't show up. How is everyone getting around this? See below diagram showing my setup. Thanks, Michael