If you have been reading up about the features of Hyper-V 2.0, you probably read about Clustered Shared Volumes or CSVs. Basically, CSVs are the main ingredient to the (not so) secret sauce that makes Live Migration work.

A clustered shared volume can be created from any existing volume in a failover cluster. If you have an existing volume formatted with NTFS, you can mark it as a CSV and it will show up in the Failover Cluster Manager as a CSV. Note that existing data on the NTFS volume is not touched in any way.

On the compatibility side you should know the following:

1. CSVs in Windows Server 2008 R2 only support Hyper-V
2. There are no special hardware requirements and you can use the same technologies as a standard cluster disk: iSCSI, FC, SAS
3. There is no limit on directory structure
4. No agents or other software needs to be installed
5. Not another file system – it is standard NTFS

Note that this is not a clustered file system like VMware VMFS of Sanbolic’s Melio FS. There is no distributed lock manager or anything like that. What CSVs deliver is a distributed access file system.

CSVs provide a single consistent file name space. This means that every node in the cluster has the same path to the volumes. You will see the CSVs under the %windir%\ClusterStorage directory. For example:

• c:\ClusterStorage\Volume1\<root>
• c:\ClusterStorage\Volume2\<root>

The only thing you need to do after adding the CSVs is to put VHDs on the clustered shared volume (using the paths shown above) and create the virtual machine using Hyper-V Manager making sure that you put the configuration files on the CSV as well. You can then use the Failover Cluster Manager console to make the virtual machine highly available just like how you do it now. Basically, the only thing that changes here is the creation of the CSV and making sure that you place your virtual machine on the CSV. All the other steps are exactly the same as how it currently works.

With the current implementation of Hyper-V, you need to put each virtual machine in its own LUN if you want the virtual machines to failover to different hosts or if you want to quick migrate the virtual machines independently from the others. CSVs in Windows Server 2008 R2 remove this limitation. This also results in less wasted storage space and basically a better storage management story.

From an architectural perspective you should know that only one node in the failover cluster still owns the CSV LUN. That node is called the coordinator and it basically manages how the disk access should work. There is one such coordinator for each shared volume. You do not have to worry about selecting a coordinator as that is taken care of automatically. When the coordinator fails, there is no impact on virtual machines that are not running on the coordinator itself.

Microsoft did not provide any clear information about how the access to disk is actually performed. Basically the answer to our questions was that the coordinator decides what the best path to the storage is: direct access or over the network. Yes, you read that right: access to the LUN from one node might be redirected over the network via SMB to another node that writes to the LUN. Again, I have no information about when that exactly happens.

We also learned that the implementation of CSVs is done with a mini file system driver called CSVfilter.sys. Being a new filter driver, there might be some impact on other components such as backup software. Microsoft is working with backup and storage vendors and its own DPM team to clear up these issues. What I can say is that there is a new VSS API call called PrepareVolumeForSnapshotSet and that this needs to be used by VSS Requesters. The node that initiates the VSS backup also needs to become the coordinator node (happens automatically) because it needs to manage exactly what happens with the CSV volumes. The CSV volumes stay online during the backup but there will be no direct I/O until the backup ends. I guess that means that access to the LUN from other nodes will go over the network to the coordinator and from there to the LUN.

What is my take on this? Well, it seems like an overly complex solution to make something like Live Migration and HA work for individual virtual machines on a single bigger LUN. I guess that results from the fact that Microsoft decided to work with the existing NTFS file system instead of creating a dedicated file system optimized for virtual machine storage. On the other hand it does deliver extra features such as SAN I/O redirection over the network when the storage path to the SAN array completely fails.

More information about CSVs can be found in the R2 reviewers guide.

As the name implies, this session presented an overview of all the new features of Windows Server 2008 R2 without going too much in the details.

Server Core

When compared to the full version of Windows Server 2008, Server Core has a 40% reduction in patches. Although the initial release of Server Core works well, the lack of .NET support was kind of an issue. In R2, a subset of .NET is supported. In addition, a subset of ASP.NET is supported as well. PowerShell 2.0 is also supported and a demo showed how to use the new PowerShell graphical editor to issue a remote PowerShell command to a Server Core box.

Virtualization

Again, Live Migration with Hyper-V 2.0 was discussed with the recommendation to trigger Live Migration with SCVMM 2008. They briefly mentioned CSVs (Clustered Shared Volumes) but I will follow another session to get a clearer picture of that technology. Hyper-V will support 32 logical CPUs and SLAT (Second Level Address Translation) that takes advantage of the support in newer CPUs for hardware memory management (Intel EPT, AMD RVI).

