Creating an NLB Cluster
There are three key steps to creating an NLB cluster in Windows Server 2008:

1. Install the NLB Feature into Server 2008 on each host that you will add to an NLB cluster.
2. Use the New Cluster wizard to create the cluster and add the first host.
3. Use the Add Host wizard to add one or more nodes to your cluster

Please create host record in DNS for cluster name (Virtual IP) before installing NLB and make sure both nodes host records are present in DNS.
Installing NLB in Server 2008
This is extremely easy. First you run Server Manager, and select Features from the tree and click on Add Features:

From the Add Features wizard just selects Network Load Balancing and click Next:

Finally from the Confirm Installation Selections click install:

After a few seconds, NLB will be installed on the first host. You need to repeat this installation on each host you plan to add to your NLB Cluster. Installing the NLB feature does NOT require a reboot, but removing it does.
Add another NIC for heart beat
Creating your NLB Cluster
Once NLB is installed, you create your cluster by first bringing up the NLB Cluster Manager:

The right clicks the Network Load Balancing cluster node in the left pane, and select New Cluster:

This brings up the first page of the New Cluster Wizard – here you select the first member of your cluster by adding the IP address or DNS name into the Host box:

This shows you the interfaces on this host that you can use for configuring a new cluster. Chose the interface and click Next:

This brings up the Host Parameters page, where you enter the IP address to be used for the cluster for the cluster, and then you click next:

This brings up the Cluster IP address page. Here you add the address used by clients to connect to nodes in the cluster:

After adding the IP address, and clicking next, the New Cluster wizard displays the Cluster Parameters where you specify the cluster IP configuration and the cluster operation mode (and click next):

Leaving all the default for the port rules; by default its set to all ports with Single affinity, which is sticky. For more information on Port Rules

The Wizard then does the necessary configuration, resulting in a single node NLB cluster, shown in the NLB manager like this:

Adding Additional Nodes
A single node cluster is not much value, so you next need to add an additional node (or nodes). To add a node, you right click your newly created cluster and select Add Host to Cluster:

This brings up the Add Host to Cluster: Connect page where you specify the host to add, and the interface used in the cluster:

Next you specify the new host’s parameters:

Then you get to update, in needed the cluster’s port rules:

Clicking next completes the wizard, resulting in a 2nd host in the cluster. As seen by NLB Manager:

• Make sure that both node’s status changes to "Converged"
• Make sure each node has a unique "host priority" ID
• Make sure each node is "started" under "initial host state"
• Make sure you see a "succeeded" message in the log window for the second node

1. Log out of the Citrix online Plug-in on the Win 7 machine and log back on as the citrix user account. Launch the WinWord application.
2. Use the Citrix online plug-in to log on as the domain\citrix user
   1. Click the Citrix online Plug-in icon and click Notepad to launch the application
3. Log on to the XenAppServer machine as the CitrixAdmin user, log on to the Web Interface using the CitrixAdmin account through Internet Explorer and launch the Notepad application
4. Switch to the win 7 virtual machine
5. Log on to the win 7 virtual machine as the CitrixAdmin user
6. Click Start > Internet Explorer and navigate to the Web Interface site athttp://xenappservername/citrix/xenapp.
7. Log on to the Web Interface as the CitrixAdmin user.
8. Launch the Notepad application.An error appears. The load evaluator that was created and applied to XenAppServer is reporting a full load and is no longer accepting connections.
9. Log off of the Web Interface and close Internet Explorer.

Enables system administrators to view and evaluate individual users' usage and experience with Microsoft Exchange Server.

Use the Microsoft Exchange Server User Monitor to gather real-time data to better understand current client usage patterns, and to plan for future work. Administrators can view several items, including IP addresses used by clients, versions and modes of Microsoft Office Outlook, and resources such as CPU usage, server-side processor latency, and total latency for network and processing. Works with Microsoft Exchange Server 2000, 2003, 2007 and 2010.

Source: http://www.microsoft.com/en-us/download/details.aspx?id=11461

Additionally exchange servers can be monitored trough built-in performance tools such as Performance Monitor and Performance Troubleshooter under EMC Toolbox.

Also PowerShell can be used to obtain e.g. top 10 users that are most actively using Exchange Server:

Get-StoreUsageStatistics -Database Database1 | Sort-Object TimeInserver -Descending | Select-Object -First 10 | ft -AutoSize

Get-StoreUsageStatistics -Server Server1 | Sort-Object TimeInserver -Descending | Select-Object -First 10 | ft -AutoSize

How to remove mailbox aliases based on pattern string?
First of all download and install Free PowerShell Commands for Active Directory
Removes all aliases of @example.local domain in User1 mailbox:

Get-QADUser -Identity User1 | Remove-QADProxyAddress -Pattern '*@example.local'

Removes all @example.local aliases from Exchange:

Get-QADUser | Remove-QADProxyAddress -Pattern '*@example.local'
Use 'X400:*' pattern to remove all X400 email addresses from Exchange: 
Get-QADUser | Remove-QADProxyAddress -Pattern 'X400:*'
Note: These cmdlets are useful when there is no ability to apply address book policies (in case of Exchange infrastructure migration when email address were migrated from former Exchange)
For Distribution groups can be user Get-QADGroup cmdlet:
Get-QADGroup | Remove-QADProxyAddress -Pattern '*@example.local'
Note: Before any changes make sure that you have backed up your Active Directory. Also you can export to CSV file current information about Users and Groups aliases:

Get-QADUser | select name,@{Name='proxyAddresses';Expression={[string]::join(";", ($_.proxyAddresses))}} | export-csv C:\FileName1.csv
Get-QADGroup | select name,@{Name='proxyAddresses';Expression={[string]::join(";", ($_.proxyAddresses))}} | export-csv C:\FileName2.csv

How to get list of huge mailboxes in Exchange 2010 via PowerShell?
Information can be obtained from Mailbox server or Database:
Get-MailboxServer -identity ServerName | Get-MailboxStatistics
Get-Mailbox -database DatabaseName | Get-MailboxStatistics
Mailboxes with more than 5Gb size:
Get-MailboxServer -identity ServerName | Get-MailboxStatistics | Where {$_.TotalItemSize -ge 5GB} | sort-Object TotalItemSize -descending | Select-Object DisplayName,ItemCount,@{name=”MailboxSize”;exp={$_.totalitemsize}}
Also output can be saved in CSV file using:
export-csv C:\filename.csv
As result:
Get-MailboxServer -identity ServerName | Get-MailboxStatistics | Where {$_.TotalItemSize -ge 5GB} | sort-Object TotalItemSize -descending | Select-Object DisplayName,ItemCount,@{name=”MailboxSize”;exp={$_.totalitemsize}} | export-csv C:\filename.csv