This training video is designed to show you how to configure the Wyse Management suite for management of Wyse Teri based zero clients. Many of the steps in this video are specific to the management of the Wyse Teri based zero clients and are not applicable for management of the Y OS Y Linux or Windows IOT clients.
However, if you do have a Wyse client, this video may be a good resource for you as it covers installing the Wyse Management suite on prem getting evaluation of the Wyse Management suite professional and installing the license configuring DNS entries to enable communication with the EMS DK server for management of the Y zero clients with the Wyse Management Suite and setting up simple profiles to configure the Y zero client for connection to a horizon view environment.
Now let's cover the requirements for management of Wyse based zero clients with the Wyse Management suite. The first requirement is Wyse Management suite 1.3 or greater. It must be the professional version. We do not support management of these devices with the standard version and that must also be the private cloud version.
Uh Meaning you need to install Wyse management suite on prem, you cannot manage terri based zero clients with the public cloud offering. The supported platforms are the Wyse 50 30 which is a product that was originally released named the P 25. The Wyse 50 50 which is the 24 inch all in one based Taichi client and the Y 70 30 which is the quad head unit originally called the P 45.
You must be running G firmware version five X or six X. You must have a EMS DK server. Uh This will be covered during the install. This is actually part of the install if you want during the installation of Wyse Management suite 1.3. And then the end points must be configured to connect to the SDK server.
You can use DNS entries or DH CP options uh for the demonstration, we're gonna use DNS entries.Now, let's start the installation of the Wyse Management suite. You can see that I have downloaded the 1.3 installer package. So go ahead and run that. I'm just using a Windows 2016 generic server, uh domain joined with a uh domain administrator to do the installation.
So I'll get to the uh welcome screen. I do get a message that it's detected. IE enhanced security is configured. Don't worry about that. You'll see I have the option to turn that off. This is an important step when managing Teric clients, make sure that you select the ems DK option. Uh then go ahead and you, we, we will install a Maria database.
So make sure you give a password here. We're just gonna use the embedded Maria uh DB go and click on next. You can see that the ports are there by default. We'll leave those the default. And then now we're gonna actually create an administrator. This part is important that you remember the email address and the password you use because that's what you will be actually logging into the Wyse Management suite with.
You'll use this uh email address and password. Uh So do not, do not forget that. And then we'll go ahead and click on next. This is something specific for the G EMS DK server. Uh I am required to either use an existing user or create a new cifs user. So in this case, I'm just gonna create cifs user um as a local user, you'll see it doesn't have administrative privileges, but it's local to the box and required for the EMS DK server.
Go ahead and click on that and create that and then click on next. Now, I'm actually just, I'm gonna take the defaults for the destination folder where we're gonna actually be installing Wyse management suite and the software repository. Once we've made all those decisions, we'll go ahead and click on next and start the install.
The install should take 3 to 4 minutes. Um and would go through here and then you'll see in this case, say, um it's done and now we're gonna click on launch W MS. So we're gonna launch the Council. And as I mentioned before, now, we need to log in with the user uh the email address and password that we set during the installation.
Let's go ahead and maximize this so we can see a little better and go ahead and sign in. So now the first time I get this, welcome to the Wyse Management Suite screen and I need to go ahead and do a few steps. So let's go ahead and get started. Now, I'm gonna select pro that's an important step.
When I'm managing the based zero clients, I need to use a professional version. So I'll show you how to get an evaluation license. I assume that most people watching this video are just gonna be testing out Wyse Management suite. So if you go to Wyse management suite dot com and then click on learn more, that'll bring you up to a screen that has some of the differences between the different versions or editions.
Uh We'll click on start free trial and then enter your information in here and click on start free trial. And now you'll see. Welcome to your free 45 day account. I'm now sign on to the council and now I'm actually signing into the cloud version of the Wyse Management Suite.
You look in the URL, you see I'm going to us one Wyse management suite dot com and I'm using the credentials. So I'm actually logging into the public cloud. The only reason for this demonstration, I'm logging into the public cloud version is because I got a 45 day evaluation and I do want to export that license.
So go ahead and accept the terms and conditions and log in here. And now I need to, once I'm in the Wyse management suite, uh public cloud offering, I can go into portal administration and then under subscription, you'll see that I have uh a license that's gonna expire in 45 days.
So I'm gonna go down to the bottom and export my licenses. So um the evaluation version that I signed up gives you 25 thin client seats and 25 software thin clients, which is for those are for managing the Wyse converter for PC product uh which I'll not cover today, but I'm gonna go ahead and export all the licenses.
And then once I have that key, I'm gonna go and right click and copy that. And now I go back to the uh the local installation that I did and you can see there's an option where I could just paste it in here. It's that simple and go ahead and import it. So now I have a Wyse Management Suite professional license installed on my local instance.
Uh Wyse Management suite 1.3. I'm gonna skip the email alerts for this demonstration and also um skip the certificate piece. But let's go ahead and proceed to the Wyse Management Suite Council. Now we're gonna flip over to the screen and we're gonna look at the uh Wyse 50 30 that I'm using.
Uh I just want to show you here that I am using the 5.51 firmware and in their configuration, if you click on management, you can see that it's not being managed by any device at this point. Uh So in order to get that device to be managed by my new Wyse management suite, I need to do a couple of DNS entries.
So the first one is I'm gonna go in and actually do an SRV record. So I go ahead in my DNS entry and then click SRV and then create the record and the service here, I'll blow this up so you can see it a little bit better is the PC IP dash uh bootstrap and then the protocol is TCP.
So again, you just put in underscore PC IP dash bootstrap and underscore TCP use the port 51 72. And then this host is just the uh server that I was actually installing my Wyse management suite. So in this case, might use demo 16 dash W MS dot demo dot Wyse dot com and click on, ok. And so now I have the required SRV record.
Now there is one other um DNS entry that's required and that's the sh a fingerprint uh for my Wyse management suite. So I'm gonna go ahead and create a text record. Uh This record name is going to be again the name of the server. So again, going back for me, it was the demo 16 W MS but yours would be the DNS name for your W MS server.
And then for the text, I'm gonna just put PC O IP dash, bootstrap dasher equals. And again, I have to put that, uh, sh a 32 fingerprint. So I'm gonna show you a couple of ways to get it. Uh, and one of these ways should work. If you look in Firefox and you go to your site, you can see there's a shaw 2 56 fingerprint and I'm gonna go ahead and get that and copy that.
So that's just using Firefox. And I'm hitting my demo 16 server and now I have a, uh, fingerprint record in there. And again, I mentioned sometimes, uh, this works, I'm gonna show another method, uh, in case that does not work, uh, to get the fingerprint. But you can see here, I've got my PC O IP bootstrap certificate and you can see that I've got my, uh TCP, um, record here, the SRV record.
So those are the only two DNS entries that I, that I found again again in this simple installation. Uh You can also use DH CP option tags. So now we're looking, um, at the device I can see. Now I've got a message. Ok? So bootstrap failed due to certificate issue. And again, I mentioned this, I'm gonna show you a second way to get the certificate if you do see this error.
Um, you can actually go into the event log on the thin client and it'll tell you the certificate fingerprint that it's looking for. Uh, so now, uh, as you probably know if you've used TGY zero clients, you can actually just put in the IP address. So this is the IP address of my Wyse 50 30.
Uh And I go ahead and just go ahead and confirm and proceed to the connection with these ssl warnings. Uh This is your default password for your Wyse 50 30 which is administrator with a capital A if you haven't changed it, uh and go ahead and log in and now under diagnostics on the device, I can actually view the event log and by examining the event log, it should kind of stand out.
You can see those two lines in the middle there. It's gonna say the expected fingerprint, which is what I gave it. Uh My Firefox method didn't work this time. Um But uh the actual thumbprint that it needs is right here, so I can go ahead and copy that. Um And now I've got the thumbprint from the event log on the Wyse 50 30 I'm gonna go back and I'm just gonna update my DNS uh record.
So here's the um I need to find the actual, the tech space. The one that says uh PC IP dash, boot trap and paste the actual thumbprint that my event log told me. All right. Now, let's go ahead and go back, we reboot the device.
So this is booting up my Wyse 50 30 and let's just check in uh after I get an IP address of this device and go ahead and we'll look under options and under management. OK? Now it does say it's managed and it's by that 19216802 16, which is my demo 16 server that I have in my environment.
So now if I flip and I log into my uh W MS server, indeed, I do see a device. So now I can begin to do some things under groups and config so you can see there's a default group policy. I'm gonna go ahead and add a policy specific for this um configuration. Um I'm gonna give it a group name and I'm just gonna call it uh uh ZC for zero client.
And then I just, I typically will copy and paste that for the description and the group token. So now I've got a uh group policy, but I don't have any settings in it. So if I select it and on the right I click edit policies and then select Teric, I will get a list of some of the uh policies.
So the most important one that I typically would do would be remote connections. Uh And you can see the connection type is a view connection server. And I'll go ahead and type in the name of my view connection server, which is demo 12 dash view dot demo dot Wyse dot com.
And I'm also gonna select a few other of the advanced options. Uh And you'll see those come into play to always connect and then auto launch. If there's only one desktop uh once that's done, I'll go ahead and save and publish and click on. Yes, here. So now I got a policy for uh zero client, although the device you can see is still in the unmanaged group.
So I'm gonna go ahead and change his group and I'm gonna move him into the Taichi ZC group. Uh So now he's checked in. If I go flip back to the device, I actually haven't even rebooted the device, but we should be able to see that policy apply in just a minute. Ok. There it goes.
So now it's actually put the uh view connection server in there. It didn't auto launch because I didn't reboot the device. It just pushed them down. If we reboot again in a minute, you'll see it'll auto launch. So I haven't changed the security warnings. So it just is warning me.
So let's go ahead and log in with credential at least see that it starts to connect to a desktop. So I log in with a basic user and I see it's authenticating and connecting to a desktop. So now if we go back to the Wyse management suite console, let's go ahead and click on restart.
You can see there if I select it, there's a restart option, the command will be sent to the device and you should see your, your Wyse 50 30 or your 50 50 or 70 30 device actually begin to reboot. So now uh because I have that policy applied, it should get my demo 12 view connection server and it actually should auto connect to that.
And then if I only have one device or one machine available in my group, which I do, it should auto launch. So again, um continuing with the security warning right now, uh I'll go ahead and log in and see it automatically connected to my my demo 12 dash view. I log in and then you see it automatically connecting me all the way through into my desktop.
Uh So I can figure that in my horizon view policy and this should be able to connect and I have a PC IP connection to my uh Windows 10 desktop from my zero client. So now I flipped back over to my my 2016 server, which is my uh demo 16 and logged back in as my uh W MS administrator. And we look at the groups and config and let's go ahead.
Um And you can see the view, connection broker and see my settings and again, just by this summary view here and you can see the name of the group. Uh I'm gonna go ahead and add another group underneath that. So this is gonna be a policy that applies underneath. So we'll call it uh GZC underscore EST. And as you can, you imagine, we're gonna set the time zone uh for this.
So this is a policy that's nested underneath the main one. But if I put a device in this new policy, it'll inherit everything in this current policy and the policy above it. Uh unless there's a difference and then the lower policy would win. So now I've just went over and I'm connecting and I'm changing the time zone when there's this policy.
So let's go ahead and set a NTP server. Uh And then I'm gonna set the time zone. So let's see in the list here. I want to go to EST uh find a city in EST. Let's pick in Detroit that will work. Um And once I set the time zone, um I'm also gonna go on my remote connections, remember how I select these advanced options.
Let's clear those options just so it'll make it easy to see that this policy is applying. So now in this policy, uh you can actually, you'll be able to see that there's a time zone sent to Eastern and then I've removed a couple of the advanced to auto connect and to launch.
If there's only one desktop, here's a view where I can see my device under device groups, you can see the policy that it's in and this can see any specific policies that are applied to the device. Um flipping back here to this device view, I'm gonna go ahead and do a change group.
So now I can't put in the 30 GZC group because that's where it is. But I'll put it in the underscore EST group. And then let's go ahead and restart the device from the Wyse Management Council. So I'm sending a command from here and flipping back to my Wyse 50 30.
You can see it'll begin to boot up and this time uh it will get the EST time zone and something that will be easy for you to see and remember we changed the advanced settings. So now it should not connect automatically to my horizon server, ok? It listed there, but I have to go ahead and click on connect and now go ahead and log in with that same user.
And you can see now it didn't auto launch the desktop because I removed that option. So I do have a single Windows 10 desktop uh that I could connect to here. Uh But I remove that option in my advanced section for this, this nested group. So again, looking back at my management console.
Uh You can see the device here, you can see some information about it um in my groups and config um you can see the summary of the settings there. Uh Here's some of the other settings and just kind of showing the other things language company logo videos. Those are the other settings that you can set.
So uh I hope this video uh was a good start. I know it went fast but I uh wanted to try to get through as much information I could in a relatively short video. Uh Thank you and have a good day.
