System Center Virtual Machine Manager 2008 R2 (beta) Released and Testing it Already

March 17, 2009 at 1:31 am | In Hyper-V, SCVMM, Virtualization | 2 Comments
Tags: , , , ,

SCVMM 2008 R2 Beta has been released last week to the public (to access the bits you have to register on Connect at this link). This new version of the platform comes with a lot of interesting improvements that are worthwhile, specially if you have on your hands a dynamic datacenter with a lot of virtual machines, shared storage and Hyper-V clustering.

As you probably know, Live Migration (check this link for more info and documentation) is a new feature that is included within Windows Server 2008 R2 and Hyper-V Server 2008 R2 (both of them are in Beta right now), that gives you a lot of help making your infrastructure more agile and dynamic by letting you to move a running virtual machines between different Hyper-V hosts without any downtime. With SCVMM 2008 R2 you will be able to execute those migrations directly from the VMM console. You will also be able to hot addition for VHDs; support for new hardware scenarios, etc etc.

For more information about new features of SCVMM 2008 R2 check MVUG Blog, and this post:

What’s New in VMM 2008 R2 Beta

System Center Virtual Machine Manager 2008 (VMM) is a comprehensive management solution for managing virtualized infrastructure running on Windows Server 2008 with Hyper-V, Virtual Server 2005 R2 and VMware ESX through Virtual Center.  Recently, Windows Server 2008 R2 Beta was released which included significant feature improvements to Hyper-V—the underlying hypervisor platform.  A corresponding beta version of VMM R2 – the next version of VMM – is due for release shortly.  VMM R2 Beta  leverages the new platform enhancements and extends the feature set of VMM 2008. This overview highlights the most important new and significantly enhanced features in the VMM 2008 R2 Beta:

Support for new features of Windows Server 2008 R2 Beta

• Live Migration: – Seen through the VMM console, this enables administrators to move virtual machines from one machine in a virtual host cluster to another with no downtime. This allows administrators greater flexibility in responding to planned or unplanned downtime, provides higher machine availability and more robust fault tolerance within virtualized infrastructure. The basic requirements for Live Migration are that all hosts must be part of a cluster and host processors must be from the same manufacturer.  Additionally all hosts in the cluster must have access to shared storage.  No changes are required to existing virtual machines, network, or storage devices in moving from Quick Migration to Live Migration other than upgrading to beta versions of Windows Server 2008 R2 and VMM 2008 R2.
• Hot addition/removal of VHDs:  Allows the addition and removal of new virtual hard disks (VHDs) on a running virtual machine.  This enables storage growth in virtual machines without downtime.  Additionally, ‘live” VHD management allows administrators to take advantage of additional backup scenarios and readily use mission critical and storage-intense applications (eg: SQL Server and Exchange).
• New optimized networking technologies: VMM 2008 R2 Beta supports two new networking technologies – Virtual Machine Queue (VMQ) and TCP Chimney – providing increased network performance while demanding less CPU burden.  NICS that support VMQ, create a unique virtual network queue for each virtual machine on a host that can pass network packets directly from the hypervisor to virtual machine. This speeds throughput as it bypasses much of the processing normally required by the virtualization stack. With TCP Chimney, TCP/IP traffic can be offloaded to a physical NIC on the host computer reducing CPU load and improving network performance.

Enhanced storage and cluster support
• Clustered Shared Volumes (CSV): Provides a single, consistent storage space that allows virtual hosts in a cluster to concurrently access virtual machine files on a single shared logical unit number (LUN). CSV eliminates the previous one LUN per virtual machine restriction and coordinates the use of storage with much greater efficiency and higher performance. CSV enables the Live Migration of virtual machines in and out of the shared LUN without impacting other virtual machines. Enabling CSV on failover clusters is straightforward and easy to monitor through the VMM administrator’s console; many storage configuration complexities prior to CSV have been eliminated.
• SAN migration into and out of clustered hosts: This allows virtual machines to migrate into and out of clustered hosts using a SAN transfer, which automatically configures the cluster nodes to recognize and support the new workload.
• Expanded Support for iSCSI SANs:  Previously, only one LUN could be bound to a single iSCSI target whereas now — with VMM 2008 R2 Beta — multiple LUNS can be mapped to a single iSCSI target.    This provides broader industry support for iSCSI SANs allowing customers more flexibility in choosing storage providers and iSCSI SAN options.

