Storage Solutions for Exchange 2010

Compellent

5000 Mailboxes or greater

Dell

1-1000 Mailboxes

1001-5000 Mailboxes

5000 Mailboxes or greater

EMC

1-1000 Mailboxes

1001-5000 Mailboxes

5000 Mailboxes or greater

Fujitsu

1001-5000 Mailboxes

HDS

5000 Mailboxes or greater

HP

1001-5000 Mailboxes

5000 Mailboxes or greater

IBM

5000 Mailboxes or greater

NetApp

1001-5000 Mailboxes

5000 Mailboxes or greater

Oracle (Sun)

5000 Mailboxes or greater

Xiotech

1-1000 Mailboxes

1001-5000 Mailboxes

5000 Mailboxes or greater

Hardware Load Balancers for Exchange Server 2010

Listed below are hardware load balancers that have been tested by the vendor and reviewed by Microsoft to meet Exchange Server 2010 requirements. It is recommended that you visit the vendor’s web site for the latest information regarding product specifications, capacity, country support and documentation including release notes and known issues. Please contact the vendor for more information on these products.

Hardware Load Balancers for Exchange Server 2010

Vendor

Qualified Product

Software Version Tested

Vendor’s Exchange Page

Barracuda Networks

Barracuda Load Balancer Model 340, 440, 640

3.3.1.005

Barracuda Deployment Guide

Brocade

ServerIron ADX 1000, 4000, 10000

V12.1

Brocade and Microsoft Exchange Server

Cisco

Application Control Engine (ACE)

A2(3.0)

Cisco Deployment Guide

Coyote Point Systems

Equalizer E250GX, E350GX, E450GX, E650GX

8.6.0b

Equalizer Deployment Guide for Exchange

Citrix Systems

Netscaler

9.1.102.8

Netscaler for Microsoft Exchange

F5

BIG-IP Local Traffic Manager (LTM)

10.0.1 and 10.1

F5 Solutions

KEMP Technologies

LoadMaster Models: 2200, 2500, 2600, 3500, 3600, 5500

5.1-28

KEMP Exchange 2010 Deployment Guide

Kemp Technologies is added to list. This is a nice thing because the customer where I work have 2 new load balancers Open-mouthed smile.

Software Load Balancers for Exchange Server 2010

Listed below are software load balancers that have been tested by the vendor and reviewed by Microsoft to meet Exchange Server 2010 requirements. It is recommended that you visit the vendor’s web site for the latest information regarding product specifications, capacity, country support and documentation including release notes and known issues. Please contact the vendor for more information on these products.

Vendor

Qualified Product

Software Version Tested

Vendor’s Exchange Page

Citrix Systems

Netscaler VPX

9.1.102.8

Netscaler for Microsoft Exchange

F5

BIG-IP Local Traffic Manager (LTM) Virtual Edition

10.1 and 10.2

F5 Solutions

KEMP Technologies

LoadMaster VLM

5.1-28

KEMP Exchange 2010 Deployment Guide

How to demote a Exchange 2007 CCR Cluster with Load balanced CAS/HUB Servers

I used the following steps to do this.

1. All public folders and system folders that are housed on the Exchange 2007 CCR Cluster computer must be replicated to another Exchange 2007/2010 computer that is in the site.

2. Verify the contents of the public folder store with the following Powershell commands
Get-PublicFolderStatistics -server <Exchange 2007_Server_Name> | fl | out-file d:\PFstat.txt

Get-PublicFolder -server < Exchange 2007_Server_Name > \ -recurse | fl | out-file d:\PFIPMSub.txt

Get-PublicFolder -server < Exchange 2007_Server_Name > \non_ipm_subtree -recurse | fl | out-file d:\PFNonIPMSub.txt.

3. Remove the replicas from the public folder store

MoveAllReplicas.ps1 -Server ccrclustername –NewServer newservername

4. Remove the public folder store

Remove–PublicFolderDatabase –Identity "Public_Folder_Store_Name"

5. Change the server that is responsible for generating the Offline Address Lists

Move-OfflineAddressBook –Identity OfflineAddressBookIdParameter -Server ServerIdParameter

