In my previous blog I wrote about how to setup a Cloud pod infrastructure, I promised to write a second blog about managing this Cloud Pod. Well here it is, let’s take a look at how you manage a Cloud Pod environment.
I haven’t seen many blog if any about the after life of a Cloud Pod, setting up is fairly easy but once you start working with it you will change things. How can you do this and what are the implications of that, that’s what we will talk about.
First let’s talk about where we left off in the last blog.
Add Desktop pools to a global entitlement
After you finished the setup of the Cloud pod environment one of the last things to do is to add the desktop pools.
Adding the desktop pools is done with the following command:
The entitlementname is the name you given the global entitlement.
The poolID is to be found in the admin console with desktop pools.
Once you entered all options correctly the pools is added.
Next you need to add the pool from the other Pod. – sure you get the picture and I don’t need to add the screenshot.
Last task in the setting up is to assign which users are allowed to connect to the Cloud pod environment. With this entitlement you take away the burden of managing both sites independently.
From now on you manage with lmvutil.cmd until you upgrade to 6.1 where you have a GUI to do that.
There are two options here, you can either entitle a user or a group. Of course doing anything in IT based on a user is bound to end in an error so let’s stick to a group and add users to that group.
The command to entitle users to the cloud pod is;
lmvutil.cmd –addGroupEntitlement –groupName [Domaingroupname] –entitlementName [Name of the Entitlement] –authDomain [Domain FQDN] –authAs [Domain Admin UID] –authPassword “*”
The Command for a user is the same except that you replace group for user.
As you perhaps remembered I used the option Homesite while setting up the cloud pod. With a homesite you can direct users to a location they normally work from, it handy if your data isn’t roaming and you rather have a desktop close to your data.
now that the environment is ready to look for a homesite we need to tell the cloud pod how it can determine what the users homesite is.
There are two options to do this, first on is one for if you work in a monastery and second one is for us IT guys. First one is per user, second one is per group.
Well I’m pretty confident you all will choose the later one, assign a group per site and every you add to that group is directed instantly to their homesite.
The commands for this are:
I will add both command, for adding a user and adding a group so you can pick your own;
After you ran this command the desktop pool is not being used in the cloud pod and you can delete it. After you setup a new desktop pool you can assign it again as written in my previous blog.
I made a mistake, can I fix it?
Like me you also make mistakes… so after setting something up you discover that you entered something wrong. I did it, when I forgot that the desktop pool was setup with a forced protocol choice and I created a global entitlement without this.
VMware’s Knowledge base has some reference to changes in the global entitlements but not all options are changable it seems.
With the command lmvutil.cmd –updateGlobalEntitlement –entitlementName you can change some settings. The settings to be changed are;
Scope , use –scope to change it from ANY to Local or site specific.
Description , use –description to change the description of the global entitlement
Disable or Enable, use –disable or –enable to disable or enable the global entitlement
disableFromHome, use –disableFromHome to stop the homesite functionality.
requireHomeSite, use –requireHomesite to only allow the user to connect to his or her home site.
disableRequireHomeSite, use –disableRequireHomeSite to disable the previous.
defaultProtocol, use –defaultProtocol to set the protocol that will be used default.
The option to change the force protocol is not there, I haven’t found it so far.
So if you decide to change something like that in your environment you’re up for a challenge.
Best thing to do is to:
Remove assignments of the pools change settings,
Remove the global entitlement
Set it up again with the correct setting
Add the desktop pools
I still see my local desktop pools
After completing all the tasks in creating a Cloud Pod and assigning user to it, your local desktop pools are still active and users see both the cloud pod assigned desktop pools and the local assigned ones.
Well that something you have to do afterwards, you have to remove the local assignments on the desktop pools. The only pool that should be available from now on is the global one.
So on both VMware Horizon View environments you have to disable the access to the desktop pool.
What if I need to recreate my desktop pool?
Sometimes maintenance is needed or you are expanding your environment for 500 to 2500 desktops. When that happens perhaps you want to recreate your desktop pool. Before Cloud pod that was not a problem, with a Cloud Pod you have to be aware of some things.
You local desktop pool is a member of a Cloud Pod so don’t just delete it.
Remove the membership of the local desktop pool before you delete the local desktop pool.
Before you remove anything first check what is there, the command to do so is;