CSVs (v2) in Server 2012

CSVs (Clustered Shared Volumes) were introduced in Windows Server 2008 R2 for use with Hyper-V which suddenly allowed for you to migrate virtual machines from one node to the other. According to Microsoft the idea of the CSV went from design board to being production ready in around 12 months which is why when it first appeared it was only supported for use with Hyper-V – when you enabled CSVs in 2008 R2 you got the message below:

clip_image002

I don’t want to go into why to use CSVs as that has been covered many times over the past few years but as a high level overview a CSV is a clustered file system that allows multiple nodes in a cluster to have simultaneous access to a LUN. CSVs became popular because not only did it offer a huge improvement in fault tolerance but it also allowed the VM to become the smallest point of failover. Before CSVs if you wanted to move a single VM from one machine to another each VM would need to be on its own LUN – in other words the LUN itself was the smallest point of failover.

CSV provides I/O fault tolerance – A CSV is able to transparently handle a node, network and HBA failure. This is achieved as the app handle is virtualized before being handed to NTFS if there is then a problem the I/O can be appended on the CSVFS filter until the problem has been solved. An example of how this works is if you have a fibre connection to your fibre SAN and you have VMs running on a node utilizing CSVs, you accidentally disconnect the fibre the I/O will be paused, redirected I/O would be established via the coordinator node and then I/O can be resumed via this new path until you reconnect the fibre and everything is OK again. Without CSVs you would instantly have problems with the VMs – you would have downtime!

Now with Server 2012 Microsoft has gone back to its drawing board and has completely rewritten CSVs from scratch to build upon its success. CSVs in Windows Server 2012 are now known as CSVs V2 (imaginative!!)

So why do we need v2 CSVs and what improvements do they bring?

Even more fault tolerance and resiliency for high availability built directly in

  • IN CSV v2 SMB multi-channel is used to detect which network should be used as the CSV network. If there are multiple networks available Windows Server will use these channels to multi-channel stream I/O to your SAN.
  • CSV Block Cache – This allows Windows to provide a cache of un-buffered I/O. The cache runs at the block level which allows caching of data right inside the VHD file. There have been caching systems like this on the market for a while but they have always been hardware based with SSD this is different as Windows Server 2012 has it built in and it utilizes system RAM (you need to factor this when looking at your hardware although by default the cache level is 512MB as Microsoft have found this gives the optimal level of performance with the minimum cost). This can dramatically improve a VDI deployment on Hyper-V (I plan on doing a demo if this in a future post.)

Les time spent in redirected I/O mode

  • Hugely improved backup interoperability. In 2008 R2 (CSV 1.0) when you started a backup the CSV would be moved to the node that started the back and it would have to be accessed by the other nodes in a redirected mode for the duration of the backup. Your backup software would have to understand CSVs and be able to work with CSV APIs – not all backup software was updated to support this. With Server 2012 Microsoft have worked far more closely with vendors to make their software CSV backup aware. With Windows Server 2012 you are only in redirected I/O mode only for the short time the VSS snapshot is taken – for the rest of the time your nodes access the disk in direct mode.
  • You can have parallel backups running on the same or different CSV volumes and cluster nodes.

CSVs were originally only supported on Hyper-V workloads originally as Microsoft had to work out what file systems APIs etc. they needed to optimize to work with Hyper-V they did not have time to do this for more than Hyper-V.

In Windows Server 2012 far more workloads are supported including the file server workload which opens up a whole range of possibilities for fault tolerance with your file servers! This is achieved by having multiple levels of CSV I/O redirection. There is the original ‘file system’ redirection and two new levels; file level and block level redirection.

Multi Subnets are now supported.

CSVs are enabled by default unlike with Windows Server 2008 R2 where you had to enable CSV and then you were able to go and assign the disk as a CSV volume you simply right click on the disk and click ‘Enable Cluster Shared Volume’ and unlike with Windows Server 2008 R2 there is no separate area for the CSV disks they all show in the same window.

clip_image004

In CSV 1.0 custom reparse points were used in 2012 standard mount points are used instead which makes it far more readable and easy to understand. E.g. you not now use C:\ClusterStorage\Volume1 when trying to setup a performance count or trying to monitor free space etc. instead of the disk GUID which was not easily understood.

