Archive
Hyper-v: Detailed step by step installing RedHat 6.1 VM in expert mode with the new Linux Integration Services 3.1
Microsoft released the a new Linux Integration Services, fully tested against RHEL 6.0, RHEL 6.1, and CentOS 6.0
http://www.microsoft.com/download/en/details.aspx?id=26837
To Create a RedHat 6 VM
1. Open Hyper-V Manager: Click Start, point to Administrative Tools, and then click
Hyper-V Manager.
2. Create a new virtual machine where you will install Linux: In the Actions menu, click New, and then click Virtual Machine.
Note: if you do not Add a legacy network adapter a this point, the virtual machine will not have network support, until you install the Linux Integration Services.
3. Specify the Linux installation media: Right-click the virtual machine that you created, and then click Settings. In IDE Controller, specify one of the following:
a. An image file in ISO format that contains the files required for installation
b. A physical CD/DVD drive that contains the installation media
4. Turn on the virtual machine: Right-click the virtual machine that you created, and then click Connect.
To Install Redhat Linux 6.1
1. After a short delay, the Welcome to Red Hat Linux 6.1! screen appears. Press <Tab>
2.At the prompt, add the text: append expert and then press <Enter>
3. Press <OK> to check the installation media or <SKIP> to not test check in the next screen
4. Click Next to continue
5. The Choose a Language screen appears. This screen asks you to select the language to be used during the installation process. Use the up-or down-arrow key to select alanguage (the system highlights your choice). Click Next
6.The Keyboard Type screen appears asking you to select a keyboard type. Use the up- or down-arrow key to select a keyboard type (the system highlights your choice). Click Next
7. At the “Devices” screen select Basic Storage Devices to install Red Hat Enterprise Linux on the following storage devices: hard drives or solid-state drives connected directly to the local system
8. As you selected Basic Storage Devices, anaconda automatically detects the local storage attached to the system and does not require further input.Click Next.
9. Enter the Hostname for your server, select OK
10 If you added the Legacy Network at the creation of the VM, then click Configure Network . At the “Network Configuration” window, Specify an IP address/gateway. Otherwise, skip this task. You can setup the network later, after installing the Linux Integration Services

Use the IPv4 Settings tab to configure the IPv4 parameters for the previously selected network connection. Select Start automatically to start the connection automatically when the system boots.
11.Click Next
12. At the “Time Zone Selection” window, highlight the correct time zone. Click Next
13.For Root Password, type and confirm the password. Click Next
14. If no readable partition tables are found on existing hard disks, the installation program asks to initialize the hard disk. This operation makes any existing data on the hard disk unreadable. If your system has a brand new hard disk with no operating system installed, or you have removed all partitions on the hard disk, click Re-initialize drive
15. Select the type of installation would you like and then click Next.
Note: If you chose one of the automatic partitioning options (first 4 options) and selected Review, you can either accept the current partition settings (click Next), or modify the setup manually in the partitioning screen. To review and make any necessary changes to the partitions created by automatic partitioning, select the Review option. After selecting Review and clicking Next to move forward, the partitions created for you by anaconda appear. You can make modifications to these partitions if they do not meet your needs.
If you chose to create a custom layout, you must tell the installation program where to install Red Hat Enterprise Linux. This is done by defining mount points for one or more disk partitions in which Red Hat Enterprise Linux is installed. You may also need to create and/or delete partitions at this time
Unless you have a reason for doing otherwise, I recommend that you create the following partitions for x86, AMD64, and Intel
64 systems:
• swap partition
• /boot partition
• / partition
Advice on Partitions:
- A swap partition (at least 256 MB) — swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. In years past, the recommended amount of swap space increased linearly with the amount of RAM in the system. But because the amount of memory in modern systems has increased into the hundreds of gigabytes, it is now recognized that the amount of swap space that a system needs is a function of the memory workload running on that system. However, given that swap space is usually designated at install time, and that it can be difficult to determine beforehand the memory workload of a system, use the recommended:
| Amount of RAM in the System | Recommended Amount of Swap Space |
| 4GB of RAM or less | a minimum of 2GB of swap space |
| 4GB to 16GB of RAM | a minimum of 4GB of swap space |
| 16GB to 64GB of RAM | a minimum of 8GB of swap space |
| 64GB to 256GB of RAM | a minimum of 16GB of swap space |
- The /var directory holds content for a number of applications. It also is used to store downloaded update packages on a temporary basis. Ensure that the partition containing the /var directory has enough space to download pending updates and hold your other content.
- The /usr directory holds the majority of software content on a Red Hat Enterprise Linux system. For an installation of the default set of software, allocate at least 4 GB of space.
If you are a software developer or plan to use your Red Hat Enterprise Linux system to learn software development skills, you may want to at least double this allocation. - Consider leaving a portion of the space in an LVM volume group unallocated. This unallocated space gives you flexibility if your space requirements change but you do not wish to remove data from other partitions to reallocate storage
16. After finishing creating the partitions, Click Next. The installer prompts you to confirm the partitioning options that you selected. Click Write changes to disk to allow the installer to partition your hard drive and install Red Hat Enterprise Linux
17.Allow the installation process to complete. The Package Installation Defaults screen appears and details the default package set for the Red Hat Enterprise Linux installation
If you select Basic Server, this option will provide a basic installation of Red Hat Enterprise Linux for use on a server.
18. Select Customize now to specify the software packages for your final system in more detail. This option causes the installation process to display an additional customization screen when you select Next. The following screens shows the customized packages selected