They then switched to Terminal Services that is now renamed to Remote Desktop Services although not much more was said. Note that R2 will have support for VDI where the TS Session Broker (now called RDS Session Broker) will be able to direct a user to a session on a desktop instead of a terminal server. You can find some more detailed information here.

Management

At last there will be a remotable Server Manager, although that really should have been a part of the first release. PowerShell 2.0 seems interesting because there will be cmdlets to explicitly manage Windows Server 2008 R2. This is the case for Failover Clustering for example, where the cluster.exe tool will be replaced by PowerShell cmdlets. In R2, cluster.exe will still be available though.

Active Directory

The new Active Directory Admin Center looks promising as does the new recycle bin feature. There is a new domain mode for R2 that will activate this recycle bin feature.

Better together with Windows 7

The two main features here are DirectAccess and BranchCache. DirectAccess provides a way for Windows 7 clients to seamlessly access the corporate network using either SSTP or IPSec.

I already discussed BranchCache here and you can find other information on Kurt Roggen’s blog as well.

Some extra features worth mentioning are enhanced GPOs (more settings) and BitLocker on removable drives.

IIS 7

IIS 7 will have support for ASP.NET on Server Core. From the management point of view, there will be PowerShell cmdlets that run on Server Core as well. As expected, FTP 7 will be included in R2. Now, this is a separate download.

Conclusion

The session provided a basic overview of many of the new features the most notable ones being Hyper-V 2.0 with clustered shared volumes (CSV) and Live Migration!

This was an interesting session that started with the different models that customers are following when it comes to branch offices:

1. Centralized
2. Distributed

With the centralized model, one of the biggest issues is performance across the WAN with high latency and typically still a high price. When customers follow the distributed model, they usually place infrastructure roles (print, DNS, DHCP, domain controllers) and LOB apps in the branch.

Microsoft has a commitment to improve the branch office deployment scenarios and does this on three levels:

1. Improve the protocols
2. Provide different features for servers in a branch (e.g. RODC)
3. WAN optimization

The protocols were already improved in Windows Vista and Windows Server 2008 with the new TCP/IP stack and features such as the auto-tuned TCP Receive Window Size. They actually made the protocols aware of the underlying network conditions to adjust the behavior accordingly.

On the application level (and here that means SMB or CIFS) we have SMB 2.0 for a while now. SMB v2.0 performs less roundtrips, puts multiple commands in a single packet and makes parallel requests to improve performance.

Functionality on top of the application level will be improved in Windows 7 with a new mode for Offline Files called “Usually Offline”. In this mode, your offline files are transparently synchronized in the background at fixed intervals. These intervals can be configured by the administrator.

The most interesting feature that was discussed was actually BranchCache. BranchCache is a Windows 7 / Windows Server 2008 R2 feature that caches files that are retrieved over the WAN for speedier retrieval afterwards. BranchCache has two modes:

1. Distributed
2. Hosted Cache

In the distributed mode, clients running Windows 7 work together. When a client gets a file from the main office across the WAN, the client stores this file on its file system and a unique ID is returned. When a second client tries to get the file from the main office, that client gets the unique ID from the server and multicasts that ID on the local subnet to check if other clients have that same file in their cache. If they have, they retrieve the file from a local client.

Note that for this to work, the clients need to be in the same subnet. The clients still have to go across the WAN to issue a request in order to retrieve the unique file ID from the remote server and to make sure that the user retrieving the file is authorized.

With the hosted cache mode, you actually have a server in the branch office that caches the content instead of have the cache distributed among clients in the branch.

Note that BranchCache works with file server and HTTP/HTTPS content.

The session went on with a couple of other new features in Windows Server 2008 R2:

• ReadOnly DFS replicas: to prevent accidental deletes of files and complete directories at a branch
• Server Core: .NET support for Server Core to run applications and things like SCCM distribution points.

To end, they discussed WAN Optimization Controllers from Citrix and Cisco that run Windows Server and also provide things such as DNS, DHCP, RODC, print, etc… This actually makes a hybrid scenario possible where LOB apps are centralized but access is accelerated using these controllers. At the same time, the controllers provide infrastructure services that are still useful in the branch.

It was an interesting session that provided useful information, especially about the new BranchCache feature.

The keynote was presented by Brad Anderson and immediately started with the IT priorities of this day and age such as cloud computing, green IT, business intelligence and compliance. The key point here was that businesses need to drive down costs and expand business capabilities at the same time and that this is something you can do with Microsoft’s solutions. Everything can be turned into an advantage and it is not the first time I hear that you can take advantage of an economic downturn like this.

