Time to Upgrade your Horizon Environment

March 22, 2018 ~ vDelboy ~ Leave a comment

Is it time to upgrade your Horizon Environment? Is your infrastructure team getting ready to upgrade the vSphere servers? Both questions that you should probably be saying yes to.

If you have read any number of blogs that have been released recently, vSphere 5.5 will be going End of General Support in less that 6 months’ time. Read more here: https://kb.vmware.com/s/article/51491

Upgrade to Horizon 7

So why am I talking about vSphere upgrades in a blog about Horizon upgrades. Well now is the time you need to ask what version of Horizon you are currently running, because if you haven’t updated to Horizon 7 yet then now would be a great time to start planning your upgrade.

You can read the rest of my post on VMware.com. Click Here

Horizon Cloud Pod Architecture 7.1 Update

March 17, 2017April 25, 2018 ~ vDelboy ~ Leave a comment

Last year with the release of Horizon 7 I wrote a blog on the new features of Cloud Pod Architecture (CPA) this included the new scale numbers. You can find that blog here.

This week VMware released Horizon 7.1 and with this release VMware has increased the scale numbers yet again for Cloud Pod Architecture.

Now with Horizon 7.1 Cloud Pod Architecture can support a maximum of 75k sessions across 5 sites.

The table below shows the new update compared with Horizon 7.0

	Horizon 7	Horizon 7.1
Total Number of Sessions	50,000	75,000
Total Number of Sites	5	5
Total Number of Pods	25	25

This is yet another great update to VMware’s Horizon and Cloud Pod Architecture.

VMware Horizon Multi-VLAN Update

March 17, 2017 ~ vDelboy ~ Leave a comment

With the release of VMware Horizon 7.1 this week, VMware has made a significant update to the way Horizon supports Multi-VLAN for Instant Clones.

Multi-VLAN support, if you are not aware of this feature allows you to assign Multiple VLANs to a single Horizon View Pool. For example if you have a Horizon View Pool with 1000 desktops these desktops could be spread across 4 different VLANs rather than all sitting on one very large VLAN.

Multi-VLAN support has been around in Horizon View for some time now, however the catch was that it needed to be configured from the command line using a PowerShell script and this wasn’t always the easiest and was not that easy to go back and change.

With the release of Horizon 7.1 when you create an Instant Clone Pool you can now configure Multi-VLANs right from the GUI.

When you get to the vCenter settings page you will now see a new option for Networks.

Once you click on Browse you will see the new screen to choose what VLANs you want to use for your new Instant Clone pool.

You will first need to uncheck the box “Use network from current parent VM image”

Once this box is unchecked you can choose just what networks you would like to use for the newly created Instant Clone Pool.

NOTE: This feature is only available for Instant Clones Pools Desktops or RDSH servers. For Linked Clones you would need to use the old way using the PowerShell script.

VMware Horizon 7 Instant Clones Best Practices

October 27, 2016October 27, 2016 ~ vDelboy ~ Leave a comment

Recently, I have been working with Instant Clones in my lab. Although I have found this easy to get up and running (for more information, see my blog here), it hasn’t been easy to find best practices around configuring Instant Clones, as they are so new.

I reached out to the engineering team, and they provided me with the following best practices for using Instant Clones in VMware Horizon 7.0.2.

Check OS Support for Instant Clones

The following table shows what desktop operating systems are supported when using Instant Clones.

Guest Operating System	Version	Edition	Service Pack
Windows 10	64-Bit and 32-Bit	Enterprise	None
Windows 7	64-Bit and 32-Bit	Enterprise and Professional	SP1

For more information, see the architecture planning guide.

To read the rest of this blog please check it out on VMware.com here

New Requirement for VMware Identity Manager when clustering

August 17, 2016August 23, 2016 ~ vDelboy ~ 1 Comment

Recently VMware released Identity Manager 2.7 and with it there is a new requirement when clustering the Identity Manager behind a load balancer.

It is now required that you have a minimum of 3 Identity Manager Appliances with in the cluster.

The diagram below shows this minimum requirement.

This will also help when upgrading to future version. If there is a minimum of 3 appliances then it will be possible to upgrade these appliances one at a time with out any downtime.

