vWorkspace Hyper-v with tiered storage pools – Part2

Hello again,

It is time for the second part. Now I will help you to configure Hyper-v in your vWorkspace farm. I assume that you already have a functioning vWorkspace farm before we begin.

The first we do is adding the Hyper-v hosts to vWorkspace. Open the vWorkspace console.

The left pane in the console looks like this: (we use version 8.5)

Right click on “Hyper-v” under “virtualization hosts” and choose “add host”, you will get a wizard. Follow that wizard:

Use the netbios name

Connection Load balancing is not necessary

Provisioning load balancing, we will do that later.

When you click fininsh, the server will show info about his state:

As you can see the server in not initialized. If you wait a few second the server will initialize itself. If not the right click on the server and choose initialize.
The server will install it Hyper-v catalyst component.

Once the catalyst component is installed the server will show more information instead of <UNKNOWN>.

This is the result after all my servers added to the Hyper-v hosts section:

As you can see the free space is different on some servers. This is because vWorkspace automatically adds the C drive as a location to store VM’s. But that is not what we want, we want to use our tiered storage!
So how to change that?

Right click on the hyper-v host and choose “properties”

Now you will see a similar wizard as when you add a new host, but now there are two extra options. “Volumes” and “HyperCache Settings”
We will go to Volumes:

Remove the checkbox for C at placement, after that the servers will only use your D drive for its VHD(X). This is the result:

Now the servers are ready. Now vWorkspace will not provision on your C drive. In this screen shot you also see “placement Volume Free Space”, on my HVVW01 this is less than other servers. This is because I already have two VM’s in Hyper-v.

So now we can provision RDSSH servers.

Right click on “Provisioning” under “Session Hosts” en select “New Computer Group”. You will get a wizard:

The name you choose here will also create a folder under “management”

The first provisioning group is created, right click the group and go to “provisioning settings”.

Her we can determine how our VM’s will look like after provisioning. Click “Edit”, a new wizard will show:


Now we can add the correct hyper-v image. I do not have a server yet so I will click “Import”.

I my case I see two images, and I will use only the Office2010 image. “Finish”

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Customize operating system is separate wizard. That will allow you to do some custom changes to your server during provisioning.

And we are done.

If you receive the following message:

It is not a problem. But we have to fix this.
This issue is because my image has instant provisioning of version 8.0.1, because I use 8.5 now I have to upgrade that.

So here we go!
Start your image VM, and install the new instant provisioning and other changes you want to make.
Once you are done shutdown your server, so we can update the image.

Ok, login on the vWorkspace console and go to locations – your location – session hosts – provisioning. Right click the created computer group “properties”, and go to “provisioning settings”.
Click Edit, the wizard will start again.

Next

The “VHD Timestamp” is my old VHD image time. So click update

That’s correct because we did not provision any RDSSH yet.

Now is my image up to date. Next

So the computer group is created, the image is imported and updated. Let’s create the first VM with hypercache.

Right click your computer group under “Provisioning” and click “Add computers”. The wizard will start:

Next


Choose the number of servers you want to create. Then you can say “Create Now”, or click next to change some settings we have added before.

Once the server is created you will see the following this in the vWorkspace console.

No you must wait until vWorkspace is finished.

In the meantime the image is copied to the Hyper-v host. But the server is already deploying the new server based on the parent VHD, this is because the server is loaded into the hypercache.
This means that the server can be online before this complete image is copied!

So now you can run server with hypercache. The last thing I will say is.

Have fun!

 

 

 

 

 

About the Author

Sander

No Comments

Comments are closed.