Then Brad talked about Dynamic IT that makes IT less of a cost center and more of an asset to the business. Microsoft focuses on four areas to make that happen:

1. Unified and virtualized approach
2. Model driven
3. Service enabled (cloud or not)
4. Focused on the user

These things are not new and were also discussed during last year’s keynote.

The focus then shifted to virtualization that you have to see as a strategy and not as a bunch of products. They demoed Hyper-V 2.0 that is a part of Windows Server 2008 R2. Of course, the demo showed the Live Migration feature but also focused on the importance of managing both your physical and virtual infrastructure with SCOM 2007. And of course, SCOM 2007 integrates nicely with System Center Virtual Machine Manager (SCVMM 2008) with the PRO tips. Essentially, SCOM delivers these tips to SCVMM where they can be implemented by the administrator or where they can be automatically implemented. This is especially useful when combined with Live Migration to optimize running workloads during business hours based on application knowledge from SCOM.

Microsoft of course uses virtualization from the datacenter to the desktop and with tools such as the acquired technology from Kidaro (now called MED-V) this becomes more and more clear. Brad also talked about the fast adoption of MDOP (Microsoft Desktop Optimization Pack) that includes App-V.

Then the presentation went on about datacenters and the fact that Microsoft are building several new and large datacenters with a big focus on green IT. Microsoft needs those datacenters to provide cloud-based services such as those announced last week (Azure) but also offerings such as Exchange Online and SharePoint Online. Brad stressed that they are actually learning from these implementations to improve their management products and that they are moving closer and closer to the Dynamic Datacenter where technologies such as hardware virtualization and software virtualization are combined. In fact, they are working to extend App-V features to server applications to make it possible to assemble a solution by combining operating system images with application images.

Then the focus shifted to Operations Manager 2007 R2 where they will extend management capabilities to Linux and Solaris. They actually make use of things such as OpenPegasus and OpenWSManagement to make this work. A new feature called ProblemPath was demonstrated. ProblemPath actually highlights the path to a problem in Diagram View to clearly show where the problem is situated. The beta of R2 will be available shortly.

The next section dealt with Windows Server 2008 R2 where they focused on the four main areas of improvements:

1. Virtualization: Hyper-V 2.0 with Live Migration, improved Terminal Services and VDI
2. Management: PowerShell 2.0 and a bunch of cmdlets to manage Windows
3. Windows 7 and R2 better together:: DirectAccess, BitLocker To Go and BranchCache
4. Web improvements

They they actually demoed BranchCache where you can actually configure a file server to cache content from a location over the WAN to improve access times. It’s good too see technology like that making its way to Windows as an out of the box solution.

Next, they talked about the next version of SQL 2008 called Kilimanjaro. Interesting in that release are the self-service BI features. They will make it easier for end-users to perform analysis, create reports and share their work with their co-workers. The demo was actually quite interesting and it is something I need to take a better look at in the coming months.

Of course, no keynote these days can be complete without saying something about cloud computing and this one was no different. Microsoft wants to offer choice to the customer when it comes to using their products. A customer can run the products on-premise, partner hosted or Microsoft hosted. In any case, users use the tools they know to work with these services. They then demonstrated Exchange Online by synchronizing Active Directory with the online service, enabling users for an online mailbox and migrating the mailbox from the customer’s server to the Microsoft servers. I already talked about this in a previous post and it is pretty easy to set these things up. Note however that passwords are not synchronized and that for now, there is no free/busy synchronization available.

To summarize it was a decent keynote that mainly put extra emphasis on things we knew already. Microsoft is clearly going forward in the virtualization and management space with a set of products that integrate well and are able to manage the physical and virtual world with the same toolset.

This week, I had to change the VirtualCenter certificate in our test environment. Changing the certificate is not that straightforward but there is quite some information available on the net. I used the information in this post: http://lraikhman.blogsite.org/?p=41.

Basically, you use OpenSSL to generate a public/private key pair and a certificate request. You then pass the certificate request to a certificate authority. I used a Microsoft Enterprise CA running on Windows Server 2008. When you obtain the certificate from the CA, you create a pfx file with OpenSSL that contains the private key and the certificate. You can then copy the files to your VirtualCenter server.

Note that when you generate the pfx file with OpenSSL, you will be asked for a password. To use the pfx file, for example to extract the certificate or the private key, the password is needed.

Now if you follow the steps you will be unable to use your existing sysprep customizations in VirtualCenter because the administrator password that is encrypted in the customization file cannot be decrypted. You will see something like:

The reason for this error is quite simple: VirtualCenter cannot get to the data in the pfx file because the password you used to protect the pfx is not correct. It seems that the password you need to use for the pfx file is testpassword. I got that information from here.

To summarize: to change the VC certificate use the steps in http://lraikhman.blogsite.org/?p=41 but when you are asked for the password during pfx creation use testpassword.

On Thursday, I went to a Microsoft TTT course about BPOS in Schiphol, The Netherlands. The abbreviation TTT stands for “train the trainer”. It’s basically a course that tells you how to deliver the training yourself and as such it is targeted to Microsoft partners.

Microsoft BPOS or Business Productivity Online Suite is a collection of hosted services for customers that do not want to implement them on-premise. BPOS should be available for purchase in the United States in November. In Europe, the target date for general availability is the first half of 2009.

BPOS is available in several versions but the course only covered the standard version. The standard version basically uses a shared model and as such does not allow for a lot of customizations. 

The following services were covered in the course:

• Microsoft Exchange Online (including Microsoft Exchange Hosted Filtering)
• Microsoft Office SharePoint Online
• Microsoft Office LiveMeeting

The course did not cover Office Communications Online.

Let’s take a brief look at the services in the following sections. Note that I am writing here about the standard version of BPOS.

Microsoft Exchange Online
This service provides Exchange Server 2007 functionality to users. By default, every user gets a 1GB mailbox that they can access with Outlook 2007, Outlook Web Access or a mobile device that can handle Server ActiveSync (Windows Mobile, iPhone, …). Extra storage can be purchased at a relatively low price. The end-user functionality is the same as with regular on-premise Exchange because the same server and client software is used.

From an administration point of view however, Microsoft Exchange Online provides only basic features. As an administrator you can create contacts, distribution lists and rooms. You can configure multiple domain names and set one domain as the default. When you add domain names, you just need to modify your MX records in order to send all mail to Microsoft’s hosted filtering servers.

I should note here that it is possible to split your users in online users and on-premise users. This is handy in a transitioning scenario where you slowly move users to the cloud. To make this scenario work, Microsoft provides a synchronization tool and a mailbox migration tool. In this scenario, your mail should still go to your on-premise servers. Those servers will then process all mails and forward mails to online users if needed. Although this scenario provides mail routing coexistence, it does not provide free/busy time synchronization making the planning of meetings with online and on-premise users a hassle.

You cannot configure things such as ActiveSync policies, journal rules, transport rules, Send As and many others because these settings are not exposed in the management interface or are (for now) difficult to implement in a shared environment.

Microsoft Office SharePoint Online
This service provides MOSS 2007 (Microsoft Office SharePoint Server) functionality to users. Indeed, Microsoft uses MOSS instead of WSS but they do not expose the full set of features to users and administrators. You can create sites and everything else you create in a site such as document libraries and lists. You can customize the site using SharePoint Designer. You can, for example, create workflows with SharePoint Designer or add a data view web part. Note that customizations cannot include custom code. Interestingly, browser-based InfoPath forms are not supported. However, you can create and use InfoPath forms with the InfoPath client.

Note that today it is not possible to access SharePoint sites using a custom domain name. So something like https://sales.contonso.com is not possible. Instead, you need to access sites using the URL provided by Microsoft. Luckily, the sites you have access to are listed on the user’s home page. The user can access the home page using https://home.microsoftonline.com. Click the picture below to see a screenshot of the home page.

Microsoft Office LiveMeeting
The LiveMeeting service in BPOS is basically the same as the existing LiveMeeting online service. In fact, BPOS uses the same infrastructure. All users that are enabled in the BPOS management console can initiate a LiveMeeting session with up to 15 people. This is different from the full Microsoft Office LiveMeeting Online offering where a session can have over a 1000 people.

Conclusion
BPOS standard is an easy way to provide your users with an e-mail account and collaboration services without having to invest in infrastructure components such as servers and storage. The management is extremely simple when compared to the full on-premise solutions but you also have less features especially for SharePoint.

The System Center User Group Belgium organizes their second event on Tuesday Oct 14th. Karandeep Anand, a Senior Program Manager on Data Protection Manager will be the speaker.

The event is held at Microsoft. For full details and registration, head over to the SCUG Events page.

I just finished watching Microsoft's virtualization launch event keynote. A couple of things to note from the event and announcements:

• System Center Virtual Machine Manager 2008 (SCVMM) will be released within 30 days.
• Hyper-V Server will be available as a free download within 30 days.
• Windows Server 2008 R2 with the next version of Hyper-V wlll contain a live migration feature.