Streamlined process for managing host upgrades
• Maintenance Mode:  Allows administrators to apply updates or perform maintenance on a host server by safely evacuating all virtual machines to other hosts on a cluster using Live Migration or putting those workloads into a saved state to be safely reactivated when maintenance or upgrades are complete. Maintenance mode is enabled for all supported hypervisor platforms on Windows Server 2008 R2 Beta.

Other VMM 2008 R2 Beta enhancements
• Support of disjoint domains:  Reduces the complexity of reconciling host servers with differing domain names in Active Directory and DNS.  In these situations, VMM 2008 R2 Beta automatically creates a custom service principal name (SPN) configured in both AD and DNS allowing for successful authentication. 
• Use of defined port groups with VMware Virtual Center:  On installation, VMM 2008 R2 Beta will present available port groups for VMM’s use with VMware Virtual Center thus allowing administrators to maintain control over which port groups are used.

Patrick Lownds

So, after taking a look to all those features, I wanted to give it a try.

SCVMM 2008 R2 Installation

The installation won’t differ on practically anything what you’ve seen on SCVMM 2008. Here’s a quick step-by-step:

As a reminder, do not forget that SCVMM 2008 installs only on Windows Server 2008 64bits edition. You can check all requirements using System Center Virtual Machine Manager 2008 Configuration Analyzer Update 1.

This tool evaluates a candidate host for installing any role of SCVMM 2008 and notifies about any anomaly.

You can start the installation using the autorun and selecting “VMM Server”

You don’t have the chance to choose if you want to participate or not in the Customer Experience Improvement Program. You have to.

I’m selecting in this case to install a SQL Server 2005 Express to store the database locally instead of connecting to a remote instance. The version included is SQL Server 2005 Express Edition SP2.

I’m creating a new VM Library Share.

Leaving the default communication settings.

The installation process will also install WAIK 1.1.

 

Installing the SCVMM Console

The VMM Console installation process will also add Powershell feature to the operating system.

You can now start using the VMM Console.

 

Adding an Hyper-V Host

So the next obvious step on a installation of SCVMM it’s to start adding virtualization host, but here I found a minor issue that sounds good to share the solution with the community.

Selecting the “Add Host” option from the Action menu, the wizard appears:

Entered the credentials that will be used to connect and add the remote host.

But when I selected “Hyper-V” for the query, 0 servers appeared. It makes no sense, the Hyper-V Server where I installed the SCVMM virtual machine belongs to the same domain.

I removed the “Hyper-V” option and this appeared

The Hyper-V (AA-W2K8-01) host is listed as “Unknown” Virtualization Software.

Again, didn’t make any sense to me, the Hyper-V server is running the right version to be listed as a valid virtualization server, so I started to look around and the answer appear thanks to (more or less) System Center Virtual Machine Manager 2008 Configuration Analyzer Update 1.

Ok, those warnings are not completely true, most of the needed updates are already installed. But the ones that are not installed were actually the problem.

I installed the following updates:

- Hyper-V Update for Windows Server 2008 x64 Edition

- BITS update for Windows Server 2008 x64

And the Hyper-V Host appears as it should by SCVMM.

SCVMM 2008 R2 Beta console with Hyper-V guest

Recommended Links

- Recommended hotfixes for System Center Virtual Machine Manager 2008

- Windows Server 2008 R2 & Microsoft Hyper-V Server 2008 R2 – Hyper-V Live Migration Overview & Architecture

- Step-by-Step Guide to Using Live Migration in Windows Server 2008 R2

- Hyper-V Step-by-Step Guide: Hyper-V and Failover Clustering

Hope you find it useful!

Cheers

Step-by-Step: Adding Hyper-V Integration Components to Windows PE using WAIK 2.0 Tools

February 28, 2009 at 12:55 pm | In Hyper-V, Microsoft Deployment Toolkit (MDT), WAIK, Windows Deployment Services (WDS) | 6 Comments
Tags: , , , ,

For those that have been using Windows Automated Installation Kit (WAIK) 2.0 released recently (download link here) or using Microsoft Deployment Toolkit 2010 Beta 1, that works only with WAIK 2.0 (check these articles of mine about MDT 2010: Post I, Post II and Post III); maybe you’ve noticed that the management tools that were included with WAIK 1.1 (and 1.0) disappeared in this new version.

