UC Unleashed

Organizations who use Exchange server typically develop checklists or procedures for day-to-day maintenance operations. This includes updates, backups, security, disaster recovery planning, etc. Sometimes, new Exchange orgs cobble together these checklists based on other server platforms already in place, or from colleagues at other organizations, online materials, etc. Microsoft has made available several checklists for each version that will allow an organization to provide comprehensive checklists for maintaining Exchange. These can be used as-is, or customized for each environment.

• Exchange Server 2010 – Operations Checklists http://msdn.microsoft.com/en-us/library/bb232187(EXCHG.140).aspx
• Daily Operations Checklist
• Weekly Operations Checklist
• Monthly Operations Checklist
• Summary Checklist
• Exchange Server 2007 – Operations Checklists http://technet.microsoft.com/en-us/library/bb232187(EXCHG.80).aspx which includes:
• Daily Operations Checklist
• Weekly Operations Checklist
• Monthly Operations Checklist
• Summary Checklist
• Exchange Server 2003 – Operations Checklists http://technet.microsoft.com/en-us/library/aa998774(EXCHG.65).aspx which includes:
• Disaster Recovery Preparation Checklist
• Summary Checklist
• Monthly Operations Checklist
• Weekly Operations Checklist
• Daily Operations Checklist

Today, Microsoft released a cumulative update for Outlook 2007 that provides access to Exchange 2010’s Archive mailbox. A long awaited feature, Outlook 2007 users previously had to rely on Outlook Web Access to access their archive. Some organizations have held off deploying Exchange’s archive feature because they had Outlook 2007 deployed. Now, the wait is over.

Hotfix 2458611 is now available for the download for the x86 platform. Among the features that will become available to Outlook 2007 users are:

1. Accessing messages in the archive
2. Moving messages into the archive
3. Accessing the archive of a manager when granted delegate access

There are some known limitations when compared to Outlook 2010 and the archive. Among them are the lack of support for archive policies and the ability to search independently of the mailbox and archive.

For more information on Exchange 2010’s personal archive feature, see:

• Email Archiving in Exchange 2010
• Understanding Personal Archives

Microsoft has released the following update rollup for Exchange Server 2010:

• Update Rollup 5 for Exchange Server 2007 SP2 (2407132)

If you’re running Exchange Server 2007 SP2, you need to apply Update Rollup 5 for Exchange 2007 to address the issues listed below.

Remember, you only need to download the latest update for the version of Exchange that you’re running.

Here is a list of the fixes included in update rollup 5:

1. MSRC 10-024 Vulnerability in Microsoft Exchange Server could allow denial of service

Download the rollup here.

Microsoft also announced that there are no plans to release further updates for Exchange Server 2007 SP2. Customers are advised to upgrade to SP3.

Installation Notes:

If you haven’t installed Exchange Server yet, you can use the info at Quicker Exchange installs complete with service packs and rollups to save you some time.

Microsoft Update can’t detect rollups for Exchange 2010 servers that are members of a Database Availability Group (DAG). See the post Installing Exchange 2010 Rollups on DAG Servers for info, and a script, for installing update rollups.

Update Rollups should be applied to Internet facing Client Access Servers before being installed on non-Internet facing Client Access Servers.

If you’re installing the update rollup on Exchange servers that don’t have Internet access, see “Installing Exchange 2007 & 2010 rollups on servers that don’t have Internet access” for some additional steps.

Also, the installer and Add/Remove Programs text is only in English – even when being installed on non-English systems.

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.

Microsoft has released the following update rollup for Exchange Server 2010:

• Update Rollup 5 for Exchange Server 2010 RTM (2407133)

If you’re running Exchange Server 2010 RTM, you need to apply Update Rollup 5 for Exchange 2010 to address the issues listed below.

Remember, you only need to download the latest update for the version of Exchange that you’re running.

Here is a list of the fixes included in update rollup 5:

1. 2266458 Setup cannot perform a mode:/uninstall on a HT role server since RU2 delivered MSFTE.msi

Download the rollup here.

Microsoft also announced that there are no plans to release further updates for Exchange 2010 RTM. Customers are advised to upgrade to SP1.

Installation Notes:

If you haven’t installed Exchange Server yet, you can use the info at Quicker Exchange installs complete with service packs and rollups to save you some time.

Microsoft Update can’t detect rollups for Exchange 2010 servers that are members of a Database Availability Group (DAG). See the post Installing Exchange 2010 Rollups on DAG Servers for info, and a script, for installing update rollups.

Update Rollups should be applied to Internet facing Client Access Servers before being installed on non-Internet facing Client Access Servers.

If you’re installing the update rollup on Exchange servers that don’t have Internet access, see “Installing Exchange 2007 & 2010 rollups on servers that don’t have Internet access” for some additional steps.

Also, the installer and Add/Remove Programs text is only in English – even when being installed on non-English systems.

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.

Microsoft has released the following update rollup for Exchange Server 2010:

• Update Rollup 2 for Exchange Server 2007 SP3 (2407025)

If you’re running Exchange Server 2007 SP3, you need to apply Update Rollup 2 for Exchange 2007 to address the issues listed below.

Remember, you only need to download the latest update for the version of Exchange that you’re running.

Here is a list of the fixes included in update rollup 2:

1. 972186 Need to include the server service as a required service for Exchange 2007 running on Server 2008
2. 2290105 OWA SharePointe/UNC Access is broken after SP3

Download the rollup here.

Microsoft also announced that UR3 for Exchange 2007 SP3 should be released in February.

Installation Notes:

If you haven’t installed Exchange Server yet, you can use the info at Quicker Exchange installs complete with service packs and rollups to save you some time.

Microsoft Update can’t detect rollups for Exchange 2010 servers that are members of a Database Availability Group (DAG). See the post Installing Exchange 2010 Rollups on DAG Servers for info, and a script, for installing update rollups.

Update Rollups should be applied to Internet facing Client Access Servers before being installed on non-Internet facing Client Access Servers.

If you’re installing the update rollup on Exchange servers that don’t have Internet access, see “Installing Exchange 2007 & 2010 rollups on servers that don’t have Internet access” for some additional steps.

Also, the installer and Add/Remove Programs text is only in English – even when being installed on non-English systems.

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.

Microsoft has released the following update rollup for Exchange Server 2010:

• Update Rollup 2 for Exchange Server 2010 SP1 (2425179)

If you’re running Exchange Server 2010 SP1, you need to apply Update Rollup 2 for Exchange 2010 to address the issues listed below.

Remember, you only need to download the latest update for the version of Exchange that you’re running.

Here is a list of the fixes included in update rollup 2:

1. 2322161 Passive DAG Copy Doesn’t Replay Logs if “Don’t mount this database at startup” is Checked
2. 2431500 Cannot connect using Outlook Anywhere as the same user from multiple XP Clients
3. 2409597 Implement OpenFlags.AlternateServer for PublicLogon

Download the rollup here.

Microsoft also announced that UR3 for Exchange 2010 SP1 should be released in February.

Installation Notes:

If you haven’t installed Exchange Server yet, you can use the info at Quicker Exchange installs complete with service packs and rollups to save you some time.

Microsoft Update can’t detect rollups for Exchange 2010 servers that are members of a Database Availability Group (DAG). See the post Installing Exchange 2010 Rollups on DAG Servers for info, and a script, for installing update rollups.

Update Rollups should be applied to Internet facing Client Access Servers before being installed on non-Internet facing Client Access Servers.

If you’re installing the update rollup on Exchange servers that don’t have Internet access, see “Installing Exchange 2007 & 2010 rollups on servers that don’t have Internet access” for some additional steps.

Also, the installer and Add/Remove Programs text is only in English – even when being installed on non-English systems.

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.