HyperV_Mon is my free tool for monitoring and diagnosing performance issues with Hyper-V.
After prompting from a user with a lot more processors then the test systems here, I updated the HyperV_Mon tool to handle resizing in general, and to adjust the root partition processor display. This new version is a minor release (1.8.0).
In the works will be a version 2.0 that will look at 2008 R2 with SP1 changes. This should come out in Q1 of next year.
Download it HERE
Microsoft provides some documentation examples of well-designed, cost-effective Exchange 2010 solutions deployed on hardware offered by some partners from Microsoft.
16000 Mailboxes in a Single Site Deployed on IBM and Brocade Hardware
500 Mailboxes in a Single Site Running Hyper-V on Dell Servers
It’s really nice info to read 
if you designing a Exchange 2010 Solution for your company or customer.
Jonathan has created a nice script. This script checks witch updates are missing from Hyper-V hosts and SCVMM Server.
What updates?
Updates are regularly released for SCVMM Server, Hosts, and the Admin Console. These updates must be applied to all Hosts no matter how many you have. Updates are also released for technologies SCVMM leverages:
As well as components SCVMM cannot function without:
The difficulty is in making sure all systems are fully updated. This is a time-consuming task.
WSUS takes care of this for me…
Not necessarily. There are certain Hotfixes that need to be downloaded manually, but for the most part Windows Update is the key. WSUS is Microsoft’s solution to distributing Windows Updates within an enterprise, and this pulls from Windows Update as well. Unfortunately, rules in WSUS are sometimes set up such that all updates required do not find their way to SCVMM systems. So, there are layers of complexity in keeping systems up to date.
Prevent problems with VMMUpdate
With this script you now or that your Hyper-V hosts & SCVMM Server are up to date.
To download the latest follow the link HERE
The management pack monitors the health status of System Center Data Protection Manager 2010 and its components. It alerts the admin on critical health state and it provides certain break fix tasks to take corrective actions.
The following alerts are new in this release of the DPM 2010 Management Pack:
You can download the System Center Data Protection Manager 2010 Monitoring Management Pack HERE
Microsoft released a nice manual for monitoring and managing DPM servers and tape libraries, and protected computers that are running Microsoft Exchange Server, Microsoft SQL Server, Windows SharePoint Services, Microsoft Virtual Server, or the Hyper-V role in Windows Server 2008 or Windows Server 2008 R2. This guide also provides instructions for setting up protection of data on desktop computers that are connected to the network, and portable computers that are connected to the network intermittently, and for setting up disaster recovery.
Microsoft has released some new sizing calculators for DPM 2010.
DPM_2010_Storage_Calculator_for_Exchange_2010.xlsx
You can download VMware vSphere 4.1 HERE
One of the new features of Exchange 2010 is DAG Database Availability Group. The Customer were i work now wants Exchange 2010 in a dag cluster because they have a datacenter for failback.
Because i going to implement Exchange 2010 at the customer i created a test setup.
Configuration:
Server 1 – HYPERVDC-01
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.90
Roles: Active Directory / Hyper-V
Server 2 – CHEK10-01
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.91
Roles: Exchange 2010 HT / CAS
Server 3 – CHEK10-02
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.92
Roles: Exchange 2010 HT / CAS
Server 4 – DAGEK10-01
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 192.168.150.93
Roles: Exchange 2010 MBX
Server 5 – DAGEK10-02
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 192.168.150.94
Roles: Exchange 2010 MBX
Creating the DAG
Groupname: DAG01
Witness Server: CHKEK10-01 (Microsoft says use one of the CAS or Hub Servers. You cannot use a DAG Server! If you want use a non Exchange 2010 server you must at the Exchange Trusted Subsystem group at the local administrators group.
Witness Directory: C:\DAG01 
Add a MB server to a DAG
Setting a IP address on a Database Availability Group
With the following command you can set the DAG Database Availability Group an IP address. Set-DatabaseAvailabilityGroup -Identity DAG01 -DatabaseAvailabilityGroupIpAddresses 192.168.150.96
When you want to use the Client Access Array function from Exchange 2010. You have to options.
1. Use the NLB function in Windows. Check this article that i blogged: Configuring NLB for Exchange 2010 for Cas load balancing.
2. When you have 2 physical load balancers in combination with a DAG cluster.
I haven’t any pre-Created CAS arrays in my hyper-v.local domain. But you would to check of there is any pre-created CAS Arrays. Run the command below. if you didn’t create a CAS Array before, you will get nothing .
Get-ClientAccessArray 
Then you should create new Client Access Array. Run below Cmdlet in Exchange Management Console
New-ClientAccessArray –Name “CasArray1” –Fqdn casarray.hyper-v.local -Site “Default-First-Site-Name”
Now we have finished creating a CAS array. Then we must associate databases with this CAS Array.
Use below CMDLet to add mailbox database to CAS array. We can attach all mailbox databases at once as shown as shown below
Get-MailboxDatabase | Set-MailboxDatabase -RPCClientAccessServer “casarray.hyper-v.local” 
Exchange’s dependence on the Client Access Server (CAS) role has increased dramatically in Exchange 2010. This is because, in Exchange 2010, on-network Outlook MAPI connectivity now connects to a mailbox through the CAS role via the RPC Client Access Service. As a result, high availability of the CAS role is crucial since any failure of CAS could affect Outlook client connectivity. For smaller implementations or those where the limitations of native Windows Network Load Balancing (NLB) are not a major problem
You need two or more Exchange 2010 servers (each with two NICs) with the CAS role installed have been deployed, you are ready to start configuring NLB to provide high availability and load balancing. First, you must allocate a dedicated private IP address and create an associated A record in DNS for the NLB cluster.
This IP address and name are what clients will connect to and against which the ClientAccessArray will be created. In this blog post, I will use 192.168.150.95 and casarray.hyper-v.local
To simplify the management of your NLB cluster members, I recommend that you name each NIC’s network connection so that it is easy to understand what function the NIC serves. For example, as depicted below, I have named the connections “LAN” (used for communication with clients and servers on the network) and “NLB” (used for internal NLB heartbeat). This process should be repeated on all NLB cluster members.
IP configuration:
Server 1:
LAN:
IP: 192.168.150.90
Subnetmask: 255.255.255.0
Gateway: 192.168.150.254
DNS: 192.168.150.1
Server 2:
LAN:
IP: 192.168.150.91
Subnetmask: 255.255.255.0
Gateway: 192.168.150.254
DNS: 192.168.150.1 
Configuring NLB – First Member
On each NLB cluster member, NLB must be installed. With Windows 2008 R2, this can be completed simply by running the command “ServerManagerCmd -i NLB” via a command prompt. Once NLB has been installed, launch the Network Load Balancing Manager to continue the configuration process.
![clip_image003[1]](https://i0.wp.com/www.wardvissers.nl/wp-content/uploads/ConfiguringNLBforExchange2010CASLoadBala_131D5/clip_image0031.jpg "clip_image003[1]")
To create your new cluster, you can right-click Network Load Balancing Clusters or simply click Cluster, New. In the New Cluster wizard, enter the name of the first server in the NLB cluster (for example, CHEK10-01) and click Connect. This will display the available NICs on the server, at which point the NLB NIC should be chosen before clicking Next.
Since this is the first member of the NLB cluster, you can leave the all of the Host Parameters at their default values, as depicted below. Please note that the Priority value should be configured as 1 for the first member.
Next we must configure the IP address and subnet mask of the NLB cluster, which is the IP address for which we created a DNS A record at the very beginning of this process. In this example, this would be 192.168.150.95 and 255.255.255.0, respectively.
For the Cluster Parameters, we want to enter the FQDN of the DNS A record we created at the very beginning of this process (casarray.hyper-v.local). In addition, Unicast should be selected as the desired clustered operation mode.
I lieve the Port Rules how they are and end with Finish 
Let the NLB cluster converge with its first member and you should eventually see the cluster report success.
![clip_image015[1]](https://i0.wp.com/www.wardvissers.nl/wp-content/uploads/ConfiguringNLBforExchange2010CASLoadBala_131D5/clip_image0151.jpg "clip_image015[1]")
Now you can proceed with adding your second cluster member.
Configuring NLB – Second/Subsequent Member
After the configuration of the NLB cluster itself and the first NLB cluster member has been completed, you are ready to add additional members. Provided that NLB has been installed, you can simply right-click on your NLB cluster in the Network Load Balancing Manager and click Add Host To Cluster.
Enter the name of the second NLB cluster member, for example CHEK10-02, and click Connect. Be sure to choose the NLB LAN NIC and click Next.
On the Host Parameters screen, ensure that the Priority is set to 2 (or as appropriate, depending on how many cluster members you have) and click Next.
Confirm that your port rules are accurate and, if they are, click Finish to add your second NLB cluster member.
Let the NLB cluster converge with the new member and, eventually, it should report success.
At this point, you have an NLB cluster with two members!
Next configure CASARRAY.