I am quite interested in the Hyper-V Server product. It is a stripped down version of Windows with just the Hyper-V role, meant to compete with VMware's ESXi product. It's like Server Core except even more stripped down with some extra commands to configure the server. To manage Hyper-V server, you will have to connect to it from a remote machine with the Hyper-V management console or the SCVMM Administration Console. Be aware of the fact that there is no clustering for this version of Hyper-V. In contrast, ESXi can be clustered but then you will have to pay for the appropriate licenses.

The keynote in itself was not very interesting because most of these things were known or could be expected.

A hot topic with any virtualization platform is virtual machine backup. Besides the traditional backup with a backup agent in the guest you can also backup the complete virtual machine as it sits on the file system on the virtualization host (in this case Windows Server 2008). Naturally, you will not want to shutdown your virtual machines just to take a backup so Hyper-V supports hot backups of running virtual machines with the Hyper-V VSS Writer.

Let's first see if the Hyper-V VSS Writer is available on the host. Issue the following command:

vssadmin list writers 

In some instances, the Hyper-V VSS writer is not listed even though Hyper-V is installed on the host. This could be due to broken symbolic links in the following directory: C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines. Remove the broken link files and issue the vssadmin list writers command again.

We will now perform a manual backup with the help of the Windows Server 2008 diskshadow.exe command. Open a command prompt and issue the diskshadow command. You will get a prompt inside diskshadow. Issue the following commands:

set context persistent

add volume <driveletter> alias <alias_you_choose>
(for example add volume s: alias svolume)

set verbose on

create

When you enter the create command, the VSS operation will create a new shadow copy. In the output you should see something like:

At the end of the output, you should see:

You can now enter the following command in diskshadow:

expose %alias% x:
(for example expose %svolume% x:)

The last command mounts the shadow copy on drive x: so that you have access to the backup. If you look at the contents of drive x:, it will be the contents of the volume you specified at the time the backup was taken. You can now copy the files from drive x: to some other location.

Note that the Hyper-V VSS writer will take care of the consistency of the virtual machines both outside and inside the vhd file. As long as you are using the integration components in the virtual machine (as you should), the virtual machine will stay running during the operation. If the volume contains virtual machines that do not have integration components, these virtual machines will be suspended to disk before the shadow copy is made and resumed afterwards. In that case, the shadow copy will contain the .bin and .vsv file with the state of the virtual machine at the time of the backup.

Inside the virtual machine that has the integration components you will see events in event viewer that indicate VSS activity:

A couple of notes on this process:

• You can use add volume multiple times for different volumes. Naturally, for each volume a shadow copy will be created.
• If you turn off the backup support of the integration components (can be done from Hyper-V manager or SCVMM 2008), the writer will suspend/resume the virtual machine.
• You can integrate the Hyper-V VSS Writer with Windows Server 2008 Backup. See http://technet.microsoft.com/en-us/magazine/cc895627.aspx for more information. By default, Windows Server Backup is not configured to use the Hyper-V VSS Writer.
• Backup software vendors are working to include support for the Hyper-V VSS Writer. BackupExec for instance should have support in version 12.5.

A following post will discuss how to restore a virtual machine from the backup location.

My colleague, Tim Jacobs, has published a good article covering virtual machine backups and VSS integration. In my opinion, VSS clearly is the way to go because the VMware sync driver or other proprietary solutions just don't cut it. Microsoft already included VSS support in Virtual Server 2005 R2 SP1 and also has it in Hyper-V.

Check out the article on his blog.

In the previous post, I talked about creating highly available virtual machines on Hyper-V and the fact that SCVMM can only create virtual machines on unused storage. The standard tools such as Hyper-V Manager and Failover Cluster Manager do support multiple virtual machines on the same volume (with a hotfix). So what happens to SCVMM in that case? Have a look at the screenshot below:

The virtual machines are in an unsupported configuration and cannot be managed from SCVMM (no starting, stopping etc...). This will probably be fixed in the final release but if you are testing the product now you know what to expect.

When you need to create a highly available virtual machine running on Microsoft's Hyper-V you need to do so on a Failover Cluster. In this post I will show you how to create a highly available virtual machine on a two-node Windows Server 2008 cluster. The cluster is using simple desktop machines with storage on an MSA2012i SAN (iSCSI).

There are two ways to create the virtual machine:

1. Use the Hyper-V Manager in conjunction with Failover Cluster Management.
2. Use System Center Virtual Machine Manager 2008 (SCVMM).