These tools were consolidated by one command-line: DISM.exe (more info on Post I about MDT 2010). Meaning that the Windows PE management (like customizing, adding drivers or inserting Hyper-V integration components to those images) that you executed on previous versions of WAIK, has significant changes.

On this post we’ll be reviewing how to add the Hyper-V Integration Components to a Windows Preinstallation Environment (Windows PE) image, including the new Windows PE 3.0.

Why should I need to add the Hyper-V Integration Components to Windows PE?

The Integration Components of Hyper-V are a set of drivers that are a significant performance change that you can apply to virtual machines for them to be able to install synthetic devices instead of emulated devices.

Some of the drivers that are installed using the Integration Components are: Video driver, network driver (with this you avoid using Hyper-V’s Legacy Network adapter), storage driver, VMBUS (transport for synthetic devices), time sync (time synchronization with the host), etc.

Adding Hyper-V Integration Components 

As I mentioned before, I prepared a set of MDT 2010 posts about LTI deployments with Windows 7, so I’m going to take the LiteTouch PE image created on that deployment instead of a common Windows PE image (boot.wim). But again, this process will work the same as using a Windows PE raw image.

Since I have already a LiteTouch image added to my Windows Deployment Services (WDS) as a boot image, I’m going to export it, mount the image to be able to apply all changes there, and then import it again to WDS.

1. Mounting Boot Image

1.1. Open the Windows Deployment Services Console and Export the image.

1.2. I’m going to place it on C:\Temp.

1.3. Create the folder where you are going to mount it. In my case C:\Temp\mount.

1.4. Run “cmd” as Administrator, place it in “cd C:\Program Files\Windows AIK\Tools\Servicing”.

1.5. Mount the image using this command line:
Dism.exe /mount-wim /wimfile:”C:\Temp\Lite Touch Windows PE.WIM” /index:1 /mountdir:”C:\Temp\mount”

/index:1 states that you want to use the first image inside the WIM file. A WIM file for operating systems, like Windows 7 for example, contain several images: Ultimate, Enterprise, Starter, etc.

2. Uncompressing Drivers from Integration Components

Now that the image is mounted and ready to be modified, we are going to uncompress the files we need from the Hyper-V Integration Components.

2.1. Since I’m using a virtual machine, I’m going to attach the Integration Components media and extract the files from there.

2.2. From the media of the IC, copy this two files to a local folder:

D:\support\amd64\Windows6.0-KB951634-x64.msu
D:\support\x86\Windows6.0-KB951634-x86.msu

We are going to use the Expand command line to extract the drivers within those updates. Place the cmd window in C:\Windows\System32\ and create a folder to store this temporary files. C:\Temp\source

2.3. Insert:
expand.exe –F:* “C:\Temp\Windows6.0-KB951634-x64.msu” “C:\Temp\source”.

Repeat the step for the x86 update.

Now we are going to also extract the drivers included in the .CAB files that we took from the MSU file.

2.4 Create another temporary folder for these drivers. C:\Temp\source\drivers.

2.5. Insert:
expand.exe -F:* "C:\Temp\source\Windows6.0-KB951634-x64.cab" "C:\Temp\source\drivers".

Inside C:\Temp\source\drivers are all the files we need to insert x64 environments. You can repeat the step 2.5 using the x86 update.

3. Injecting the drivers

You will notice that hundreds of files have been uncompressed, but we are not going to add them all, we are just going to inject the ones that we need.

Here are all the necessary drivers and the command lines to execute:

dism /image:"C:\Temp\mount" /add-driver  /driver:"C:\Temp\source\drivers\amd64_wnetvsc.inf_31bf3856ad364e35_6.0.6001.18016_none_b337f91d87dbf1d0\wnetvsc.inf"

dism /image:"C:\Temp\mount" /add-driver /driver:"C:\Temp\source\drivers\amd64_ws3cap.inf_31bf3856ad364e35_6.0.6001.18016_none_f2e1ba67fcb48f61\ws3cap.inf" /forceunsigned

dism /image:"C:\Temp\mount" /add-driver /driver:"C:\Temp\source\drivers\amd64_wstorflt.inf_31bf3856ad364e35_6.0.6001.18016_none_1cadbbeed0ad55a3\wstorflt.inf" /forceunsigned

dism /image:"C:\Temp\mount" /add-driver /driver:"C:\Temp\source\drivers\amd64_wstorvsc.inf_31bf3856ad364e35_6.0.6001.18016_none_836399a4204c4863\wstorvsc.inf" /forceunsigned

