Network Ports used in Exchange 2010

Which ports Exchange 2010 uses?, you probably already read the Exchange 2010 Network Port Reference TechNet article located here.

At some point, when discussing with the network/firewall people or documenting your design, it might be required to visualize things. For this purpose you can use the following diagram.

network ports

Note that it’s a v1 and not all things are included.

Also, all ports are left at their default values and the diagram doesn’t reflect the fact that you can fix certain ports like the one for the DAG or the MAPI RPC port; that might be added in a later version


What’s new in Outlook 2010?

Well, Microsoft has published an detailing all of the new features in Outlook 2010.  There is a lot of new or improved features in this version, and as I said , this release of Outlook and Office 2010 for that matter are a fantastic example of when Microsoft listens to customers and responds with much needed updates.

Some of the changes detailed in the article are:

  • 64 bit and 32 bit versions
    • Just be careful that your add-ins will work with the 64 bit version.
    • Also, you must install the entire Office Suite in the same “bitness”, no intermixing of 32 and 64 bit.
  • Calendar preview in the meeting request
    • You no longer have to click on view calendar to see what in the world is conflicting with that new meeting request you just got.
  • Conversation view and Conversation cleanup
    • This enables you to see the entire conversation even if parts of it are not in the same folder and you can have Outlook delete parts of the conversation you have in newer messages.
  • Multiple Exchange Accounts
    • Currently, I have 4 mailboxes open against 3 different Exchange Orgs, all using Outlook Anywhere.  How cool is that!
  • Tighter integration with OCS and Communicator
  • Roaming Auto Complete (Nicknames)
    • Remember the fun NK2 files, they are now a thing of the past.  Your personal auto-complete list (Nicknames) are now stores in Exchange and go where you go.
  • And if you have Exchange 2010 to boot, you also get these:
    • Call answering and routing rules
    • Centralized Rights Management
    • Integrated Email Online Archive
    • Mailtips
    • Text Messaging through Exchange Activesync
  • Many many more…

Some of the items that have been removed are:

  • ANSI OST File creation support (Unicode will be used only)
  • Calendar rebasing tool (to fix DST issues)
  • WebDav protocol
  • Exchange 2000 and earlier server version connections
  • Most Recently Used list (this was the list of last opened “Other User’s Folders).
  • ScanOST.exe
  • Postmarking of email to signify it isn’t junk email.
  • Quick View (this was the file viewer in Windows 95, 98, and NT4)
  • Remote Mail (now replaced fully with Cache Mode)

DAG Maintenance on Exchange 2010 SP1

It's a simple process; you run a script to put a DAG member into maintenance mode, moving the active databases off the server. After maintenance has been completed, you run another script to take the server out of maintenance mode and then you can redistribute the databases across the DAG. The process is outlined in detail below.

1. Run the StartDagServerMaintenance.ps1 script to put the DAG member in maintenance mode
When you run this script, it moves all the active databases to other DAG members. It pauses the node in the cluster, and sets the DatabaseCopyAutoActivationPolicy mailbox server setting to Blocked. The Suspend-MailboxDatabaseCopy cmdlet is run for each database hosted by the DAG member, and the cluster core resources will be moved to another server in the DAG if needed.

[PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>.\StartDagServerMaintenance.ps1 -serverName testmbx-dag1

2. Run the StopDagServerMaintenance.ps1 script to take the DAG member out of maintenance mode
After maintenance is complete, run this script to take the server out of maintenance mode. It will run the Resume-MailboxDatabaseCopy cmdlet for each database its hosting, resume the node in the cluster, and set the DatabaseCopyAutoActivationPolicy setting to Unrestricted.

[PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>.\StopDagServerMaintenance.ps1 -serverName testmbx-dag1

You can run these scripts remotely from another server with the Exchange tools installed and specify the DAG member using the serverName parameter. Just make sure that the server you are running the scripts from has the Windows Failover Cluster Management tools installed.

3. Run RedistributeActiveDatabases.ps1 script to re-balance the active database copies across the DAG
Finally, you can run this script to redistribute the active mailbox databases across the DAG. There are two options for balancing active database copies within a DAG: by activation preference and by site and activation preference.

[PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>.\RedistributeActiveDatabases.ps1 -DagName TESTMBX-DAG -BalanceDbsByActivationPreference -ShowFinalDatabaseDistribution -Confirm:$false

When using the BalanceDbsByActivationPreference parameter the script tries to move the databases to their most preferred copy based on activation preference, regardless of the AD site. If you use the BalanceDbsBySiteAndActivationPreference parameter, the script will attempt to active the most preferred copy and also try to balance them within each AD site.

There are a number of parameters that can be used with this script. Run get-help .\RedistributeActiveDatabases.ps1 for more details. Also, all of these scripts are documented in Managing Mailbox Database Copies and Managing Database Availability Groups on TechNet.

Multiple Exchange Update Rollup Releases for Exchange 2007 Exchange 2010

Exchange CXP team released a number of Update Rollups for versions of Exchange Server to the Download Center and via Microsoft Update.

Update Rollup 2 for Exchange Server 2010 Service Pack 1
Update Rollup 2 for Exchange Server 2007 Service Pack 3
Update Rollup 5 for Exchange Server 2010 RTM
Update Rollup 5 for Exchange Server 2007 Service Pack 2

Note for Forefront users:

For those of you running Forefront, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup’s installation process. Without these steps, Exchange services for Information Store and Transport will not start back up. You will need to disable ForeFront via “fscutility /disable” before installing the patch and then re-enable after the patch by running “fscutility /enable” to start it up again post installation.

DAG’s Best practice Network Configuration

The table below shows recommended best practice on how to configure network cards for Mailbox Servers within one DAG

Adaptor Component


Replication NIC Setting

Client for Microsoft Networks



QoS Packet Scheduler



File and Printer Sharing for Microsoft Networks



Internet Protocol Version 6 (TCP/IP v6)



Internet Protocol Version 4 (TCP/IP v4)



Link-Layer Topology Discovery Mapper I/O Driver



Link-Layer Topology Discovery Responder



Register Connection in DNS



Default Gateway


(use static routes)

Experience Avaya Flare

Avaya announced a new family of real-time enterprise video products and services that focus on the end user experience. This is the next wave of Avaya’s “Fit for Purpose” solutions that is focused on “people”. The Avaya Flare Experience is a next-generation user experience that delivers unique collaboration capabilities across video, voice and text. The new solutions make high definition, low bandwidth video collaboration accessible for more employees in more enterprises through compelling cost and performance delivered by Avaya Aura™

By msexchangeanywhere Posted in Avaya