The first method is a bit clumsy because it involves two different consoles. That method, however, has more flexibility as you will see later. Let's take a look at the first method and see how you could create a virtual machine in the cluster on a shared volume.

Creating the virtual machine without SCVMM
Without SCVMM you need Hyper-V Manager and Failover Cluster Manager. To start, you need to have a volume available to the cluster. In my case, I had a volume with drive letter S: as available storage to the cluster as shown in the screenshot below.

Even a volume that is not part of a service or application (a resource group in old terminology) is owned by a particular host. In the screenshot you see that hyperv2 owns the disk.

The next step is to use Hyper-V Manager to create a virtual machine. It is important that you store both the virtual machine configuration and hard disk(s) on shared storage. To create the virtual machine, open Hyper-V Manager on the host that owns the disk and create a new virtual machine as shown below. This is the same as on a standalone host as this tool is not aware of the cluster.

A wizard will start to create the virtual machine. Just follow the wizard and make sure you use shared storage. We can now proceed to the next step and that is adding the machine to the cluster.

Now open Failover Cluster Management, right click Services and Applications and click Configure a Service or Application. A wizard will start. Follow the wizard until the screen below and select Virtual Machine (only available when Hyper-V is installed):

When you click Next, the wizard will enumerate the virtual machines on shared storage so that you can select them:

After the virtual machine has been selected, continue the wizard. The end result will be a new service called Virtual Machine with two resources (well, actually three): the virtual machine configuration, the virtual machine and the storage volume. The screenshot below illustrates what you see in the Failover Cluster Management console after running the wizard a few times to add other virtual machines on the same volume.

You can now start the virtual machine directly from Failover Cluster Management and install a guest operating system. If you need to attach an iso first, you will need to use Hyper-V Manager. The Failover Cluster Management tool provides an easy way to start Hyper-V Manager. Just right click the service (here called by default Virtual Machine).

From the moment the virtual machine is part of the cluster you will need to perform actions such as stopping, shutting down and saving state from Failover Cluster Management. If you use Hyper-V Manager to stop the virtual machine for example, the cluster will restart the virtual machine again (with the default resource settings).

Creating the virtual machine with SCVMM
SCVMM, being the 'single pane of glass' for virtualization management provides a way to create new virtual machines on both clusters and standalone Hyper-V hosts. Before you can create a virtual machine on a cluster you need to add the cluster to SCVMM. From the Actions pane, select Add Host as shown below:

In the Add Hosts wizard, type the cluster name in Host server name and press Enter. The cluster should be added to the list as shown below:

Now continue the wizard to deploy the SCVMM agent on each node in the cluster (=automatic). The cluster will be shown in SCVMM as shown below:

Adding a virtual machine is easy but the current beta of SCVMM has some limitations:

• SCVMM only supports one virtual machine per cluster volume. This effectively means I need one LUN per virtual machine, something I need anyway if I want to 'Quick Migrate' individual virtual machines.
• SCVMM only supports volumes with drive letters (no mount points).

Before you create the virtual machine, make sure there is available storage in the cluster that is not used by any other virtual machine. To create the virtual machine, just select New Virtual Machine from the Actions pane at the right to launch the wizard. The wizard is straightforward but you should not forget to configure the virtual machine as highly available. You do so from the Configure Hardware dialog in the wizard. Scroll to the bottom where there is an Availability section. When the wizard is finished, SCVMM will have created a new service in the cluster called SCVMM vmname Resources. You can now start the virtual machine from SCVMM and start installing a guest operating system.

Conclusion
Creating a highly available virtual machine is easy but as you have seen, there are several ways to do it. There are also some discrepancies between what you can do with and without SCVMM. The final version of SCVMM will have to solve this so that you can truly use it as your primary management tool for Hyper-V.

REMARK: I my setup I installed the following hotfix: http://support.microsoft.com/?id=951308. This hotfix provides more functionality and virtual machine control for Hyper-V in a failover cluster.

I got my hands on an HP MSA2012i and thought I'd share some of the configuration screens with you. Part of the HP StorageWorks 2000 Modular Smart Array family, this particular model is the iSCSI model with one controller (it is not meant for production so we did not need the 2nd controller). The MSA2012i has twelve SAS drive bays for 3.5 inch disks and we filled it with 146GB 15K disks. There are two other models: one fibre channel and one SAS.

Each controller has three ethernet ports, one for management and two for data access. I connected the management port to our network and pointed my browser to the IP address assigned by our DHCP server. After logging in with username manage and password !manage (defaults) the configuration can start.

