Here’s what’s new
· Rich application performance monitoring and diagnostics for .NET applications plus JEE application health monitoring
· Support for monitoring heterogeneous environments
· Integrated network device monitoring and alerts
· Simplified management infrastructure
· Common console across datacenter and clouds with customizable dashboards
Download from Connect : https://connect.microsoft.com/site799/Downloads/DownloadDetails.aspx?DownloadID=37329
What is comming in the new version?
16+virtual processors within a Hyper-V VM, to support large scale up workloads.
Hyper-V Replica. Today, replication is complex to configure and often requires expensive proprietary hardware. Hyper-V Replica is asynchronous, application consistent, virtual machine replication built-in to Windows Server 8. With Hyper-V Replica, you can replicate a virtual machine from one location to another with Hyper-V and a network connection. Hyper-V Replica works with any server vendor, any network vendor and any storage vendor. In addition, we will provide unlimited replication in the box.
Microsoft also is going to allow Windows Server 8 users to replicate unlimitedly without charging additional fees per virtual machine. On the other hand, VMware with their upcoming version of Site Recovery Manager (SRM) is going to charge customers a per VM replication to replicate. This is going to be interesting….
Several others new features coming in the next version of Windows Server. Stay Tuned…
Every since I came along with questions regarding Hyper-V and Network
In fact there are good articles talking about, but let’s summarize here:
1. Network Configuration
In Production, use multiple networks in your cluster. For a complete HA environment, I recommend at least 8 :
- 1 for Management. Microsoft recommends a dedicated network adapter for Hyper-V server management.
- 2 (teamed ) for Virtual machines.Virtual network configurations of the external type require a minimum of one network adapter.
- 2 (MPIO ) for SCSI.Microsoft recommends that IP storage communication have a dedicated network, so one adapter is required and two or more are necessary to support multipathing.
- 1 for Failover cluster.Windows failover cluster requires a private network.
- 1 for Live migration.This new Hyper-V R2 feature supports the migration of running virtual machines between Hyper-V servers. Microsoft recommends configuring a dedicated physical network adapter for live migration traffic. This network should be separate from the network for private communication between the cluster nodes, from the network for the virtual machine, and from the network for storage
- 1 for CSV. Microsoft recommends a dedicated network to support the communications traffic created by this new Hyper-V R2 feature. In the network adapter properties, Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks must be enabled to support SMB
Note: If your Hardware vendor supports NPAR ( Broadcom, Qlogic ), you can create “Virtual logical NIC’s” . The NPAR technology allows you to create up to 4 logical Nic’s, which means for example that a Blade with 4 10Gb NIC’s with NPAR that support the technology it’s a good start.
2. Network Prioritization
To rank a network, it is given a unique integer from 1 to 268,000,000+, which is called a “metric”. To view the networks, their metric values, and if they were automatically or manually configured, run the clustering PowerShell cmdlet:
PS > Get-ClusterNetwork | ft Name, Metric, AutoMetric
By default, all internal cluster network will have a metric value starting at 1000 and incrementing by 100. The first internal network which the cluster sees when it first comes online has a metric of 1000, the second has a metric of 1100, …
To change the value of a network metric, run:
PS > $n = Get-ClusterNetwork “Live Migration”
PS > $n.Metric = 1050
Overriding network prioritization behavior:
– Right-click on the network in Failover Cluster Manager
– Select Properties
– Change the radio buttons or checkboxes. If you select “Do not allow cluster network communication on this network”, then it will not be possible to send any “Cluster & CSV Traffic” or “Live Migration Traffic” through this network, even if the network has the lowest metric values. The cluster will honor this override and find the network with the next lowest value to send this type of traffic.
Overriding network prioritization behavior “Live Migration Traffic” , by changing the network’s properties:
The networks for live migration can be configured more granularly :
– Right-click on any Virtual Machine resource
– Select Properties
– Click the Network for live migration tab and then specify which networks can and cannot be used for “Live Migration Traffic” and in which order they should be used.
Note: Even though it appears that this setting may be unique to that specific VM, it is actually a global setting for live migration.
Upcoming end of support announcement
Windows Vista Service Pack 1 (SP1) will reach the end of support on July 12, 2011. From that date onward, Microsoft will no longer provide support or free security updates for Windows Vista Service Pack 1 (SP1). In order to stay secure and continue support you must upgrade to Service Pack 2 (SP2).
Products no longer supported
- As announced in 2008, support for Windows XP Service Pack 2 (SP2) ended on July 13, 2010.
- Also announced in 2008, support for Windows 2000 ended on July 13, 2010.
- Support for Windows Vista Release to Manufacturing (RTM) ended April 13, 2010.
Important: There is no Service Pack 3 for a 64-bit version of Windows XP. If you are running a 64-bit version of Windows XP with Service Pack 2, you are on the latest service pack and will continue to be eligible for support and receive updates until April 8, 2014.
To find out if you are running a 64-bit version of Windows XP :
- Right-click My Computer, then click Properties.
- If you do not see “64-bit” listed, then you are running a 32-bit version and you need to install Service
- If “64-bit” is listed under System, then you are running a 64-bit version.)