VMware Workspace ONE & Horizon 7: On-Premises Reference Architecture – Expert Q&A

VMware Workspace ONE & Horizon 7: On-Premises Reference Architecture – Expert Q&A


welcome everyone to the digital
workspace Tech Zone expert series today’s expert or today’s guru is Graeme
Gordon welcome Graham so I’m gonna read this cuz I’m gonna get it wrong you’re
here to talk about the workspace one and horizons seven Enterprise on Prem
reference architecture right that’s create the on-premises reference
architecture where we deploy all the components on a customer’s premise so
there’s a lot to unwrap workspace one horizon seven enterprise on Prem
reference architecture what his workspace one what is horizon seven
Enterprise on purim what is reference architecture so everything kind of comes
under the umbrella of workspace one you know that companies almost every product
we do right we kind of break down workspace one is primarily being the
product formerly known as AirWatch so workspace one use um and and also
Identity Manager (aka VMware Workspace ONE Access) that’s what we tend to put under that umbrella and then the
other part of the reference architects our horizon seven enterprise the ability
to deliver desktops or published applications either on Linux or Windows
and to write paint technologies like volumes to deliver those applications
and then user environment manager to kind of personalize and control the
environment so we have lots of moving components they’re brought in as one
deliverable to the end-user and this reference architecture tries to
encompass all of it so if I understood that correctly basically this is
everything you need if you’re going to deliver a desktop of virtually any kind
to any platform to your users in one box and also if you’re going to manage
mobile devices provide identity single sign-on workspace any other solution
that we provide how do you deliver that when you want to host those components
yourselves on-premises okay so what’s a reference architecture and why do I care
so why you care let’s address that but first because it makes your life easy
this gives you a blueprint approach to designing architecting and implementing
a solution based on our technologies so blueprint you’re talking about a lot of
technology that we have assembled in a way that we know works validated it with
customers and blah blah blah and this is the way we
would build this thing solving a certain problem we’ve taken several use cases
the way we like to portray it we think our one hit most people’s problems the
the requirements are trying to satisfy it and we’ve also done it in a very
modular and granular way okay so you can pick and choose you can combine them you
can also add components drop components and tailor them to your own needs so
allows you to understand how you take what we’ve done in a more general
fashion adapt it to your needs got it all right so we have this
reference architecture I assume it’s like a 10-page document slightly more so
roughly about 340 pages in total right and the reason you walk through 40 pages
what’s in it there’s a lot of technical detail the bit I’ve talked about to know
is the blue printing and describing what you’re going to build a lot of the
content in the document is how you architect identity manager (aka VMware Workspace ONE Access) how do you
architect horizon 7 a UHC follows the best practice the rules why would you do
things a certain way and why would you choose one decision over another so
we’ve kind of given all that information in there and then we’ve kind of built a
platform at the backend of it based on those decisions and validated everything
we’ve said in the paper to make sure that yes it stands up it works and if
you follow this you’re gonna get a working best practice environment so I’m
guessing that there’s a process that this document follows through discrete
steps discrete chapters that talk about phases of the journey the customers
about to go on we do we try and follow a methodology so that it’s easy to
approach you can also jump into certain stages within that methodology but if
you follow it through you’re gonna follow a proper design process you know
understanding the requirements understanding how you’re going to
fulfill those and then getting into the technology to deliver on that
so we’ve given a kind of complete methodology there and the document
structure drawing about that as well ok and if the the IT practitioner who’s
listening to us right now reads the opening paragraph reads the use cases
and says but they’re not mine is there still value in the document absolutely
and again it comes back to the way we made the modular and adaptable you take
them you drop components in amend them combine multiple blueprints together to
get what you want a lot of the architecture
design is still the same and it’s just constructing the end services out the
back in slightly differently very very easy to amend it to you know right so
this isn’t but I think a blueprints I think of house designs and that kind of
thing just to steal a story we were talking about off-camera earlier this
isn’t that this is designing rooms that are the work together and you can mix
and match because you know everyone wants to live in the same house it is
but we’re gonna take a night to take that architecture approach we’re
teaching you how to architect a house we’ve architected a house in that
process and through the document you should then be able to architect any
house got it so what would you ask the audience to do now and now that we’ve
made them aware that this document exists and clearly it took many months
of you and your team’s work to build so congratulations on that what do they do
with it well how do they start what do they get it is it just you print it out
and read it on the train what is this thing it’s something you haven’t dip
into you know start with the blueprints is where I would go start understanding
what’s modular how you would approach it what’s a value to you and then where a
lot of people will use it will dip into particular sections of the architecture
or the design so maybe you’re interested in identity manager (aka VMware Workspace ONE Access) maybe you’re
interested in delivering apps types your horizon desktops dip into those section
to understand how you’d architect and how you give value from it all right and
then one final thing I’m still not clear on if I were the customer at what point
would I do this is this one of my boss comes to me and say hey we’ve engaged
with VMware and I have to go read this thing or am I am I already six months
into deploying it and this Tunes it we’re in the lifecycle of rolling this
stuff out do I use this reference architecture so it’s probably going to
be mainly implementation so you’re starting to build a production
environment you know what does that mean what’s the best practice what the rules
you should follow but we’ll also see lots of people use it in that proof of
concept phase as well okay so I’m trying to put together a service and how do I
do that you know because lots of moving parts
here both from VMware aren’t from third-party vendors in delivering an
easy solution so what do I need to consider and how do I put that together
so the value throughout the different phases as well ok perfect well thank you
for coming in and explaining that to us Graham so I think what I just heard is
that if you’re at the point where you are about to build or in the middle of
building a workspace one horizon 7 installation
on your own premises we have a document that you should come and read because
the answer to the question that you’re about to ask is already in that document
so visit Texoma vmware.com and also ignoring the the reference architecture
you should be visiting Tech Zone anyway because there’s tons of stuff on there
experts like graham who are just building videos building documents
helping you do your job so thank you for listening and please come back and watch
again thank you

Leave a Reply

Your email address will not be published. Required fields are marked *