The first thing to do is to configure the ethernet ports. To configure the data ports, go to General Config and then host port configuration:

The addresses above (port 0 and port 1) are used for the iSCSI discovery process and of course disk access as well. In the Microsoft iSCSI initiator for example, you would set one of these (or both) in the Discovery tab:

The MSA2000 works with the concept of vdisks and volumes. A vdisk is nothing more than a collection of physical disks configured with some protection level (RAID5, RAID10, ...) and optional spare disk(s). There are two ways to create a vdisk:

1. Automatic virtual disk creation (policy-based)
2. Manual virtual disk creation (detail-based)

The policy-based method just asks you for a fault tolerance level (none=RAID0, medium=RAID5 or high=RAID50), the size of the vdisk in GB and the number of volumes to create in the vdisk.

I will show manual disk creation to create a vdisk with 11 disks and one spare (no best practice or anything, just demo). The first screen asks for the vdisk name and the RAID level (RAID0, 1, 3, 5, 6, 10, 50):

The second screen asks for the disks and whether or not you want spare drives:

The third screen asks for the spare disk(s):

After clicking continue, a summary is shown with a button to create the vdisk:

After clicking Create Virtual Disk, the vdisk will be created and initialized. Initialization can take a long time but during that time volumes can already be created and used.

The next thing to do is to create volumes. Let's create a 100GB volume on the vdisk we just created. From the Volume Management section at the left there is the add volume option. In the screenshot below, a volume of 100GB is created without assigning a LUN number. When you assign a LUN number you present the LUN globally. If you do not want that you set LUN to NONE and assign the volume to a host from the volume mapping link.

After clicking Add Volume the volume is shown in the volume map of the vdisk:

To map the volume to a host:

Of course, hosts don't just magically appear in the above list. You can add hosts manually (there is a link somewhere in the menu at the left) or make them appear by using the iSCSI initiator on the host to connect to the MSA target. When the volume is mapped to the host it will appear if the iSCSI initiator was configured correctly:

As you can see, configuration is very simple although not as easy as an Equallogic box, a reference for configuration simplicity. I did notice one bug though and that is the fact that every other vdisk is owned by the second (in our case, non existent) controller. This might be solved by a more recent firmware though.

Application link is a feature VMware added to the Thinstall product they acquired a while ago. As the feature name implies, it allows you to link ThinApp'ed applications. You could for example link a browser to a Flash plugin or a Java plugin. In this post I will show you the basics of application link. I will link Opera 9.5 to a Flash plugin. The steps to get this to work are as follows:

1. Create separate projects for Opera 9.5 and the Flash plugin.
2. Configure the package.ini of Opera 9.5 with the application link.
3. Deliver the packages to end-users taking into account the placement of the plugins.

This post does not discuss the first step. Check the two previous blog posts to see how to do that. When you create the project for the Flash plugin, download a standalone installer for Flash and use it during Setup Capture. I ended up with the following projects:

The second step, configuring the application link, is easy. In the package.ini of Opera 9.51 you will find the following line:

Just remove the ; in front of the highlighted line and build the project using build.bat. With this default configuration (plugins\*.exe) you need to put a plugins folder in the folder that contains Opera.exe:

The Flash project resulted in a file called NPSWF32_FlashUtil.exe and that file is put in the plugins folder. Because application link is configured with *.exe, the plugin will be picked up at runtime. It does not matter where the exe's are located. They can be put on the local workstation, a USB drive or a network share.

In the previous post I showed you how to install ThinApp and run a Setup Capture. Unless you are completely new to the technology, those things are rather straightforward. Now we will take a look at some other aspects of the package building process.

Setup Capture generates a project that you can customize before the build process. The default project location is in C:\Program Files\VMware\VMware ThinApp\Captures\. As an example, I chose to virtualize Opera 9.5 and that resulted in this project folder: C:\Program Files\VMware\VMware ThinApp\Captures\Opera 9.51.

When you open the project folder you will get something like in the screenshot below.

One of the most important files is the package.ini file because it contains parameters that drive the build process. The VMware site has full details about the settings in package.ini here.

Some interesting parameters can be found in the general purpose parameters section:

• SandboxName: the sandbox is the location where the user's application settings are stored. By default that is %appdata%\Thinstall\SANDBOXNAME. %appdata% is a directory in the user's profile that can be redirected to a network location using Group Policies. Note that VMware did not change Thinstall to ThinApp here.
• PermittedGroups: to configure who is allowed to run the application
• RemoveSandboxonExit: to clear the sandbox when the user quits the application, useful when you always want the user to start from the default settings in the package.
• SandboxNetworkDrives: to allow or disallow access to network drives from the package. Access is allowed by default.
• SandboxRemovableDisk: similar to the network drives setting but for removable disks.

