Quantcast
Channel: VMware Communities : All Content - VMware View
Viewing all articles
Browse latest Browse all 9103

Tunnel external users, directly connect internal users

$
0
0

Hi there,

 

We have a Horizon View 6 deployment going live soon (ish). One of the steps we would like to take either now or soon after go-live is to have all internal users connect directly to their desktops after the initial connection, and for external users to be tunnelled via the Security/Connection server pairing. I am pretty happy with how the config would roughly look, but in lieu of a decent test bed (and not wanting to go installing/re-configuring/uninstalling on the Prod platform for the sake of cleanliness) can anyone answer some basic questions about the practicalities?

 

Assuming I don't care about resilience it seems that I should have one Connection Server handling the tunnelled users and another connection server paired with a Security Server handling the external users (reference here:Documentation Center for VMware Horizon 6.0 with View). However, should either of those Connection Servers be a replica of the other or would they then simply inherit the tunnelling config of the other? If that is the case and the Connection Servers had to be two standalone instances with their own pairings and tunnelling config does that then mean managing two identical sets of desktop pools or can that be aggregated across the Connection Server instances.

 

Sorry if this seems like a fundamental question but I don't see everything I've asked definitively answered all in one place.


Viewing all articles
Browse latest Browse all 9103

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>