To upgrade with a minimum of 3 in the cluster you and simply take a single appliance out of the load balanced pool upgrade the server and then add it back to the load balanced pool. Simply do this for each appliance in the load balanced pool and not down time will be required.

Configuring VMware Identity Manager and VMware Horizon 7 Cloud Pod Architecture

July 7, 2016 ~ vDelboy ~ Leave a comment

With the release of VMware Horizon® 7 and VMware Identity Manager™ 2.6, it is now possible to configure VMware Identity Manager to work with Horizon Cloud Pod Architecture when deploying your desktop and application pools over multiple data centers or locations.

Using VMware Identity Manager in front of your VMware Horizon deployments that are using Cloud Pod Architecture makes it much easier for users to get access to their desktops and applications. The user has just one place to connect to, and they will be able to see all of their available desktops and applications. Identity Manager will direct the user to the application hosted in the best datacenter for their location. This can also include SaaS applications as well as the applications that are available through VMware Horizon 7.

For the full blog please see my blog on VMware.com

http://blogs.vmware.com/consulting/2016/07/configuring-vmware-identity-manager.html

Configuring VMware Identity Manager with SQL Always On

May 18, 2016 ~ vDelboy ~ Leave a comment

For the last few weeks I have been testing VMware Identity Manager with SQL Always On database for multi-site deployments. This has been an interesting learning curve as its been some time since I last did anything substantial with Microsoft SQL. Before I start with the VMware Identity Manager I think it is worth calling out these 2 resources that I found really useful for setting up SQL Always On in my Lab.

This is a quick intro in to SQL Always On and how to configure it

https://www.youtube.com/watch?v=VKCqRgqLAuo

This was a useful step by step guide for deploying SQL Always On

http://www.careexchange.in/installingconfiguring-sql-2014-always-on-cluster-on-windows-2012-r2-recommended-way/

Now before configuring VMware Identity Manager with an SQL Always On Database you should be aware that even though there is a database in each of the datacenter’s all Read and Writes operations will take place on the Primary database with in the Availability Group.

From my testing I found that setting the database to automatic failover worked as expected and the database was only unavailable for a very short time less than a couple of seconds. However, I did find that when I failed the database back after an outage this took a bit more time and I would recommend that any failback is done in a much more controlled manner. In my testing fail back took about 40 seconds so a noticeable difference.

Creating the VMware Identity Manager SQL Always On Database

Open SQL Management Studio and log in with sysadmin privileges (This should be done on the primary server)
Click File – New – Query with current connection
In the editor window paste the following SQL Commands

CREATE DATABASE saas

COLLATE Latin1_General_CS_AS;

ALTER DATABASE saas SET READ_COMMITTED_SNAPSHOT ON;

GO

BEGIN

CREATE LOGIN horizon WITH PASSWORD = N'H0rizon!';

END

GO

USE saas;

IF EXISTS (SELECT * FROM sys.database_principals WHERE name = N'horizon')

DROP USER [horizon]

GO

CREATE USER horizon FOR LOGIN horizon

with default_schema = saas;

GO

CREATE SCHEMA saas AUTHORIZATION horizon

GRANT ALL ON DATABASE::saas TO horizon;

GO

Click Execute

The saas Database will now be created
Make a Full backup of the database (This must be done before adding the database to an Always On High Availability Group)
- Right click the database – Tasks – Back Up
Add the database to the Always On High Availability Group

NOTE: It is also recommended to make the following changes to SQL

Change ‘HostRecordTTL to a lower value than the default in multi-site deployments. 120 seconds is a good value
Change ‘RegisterAllProvidersIP’ to false in multi-site deployments

Connect VMware Identity Manager to the SQL Database

During the install of VMware Identity Manager connect to the SQL Database using the following settings

Jdbc:sqlserver://SQLAGListener;DatabaseName=saas

SQLAGListener = the SQL Availability Group Listener, in the example below that is SQLProdServer
If the secondary SQL server is on a different subnet add the following to the jdbc string
- multiSubnetFailover=true
  - Jdbc:sqlserver://SQLAGListener;DatabaseName=saas; multiSubnetFailover=true

VMware Identity Manager and F5 New Step in Configuration

April 22, 2016April 22, 2016 ~ vDelboy ~ Leave a comment

This week I deployed VMware Identity Manager in my lab to do some testing with SQL Always-On and F5.

