in this short video I want to cover some of the technical aspects and
architecture of horizon 7 version 7.1 so from a logical architecture point of
view we have clients installed on devices endpoints that the users are
going to interact with and they're going to connect in to our connection server
or servers in plural if they're coming over an insecure connection like the
internet we may also want to direct this via a VM our unified access gateway this
provides secure edge services and a way of routing people in securely the first
thing the client is going to do is authenticate and we can decide what kind
of authentication we want to have here whether it's just simple username
password or more advanced a two-factor once authenticated the user is going to
choose an Internet application or desktop the desktops can be created
tools the applications can be hosted on pools of RTC's servers which we call
forms to make those creation of those farms or desktop tools easier we can use
two different technologies our preferences to use instant clone
technology which very rapidly spins up clones of our ds8 server scape farms or
desktops to create desktop tools we can also use the second method which is a
link clone method the disk link on using view composer optionally we can drive in
up volumes manage your app stacks and these can very rapidly deliver
applications on mass to the desktop onto the RTC servers make lifecycle
management very very easy and lastly we can drive in profile information
settings and IT configuration into the desktops and applications
let's look at the components that make up that environment we talked about
there so we'll go to connection server it
means your biz tentacle user and then broker them through to the resources to
desktop the applications that they're entitled to but it also runs an admin
console but we can configure the whole environment and we can also monitor
what's going on and lastly it also runs the internal engine it's going to be
time for going and carrying out the creation of those instant clones I
mentioned this that unified access gateway provides secure edge services
and it usually sits in the DMZ to avoid and those services through to the
connection server and ultimately through to the desktop of the application
previously we call this access point but we renamed this to unified access
gateway there's an optional component here if we want to do linked one's
called composer server and this requires an external database or either a sequel
database or an Oracle database but as I said this is optional and only required
for module includes the last two components here the agent and the client
the agent sits on the virtual and resource so either the rd8 server or the
desktop this job is very connectivity in there and deliver whole host of remote
experience features the other part the client officer sits on the end device
and it provides connectivity into the horizon environment obviously it's
available for most popular devices and Oasis but we've also got an html5 client
so browser-based access when we've got the option not to install any software
so obviously we can create and pools and farms as I mentioned the desktop pools
can be automated or manual typically we prefer to automate it in terms of
assignment we can either be floating or dedicated they can be based on instant
clones or link loans as I've shown so far or we can also do fluke loans
typically those it will be cloned from a common primary virtual machine so we
update we manage that and then we clone it in some way
similarly rdfa farms can be created from a primary and based on instant clones
link clones or focal and depending on what we're trying to achieve instant
clones are our preference as I said because a really fast ly provisioned
customizable and then available for use and so we do this by using a VCR
technology called VM pork where we take a running virtual machine a parent
that's running on the beach or a host and we very quickly copy the memory and
disk there's no reboot of the instant clones
required so very little impact in them bar
the host environment and but very very rapidly available for use Lync loans are
an older technology and it's all about disk replication and copying and linking
back to the original disk slightly slower because we do need to boot the
clone but still very useful in terms of how we can actually update and link
links together
so in terms of compatible with the requirements each of the components I've
talked about how different operating systems that are supported on all the
way up to 2016 and the unified access gateway comes as a virtual appliance so
it's a hardened linux appliance that you just install and forget the resources
I've mentioned here are recommendations and you can go with lower minimums
according to the documentation you'll notice they are the only part that
really needs external database is the composer server and I'll remind you that
is an optional component only when you're doing linked clones terms are be
sphere and be Center we can run horizon 7.1 on top of 5.0 update 1 all the way
up to the very latest 6.50 but obviously we want to use infant colon technology
we need to use a version that supports that but architecting horizon we follow
a pod and blocker pollution each block is made up of one or more vSphere
clusters and a virtual Center or a V Center now the current recommendation is
to keep these block to a limit of about 2000 sessions we understand that ver
Center can actually handle a lot more up to ten thousand and in 6.5 up to 25,000
but currently the recommendation is the virtual Center should hold and control a
block of vSphere clusters holding resources for up to about 2000 desktops
if we need more than 2000 we build another block and we repeat the block
reports up until we get to a pod now each pod should also have a management
block when it gets to scale there's going to be its own dedicated beasts or
hosts where we're going to run the infrastructure of us machines so the
connection servers the access points the virtual centers potential even the
database and when we get up to a number of blocks we're going to delimit it with
what we call a view pod view pod is limited currently to 10,000 sessions
we want to go to more than 10,000 sessions we use cloud pod architecture
we can group together 25 independent pods either on the same site or across
multiple sites up to maximum of 75,000 sessions
ultimately with horizon we're trying to deliver services to end-users so one of
the therapies will be published applications with published applications
that can be delivered through RDS H clones and and we can also present them
optionally through Identity Manager (aka VMware Workspace ONE Access), workspace one the clones are going to be
created as part of a farm using the insulin technology I mentioned earlier
we're also going to control profile information with user environment
manager and we typically use stuff like folder redirection to extract user data
and files and not store them on the virtual machines themselves and lastly
we can also use and things like app volumes with app sites to attach the
applications to the RDS H clones and we can also use thin app to stream in
individual applications both to the clones and also into identity manager
obviously this is all surrounded by an environment and usually based on top of
vSphere and optionally based on top of virtual central storage simply we can
deliver desktop service we're delivering a whole desktop out to the user and
again these desktops are going to be created as part of a pool from a primary
VM using instant clones suddenly we're going to have profile information kind
of a user environment manager and that information can actually be common
between an application that's inside a desktop or an application that's
delivered as a published application so we keep the same experience with user
similarly we can use stuff like app volumes and thin app to deliver
applications one key difference here is we can actually deliver the app volumes
app stacks on demand as the user logs in and we've also got an optional writable
volume where we can actually store user installed applications
again this is all going to be based on top of vSphere with option of virtual
Sam and we've all stood at options of doing graphical acceleration with V GPU