Note : The packages that you select are not permanent. After you boot your system, use the Add/Remove Software tool to either install new
software or remove installed packages. To run this tool, from the main menu, select System -> Administration -> Add/Remove Software
19. Click Next to continue the installation. The installer checks your selection, and automatically adds any extra packages required to use the software you selected. The installation process will start. At this point there is nothing left for you to do until all the packages have been installed.
20. Installation Complete: Red Hat Enterprise Linux installation is now complete. select Reboot to restart your Virtual Machine

Now it’s time for the first-boot configuration.
21. First Boot lets you configure your environment at the beginning. Click Forward to proceed
22. Accept the License and Click Forward to proceed
23. Setting up software updates. Select whether to register the system immediately with Red Hat Network. To register the system, select Yes, I’d like to register now, and click Forward.
Note : it can be registered with the RedHat Entitlement Service later using the Red Hat Subscription Manager tools
24. Create User to use as a regular non-administrative use. Enter a user name and your full name, and then enter your chosen password. Type your password once more in the Confirm Password box to ensure that it is correct.
Note: If you do not create at least one user account in this step, you will not be able to log in to the RedHat Enterprise Linux graphical environment
25. Click Forward to proceed
26. Date and Time. Use this screen to adjust the date and time of the system clock.
27. Click Forward to proceed
28. Kdump. Use this screen to select whether or not to use the Kdump kernel crash dumping mechanism on this system. Note that if you
select this option, you will need to reserve memory for Kdump and that this memory will not be available for any other purpose.
29 Click Finish to proceed.
Done installation and configuration of RedHat Linux 6.1 completed. Not let’s configure the Linux Integration Services.
To install Linux Integration Services Version 3.1
Important Note: There is an issue where the SCVMM 2008 Service can crash with VMs running Linux Integration Components v3.1 for Hyper-V.
Resolution: Disabling the KVP daemon on the Linux virtual machine will prevent the SCVMM service crash. The command to make this change must be run as root.#/sbin/chkconfig –level 35 hv_kvp_daemon off
This will prevent the KVP service from auto starting while retaining all other functionality of hv_utils. hv_utils provides integrated shutdown, key value pair data exchange, and heartbeat features. More info : http://blogs.technet.com/b/scvmm/archive/2011/07/28/new-kb-the-scvmm-2008-virtual-machine-manager-service-crashes-with-vms-running-linux-integration-components-v3-1-for-hyper-v.aspx
1. Log on to the virtual machine.
2. In Hyper-V Manager, configure LinuxIC v30.ISO (located in the directory where you extracted the downloaded files) as a physical CD/DVD drive on the virtual machine.

