This training video is designed to show you how to use the Wise Management suite to automatically configure Y OS clients. The ability to simply take y then o thin clients out of the box connected to your network and have zero configuration on the endpoint is one of the great advantages of using a Dell wise TH OS client. In this training you will see screen captures from an actual insulation and configuration of thin clients in my lab. You may need to run the video in full screen mode to see the installation clearly. In the past.
The recommended method for doing this automatic configuration of Y stalest clients was by using text based I and I files on a central FTP or http server. Although this method is extremely effective configuration can become complicated if devices require unique settings. And the I and I file configuration may be seen as complex particularly for someone new to this type of management. Dell has now introduced the Wise Management suite. This next generation of thin client management software allows organizations to effectively deploy group and manage devices.
This is all done with the web-based G I and there is no need to manually configure I and I files. The Wise management suite is available in both standard and professional versions. One of the advantages of the professional version is the ability to have management solution hosted in the cloud. There are other features only available in the professional version for both cloud and on prem for the purpose of this training. I'm going to focus on the wise management suite standard. This version supports up to 10 000 clients is available only as an on premise solution and is a free solution for management of wise then o clients. The Wise Management suite supports the management of Dell wise clients with windows embedded Lenox and Yin OS. But for the purpose of this training I'm gonna be showing the configuration of a YN OS client. Now let's review the steps for automatic configuration of the Wise N OS client with the Wise Management suite standard.
I'm going to demonstrate all of these steps in this video today. So you may want to follow along and pause the video as necessary after
you are using this training as a tool for configuring your own environment. Step one we will install the Wise Management suite. It is recommended using a new install of windows 2012 R two or windows server 2016 in a virtual machine creating a snapshot of the virtual machine before the install would also be recommended. So you can roll back if you want to start the installation again. Step two will be to log into the Wise Management suite Council and modify the default policy group and create a new policy group with settings to configure the thin client. Step
three is optional but I recommend to test by manually configuring the wise client to communicate with the management server before making any network changes. And step four is to configure custom DH CP option tags or DNS entries. In this training you will see how to do both but you would only want to use one method for each setting for step one installing the Wise Management suite. The server and hardware requirements are listed here on the screen. Now let's begin the installation. You can see in this case I am using a windows 2016 standard server.
The server is joined to the domain and I am logged in as a domain administrator. During the install you will need to set a password for the Wise Management Suite database account. You also need to set up administrator credentials. Make sure you remember the email address you use as the administrator and the password you set as this will be needed to log into the console. You will also need to create and specify a directory to use for the local software repository during normal circumstances. The entire local insulation should take about five minutes once the installation has completed successfully click on the launch button then click on get started for this training. We are going to select a license type of standard.
The next two items are setting up email alerts and importing a certificate to keep this demo as simple as possible. I am choosing to skip these two optional steps. Now you can sign into the council. Now let's move on to step two and configure the group policies for this demo. I will go to apps and data and under file repository add three JPEG files to use as desktop wallpapers for the devices. Here you can see the default wallpaper. I'm going to add another one for a VM ware background and then I will add a third one with some orange circles by using custom wallpaper. It makes it very visible when the policy is applied. Now let's go to the default policy group and click on edit. I like to change the group token for the default policy group from the default to default group. Now we'll select edit policies then os under visual experience change the desktop to classic.
This is a personal preference. Selected wallpaper. We're going to use the default JP G and change the wallpaper to stretch for security. Let's change the privilege to known which prevents any unwanted local changes and will set up a local admin account under remote connections. We're gonna make sure the broker is set to none. Finally under advanced we're gonna select no global in I file. This is just to ensure that the settings are only coming from the wise management suite not from a legacy FTP or http server that hosts an in I file. Here you can review the settings for the default policy group which include classic desktop privileged non local user name and password setting broken or none and setting no global in I file. Now I will create a new policy group this group and all other groups will be under the default policy group and thus inherit all the settings from the default policy for this group. I will set the token to something easy to remember.
Horizon view enable it and click on save. Now we will edit the newly created Horizon view policy group. For the thin O policy we will change a visual experience to the VMWARE JPEG wallpaper the broker server. We'll select to vmware and specify my Horizon seven connection server. Then we'll click on save and publish. Before we move to the next step. I'll go ahead and show you the three JPEG files which I loaded to the software repository. You can actually see a default JPEG some orange circles and a VM background screen using unique wallpapers. Makes it very visual to just verify if a policy has been applied correctly. For step three I'm gonna test the Wise Management suite and the policy groups by entering the Wise Management suite information directly on the Wise N OS client to best demonstrate this. I have split my screen capture to show my Wise then and West client on the left and the Wise Management Suite Council on the right after opening a council you can see the default policy group which over here it's de fa dash default group on the thin client.
We're gonna go to system set up central configuration in the WD A tab select CCM and enable cloud client manager. Cloud client manager was a product name for Wise Management suite when there was only a cloud hosted version. Therefore any references to cloud client manager in the Thow gooey can be used interchangeably with the Wise Management suite. As you can see I'm also entering my CCM server and my MQ TT server. The default is to point to the cloud hosted version. It's recommended to use the default ports which is 443 for the CCM server and 1883 for the MQ TT server. In testing in my lab I was able to succeed even without using the without using the ports. But uh it's best practice to use them since we're not using uh C A certificates. Let's go ahead and clear that and then click on validate key.
Once I click on validate key the device will reboot. And if I look in my Wise management suite console I can actually see now that I have one device that's checked in and listed as manageable. Um The group is set to the default policy group and you can see the uh wallpaper that we specified is there. We can also check the advice. Remember we set this privilege to none. So I can't make any changes. And I did specify a local admin account. If I wanted uh to make changes there locally let's go and select the device under more actions. We're gonna select change group and now we're gonna change it into that VM ware horizon view group and go ahead and save that. Now the device recognizes the changes communicates with the wise management suite server and begins to reboot so that it can apply the new changes.
Keeping in mind it will apply all the policy settings in a default policy group plus the ones that it inherits from the Horizon view group. So the default policy for example specified to the privileged none and then the VM Ware group specified my view connection server. Uh And I also set the background. So now I can go ahead and log in uh just to verify that that's working. And now you can see I have several desktops available. I'll just select one. Um The device is still locked down. Can't make changes here. I'll select a desktop and you can see that I can log in here. Go ahead and log off I can show you some other management features here. I can go ahead and do things like restart. You can see how the real time interaction with the device as I select the device and did a restart. Now the device begins to uh restart. So again this is just testing. I manually entered the settings for the uh wise management suite server on the device. So for the next part of the demo I'm gonna go ahead and select the device and I'm gonna choose the option to wipe it which will clear out any settings the device has.
So I'm gonna do a remote wipe of my device which will essentially uh reset the device to its factory defaults. Now you can see in my We Wise Management suite uh there are no devices listed as managed and the device when it boots up uh will not have any information about the Wise Management suite. Can we go ahead and look now on the device under central configuration? Uh You can see there there are no settings here. Now let's move on to step four A and we're gonna create and configure the custom DH CP option tags for the wise management server. Here you can see uh this is on the device the settings that we need to specify. We're gonna use option tag. So for the group registration key we're gonna use custom option tag 199 for the server option tag 165 MQ TT server 166 and the C A validation status with option tag Here you can actually see in DNS what I need to do is I go into set predefined options and then I click on add and I'll go ahead and add them in order. So for my wise management suite server um I'm gonna do code 165. All of these custom options are type string.
This is just the default value. So I'll go ahead and put that in which is my full DNS name of my wise management suite server uh including the port. Again that's a recommended best practice. So now I'm gonna go and move on and add the next one. So for my MQ TT server uh the code is 166 again type string you can see all of these listed down at the bottom of the screen as well. The four that we're gonna need uh for this part of the test uh pay special attention to the format. So you can see where I've got the DNS name colon port. This is gonna be for the C A validation status option tag 167 which again we're not using that for this uh simple demo. So the value is gonna be simply false. And the last one DH CP custom option tag 199 type string and this is my group key. Now remember for the demo I'm putting them in the default group.
There's no reason you couldn't put it directly into any other group that you uh found beneficial. So in this case if we knew we wanted to go to that uh VM Ware Horizon View group I could put the token uh in specifically for that group. But again I'm gonna go ahead and use the default group in this case. And now that we've uh defined them we actually need to enable them. So that's one step. Sometimes I see people create the DH B option tags. Um but they're not enabled. Remember you can enable these custom option tags per scope uh or per server. Um I'm setting them for the scope in my lab. One of the advantages of setting them per scope is you could actually perhaps have different group keys uh unique to each custom scope. So if you want them to show up and have different policy groups apply to devices based on their Subnet scope um you could do that easily just by setting a different uh um that'd be option tag 199. So again here's the screen uh with the Wise Management Suite Council on the right. Let's go ahead and log in. And now again there's no devices there and you can see here uh There is no management server specified on the device and just to you know make sure that anything is cleared out.
We're gonna go ahead and restart it to factory defaults one more time locally on the device really to simulate what you might see if you were taking a box a a device out of its box and unpacking it and hooking it to your network for the very first time. So you can see obviously when the DH CP server responds to the device it's gonna provide its IP address and also pro provide the four bits of information that it needs including the CCM server the MQ TT server the policy group and the validation status. And you can see the device here. Now has those settings applied that go into the default policy group. Let's go ahead and change it to the horizon view group. Go ahead and save that. And again you'll see the group token has changed for the device so it will restart. You can also see it's reflected on the right and the management suite the group that the device is in. Now let's go ahead and once the device boots up I want to show you what I have set here for the time zone and the time server you can actually see because I haven't specified it. If I go under my system preferences you can see the the date and time and the time zone is unspecified and the time server is actually not a valid time server.
So if I want to set those values through the wise management suite I may decide that it's best to go ahead and go to the Horizon View group and specify a time server. So just go back to the Horizon view group edit the policy select th Os and then under other you can actually see the time server settings. I'm going to set it to time.nist.gov and then save and publish. Now I may also want to set a time zone but I'm gonna actually create a group under horizon view for each specific time zone. So I'm gonna call this in horizon view est and give that a description and the purpose of this is so that uh this will be underneath the horizon view. So anyone in this this setting will get the things from horizon view we got to enable the group token and we're gonna give it a group token that makes sense. Horizon view Est. And as I was saying um they'll get the horizon and the time server. But now we go into this specific policy horizon view et and edit the policy for TH OS. And remember we go to other for the time settings.
It's inherited time.nast.gov. But the time zone for this group we were gonna go find GMT minus five Eastern time zone and save and publish. So now all you would really need to do is go to the um uh device here. You can see the the summary that's all that's set there. But we'll go to the device and under more actions we're gonna change the group stand out under horizon view and we'll find Horizon View Est and go ahead and save and that will change that device to that new policy group you see the my Y in and West Incline on the left screen uh is about to reboot so we can get these new changes. So let's go ahead and log in with admin mode just to verify the changes have been applied correctly. Again the admin credentials were set in the default policy. Um And now you can see the time zone is Eastern and the time server is time dot ne Inis t.gov. So I wanna show you uh one more quick demo if we take this group.
Remember I said that applying desktop wallpapers was a very visual way to show changes. Uh I wanna show you this change in real time uh without any reboots required. So I'll just configure the visual experience again here. Now we've inherited the VM ware dot JPEG but we're gonna select the orange circles and we're gonna go ahead and save and publish. Uh And this is not a change that requires any reboot on the device. And you can see it just automatically pops up uh on my TH OS client. And you can see the group here on the right of the device uh is Horizon view est. So now you see the device has it automatically configured itself. I didn't have to make any changes local on the device.
Everything it needed to find the uh management suite server was on the option tags. So we might want to do this with DNS entries again to do this we're gonna need to get the same four bits of information to the device. Um We need to get the default group. So what we'll do is we'll use two SRV records. Uh We'll create those for the wise management suite server and the MQQT server. And then we're gonna use DNS text records uh for the group key and the C A validation status. So here's screenshots of my SRV record again pay special attention to the format. You can see the full DNS name uh the ports are specified. And then for my uh text records you can see here I've got that default group as well as the uh C A validation status set to fall. So go ahead and bring up one last time. These are the four steps that we did. Hopefully you found this demonstration useful. Um And got you all the information you need. Thanks for viewing and have a good time deploying many many wise thin clients.