When I configured VMware Identity Manager to work with F5, something I have done many times in the past, I came across and issue. After I logged out I couldn’t log in to VMware Identity Manager with a domain account but could login with a local account. The issue is below

After testing a few things and trying to figure out the issue I found that when changing the FQDN of VMware Identity Manager there is a new step that need to be done.

Basically after changing the FQDN go back to the Admin UI.

Click Catalog and then settings.

From there select New End User Portal UI and click Enable New Portal UI

After this log out and you should now be able to log back in with a domain account.

Configuring VMware Horizon Instant Clones

March 22, 2016March 22, 2016 ~ vDelboy ~ 4 Comments

I have been testing VMware Horizon Instant Clones for some time now and several people have asked me how I configured instant clones as when they tried to test them either the instant clone option was grayed out or when instant clones is selected the next button is grayed out. The other issue I see is some people have issues deploying instant clones and they fail to deploy.

Below are all of the things to check when configuring View Instant Clones. One of these issues has fixed all of the question I have been asked over the last few week during testing.

Licensing

Make sure you have the correct VMware Horizon license, there is a new license that include the Instant Clone feature. If you do not have the correct license then the option will be grayed out.

View Storage Accelerator

One of the requirements for Instant Clones is to enable the View Storage Accelerator. Before you try and deploy a new Desktop pool using Instant Clones make sure you have configured the View Storage Accelorator on you vCenter server.

Select the vCenter Server

If you have the View Storage Accelorator enabled and you select Instant Clones but the Next option is still grayed out make sure to select the vCenter itself.

Configure Instant Clone Domain Admin

Make sure you configure the Instant Clone Domain Admin, this account will need to be able to add new computers to your Active Directory.

Horizon View 7 Agent

Make sure you install the new Horizon View 7 Agent on to the gold image. There are a couple of things here you need to know

First if you want to use the gold image for View Instant Clones, then during the install of the View 7 agent you need to select this option
If you do select the View instant clone during the install then you can not install the view composer option, it is one or the other
Unlike with view composer with View Instant Clones it is the Agent its self that adds the VM to active directory and not a separate composer server. This make View Instant Clones much more light weight, no extra server or database is needed for View Instant Clones.

If you make sure you have checked all of these things, then I am sure that View Instant Clones will work and you will see just how fast this new option is when deploying desktops.

Final Note

One last thing to Note, you will see a number of new VM’s in your vCenter that relate to your newly deployed instance clone desktops. I have listed these below.

cp-template-XXXXXXXXX This is the template VM that will be used to create your Instant Clones, this will be created from your Gold Image. This will be created on the destination storage or your desktops, but under storage you will also see that it is on the same storage as your gold image. You will also notice you can not edit this VM.

cp-replica-XXXXXXXXX this is the replica that is created for your VM parents. This is created from the cp-template and is placed on the destination storage.

cp-parent-XXXXXXXXX you will see one of these for each of the servers in your cluster, so in my case you see 6 as there are 6 ESXi servers in my cluster. These are all created on the destination storage and will be powered on, each ESXi server will have 1 of these cp-parents powered on and in memory ready to create a new desktop.

Horizon 7 Desktop Pool Deletion Feature

March 22, 2016 ~ vDelboy ~ 3 Comments

One of the great new features in VMware Horizon 7 is the ability to stop desktop administrators from accidentally deleting a desktop pool that is currently full of active desktops. Once this feature is enabled the administrator will have to delete all of the desktops before deleting the desktop pool.

In this blog I will document how to configure the Desktop Pool Deletion feature. Before you configure this setting you should be aware that this is a global setting and as such once enabled it will be enabled for all desktop and application pools.

Follow these steps to enable the Desktop Pool Deletion feature

Upgrade all Connections Servers to Horizon 6.2
1. Note that signed Certificates are required
Start the ADSI Edit utility on the View Connection Server host.
In the Connection Settings dialog box, select or connect to DC=vdi,DC=vmware,DC=int
In the Computer pane, select or type localhost:389
Double click on the object CN=Common, OU=Global, OU=Properties
Edit the pae-NameValuePair attribute
Add the value cs-disableNonEmptyPoolDelete=1
Click Add and OK
Now when you try and delete a pool you will see the following message

vDelboy'sView

vDelboys thoughts on VMware EUC and other topics

Design