Near the end of package.ini you will find the entry points to the application. In my case there is a section called [Opera.exe]. In some cases you will find other entry points that you don't need. In my case I had entry points called [cmd.exe], [regedit.exe] and [iexplore.exe]. Although you can disable these entry points during Setup Capture I usually remove them from package.ini afterwards as well.

Now that you know about package.ini, let's build the project. In the project folder there is a batch file called build.bat. Just run that file to start the build. It's that simple! You will get a new folder called bin. In my case there are two files:

You can just take the opera.exe application and run it on another computer. One of the strengths of ThinApp is the fact that it is agentless. It is agentless because the virtualization engine is actually included in each executable that is generated.

When you run a ThinApp'ed application you get the following in the right bottom corner of the screen:

The application then starts as if it was installed locally. In virtual Opera, I added my blog to the list of bookmarks. Since that is a user preference, it is saved in the sandbox at C:\Documents and Settings\USERNAME\Application Data\Thinstall\Opera 9.51. You should note that by default, if you install add-ons like Flash, they are also installed to the sandbox. When you delete the sandbox directory and start the application again you start with default settings in the package. Talk about a simple way to reset the user environment on a per application basis.

The features described above are essentially the same as in Thinstall 3.0. VMware added some new features like Application Sync and Application Link but that is for another post.

I just downloaded ThinApp 4.0 from the VMware website. The screens below show the installation screens and setup capture screens to have some idea about what the product looks like.

The installer is very small (around 7MB). I created a Windows XP virtual machine in VMware Workstation, installed ThinApp 4.0 and created a snapshot. The snapshot allows me to revert to it after creating a package in order to start with a clean machine whenever I create a package. Note that it is recommended to start the ThinApp setup capture process from a network share instead of installing it on your capture workstation.

First, let's start the installation.

You have to enter a serial number and license display name. You can get a trial key at www.vmware.com for 60 days. The trial includes VMware Workstation 6 as well if you don't have it yet.

After installation you get the following shortcuts in the Start Menu:

With ThinApp Setup Capture you capture the installation of a piece of software. When launched, you get the following screens:

Of course, you need to run setup capture on a clean computer. The next dialog tells you that but also allows you to set advanced settings.

The advanced settings:

You normally don't need to change anything in the Advanced settings. Continuing with the setup wizard, the prescan starts. Scanning is very fast.

When the prescan finishes you get the dialog below. Now it is time to start an installation. I installed Opera 9 (not shown).

After installation, you click Next in the dialog above. ThinApp can now start the postscan in order to determine the differences.

Now you can select the entry points. Multiple entry points are possible, for example when you virtualize Office with Excel, Word and PowerPoint.

You can configure the application so that only specific users can run it. AD groups are used for this purpose. The sandbox location is a location where ThinApp can store the user's settings. If the user sets favorites in Opera for example, they are stored in the sandbox.

The next dialog asks for the isolation mode. The explanations in the dialog speak for themselves.

You can accept the default location for the project. The MSI generation checkbox is not checked by default. It generates a standard MSI that can be deployed to user's desktops with tools such as Altiris or SCCM 2007.

The project is then created.

In the final screen you can browse the project and make changes or build the project. I will not do that and click Finish to end the capture.

Note that when you just click Finish, your virtualized application is not created. You need to actually build the project for that. A next post will show you how the build process works without using the Build Now button in the dialog above.

From Arlindo's Blog I picked up that there is a hotfix to get SCVMM (System Center Virtual Machine Manager) 2008 to work with Hyper-V RC1. Now I can finally update my Hyper-V test system.

You can get the hotfix from http://connect.microsoft.com.

From Jorge's Quest For Knowledge I learned that there is a compatibility pack for Windows Server 2003 and XP clients that are deployed in conjunction with Read-Only Domain Controllers (RODCs). Because an RODC is read-only, several functions might not work as expected and those are described in KB article 944043.

Douglas Brown has written a reviewers guide for Virtual Desktop Manager 2.1. I am not sure if this guide is really needed as the VMware documentation is clear and the product is simple to install and use. However, if you are looking for one document that contains an overview from start to finish it is a very good read.

Get it here.

As a side remark it seems that Provision Networks VAS (Virtual Access Suite) still has the upper hand when you look at the features and the price of the product. They just need to put some extra work in their documentation, support site and troubleshooting FAQs because those leave a lot to be desired.