3. Open a Terminal Console ( command line )
4. As the root user, mount the CD in the virtual machine by issuing the following command at a shell prompt:
#mount /dev/cdrom /media

4. As the root user, run the following command to install the synthetic drivers. A reboot is required after installation.
For 64-bit versions:
# yum install /media/x86_64/kmod-microsoft-hyper-v-rhel6-60.1.x86_64
# yum install /media/x86_64/microsoft-hyper-v-rhel6-60.1.x86_64
# reboot
or if you prefer to use rpm:
# rpm –ivh /media/x86_64/kmod-microsoft-hyper-v-rhel6-60.1.x86_64.rpm
# rpm –ivh /media/x86_64/microsoft-hyper-v-rhel6-60.1.x86_64.rpm
# reboot
For 32-bit versions:
# yum install /media/x86/kmod-microsoft-hyper-v-rhel6-60.1.i686
#yum install /media/x86/microsoft-hyper-v-rhel6-60.1.i686
# reboot
or
# rpm –ivh /media/x86/kmod-microsoft-hyper-v-rhel6-60.1.i686.rpm
# rpm –ivh /media/x86/microsoft-hyper-v-rhel6-60.1.i686.rpm
# reboot
DONE! You should now have RedHat 6.1 running as VM on Hyper-V.
Note:
After Linux Integration Services are installed on the virtual machine, Key Value Pair exchange functionality is activated. This allows the virtual machine to provide the following information to the virtualization server:
-
Fully Qualified Domain Name of the virtual machine
-
Version of the Linux Integration Services that are installed
-
IP Addresses (both IPv4 and IPv6) for all Ethernet adapters in the virtual machine
-
OS Build information, including the distribution and kernel version
-
Processor architecture (x86 or x86-64)
The data can be viewed using the Hyper-V WMI provider, and accessed via Windows PowerShell. Instructions for viewing Key Value Pair exchange data are available at these websites:
http://social.technet.microsoft.com/wiki/contents/articles/hyper-v-script-to-check-icversion.aspx
http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/11/18/hyper-v-script-looking-at-kvpguestintrinsicexchangeitems.aspx
SCVMM 2008 Ports and Protocols
SCVMM 2008, SCVMM 2008 R2 and SCVMM 2008 R2 SP1 default ports :
| Connection type | Protocol | Default port | Where to change the port setting |
|---|---|---|---|
| VMM server to VMM agent on Windows Server–based host (control) | WS-Management | 80 | at VMM setup, registry |
| VMM server to VMM agent on Windows Server–based host (file transfers) |
HTTPS (using BITS) | 443 (Maximum value: 32768) | Registry |
| VMM server to remote Microsoft SQL Server database | TDS | 1433 | Registry |
| VMM server to P2V source agent | DCOM | 135 | Registry |
| VMM Administrator Console to VMM server | WCF | 8100 | at VMM setup, registry |
| VMM Self-Service Portal Web server to VMM server | WCF | 8100 | at VMM setup |
| VMM Self-Service Portal to VMM self-service Web server | HTTPS | 443 | at VMM setup |
| VMM library server to hosts | BITS | 443 (Maximum value: 32768) | at VMM setup, registry |
| VMM host-to-host file transfer | BITS | 443* (Maximum value: 32768)
* VMM 2008 R2 : port 30443 (http://support.microsoft.com/kb/971816) |
Registry |
| VMRC connection to Virtual Server host | VMRC | 5900 | VMM Administrator Console, registry |
| VMConnect (RDP) to Hyper-V hosts | RDP | 2179 | VMM Administrator Console, registry |
| Remote Desktop to virtual machines | RDP | 3389 | Registry |
| VMware Web Services communication | HTTPS | 443 | VMM Administrator Console, registry |
| SFTP file transfer from VMWare ESX Server 3.0 and VMware ESX Server 3.5 hosts |
SFTP | 22 | Registry |
| SFTP file transfer from VMM server to VMWare ESX Server 3i hosts | HTTPS | 443 | Registry |
More info : http://technet.microsoft.com/en-us/library/cc764268.aspx
SCVMM 2012 Management ports and protocols. Detailed
Here are the list of ports/protocols for the new SCVMM 2012.
| From | To | Protocol | Default port |
Where to change port setting |
| VMM management server | P2V source agent (control channel) |
DCOM | 135 | |
| Load Balancer | HTTP/HTTPS | 80/443 | Load balancer configuration provider | |
| WSUS server (data channel) | HTTP/HTTPS | 80/8530 (non-SSL), 443/8531 (with SSL) |
These ports are the IIS port binding with WSUS. They cannot be changed from VMM. | |
| WSUS server (control channel) | HTTP/HTTPS | 80/8530 (non-SSL), 443/8531 (with SSL) |
These ports are the IIS port binding with WSUS. They cannot be changed from VMM. | |
| VMM agent on Windows Server–based host (data channel for file transfers) |
HTTPS (using BITS) |
443 (Maximum value: 32768) |
||
| Citrix XenServer host (customization data channel) |
iSCSI | 3260 | On XenServer in transfer VM | |
| XenServer host (control channel) | HTTPS | 5989 | On XenServer host in: /opt/cimserver/cimserver_planned.conf | |
| remote Microsoft SQL Server database | TDS | 1433 | ||
| VMM agent on Windows Server–based host (control channel) |
WS-Management | 5985 | VMM setup | |
| VMM agent on Windows Server–based host (control channel – SSL) |
WS-Management | 5986 | ||
| in-guest agent (VMM to virtual machine control channel) |
WS-Management | 5985 | ||
| Storage Management Service | WMI | Local call |
||
| Cluster PowerShell interface | PowerShell | n/a | ||
| P2V source agent (data channel) | BITS | User-Defined | P2V cmdlet option | |
| VMM library server | hosts file transfer |
BITS | 443 (Maximum value: 32768) |
VMM setup |
| VMM host-to-host file transfer | BITS | 443 (Maximum value: 32768) |
||
| VMM Self-Service Portal | VMM Self-Service Portal web server |
HTTPS | 443 | VMM setup |
| VMM Self-Service Portal web server | VMM management server |
WCF | 8100 | VMM setup |
| Console connections (RDP) | virtual machines through Hyper-V hosts (VMConnect) |
RDP | 2179 | VMM console |
| Remote Desktop | virtual machines |
RDP | 3389 | On the virtual machine |
| VMM console | VMM management server |
WCF | 8100 | VMM setup |
| VMM management server (HTTPS) | WCF | 8101 | VMM setup | |
| VMM management server (NET.TCP) | WCF | 8102 | VMM setup | |
| VMM management server (HTTP) | WCF | 8103 | VMM setup | |
| Windows PE agent | VMM management server (control channel) |
WCF | 8101 | VMM setup |
| VMM management server (time sync) | WCF | 8103 | VMM setup | |
| WDS provider | VMM management server |
WCF | 8102 | VMM setup |
| Storage Management Service | SMI-S Provider | CIM-XML | Provider-specific port |
|
| VMM management server | VMware ESX Server 3i hosts |
HTTPS | 443 | |
Others
| Connection Type | Protocol | Default port | Where to change port setting |
| OOB Connection – SMASH over WS-Man | HTTPS | 443 | On BMC |
| OOB Connection IPMI | IPMI | 623 | On BMC |
|
BITS port for VMM transfers (data channel)
|
BITS | 443 | VMM setup |
| VMware ESX Server 3.0 and VMware ESX Server 3.5 hosts | SFTP | 22 | |
| VMware Web Services communication |
HTTPS | 443 | VMM console |
Note: When you install the VMM management server you can assign some of the ports that it will use for communications and file transfers between the VMM components.
MS Virtualization for VMware Pros : Jump Start
Exclusive Jump Start virtual training event – “Microsoft Virtualization for VMware Professionals” FREE – on TechNet Edge
Where do I go for this great training?
The HD-quality video recordings of this course are on TechNet Edge. If you’re interested in one specific topic, I’ve included links to each module as well.
· Entire course on TechNet Edge: “Microsoft Virtualization for VMware Professionals” Jump Start
o Virtualization Jump Start (01): Virtualization Overview
o Virtualization Jump Start (02): Differentiating Microsoft & VMware
o Virtualization Jump Start (03a): Hyper-V Deployment Options & Architecture | Part 1
o Virtualization Jump Start (03b): Hyper-V Deployment Options & Architecture | Part 2
o Virtualization Jump Start (04): High-Availability & Clustering
o Virtualization Jump Start (05): System Center Suite Overview with focus on DPM
o Virtualization Jump Start (06): Automation with Opalis, Service Manager & PowerShell
o Virtualization Jump Start (07): System Center Virtual Machine Manager 2012
o Virtualization Jump Start (08): Private Cloud Solutions, Architecture & VMM Self-Service Portal 2.0
o Virtualization Jump Start (09): Virtual Desktop Infrastructure (VDI) Architecture | Part 1
o Virtualization Jump Start (10): Virtual Desktop Infrastructure (VDI) Architecture | Part 2
o Virtualization Jump Start (11): v-Alliance Solution Overview
o Virtualization Jump Start (12): Application Delivery for VDI
· Links to course materials on Born to Learn
SCVMM 2008 R2 SP1 : available for download. Support for DM and Remote FX
With support for new features of Windows Server 2008 R2 SP1
- Dynamic Memory: Windows Server 2008 R2 SP1 Hyper-V supports Dynamic Memory enabling customers to better utilize the memory resources of a Hyper-V host. VMM 2008 R2 SP1 allows administrators to create and deploy Virtual Machines onto Windows Server 2008 R2 SP1 Hyper-V hosts and will report on the memory currently in use for these VMs where Dynamic Memory is enabled. Using Dynamic Memory for supported VMs allows for more efficient utilization of memory, with consistent performance, and higher consolidation ratios.
- Microsoft RemoteFX: Windows Server 2008 R2 SP1 introduces a new set of end user experience enhancements with Microsoft RemoteFX. VMM 2008 R2 SP1 allows administrators to create and deploy Virtual Machines with RemoteFX enabled to qualified Windows Server 2008 R2 SP1 Hyper-V hosts. This enables a rich, local-like desktop environment over the network.
SCVMM 2012: Private Cloud Management. Got it!?
It’s great pleasure to see how far Microsoft SCVMM went with the SCVMM 2012.
Belevie me, it’s a whole new product.
So, if you are seriuos about Private Cloud Management, that’s the product you will look into.
•Fabric Management
◦Hyper-V and Cluster Lifecycle Management – Deploy Hyper-V to bare metal server, create Hyper-V clusters, orchestrate patching of a Hyper-V Cluster
◦Third Party Virtualization Platforms – Add and Manage Citrix XenServer and VMware ESX Hosts and Clusters
◦Network Management – Manage IP Address Pools, MAC Address Pools and Load Balancers
◦Storage Management – Classify storage, Manage Storage Pools and LUNs
•Resource Optimization
◦Dynamic Optimization – proactively balance the load of VMs across a cluster
◦Power Optimization – schedule power savings to use the right number of hosts to run your workloads – power the rest off until they are needed.
◦PRO – integrate with System Center Operations Manager to respond to application-level performance monitors.
•Cloud Management
◦Abstract server, network and storage resources into private clouds
◦Delegate access to private clouds with control of capacity, capabilities and user quotas
◦Enable self-service usage for application administrator to author, deploy, manage and decommission applications in the private cloud
•Service Lifecycle Management
◦Define service templates to create sets of connected virtual machines, os images and application packages
◦Compose operating system images and applications during service deployment
◦Scale out the number of virtual machines in a service
◦Service performance and health monitoring integrated with System Center Operations Manager
◦Decouple OS image and application updates through image-based servicing.
◦Leverage powerful application virtualization technologies such as Server App-V
Note: The SCVMM 2012 Beta is NOT Supported in production environments.
Download SCVMM 2012 Beta Now
SCVMM for VDI deplyoments: tuning
SCVMM as a platform
While most people are aware of SCVMM (System Center Virtual Machine Manager) being used for managing virtualized datacenters, it’s probably less well known that a number of partners have built products using SCVMM as a platform by using the powershell based API. Products that use SCVMM as a platform include Citrix XenDesktop, Quest vWorkspace and Visual Studio Lab Management (this is not an exhaustive list by any means). Two of those products (XenDesktop and Quest workspace) are VDI (Virtual Desktop Infrastructure) management products that can be used to manage VDI desktop VMs.
VDI
VDI management has different usage patterns compared to server virtualization management. For example, VDI VMs are powered on during the morning when the users need to log on to their desktops and they get powered off in the evening after users log off (all this is controllable via policy). So it’s fairly common to power on large number of VMs in a short period of time which causes a spike in load on VMM to handle large number of parallel jobs. These kind of spikes in load can cause the system to become overloaded. While we continue to make improvements in future versions of SCVMM to handle such scenarios, this post is about best practices for configuring SCVMM 2008 R2 for managing VDI environments. The size of the environment is around 1000 desktop VMs, if you have larger environments, you’ll probably need to use multiple instances of SCVMM
to read the full article : http://blogs.technet.com/b/vishwa/archive/2011/02/01/tuning-scvmm-for-vdi-deployments.aspx
Hotfixes for SCVMM 2008 R2
Hi
Here is the recommended hotfixes for System Center Virtual Machine Manager 2008 R2
Recommended updates for the Virtual Machine Manager (VMM) Server and Admin Console
2308590 (http://support.microsoft.com/kb/2308590) Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: September 14, 2010
982523 (http://support.microsoft.com/kb/982523) Description of the System Center Virtual Machine Manager 2008 R2 Admin Console hotfix rollup package: June 8, 2010
Windows Server 2008 – Recommended updates for Microsoft Hyper-V Server and for the VMM server
The following list applies only to systems that are running Windows Server 2008 Service Pack 1
954563 (http://support.microsoft.com/kb/954563) Memory corruption may occur with the Windows Management Instrumentation (WMI) service on a computer that is running Windows Server 2008 or Windows Vista Service Pack 1
955805 (http://support.microsoft.com/kb/955805) Certain applications become very slow on a Windows Server 2008-based or Windows Vista SP1-based computer when a certificate with the SIA extension is installed
956774 (http://support.microsoft.com/kb/956774) A Background Intelligent Transfer Service (BITS) client cannot handle files that have paths that contain the volume GUID in Windows Server 2008 or in Windows Vista
958124 (http://support.microsoft.com/kb/958124) A wmiprvse.exe process may leak memory when a WMI notification query is used heavily on a Windows Server 2008-based or Windows Vista-based computer
The following list applies to systems that are running Windows Server 2008 Service Pack 1 or Windows Server 2008 Service Pack 2
968936 (http://support.microsoft.com/kb/968936) A rollup hotfix package for Windows Server 2008 Failover Clustering WMI provider
970520 (http://support.microsoft.com/kb/970520) The Wmiprvse.exe process creates a memory leak on a computer that is running Windows Server 2008 if you remotely monitor this process by using the WMI interface on a computer that is running Windows Server 2003 or Windows XP
971244 (http://support.microsoft.com/kb/971244) Windows Remote Management (WinRM) does not accept HTTP authorization requests that are larger than 16 KB on a computer that is running Windows Server 2008 or Windows Vista
971403 (http://support.microsoft.com/kb/971403) The “Win32_share” WMI class cannot enumerate file shares or create file shares on a node in a Windows Server 2008 failover cluster
To see a list of recommended Hyper-V updates for Windows Server 2008 and for Microsoft Hyper-V Server 2008, visit the following Microsoft TechNet website: http://technet.microsoft.com/en-us/library/dd430893(WS.10).aspx (http://technet.microsoft.com/en-us/library/dd430893(WS.10).aspx)
Windows Server 2008 – Recommended updates for Hyper-V Failover Cluster nodes
957311 (http://support.microsoft.com/kb/957311) Recommended hotfixes for Windows Server 2008-based server clusters
Windows Server 2008 R2 – Recommended updates for Microsoft Hyper-V Server and for the VMM server
981314 (http://support.microsoft.com/kb/981314) The “Win32_Service” WMI class leaks memory in Windows Server 2008 R2 and in Windows 7
981845 (http://support.microsoft.com/kb/981845) The Windows Remote Management service stops responding in Windows 7 or in Windows Server 2008 R2
To see a list of recommended Hyper-V updates for Windows Server 2008 R2 and for Microsoft Hyper-V Server 2008 R2, visit the following Microsoft TechNet website: http://technet.microsoft.com/en-us/library/ff394763(WS.10).aspx (http://technet.microsoft.com/en-us/library/ff394763(WS.10).aspx)
Windows Server 2008 R2 – Recommended updates for Hyper-V Failover Cluster nodes
974930 (http://support.microsoft.com/kb/974930) An application or service that queries information about a failover cluster by using the WMI provider may experience low performance or a time-out exception
980054 (http://support.microsoft.com/kb/980054) Recommended hotfixes and updates for Windows Server 2008 R2-based server clusters
Recommended updates for Windows Server 2003 systems that have Virtual Server installed
936059 (http://support.microsoft.com/kb/936059) An update is available for the Windows Remote Management feature in Windows Server 2003 and in Windows XP
Recommended updates that should be applied to Windows 2000 systems before a P2V is performed
834010 (http://support.microsoft.com/kb/834010) A deadlock occurs when a program that uses WMI calls the LoadLibrary() or the FreeLibrary() function in Windows 2000
843527 (http://support.microsoft.com/kb/843527) The Win32_SCSIController WMI class cannot obtain SCSI controller information after you install the MS04-011 security update
892294 (http://support.microsoft.com/kb/892294) A WMI event notification query does not detect a user permissions change on Windows 2000 or Windows Server 2003
More info : http://support.microsoft.com/kb/2397711
Enhances the performance of the Cluster WMI (MSCluster) calls by SCVMM
The cluster team is constantly trying to optimize VMI performance, and this especially true for Hyper-V and SCVMM integration.
If you are using SCVMM or WMI, Microsoft Cluster Team recommend installing the following hotfix on all cluster nodes which enhances the performance of the Cluster WMI (MSCluster) calls by SCVMM: http://support.microsoft.com/kb/974930
(Thanks to Symon Perriman)
SCVMM 2008 R2 SP1 RC is now ready to download
For those who are participant in a Microsoft Connect beta program : SCVMM 2008 R2 Beta :
The SCVMM 2008 R2 Service Pack 1 Release Candidate is now ready to download from https://connect.microsoft.com/site799
This release adds support for Windows Server 2008 R2 SP1 RC to SCVMM. We’ve added the necessary properties and controls to allow you to create and manage Dynamic Memory and RemoteFX enabled on virtual machines on Windows Server 2008 R2 SP1 Hyper-V hosts.
Since this is a pre-release version, usage of this is limited to test environments. You’re encouraged to ask questions via theSCVMM forums





