Removed the external authentication dependencies. The dependency on AD has been removed, being replaced by local user accounts which exist on each node of the cluster (they are synchronized).

You may have noticed a slow response when you try to browse the Cluster Volume folder any node other than the coordinator node – this will stop this from happening and it will also mean that there is no longer need to be a domain controller up and running before you can access the CSV volumes.

A mini-filter driver is no longer used it has been replaced by a CSV proxy file system. If you look in disk management you will see that the disks now show as CSVFS formatted (although it is still NTFS when you pull back the covers). This was required because now that CSV supports more than Hyper-V applications needed to know what they were running on. This will allow an application to detect it’s on a CSV volume, this will be useful if a particular bit of software will not be supported for CSV it can have a hard block coded into it. This new approach is also better than the mini-filter as the mini-filter driver sat above the file system and intercepted I/O which means it bypassed things such as AV. With the new file system approach you will be able to attach to this file system as you would with NTFS.

clip_image006

Supports the huge number of improvements made in file server areas such as:

  • Bit-Locker is supported on CSV volumes.
  • Fully supports Offloaded Data Transfer
  • Defrag improvements and check disk Spot Fix features.
  • Support for Storage spaces

That was just a very quick overview of some of the new features and improvements made for Cluster Shared Volumes in 2012. Next I’ll look at how VMware’s offering compares to CSV v2!

Advertisements

Hyper-V Replica in Windows Server 2012 – Amazing!!

UPDATE – Have a look here for some of the new features that Windows Server 2012 R2 will bring to Hyper-V Replica (its even more amazing Open-mouthed smile)

Hyper-v replica is one of the most highly anticipated features of Windows Server 2012. With it comes a whole new range of DR possibilities, something that would have not been possible or taken a large amount of money to achieve is now free and in the box!

The basic concept of Hyper-V replica is, as the name suggests, to replicate VMs from one site to another (or one live server to a backup server on the same site). Some of the possibilities that come to mind is the ability to replicate branch office VMs back to the main office location or from a main office up into the cloud to easily and very quickly recover in a DR situation.

How does replication work?

I have heard people when describing Hyper-v replica say ‘we can already do this with DFS’ – you can’t! DFS will only replicate a file when it has been closed and no longer in use (also Microsoft does not support using DFS to replicate VHDs /VHDXs for this purpose even if you turn the VM off).