dism /image:"C:\Temp\mount" /add-driver /driver:"C:\Temp\source\drivers\amd64_wvmbus.inf_31bf3856ad364e35_6.0.6001.18016_none_959a72f36267838a
\wvmbus.inf" /forceunsigned

dism /image:"C:\Temp\mount" /add-driver /driver:"C:\Temp\source\drivers\amd64_wvmbushid.inf_31bf3856ad364e35_6.0.6001.18016_none_4ccff81064c7c78f
\wvmbushid.inf" /forceunsigned

dism /image:"C:\Temp\mount" /add-driver /driver:"C:\Temp\source\drivers\amd64_wvmic.inf_31bf3856ad364e35_6.0.6001.18016_none_5dfb8c2804cc9e9a
\wvmic.inf" /forceunsigned

 

Injecting drivers

Note that on most of them, the /forceunsigned parameter was necessary. If you don’t use it, this error will appear: “Error 50 The request is not supported”

4. Committing and Unmounting the Boot Image

Now we have are image ready to use it, so we are going to commit the changes and unmount it.

4.1. From cmd:
Dism /unmount-wim /Mountdir:"C:\Temp\mount" /commit

5. Deploying the Image

On C:\Temp you’ll find the WIM file modified and ready to be added to WDS.

5.1. Open the WDS Console, select “Add Boot Image” and complete the wizard.

On the new boot image, I’m adding the Integration Components description

5.2. Boot the new virtual machine from the network and select the image you just added.

And the new virtual machine should be fully functional with the Hyper-V Integration Components included.

How you can you test it? In my case, I’m connecting with RDP to the Hyper-V host and the mouse from inside the virtual machine is working perfectly; if the IC components are not present a message will appear saying that the “Mouse session could not be captured”.

Adding Drivers Using WAIK 1.1 Tools

If you were wondering how to execute the procedure using the WAIK 1.0 or 1.1 tools, here it is:

1. Mount the WIM file using imagex tool:
imagex /mountrw “C:\Temp\Lite Touch Windows PE.WIM” 2 “C:\Temp\mount”

2. Inject drivers using peimg tool:
peimg /inf=C:\Temp\source\drivers\*.inf /image=”C:\Temp\mount”

*.inf is representing all the previous drivers that we added above. Repeat the command line for each file.

3. Commit changes:
imagex /unmount /commit C:\Temp\mount

4. Add the new “Lite Touch Windows PE.WIM” on WDS as a “Boot Image”

Enjoy!

Cheers!

Windows Server 2008 R2 Live Migration: “Overview & Architecture” and “Step-by-Step Guide” Documents Released

January 30, 2009 at 4:55 pm | In Documentation, Hyper-V, Virtualization, Windows Server 2008, Windows Server 2008 R2 | 1 Comment
Tags: , , , ,

Microsoft released in the last days two new more documents about one of the most expected technologies on Windows Server 2008 R2: Live Migration. This new technology will allow you to move any running virtual machine using Hyper-V from Windows Server 2008 R2 or Hyper-V Server 2008 R2 (the free hypervisor offered by Microsoft) to another machine with any of those operating systems, without any downtime or disruption of the service.

Here are the two links for the new articles:

Windows Server 2008 R2 & Microsoft Hyper-V Server 2008 R2 – Hyper-V Live Migration Overview & Architecture

Step-by-Step Guide to Using Live Migration in Windows Server 2008 R2

Here’s an example graphic of how Live Migration setup handles Configuration Files of the virtual machines:

It is important for you to notice that Live Migration requires Failover Clustering to be configured on all hosts, access to a shared storage (like in NAS or SAN environments) and a special network configured between them to be used only for Live Migration feature.

For more information about Hyper-V Failover Clustering check this guide:Hyper-V Step-by-Step Guide: Hyper-V and Failover Clustering

Complete list of requirements for Live Migration:

  • Windows Server 2008 R2 x64 Enterprise Edition
  • Windows Server 2008 R2 x64 Datacenter Edition
  • Live migration is also supported on Microsoft® Hyper-V™ Server 2008 R2.
  • Microsoft Failover Clustering must be configured on all physical hosts that will use live migration
  • Failover Clustering supports up to 16 nodes per cluster
  • The cluster should be configured with a dedicated network for the live migration traffic
  • Physical host servers must use a processor or processors from the same manufacturer
  • Physical hosts must be configured on the same TCP/IP subnet
  • Physical hosts must have access to shared storage