6. Move the Routing Group Connectors by using the following command:

Get-RoutingGroupConnector | where {$_.SourceTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -SourceTransportServers "<Second Exchange 2007 server>"
Get-RoutingGroupConnector | where {$_.TargetTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -TargetTransportServers <Second Exchange 2007 server>

7. To modify any Send connectors that have the first Exchange 2007 server as the source transport server, run the following commands:

Get-SendConnector | where {$_.SourceTransportServers -like "<First Exchange 2007 server>"} | Set-SendConnector -SourceTransportServers "<Second Exchange 2007 server>"

8.Important:
How to use the Exchange Server SP1 2007 Setup wizard to remove Exchange 2007

  1. Log on to the server from which you want to remove Exchange 2007.

  2. Open Control Panel, and then double-click Programs and Features.

  3. In Programs and Features, select Microsoft Exchange Server 2007, and then click Uninstall.

    If you click Change instead of Uninstall, you can add server roles, but you cannot remove server roles.

  4. In the Exchange Server 2007 SP1 Setup wizard, on the Exchange Maintenance Mode page, click Next.

  5. On the Server Role Selection page, clear all the server role check boxes, clear the Management Tools check box, and then click Next.

    By default, all server roles are selected. This indicates that no server roles will be removed. To remove a server role, you must clear the appropriate check box.

  6. On the Readiness Checks page, after the check completes, click Uninstall.

  7. On the Completion page, click Finish.

  8. (Optional) If you are removing Exchange from a Mailbox server, remove the Exchange database files (*.edb) and storage group log files (*.log).

    If you reinstall the Mailbox server role on this server, you must first remove the database and log files from the server.

  9. (Optional) Remove the setup log files that are located at %systemdrive%\ExchangeSetupLogs.

  10. (Optional) Remove the following virtual servers that are created for Exchange 2007 under the Default Web Site in IIS:

    • Microsoft-Server-ActiveSync
    • OAB
    • Owa

    When you remove Exchange 2007, neither IIS nor these virtual servers are removed

9.  First Remove the Passive Mailbox Node

10. Second the Primary Mailbox Role

11. Remove the CAS/HUB’s Role on the nodes
Important: NOT AT THE SAME TIME

12. Demote the Cluster

13. Demote the NLB Cluster

14. Remove the Servers from the domain

15. Shutdown the Servers

16. Take a cold bier when you are don with testing and everything works Winking smile

Exchange 2010 Free space within a Mailbox Database

In previous versions of Exchange Server there was a process called "online maintenance". This process ran at night and one of the tasks was to an online defragmentation to do within the database. The task was that the empty spaces are grouped together resulting in more efficient use of the Mailbox Database.

In Exchange 2010 has changed and there is a 24×7 online process. There is also the option of online, direct to see how much space is available within the databases with the Powershell command:

Get-MailboxDatabase –Status | fl Name,AvailableNewMailboxSpace

Output:

image

If we were to do an offline defragmentation on the Mailbox Database the mailbox database would be approximately a 90MB smaller.

This is on my test Exchange 2010 server with only a few mailboxes. In normal production enjoinment this will  be a lot more.

In Exchange 2010 you can you a online mailbox move. There fore you can
better create a new mailbox database en move all the mailboxes to the new mailbox database.
Then you have the same result with no down time.

Microsoft Assessment and Planning Toolkit 5.5

The Microsoft Assessment and Planning Toolkit (MAP) is an agentless, automated, multi-product planning and assessment tool for quicker and easier desktop and server migrations. MAP provides detailed readiness assessment reports and executive proposals with extensive hardware and software information, and actionable recommendations to help organizations accelerate their IT infrastructure planning process, and gather more detail on assets that reside within their current environment. MAP also provides server utilization data for Hyper-V server virtualization planning; identifying server placements, and performing virtualization candidate assessments, including ROI analysis for server consolidation with Hyper-V.

MAP helps make the following IT planning projects faster and easier:

  • Migration to Windows 7, Windows Server 2008 R2, and Microsoft Office 2010
  • Migration to Windows 7 compatible versions of Internet Explorer
  • Migration to cloud-based services
  • Server virtualization with Hyper-V
  • SQL Server consolidation and migration to SQL Server 2008 R2
  • Assessment of current software usage and client access history for simplified software asset management
  • PC security assessment and migration to Microsoft Forefront Client Security

You can use MAP to inventory the following technologies:

  • Windows 7
  • Windows Vista
  • Windows XP Professional
  • Office 2010 and previous versions
  • Windows Server 2008 or Windows Server 2008 R2
  • Windows Server 2003 or Windows Server 2003 R2
  • Windows 2000 Professional or Windows 2000 Server
  • VMware ESX
  • VMware ESXi
  • VMware Server
  • Linux variants
  • LAMP application stack discovery
  • SQL Server 2008
  • SQL Server 2008 R2
  • MySQL
  • Oracle
  • Sybase

Download MAP 5.5 HERE

Rollup 5 for Exchange Server 2010

Microsoft has released rollup 5 for Exchange Server 2010:

This update rollup is highly recommended for all Exchange Server 2010 customers.

For a list of changes that are included in this update rollup, see KB2407113.

The is only one fix:

You cannot uninstall Exchange Server 2010 RTM after you install Update Rollup 2, Update Rollup 3, or Update Rollup 4 for Exchange Server 2010

Download the rollup here

Note to Forefront users:

If you don’t disable Forefront before installing a rollup or service pack, and enable afterwards, you run the risk of Exchange related services not starting. You can disable Forefront by going to a command prompt and navigating to the Forefront directory and running FSCUtility /disable. To enable Forefront after installation of a UR or SP, run FSCUtility /enable.

Favo links for Microsoft Lync

The Lync Server Open Interoperability Program is now available

http://technet.microsoft.com/en-us/lync/gg131938.aspx

Other useful Links:

Hardware Requirements. Link

Bandwidth Table. Link

Lync New features – server side. Link

Lync New features – Client Side. Link

Port Requirements. Link

Lync Server 2010 Protocol Workloads Poster. Link

Architecture – Server Roles. Link

Architecture – Topologies. Link

Publishing Outlook Anywhere Using NTLM Authentication With Forefront TMG or Forefront UAG

This white paper provides detailed information about publishing Microsoft Exchange Server 2010 using Forefront TMG or Forefront UAG to secure access for Outlook Anywhere when using NTLM Authentication.

When you publish Exchange, Microsoft offers two software-based options: Microsoft Forefront Threat Management Gateway 2010 and Microsoft Forefront Unified Access Gateway 2010. Both options offer publishing wizards and security features to provide secure access to Exchange when it’s accessed from outside the safety of the corporate network.

This white paper provides detailed information about publishing Microsoft Exchange Server 2010 using Forefront TMG or Forefront UAG, including how to choose between them for different scenarios, and provides specific steps you can take to configure Forefront TMG and Forefront UAG to publish Exchange 2010 while using NTLM authentication for Outlook Anywhere access.

Download details Publishing Outlook Anywhere Using NTLM Authentication With Forefront TMG or Forefront UAG

Microsoft Lync Error: Microsoft.Rtc.Common.Data.SqlConnectionException Cannot open database xds requested by the login. The login failed. Login failed for user Domain\administrator.

Lync

Error:

An error occurred: Microsoft.Rtc.Common.Data.SqlConnectionException Cannot open database xds requested by the login. The login failed. Login failed for user CONTOSO\administrator.

When Installing Lync there is automatically added a firewall rule that opend the port for the SQL Server Service

Solution:

Create a Windows Firewall port exceptions to enable access to the SQL Server Browser service, follow these steps:

    1. Click Start, and then click Control Panel.
    2. Open the Windows Firewall program.
    3. Click Change Settings to open the Windows Firewall Settings dialog box.
    4. Make sure that Windows Firewall is turned on, and then click the Exceptions tab.
    5. Click Add port to open the Add a port dialog box.
    6. Enter a name for the port exception, such as SQL Server Browser Service.
    7. Make sure that UDP is selected, and then enter UDP port number 1434. This is the default port that the SQL Server Browser service listens on.
    8. Click OK two times to close the Windows Firewall Settings dialog box