Hyper-v replica is able to replicate the files even when they are in use in your production environment. Replication is achieved by an initial replica (IR) of your data being replicated from the primary server to the replica server (this can either be over the wire or a copy can be copied to physical media, taken to the backup server and then copied onto it. Once you have the initial copy in place, the primary server makes use of a change tracking module which keeps track of the write-operations that happen in the virtual machine.

Every 5 minutes (this is none configurable at present) a delta replication will take place. The log file being used is frozen, a new log file is created to continue tracking changes and the original log file is sent to the replica server (provided the last log file was acknowledged as being received). The changes can be seen by looking in the Hyper-V Replication Log (*.hrl) that is located in the same directory as it is associated to.

Types of delta replicas

There are a few options for the delta replicas. In the most simple case you will have selected ‘Store only the latest point for recovery’, in which case all of the replication log data is merged into the VHD file that was initially replicated to the Replica server.

The second possibility is that you have chosen to store multiple recovery points in which case when the log file is received every 5 minutes these are stored and every 1 hour / 12 log files (again this is none configurable) a snapshot is created to which the log files are written. The number of snap shots is determined by the number of recovery points you opted to keep when replication is configured. Once the limit is reached, a merge is initiated which merges the oldest snapshot to the base replica VHD.

The third possibility allows for an application consistent snapshot to be created. Application-consistent recovery points are created by using the Volume Shadow Copy Service in the virtual machine to create snapshots. The log file are sent every 5 minutes as with the two examples above but as the 12th log arrives the log files will create a snapshot (as above) and the snap shot will the app consistent (if you chose for an app consistent every 2 hours every other snapshot would be app consistent etc.)

If at any time on the Primary Server a new log cannot be created, changes continue to be tracked in the existing log and an error is registered. Replication will be suspended and a Warning is reflected in the Replication Health Report for the virtual machine.

Clustered Replica Servers

If your replica server is part of a cluster you may want to move the Replica VM from one node to another (or it may move automatically by use of VVM). To keep track of where the replica VM is the VMMS (Virtual Machine Manager Service) uses a new object called the Hyper-V Replica Broker Manager.

Hyper-V Replica Communications

Communications Architecture

Communications Architecture

The replica communications is achieved by the use of the ‘Hyper-V Replica Network transport layer’. This transport layer is responsible for authorizing access to a Replica server as well as authenticating the Primary and Replica servers. It also provides the ability to encrypt (if you are using a certificate), compress and throttle (with the use of QoS) data that is sent by the primary server.

The first connection to be made between the Primary Server and the Replica server is the ‘control channel’ the Hyper-V Replica Network Services checks to see if a control channel exists – if it does it will use it, if not it will create the connection and then transmits a control message which contains a list of files that will be sent from the Primary server to the Replica server (this is used if data transfer is cancelled mid-way through). Hyper-V Replica Network Services on the Replica server forwards the package to the Hyper-V Replica Replication Engine, which then sends a response back which contains information about which, if any, of the files already exist within a timeout interval of 120 seconds.

Once the control message has been acknowledged as being received by the Replica server data transfer can begin. This data transfer is done over a different connection to the control channel – called the ‘data channel’. The files to be transmitted will be either for an Initial Replication or for a Delta Replication. The Hyper-V Replica Network Service layer chunks the data into 2 Mb chunks and compresses it. Once the data chunks have been received by the Replica server they are decrypted and put back together before being saved to the save location specified for the replica virtual machine.

Hyper-V replica handle virtual machine migrations from one host to another and even storage migration during a data transfer. If migration of a virtual machine takes place while data transfer is in progress the Hyper-V Replica Network Service closes any open connections and will automatically re-establish connection with the Replica server once the migration is complete. The control message is used to do a comparison to see which files were missed due to the cancelled connection. The exact same procedure is used if a storage migration is carried out during a data transfer.

Configuring Hyper-V Replica

Hardware Requirements:
This is fairly simple – all you need is two servers capable of running the Hyper-V role. The replica site is completely hardware and storage agnostic.

Software Requirements:
Again there is not much to this – obviously Windows Server 2012 is required and also if you want to encrypt the data during transmission (defiantly recommended if you are replicating offsite to a DR center for example) you will need a certificate which can either be self-signed or provided by your PKI infrastructure.

There are two possibilities for the Replica server – either stand alone or a failover cluster.

To configure a standalone Replica server:

  1. Right click on the Hyper-V server on the Hyper-V Manager and ‘Hyper-V Settings’
  2. Click on ‘Enable this computer as a Replica server.’ You will need to do this on both the primary and Replica servers.
  3. Next you have a couple of options for authentication you can use Kerberos or an SSL certificate. To further enhance security you can select the servers you want to allow replication from. You can select any server or you can be more restrictive and specify servers by wildcard e.g. *.contoso.local or by actual server name MANHYP01.contoso.local.
Replication Config

Replication Configuration

  

To configure clustered Replica servers:

  1. Install and configure your failover cluster as you normally would and ensure you introduce enough nodes into the cluster to meet the demand.
  2. Once you have the cluster in place and configured as required right click on your cluster and go to ‘Configure Role’
High Availability Wizard

High Availability Wizard

  1. You will need to specify a NETBIOS name for the broker service that      you will use as the Client Access Point when configuring the VMs for      replication. This will create a computer object in AD for you.
AD Computer Object

AD Computer Object

  1. Next, right      click the Replica Broker you created and click on ‘Replication Settings’
Replication Settings

Replication Settings

  1. You will then see the configuration wizard as in the standalone configuration. You can select http or a certificate based authentication (this depends on if the remote cluster is part of the same domain or has a trust in place – if not you will need to use a certificate based approach) You can as before also select the servers that are allowed to replicate by server name or wildcard and you can select the security tag to use.
Authentication

Authentication

  1. Once the server is configured for replication you can then enable replication a per virtual machine basis. Instead of selecting the physical server to migrate to you need to select the Client Access Point e.g. in my case ‘HyperVReplica’.
Replica Server

Replica Server

Replication from this point on works in exactly the same way as described earlier with the log files being transmitted every 5 minutes. The newly created virtual machine on the Replica server will be made highly available.

Folder Structure for Hyper-V Replica

The standard folder structure you are used to with Hyper-V is created with the addition of a folder called ‘Hyper-V Replica’ with several subfolders as seen below (The Snapshots folder is only created if recovery history is enabled) with each of the virtual machines being identified by its GUID.

Storage Paths

Storage Paths

Networking with Hyper-V Replica

In a real world situation you would most likely be replicating your virtual machines off site to another office or to a partners DR facility over a WAN connection. The network addressing schema will obviously be different at this site and will cause problems for your users trying to access your servers. Microsoft has thought about this and has included the ability to configure different network settings at the Replica site.

Replica Network

Replica Network

To configure this you need to modify the virtual machine properties of each machine and each of the virtual adaptors connected to the machine. This is only available on synthetic network adaptors – you can’t set this for legacy adaptors. The only other pre-requisite for this to work is that your virtual machine must be running any of the following OS’s Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 SP2 (or higher), Windows 7, Vista SP2 (or higher), and Windows XP SP2 (or higher). The latest Windows Server 2012 Integration Services must be installed in the virtual machine.

Using Hyper-V Replica

Once you have all this in place and you are successfully replicating your VMs to another stand alone or cluster server you have a few ways to move over to your replicated VMs.

Planned Failover – A planned failover allows you to failover to your Replica VMs in a planned and controlled manor. This can be used if you have prior warning of an event that you know is going to cause potential problems to your primary datacenter such as a power outage or natural disaster etc.

In a planned failover reverse replication must be enabled (this is checked as a pre-requisite) so that when you failback your Primary VMs are up to date. The second pre-requisite to a planned failover is that the VMs must be shutdown prior to the failover taking place. Due to this a planned failover does require a small amount of downtime but no data will be lost.

Test Failover – A test failover is a good way to test your DR plan. When you initiate a test failover a new virtual machine is created on the replica server with the name <your VM name – Test> This VM is added to a different network (You can specify a test failover network on the VM properties) this is so it will not affect your live production environment. You can add a few test workstations to this test network and check everything works as required.

Test Failover Network

Test Failover Network

This type of failover does not require any downtime of your live production machines and so can safely be carried out during the working day.

The final failover is the un-unplanned failover – the one no-one wants!

Unplanned Failover – An un-planned failover is as the name suggests. This can happen if you have a hardware problem in your main datacenter or an environmental problem – failed generator during a power outage or failed air-conditioning unit (from experience!) and no redundancy. This allows you to bring up your replica VMs and get your users up and running very quickly. When you’re primary datacenter is up and running again you can simply replicate the VMs back and get everything back to how it was.

Although this is a great additional to a DR policy by no means is it a replacement to you back routine! You MUST continue to preform your backups as you are now.

NIC Teaming in Server 2012

Having spent the last few days battling with the HP Network Configuration Utility (HP NCU) Microsoft’s decision to do away with the need for third party NIC teaming software is a very welcome addition of Server 2012.

Microsoft have never officially supported NIC teaming for Hyper-V (if you had problems and needed to talk to Microsoft support, more than likely you would have to dissolve the team before you could progress your support call too far). I have seen many network related Hyper-V issues that have boiled down to either be NIC driver or a third party teaming utility not playing nicely.

Built in NIC teaming has been a long requested feature, VMWare have had NIC teaming for a while so it’s no great surprise Microsoft have decided to include it. A great feature of this teaming solution is that you will be able to take a NIC from any manufacturer and team them e.g. I could team an Intel and a Broadcom card into a single team. This gives you some great redundancy advantages – if you upgrade the Intel driver and it stops working, no problem the Broadcom can keep the team up and running.

Creating a team is simple – just go to the Server Manager > Locate the teaming link under server properties and follow the very easy wizard.

Next just select the NIC ports you wanted to be included in the team (you can have a whopping 32 ports per team – using LBFO I could have 32 x 10Gb ports (although that would come in at a hefty price) simply having 32x 1Gb ports allows for some extreme bandwidth! This will be very useful for networks such as the live migration, especially as now you can have simultaneous migration happening at once.

Next give your new team a name and off you go. There are a few more additional options you can set, such as:

Team Mode:

Static Teaming: This mode is supported by most server-class switches. As the name suggests this is a manual configuration on the switch and server to form the teams.

Switch Independent: You don’t need to tell the switch anything or connect to different switches – although you can (and should) for better redundancy.

LACP (Link Aggregation Control Protocol): This will dynamically identify the links between the server and the switch. This will allow for the automatic creating of a team. LACP could also expand or reduce the number of NICs in the team.

Load Balancing Mode:

Hyper-V Port: The switch will balance the traffic on multiple links, based on the destination MAC address for the virtual machine.

Address Hash: This is a simple algorithm approach. Based in the components of the packet it creates a hash, it then sends packets with that hash to one of the available NICs.

Stand-by Adaptor: The name says it all – but you can have an active, active or active passive set-up by selecting the NIC you want to be waiting in the wings in case one of the active ports runs into problems.

Once the team has been created you can easily add or remove ports as required. You will see your newly created team in your adaptor settings of the ‘Network & Sharing Center’ as you would any other adaptor and this is where you can set your IP addressing requirements.

Obviously all this can also be achieved with PowerShell using the module ‘Netlbfo’

PS C:\Users\Administrator> Get-Command -Module Netlbfo

CommandType      Name                                              
Function         Add-NetLbfoTeamMember                       
Function        Add-NetLbfoTeamNic                              
Function         Get-NetLbfoTeam                                     
Function         Get-NetLbfoTeamMember                        
Function         Get-NetLbfoTeamNic                                  
Function         New-NetLbfoTeam                                     
Function         Remove-NetLbfoTeam                                  
Function         Remove-NetLbfoTeamMember               
Function         Remove-NetLbfoTeamNic                         
Function       Rename-NetLbfoTeam                                  
Function        Set-NetLbfoTeam                                    
Function         Set-NetLbfoTeamMember                          
Function         Set-NetLbfoTeamNic    

To create your team:
New-NetLbfoTeam -Name “ProductionTeam1” -TeamMembers LAN04,LAN02,LAN03 -TeamingMode Static

PS C:\Users\Administrator> Get-NetLbfoTeam
Name                   : Production Team 1
Members                : {Ethernet 4, Ethernet 3, Ethernet 2}
TeamNics               : Production Team 1
TeamingMode            : SwitchIndependent
LoadBalancingAlgorithm  : TransportPorts
Status                 : Down

One VERY cool feature is that all of this will also work within a virtual machine! This will mean that a VM will be able to be connected to more than one virtual switch. This will provide great redundancy all the way though the network layer from physical switch through to VM.

I think this is a great new feature for Windows Server 2012 and I’m sure many people will be recreating their teams with this ASAP and uninstalling their 3rd party vendor applications.

Windows Server 2012 Hyper-V Component Architecture Poster

Microsoft have recently released their updated component architecture for Windows Server 2012 Hyper-V. Like the 2008 R2 version this latest version is HUGE and includes all you could want to know including the new cool 2012 fatures such as storage migration and Hyper-V Replica. You can download the 2012 version from the Microsoft download site.

Windows Server 2012 Hyper-V Component Architecture Poster

SCVMM 2012 Pre-Requisites

There are a few pre-requisites before you are able to perform an in place upgrade to SCVMM 2012, these include:

Software Requirements

  • You must be running SCVMM 2008 R2 SP1 (upgrading without the service pack is not supported!)
  • You must be running Windows Server 2008 R2 for the VMM Management Server. This has to be the full GUI version (i.e. not core). Standard, Enterprise and Datacentre are all supported. Note there is currently no support for running SCVMM 2012 on Windows Server 2012 (Server ‘8’ Beta) I’m sure this will come soon.
  • The server must be a member of a domain and the computer account cannot exceed 15 characters. Also worth noting you cannot use the string ‘-SCVMM-‘ in the computer name but you can use ‘SCVMM’.
  • For your SQL server VMM 2012 does NOT support Express versions of SQL. The only supported SQL server versions are:
    • SQL Server 2008 R2 Datacentre (64-bit)
    • SQL Server 2008 R2 Enterprise (64-bit)
    • SQL Server 2008 R2 Standard (64-bit)
    • SQL Server 2008 Enterprise (64-bit)
    • SQL Server 2008 Standard (64-bit)
    • Notice the current lack of SQL Server 2012 support – I’m sure this will come soon.
    • A few other SQL requirements are:
      • You MUST use a case-insensitive instance of SQL server
      • The computer name must not exceed 15 characters.
      • Microsoft also highly recommends you install the SQL Server 2008 R2 Command Line Utilities – although they are not strictly a pre-requisite.
  • You must uninstall any previous versions of the Windows Automated Installation Kit (WAIK) and install the latest Windows 7 version.
  • You need the latest .NET 3.5.1 (this is included in SQL Server 2008 R2 and the VMM 2012 installer will enable it automatically if it’s not already.
  • Windows Remote Management (WinRM 2.0) this should be started it is set to automatic start-delayed on Windows Server 2008 R2 anyway. If is not started you will see an error during the pre-requisites check.

Hardware Requirements:

Less   than 150 hosts

More   than150 hosts

Minimum

Recommended

Minimum

Recommended

Processor

Pentium 4 – 2GHz (x64)

Duel Core – 2.8 GHz (x64) +

Duel Core – 2.8 GHz (x64) +

Duel Core – 3.6 GHz (x64) +

RAM

2Gb

4GB

4Gb

8Gb

HDD (Without DB)

2GB*

40GB*

10GB*

50GB*

HDD (With local SQL DB)

80GB

150GB

Recommended the VMM management server   is on a dedicated server

If you are making VMM Management server highly   available it is recommended to use a separate highly available SQL server.

* If you are running the library server on the server more disk space will be required. Although it is recommended you run the library on highly available file server.

 

Other things to note:

  • Hosts running Microsoft Virtual Server 2005 R2 are no longer supported – I presume Microsoft is trying to push people into moving to Hyper-V!
  • Not all versions of ESX & VMWare vCenter Server are now supported, you must be running one of these versions:
    • VMWare vCenter Server 4.1
    • ESXi 4.1 & ESX 4.1
    • ESXi 3.5 & ESX 3.5

If you upgrade with VMWare hosts (and VMWare VMs) that are not supported they will automatically be removed from the VMM database.

  • Performance & Resource Optimization (PRO)
    • PRO configurations will not be maintained during the upgrade process. This is because during the install the connection to Operations Manager will be removed and you will need to manually recreate it after the upgrade is complete.
  • Library Server
    • SCVMM 2012 does not support a library server being hosted on a Windows Server 2003 server you will need t. migrate these to another server (or upgrade from 2003) before you upgrade. If you continue with a 2003 library server they only thing you will be able to do in the VMM 2012 console is to remove it.
  • Service Accounts
    • Microsoft recommends that you store encryption keys for VMM2012 in AD DS (Distributed Key Management) this is a requirement if you are going to be making your VMM Management server highly available. This is a change in 2012 as Distributed Key Management was not available in VMM 2008 R2.

Using Distributed Key Management is also an advantage if you ever have to re-install VMM 2012 on a different computer in the future. In VMM 2008 (R2) you would not be able to preserve encrypted data as the keys are local to the server. This is also true if you are installing VMM 2012 on a different computer (and not doing an in-place upgrade)

  • For the service account you can either use the local system account or a domain user account – again if you are making this highly available you have to use a domain user account.

During the upgrade process:

If the VMM 2012 installer detects a problem during the install it will automatically roll back and you will be left with your original VMM 2008 R2 SP1 configuration.

Post upgrade:

Some of the service names have changed in VMM 2012 so if you have any service monitoring you will need to update it with the new names. The changes are:

Version Display Name Service Name
VMM 2008 R2 SP1 Virtual   Machine Manager VMMService
Virtual   Machine Management Agent VMMAgent
VMM 2012 System   Center Virtual Machine Manager SCVMMService
System   Center Virtual Machine Manager Agent SCVMMAgent

Once all that is in place you are ready to proceed with the install!! This is where it gets exciting!

Stability Issues with Windows Server “8” Beta on Sever 2008 R2 Hyper-V

If while trying out Windows Server “8” (now officially confirmed to be Windows Server 2012) you have stability issues and your Hyper-V server suddenly crashes you may need this Windows Hotfix.

http://support.microsoft.com/kb/2526776

The hotfix is specifically to fix the following:

  • The Windows 8 Consumer Preview or Windows Server “8” Beta virtual machine stops responding.
  • The Windows Server 2008 R2 host computer displays a stop error message and restarts automatically. This behavior brings down all other running virtual machines together with the host computer.

Definitely one to look at if you having a play with Sever “8” beta in a virtual machine!