Other interesting links about Hyper-V, Hyper-V Server and Failover Cluster:

- Hyper-V Planning and Deployment Guide
- Failover Cluster Deployment Guide
- Failover Cluster Step-by-Step Guide: Validating Hardware for a Failover Cluster
- The Microsoft Support Policy for Windows Server 2008 Failover Clusters
- Hyper-V Server 2008 R2 Beta Available for Download
- Hyper-V Server: Installing, configuring and troubleshooting

Cheers!

Hyper-V Server 2008 R2 Beta Available for Download!

January 11, 2009 at 4:43 pm | In Hyper-V, Virtualization | 1 Comment
Tags: , ,

Did you get the chance to try on the free Hyper-Visor released by Microsoft a few months ago, Hyper-V Server 2008?.

Don’t get confused, this is not a version of Windows Server 2008, it’s just the hyper-visor released as a "bare-metal" operating system, based significantly on remote administration (nothing much to do locally), but the great feature is that is completely free.

Now they’ve also released the R2 version of this operating system, and you can download it from here (~1.2gb).

The main improvements from the previous versions:

  • Hyper-V clustering supported!
  • Live Migration.
  • Processor and memory upgrades (up to 32 cores and 1TB of RAM).
  • Includes an Hyper-V configuration utility.

I had the chance to work with the first version and it’s been a great experience. Since it’s just an hyper-visor with a really small footprint, has an awesome performance on their virtual machines, including a small attack surface design.

One of the significant drawbacks that I found on the first version is that Hyper-V clustering/failover was not supported, but this new release sounded like a great news when I saw that is going to support this feature. Making this free operating system with a great performance, high-available and scalable design.

Give this one a chance to test it, you won’t regret it.

Check a previous guide I’ve made regarding Hyper-V Server 2008 (applies as well for the R2 version):

“Hyper-V Server: Installing, Configuring and Troubleshooting”

Cheers!

Looking for VHDs?

January 4, 2009 at 6:34 pm | In Hyper-V, Virtualization | Leave a Comment
Tags: , ,

Some of you already know about the official Microsoft VHD Download Page; where you can get the VHD file of a pre-builded virtual machine with an special configuration, like Exchange Server 2007, Windows 2008 Server Core, etc. All of them of course are trial versions (including the operating system).

 

The latest relase was made in late December, Intelligent Application Gateway 2007 SP2 with Applications Optimizer. You can download it from here.

IAG 2007 SP2 Overview

Intelligent Application Gateway (IAG) is a remote access gateway that boosts productivity by giving mobile and remote workers, partners and customers easy, flexible and secure access to virtually any application from a broad range of devices and locations.
IAG enables IT administrators to truly enforce compliance and address virtually any remote access scenario by providing easy to configure, built-in, policies that address common applications and user environments.
IAG SP2 delivers a range of new, important enhancements for customers:
1. Runs as a virtual machine on Hyper-V for low TCO, flexible/secure deployment and simple disaster recovery.
2. Interoperability for non-Windows environments with support for Firefox, Linux and Mac.
3. New application support for Microsoft Dynamics CRM and OCS Web client.

Looking around and reading some blogs, I found also a very useful post related to this Microsoft Site: The links of every VHD available to this date, including several other interesting tools and links.

http://blog.windowsvirtualization.com/downloads

Also I highly recommend you to visit the main blog where I found those links, it has always the latest news on the Virtualization World.

http://blog.windowsvirtualization.com/

Cheers!

Hyper-V Server: Installing, configuring and troubleshooting

December 12, 2008 at 7:42 pm | In Hyper-V, Virtualization, Windows Server 2008 | 3 Comments
Tags: , , ,

It’s been a few weeks since its release but I finally managed to put my hands on to Hyper-V Server.

I was very curious about it: A free operating system released by Microsoft working only as an HyperVisor it makes wonder about a lot of things. Also recently I’ve been working with VMWare ESX Server 3i, that is also the hypervisor working directly on the machine, and I had a good experience (I really loved the monitoring and reporting features that you can use).

From the moment I started using Hyper-V Server few troubleshooting tasks needed to be done.

Installing Hyper-V Server

If you ever installed any operating system, ever, you should not have any problem with this. You’ll of course see that the process is identical from Vista and Windows 2008.

