welcome back it's Adarsh and Brooks again we're on to episode four
and what we're going to go through in this particular session is doing a GUI based enrollment
of your Windows 10 device so the last episode to recap we went through command line enrollment
we went through that staging enrollment workflow now Brooks is actually going to take you through
what you would typically do for a bring your own device for those users where you've got a device
that you really just need to get them enrolled and you want to find the fastest way so we're going to
go through some of the setups for auto discovery correct Brooks and then we're going to do GUI yep
so take it away show us how this thing works and why do you need auto discovery in the first place
yeah so auto discovery is just mainly for your users and this applies not just for Windows but
for mobile as well it allows them to use their email address to enroll so it's essentially tying
the uem server to your email domain so obviously you have to own your email domain so and then
basically validate it so we're gonna do that first and then we'll show the actual enrollment piece
and so what's the alternative right if you didn't have your email domain registered then
what happens yeah so then they're gonna try to the pop-up will say hey enter your email address
they'll do that and then it will basically say cannot find server
and so that uh then they're gonna have to know the the server name like cn1506 like your users aren't
going to really ever know that so it just makes it a better user experience that makes sense so we're
back in our UEM console here modern peak and so to set up auto discovery we simply go to devices and
users and then enrollment down here is where we can add our email domains so we'll go ahead and
add this so the email domain we just type modern peak.com and then Adarsh is actually
going to do this on his email which is Adarsh modern peak dot modern peak or modern dash peak
i think it's modern dashboard business email domain yep our business email domain
also sweet yep so then you do the domain adarsh and then he has his email set up
on his side so it's pending yep so this will send me an email right yep yep i got it
okay i got it it's an email domain registration email and click on that link to complete it
and it says email domain registration success okay there we go that was fast
pretty easy right so status is complete and now we can use the domain
uh modern peak.com anyone in our company with that email address and the key part here is it
is linking them to this main group id so this is our our main organizational group group id
modern peak we don't have more than one right now and that's okay we'll do that in a later episode
and there's a different way to move users down but their entry point for this is always going
to be what's specified here so this has the other benefit of not only do they not have to know the
UEM server they don't have to know the group id um as well so now if they type that email domain
it'll say oh well that email domain means that server and that group yep it'll just basically
go straight to the authentication yeah cool that makes it really easy so we'll save this
and that's a one-time process so you don't have to register over and over right one time yep
and then I've got my client here
log login
so I've gone ahead and reverted or uninstalled the enrollment from before with our command line
enrollment and then just as a reminder are to get the actual agent we simply go to gitws1.com
so definitely make sure you know about this and your users can know about this
and make sure you spell it correctly and then it will automatically detect it and then it will say
download hub for Windows 10. so I have this one here it's always going to be the latest
and then all we have to really do is just install it through the click click wizard that will take
all the defaults install which in the previous episode we did this as a command line right so
all of these wizard windows we just scripted that it does it quietly and that's correct yeah it's
all silently and in the command line we're specifying this the enrollment automatically
but now we're not it doesn't know where it's going to enroll to so it's simply a generic install
and then in previous versions of the hub pre-2008 you may have seen it if you've
done this before it'll actually try to download the Workspace ONE App catalog
it no longer does that all of the Unified Hub is inside of the agent itself which is nice
so it's installed and now in the background it is initializing and we should see a pop-up here
in a second prompting for enrollment I see the little icon that came up at the bottom sweet
sometimes it can take a second
gotta love it right yep
there it goes there we go just had to like coax it on a little bit
so now at the moment this hub knows nothing about our environment right this is just
generic from the from the git ws1.com website yeah so now you need to go give
it some sort of pointer record of which tenant you want to enroll that's right
so here it comes it's going to say email or server address now we can go ahead and
do the server address if we're in admin and we know it and if we don't have the setup yet but
we we've now that we've set up auto discovery we can use our email modern dash peak.com
and so now it should look for that server and group id based upon that email oh there we go
you got a username and password prompt so I found it and it actually identified
my user account as well so that it's another important piece the UEM users have to be in UEM
or you rather your domain users have to be in UEM and then now I can just authenticate
if I remember my password
it's always hard did you not write it down on like a sticky note like the rest of us gosh hold on
there we go that looks far more promising don't get it I think so looks like it's spinning it's
doing its thing and I mean on the console side you'd actually just go in and as this is
doing you'll see a record get created it comes up saying enrollment in progress so it actually does
work you through the steps at the same time there we go so you'll see there there's an
enrollment in progress requests coming through it's being enrolled as brooks so now if we can
you'll you'll start seeing all of the various device information come through
and it's completed here is congratulations you've been successfully enrolled
so pretty straightforward right not too hard the auto discovery makes it easy doesn't it yep
so that's that's the flow on windows this is you know obviously your users aren't going to
do this uh at an enterprise level most of the time because you're going to want to
you know for corporate owned you're going to want to admin driven in the last episode
but it's still useful for testing you know you're setting up vms for testing profiles just just fire
up a basic UI enrollment also it's useful if i um if you're doing the staging enrollment staging
credentials that for some reason the staging enrollment isn't working go through that same
you uh step-by-step wizard when it pops up uh you just you'll enter your server name and then you
can actually enter in the staging credentials there as well that's a good tip and sometimes
that can help show if it's an invalid username and password or something else is going on
um it's just a bit easier to see errors versus uh in the command line it can be a little bit harder
yeah that's a good pro tip actually yeah especially with staging if you're running
into issues when you do it through command line enrollment and staging just do it through the gui
do the staging user and it will it'll pop up if you've made a fat finger error
yep and then it'll pop up this it does not have the catalog yet so this is just the
default enrollment screen we'll be setting up the catalog in another episode but this is where
you can validate the server name the version of the hub if you fill out the support information
and the user name and all that nice then just as a reminder in case there are issues with enrollment
this log here device enrollment dot log in program data airwatch
unified agent logs this is what handles all of the enrollment
steps so if there is an error here you can also see and this is verbose by default so it
can sometimes give you a bit more information although i would say that there is a lot of
extra stuff in here that you probably don't need but there's it will say as well if there's
an invalid username and password or something else that's going on can't contact the server
sometimes if there's proxies that can be problematic so we didn't show this but
you may have noticed on the username and password screen there's a little gear at the top right
you can click on that and configure a proxy um if you do have to do that makes sense all right so
that's cool yeah that's helpful so then that's and then you'll see the device turn up yeah in
the console in the console and then if we go to councilwork we'll just develop validate this
access worker school there i am nice connected to AD and you're connected
to your Workspace ONE environment yeah that's cool so some people and a little bit
i guess older way of doing it was going directly into access worker school first and then doing
like clicking on enrolling into mdm device management we don't normally recommend that mainly
because one you have to set up an additional auto discovery service called Windows auto discovery
and you have to have the cert from your domain name it's a little bit more complicated
and as well as that it does OMADM first and then it has to download the full hub from our console
and so that just takes a little bit longer to do and so that's why we just tend to say hey just
go grab the agent install it it's a little bit easier and it has a little bit better ui to it
but if you do want to have that for some reason this auto discovery
section is where you'd set that up and then you can either specify cloud hosted or on premise
there's the installation guide there um we won't show that so that's just definitely not the
preferred yeah yeah just enough it's not the not the more preferred approach definitely go through
get Workspace ONE or get the agent and do that way of enrollment that's right it's definitely
going to give you that better experience but it's good to know we've we've run into this in the past
with a couple of customers but now especially with the way that the hub and the agent is all together
it makes sense to do the get Workspace ONE and grab the package from there
so that's that's the super easy simple one for this episode
um one more thing i wanted to highlight as well if you're looking for more scripts or sample
enrollment um items on online we do have us this whole samples area on github the VMware samples
and then there's EUC samples so if we go EUC samples a bunch of stuff with a lot of different
platforms but if you go into Windows here there's kind of main a few different sections um
I have a cup i've put a bunch of stuff out here other people in the community have
but if we go into for example product provisioning I have this Workspace ONE re-enrollment script
that is kind of a combination of a bunch of stuff that we've learned last episode as well as this
episode but it's got all these parameters plus it does a full unenrollment and re-enrollment
and so this is just more of an fyi that if you want to take a look at the script and read about
it it allows you to do a full re-enrollment for problematic devices or it can just do
a regular enrollment as well so there's kind of these three different switches here always
on sid mismatch and never we'll probably get into more details on why you use it for
like says mismatch and some other situations but if you are looking for just a basic script
this can help you out and then we have episodes coming to show you how to put
these scripts into the console because you're obviously going to just deploy
all sorts of scripts so lots more fun stuff to come but this is helpful thank you for joining uh
stay tuned we've got a whole bunch more content ready to go alright see you in the next one