To get started with Hyper-V Server there’s available the Hyper-V Server 2008 Configuration Guide.

If you want to avoid almost any command line to be executed from now on, Hyper-V Server has a simple tool where you’ll load a menu to access most of the configurations you will need. You can access it using this cmd:

C:windowssystem32hvconfig.cmd

But I’ll execute the next steps using the command line features, so this procedure will apply as well for Windows 2008 Server Core.

Managing Remotely

To start using Hyper-V Server you will need Hyper-V Console on your Vista SP1 (remember: there’s no other option for an Hyper-V Server to be managed remotely), it is the same console to manage remotely any other Windows 2008 with Hyper-V. If you don’t have it yet, you can download it from here:

Windows Vista Service Pack 1 Management Tools update for the release version of Hyper-V

But, from this moment I started to have a few problems.

1. Solving “Access denied. Unable to establish communication between: <Hyper-V Server> and <Vista client>”

For all of those who were using the early versions of this remote console probably had the same error.

The solution is the same, so I want to reference this post from John Howard’s blog; where it explain almost everything you must know about configuring Hyper-V role on a Windows 2008 Core Server. Hyper-V Server works the same way as this Core version of Windows 2008, so every step of configuration will apply.

Here’s a quick summary of the steps involved, I’m only applying the steps I considered necessary for my environment.

1. Since I’m using a domain environment, I joined this machine to the domain using NETDOM utility:

netdom join <ComputerName> /domain:<DomainName> /userd:<UserName> /passwordd:*

/passwordd: * Requires user password to be entered.

Reboot the machine to apply the changes:
shutdown /t 0 /r

2. Adding necessary rules on the Firewall to allow remote connections.

a. Remote Management:

netsh advfirewall firewall set rule group=”Remote Administration” new enable=yes

Note: You can also use netsh to change server’s IP, using the following syntax:
netsh interface ip set address “<Adapter Name>” static ipaddr subnetmask gateway metric.

b. Enable Remote Desktop

cscript windowssystem32scregedit.wsf /ar 0
cscript windowssystem32scregedit.wsf /cs 0

c. Reboot the machine to apply the changes:
shutdown /t 0 /r

3. Solving the “Access denied” error from the client:

Now that the server is properly configured for remote management, you have to run a simple procedure to fix this common error:

a. On “Run” insert “DCOMCNFG“. Click OK
b. Expand “Component Services“, expand “Computers“. Right click on “My Computer” and click on “Properties” (imagen)
c. Now click on “COM Security”
d. In “Access Permission” click “Edit Limits”
e. Select “ANONYMOUS LOGON” in “Group or User Name“. In the column “Allow“, set the “Permissions for User” with “Remote Access“.

Now you should be able to connect remotely using the Hyper-V console.

Since I finally completed the Hyper-V Server configurations for remote management, so the obvious next step is creating a new virtual machine.

I started with a dummy virtual machine, just for testing. But in the last step of the virtual machine creation wizard I got “The virtual machine could not be started because the hypervisor is not running.” Ouch!

2. Solving “The virtual machine could not be started because the hypervisor is not running”

You should not worry if you see this error. There’s a good chance that your hardware is not the problem and that the hypervisor feature on your processor it is running.

Even though that the hardware on your server supports Hyper-V and that the service is correctly installed, what happens is that the hypervisor was not added on the boot environment and the service was not started.

To solve this, you only need to run this command line:

BCDEdit /set hypervisorlaunchtype auto

Ok, NOW you can start using Hyper-V Server.

Adding Features to Hyper-V Server

Don’t get all excited, as we mentioned before, this is just an HyperVisor and you should not expect that much functionality available.

Most of the features (not roles) that you can install are there to increase security and to achieve interoperability with other platforms like System Center Virtual Machine Manager or Data Protection Manager, supporting Live Backup (backing up virtual machine without downtime) as well. 

To access all features available, as in Server Core, from cmd:

oclist

To install one of the features use: start /w ocsetup <NameofService> (for instance, I installed on this Hyper-V Server the TelnetClient)

You’ll find as well that Hyper-V Server includes a WMI interface for remote management extensibility. Here you can find more information:

Virtualization WMI Provider.

Hope you find it useful.

Cheers! 

Blog at WordPress.com. | Theme: Pool by Borja Fernandez.
Entries and comments feeds.