Multiple December Update Rollup Releases


 

Earlier today the 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 SP1

This update contains a number of customer reported and internally found issues since the release of RU1. In particular we would like to specifically call out the following fixes which are included in this release:

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

Update Rollup 3 for Exchange Server 2010 Service Pack 1 is currently scheduled to release in February.

Update Rollup 2 for Exchange Server 2007 SP3

This update contains a number of customer reported and internally found issues since the release of RU1. In particular we would like to specifically call out the following fixes which are included in this release:

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

Update Rollup 3 for Exchange Server 2007 Service Pack 3 is currently scheduled to release in February.

Update Rollup 5 for Exchange Server 2010 RTM

This update contains an internally found issue which can impact upgrades from RTM RU4 to Service Pack 1. We have opted to release an out-of-band update rollup for Exchange 2010 RTM proactively to ensure customers have as smooth an upgrade experience as possible.

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

Currently, we have no plans to release future update rollups for Exchange Server 2010 RTM. We strongly recommend customers upgrade to Service Pack 1 with the latest Update Rollup after installing this update.

Update Rollup 5 for Exchange Server 2007 SP2

This security update was released earlier this morning via the Microsoft Security Response Center. Details of this bulletin and it’s fix can be found below:

Currently, we have no plans to release future update rollups for Exchange Server 2007 SP2. Instead, we strongly recommend customers upgrade to Service Pack 3 with the latest Update Rollup.

General Notes:

Note for Exchange 2010 Customers using the Arabic and Hebrew language version:

We introduced two new languages with the release of Service Pack 1, Arabic and Hebrew. At present we are working through the process of modifying our installers to incorporate these two languages. Due to the timing of RU1 we were unable to complete this work in time.

Customers running either of the two language versions affected are advised to download and install the English language version of the rollup which contains all of the same fixes.

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. 

Thanks

Catastrophic Failure “JV”

Source: Kevin Bellinger

Configuring inter-org Free/Busy lookups for Exchange 2007 mailboxes in an Exchange 2010 SP1 federated organization


To enable cross organization/premise Free/Busy lookup for users located on Exchange 2007 servers when there is an organization relationship in place with the business instance of the Microsoft Federation Gateway (default instance for Exchange 2010 SP1) it is necessary to add the availability address space for the remote organization and have at least one Exchange 2010 SP1 CAS. This is to provide the Exchange 2007 server with a valid path to route the remote availability requests. Because there is only an Organization relationship in place between the organizations then there is no way for the Exchange 2007 servers to utilize this connection without proper configuration. The following is the process to allow the 2007 servers to proxy the request to the servers that understands and can handle the federated Free/busy requests.

The main issue is that Exchange 2007 will first look locally for the free busy requests, when there is an external recipient that needs to be looked up it will then look to the availability address space that has been configured to see if there is a domain match. Exchange 2010 will perform the local lookup first just as the 2007 server but then will do the Organization Relationship lookup to see if there is a relationship in place with the External recipients SMTP domain.

The solution is to run the Add-AvailabilityAddressSpace CMDlet and the proxyUrl parameter to allow the relay to occur from the Exchange 2007 to the Exchange 2010 sp1 servers. The ProxyUrl parameter that is included with Exchange 2007 SP2 specifies whether to direct a Microsoft Exchange Server 2007 Client Access server to proxy its free/busy requests through an Exchange Server 2010 sp1 CAS when requesting federated free/busy data for a user in another organization for which you have an organization relationship in place. The proxyUrl should point to the local Exchange 2010 servers availability service (EWS URL).

After this is configured correctly, the flow of information will go as follows:

  1. Exchange 2007 Mailbox in Organization 1 requests Free/busy for a user in Organization 2
  2. The Exchange 2007 server submits the request to the Exchange 2010 server in Organization 1 because of the new Add-AvailabilityAddressSpace  with the internal Relay option
  3. The Exchange 2010 SP1 server in Organization 1 submits the request on behalf of the 2007 mailbox
  4. The Exchange 2010 server in Organization 2 returns the requested data

Steps to Add-Availability Address Space for the 2007 Mailboxes

Open the Exchange Management Shell on the Exchange 2007 CAS server and run the following (the Fabrikam.com should be the external domain name you are trying to view the Free/Busy data for) (The Proxy URL should reflect the 2010 sp1 CAS URL that in the same organization as the 2007 mailboxes requesting the data). The Proxy URL can be a load balanced address or a single CAS.

Add-AvailabilityAddressSpace -AccessMethod InternalProxy -ProxyUrl https://Exchange2010CAS.InternalDomain.com/ews/exchange.asmx -ForestName Fabrikam.com -UseServiceAccount $True

Link to information on the Microsoft Federation Gateway:
http://technet.microsoft.com/en-us/library/dd335047.aspx

Link to information on the Organization Relationship:
http://technet.microsoft.com/en-us/library/dd351260.aspx

Link to information on the Add-AvailabilityAddressSpace:
http://technet.microsoft.com/en-us/library/bb124122.aspx

Source: Timothy Heeney

Kind Regards
Catastrophic Failure “JV”

Exchange Posters


 

Exchange 2010

Visio Stencils Exchange 2010

Exchange 2007

Visio Stencils for Exchange Server 2007

Kind Regards
Catastrophic Failure “JV”Nerd smile

Announcing Microsoft Exchange 2010 Visio Stencil


Available for download the Microsoft Exchange 2010 Visio Stencil.

This download contains a Microsoft Office Visio stencil with shapes for Microsoft Exchange Server 2010 and Exchange Server 2010 Service Pack 1 (SP1).

Use this stencil to create Visio drawings that contain Exchange 2010 objects. These shapes include icons for the following:

  • Exchange 2010 server roles
  • Features new to Exchange 2010 SP1
  • Networking, telephony, and Unified Messaging objects
  • Active Directory and directory service objects
  • Client computers and devices
  • Other Exchange organization elements

Download details: Microsoft Exchange 2010 Visio Stencil
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=901d471c-8bd9-47ad-b6db-452309f12ebe&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+MicrosoftDownloadCenter+%28Microsoft+Download+Center%29

 

Kind Regards
Catastrophic Failure “JV”Nerd smile

Hotmail security improves with full-session HTTPS encryption


Beginning today, Hotmail is providing you with the option to enhance the security of your entire Hotmail session with HTTPS data encryption (via secure socket layers, or SSL), which is currently used to help secure your Hotmail sign-in. Today’s update joins a series of other recent security updates, with which Hotmail offers advanced security safeguards to help protect your email account from hijackers and fraud.

Also starting today, SkyDrive, Photos, Docs, and Devices pages all automatically use SSL encryption, transferring all their data over HTTPS. By using a connection with advanced security features, you can be even more confident that your account is safer from hijackers, and your private information is less likely to fall into someone else’s hands.

To enable HTTPS for your Hotmail inbox, calendar, and contacts, go to https://account.live.com/ManageSSL. Once you enable this feature, all of your future connections to Hotmail will be delivered over SSL.

Some connections to Hotmail won’t be available if you turn on HTTPS, including:

  • Outlook Hotmail Connector
  • Windows Live Mail
  • The Windows Live application for Windows Mobile (version 6.5 and earlier) and Symbian

We’re constantly working to continue providing great security for our customers, so stay tuned.

Dick Craddock
Group Program Manager
Windows Live Hotmail

Also posted on :

Hotmail security improves with full-session HTTPS encryption
http://windowsteamblog.com/windows_live/b/windowslive/archive/2010/11/09/hotmail-security-improves-with-full-session-https-encryption.aspx

 

Kind Regards
Catastrophic Failure “JV”Nerd smile

DPM 2010 Protecting Exchange 2010 DAG in a Single Site


System Center Data Protection Manager 2010

Why should you backup an Exchange 2010 DAG implementation with DPM? 

What should you be thinking about before you make a final decision?

What is the way out of this conundrum?  

….Well, it depends.  Let me walk you through a scenario. 

First, let us make a couple of seminal assumptions:

· That you will you will have more than one copy of an Exchange DB in a DAG.  OK, you are allowed a duh!

· That you will be deploying Exchange 2010 DAG with cheap JBODs, which will undoubtedly save you a bundle.

· If you are going to use JBOD, then you really understand how to interpret MTBF and its relationship to uptime SLA.

All Exchange Mailbox Servers in one site (HA but no DR)

If you want to deploy Exchange 2010 with JBOD, it is recommended that you should deploy with at least three copies.  In addition to this, if you want to also use the DAG copies for Point In Time (PIT) recovery, then you will need a server to host the lagged copy of the DB.  Lagged copies are a means to safeguard against store/logical corruption events (and possibly accidental mailbox deletions). If you are going to distribute the lagged copies among your primary severs, then you will need at least two lagged copies.  If you are going to use dedicated servers with lagged copies with JBOD, for better reliability you are well advised to deploy enough servers to house two lagged copies; otherwise you could deploy dedicated lagged copy servers with RAID and thus only have one lagged copy per database.

So how many copies are we up to? …and how many servers?  

OK, three copies per DB; two more for PIT lagged copies; one less if you share and distribute the lagged copy on more than one primary server or if you use RAID for PIT.  That is, 1, 2, 3, wait.  All right, you are big boys/girls (smart Admin people), you know how to fire up Microsoft Excel to do the math and cost it out.

From all accounts, recovering PIT from lagged copies is not a walk in the park.  In fact, you are well advised not to plan for it too frequently.  Plus, you can only have a maximum of 14 day replay lag for lagged copies.  This is a limit imposed by Exchange 2010.  If you also decide to share the primary servers and implement lagged copies, then you will be using the primary mailbox server for your recoveries – so plan your IOPS so that you do not impact Outlook client SLAs during these recoveries and re-seeds and manage your Active and Passive nodes carefully.

Introduce DPM into this equation:

Let us say you implement only three copies of an Exchange DB with JBOD, and use DPM for backup and PIT recovery.  Now what?  You have:

· As many PIT as you like J

· Recovering a PIT from DPM is far easier J

· You may not need that 4th DAG copy J

Wait, it is not all smiles; most of the time we recommend RAID for DPM.  DPM is typically configured with RAID but is just as happy with JBOD, particularly if you do D2T, DPM2DPM or protect a secondary copy as well DPM-DR. Make sure that these choices are part of the spreadsheet you are working on. And, some of the following features may require you to move up to a higher version of Exchange 2010.

· Deleted items in Exchange 2010 no longer require PIT recovery; this can be implemented with the single item recovery and litigation hold functionality. 

· The lagged copy or a DPM backup is useful for logical corruption prevention and for recovery of deleted mailboxes (since their purge cannot be prevented)

Additional reasons why you should consider DPM

In addition to direct storage costs attributable to backup, you should also consider these additional advantages.  Some of these may very well be primary reasons for opting for DPM. You may also be able to use one less DAG node, and, in the process get some additional features

· Ease of use for recovery from backup with a simple and easy to use GUI.

o No time consuming steps to find and replay log files

o No need to (possibly) create scripts for recovering from a lagged copy.

o No need to guess how many log files you need to replay for a PIT.

· Faster recovery RPO

o No need to play back all the log files, etc.

· You can easily backup to tape, for offsite storage for compliance, etc.

· Centralized standard (corporate) processes to implement backup and recovery across multiple workloads (File systems, SharePoint, Hyper-V, SQL, etc.)

So there you have it.  Two solutions from Microsoft, working together to give you an optimal solution for your IT problems.

Some useful links

DPM 2010 Overview: For an overview of how DPM 2010 and Exchange 2010 work together, including a quick demo – check out our recent podcast at:

http://edge.technet.com/Media/System-Center-Data-Protection-Manager-2010-and-Microsoft-Exchange/

Exchange 2010: Planning for High Availability and Site Resilience

http://technet.microsoft.com/en-us/library/dd638104.aspx

Kind Regards
Catastrophic Failure “JV”Nerd smile

Released: Exchange 2010 SP1 Software Development Kits


tweetmeme_source = ‘Catastrophic_JV’;

Microsoft just released updated Software Development Kits for Exchange 2010 SP1. If you develop applications for Exchange Server, grab these SDKs from the Download Center.

  1. Microsoft Exchange Server 2010 SP1 Web Services SDK October 2010

    This release of the Exchange 2010 Service Pack 1 (SP1) Web Services Software Development Kit (SDK) provides new and updated documentation and samples for building applications that use Web services in Exchange 2010 SP1 . Use this SDK to help you develop collaborative Web services-based enterprise applications. Download

  2. Microsoft Exchange Server 2010 SP1 Backup and Restore SDK October 2010

    This release of the Exchange Server 2010 Service Pack 1 (SP1) Backup and Restore SDK provides information about how to create applications that back up, restore, and recover Exchange 2010 databases. Download

  3. Microsoft Exchange Server 2010 SP1 Transport Agents SDK October 2010

    This release of the Exchange 2010 Service Pack 1 (SP1) Transport Agents Software Development Kit (SDK) provides new and updated documentation and samples for building applications that use Microsoft Exchange transport agents. Use this SDK to help you develop collaborative enterprise applications for Exchange transport. Download

Kind Regards

Catastrophic Failure “JV” Nerd smile

Graphical user interface (GUI) enhancements in Exchange 2010 SP1


SP1 whets the appetite of administrators who want to use Exchange Management Console (EMC) and Exchange Control Panel (ECP) to administer various features. More and more features are exposed in the EMC and ECP, helping Exchange Administrators to manage their Exchange 2010 infrastructure.

Exchange 2010 SP1 brings a long list of improvements. This blog focuses mostly on the GUI enhancements both in EMC and ECP.

Deployment switch for roles and features

Deployment is the gateway after which everything else occurs. There has been a lot of work done to improve the setup experience. SP1 brings new options such as the ability for Exchange to install the OS roles and prerequisites. The prerequisite Windows features that are installed by setup are determined by the Exchange server roles selected for installation. Setup uses the appropriate XML Answer files for each server role to install the prerequisites. Only the prerequisites required for the selected server roles are installed by setup as part of the prerequisite check portion of setup before roles are installed.

If you are doing an RTM to SP1 upgrade, the CMD line command to run is "setup.com /m:upgrade /installwindowscomponents" and any of the components that the setup needs from Windows to get you to SP1 will automatically get installed by the system. The GUI equivalent of this is to check the "Automatically install Windows Server roles and features required for Exchange Server" check box. This option also appears on the Server Role Selection page when the Custom Exchange Server Installation type has been selected from the Installation Type page.

Note: If any of the components require a reboot, the system will reboot and at the end of the reboot, you will have to restart setup manually. When setup is launched after the system restart, it picks back up at the point where the restart was required

Choosing your permissions model in Setup

We now have the ability to go back to the AD split permissions model when creating a brand new Exchange organization. By default, Exchange 2010 uses a "shared" permissions model where the recipient administrators have the access rights to create recipient objects in the Active Directory. When deploying a new org, setup will now ask you if you want to go with default Exchange permissions (the RBAC model) or if you want to go with split permissions model where there are separate permissions for AD administrators and separate permissions for Exchange administrators. By selecting the option Apply strict split permissions security model to the Exchange Organization, this behavior changes such that only administrators with explicit rights are able to create recipient objects.

Note: You will only see this when you are doing a brand new organization. To learn a lot more about different permissions models, please see Understanding Split Permissions.

Exchange Control Panel UI improvements

A lot of new functionality has been added in ECP. Administrators don’t necessarily need to bring the full console anymore or if you are not completely comfortable with PowerShell, you now have more management features incorporated into the ECP web interface. You can now do the following under Mail > Options> Manage My Organization or Manage Myself:

  • Create and manage mail enabled security groups (Manage My Organization > Users and Groups tab)
  • Manage RBAC Roles Groups and User Roles (Manage My Organization > Roles and Auditing tab)
  • Create and configure transport rules (Manage My Organization > Mail Control tab)
  • Create and configure journaling rules (Manage My Organization > Mail Control tab)
  • Manage Exchange ActiveSync policies (Manage My Organization > Mail Control tab)
  • Create and manage Allow/Block/Quarantine policies (Manage Myself > Block or Allow)
  • Litigation Hold (Manage My Organization > Users and Groups tab | Mailboxes)

Note: In SP1, Administrators no longer need to have a mailbox to be able to access ECP.

The ECP also provides the primary graphical interface for MRM Self-Management (this is located at Options | Manage Myself | Organize E-mail | Retention Policies), Multi-mailbox search (this feature has been improved with more options in SP1), MailTips amongst others.

Manage RBAC Roles Groups and User Roles

Exchange 2010 RTM relied on management tasks in the Exchange Management Shell for managing RBAC, although there was limited management of Role Groups and User Role Assignment available through from the ECP. Exchange 2010 SP1 improves the management experience through ECP although there are limitations to RBAC management that can be accomplished through the ECP. To manage RBAC from the ECP the administrator must have the level of access control granted to the Organization Management role group, or by assignment of the Role Management management role.

The RBAC management interfaces available from the ECP are located on the Roles and Auditing tab as shown below:

From the Roles and Auditing tab there are two secondary navigation tabs, Administrator Roles and User Roles Tab.

The Administrator Role Groups slab includes links to tasks that make it possible to manage Role groups. This is divided into two main sections; the Result pane on the left, and the Detail pane on the right. You can create a new Role Group while simultaneously assigning Management Roles and adding group members, copy an existing Role Group to make an identical new Role Group, remove a Role Group that is no longer needed, add or remove Management Role Assignments to a Role Group, add or remove members of a Role Group, change the Write Scope for all Management Role Assignments made to a Role Group, create a new Role Assignment Policy and simultaneously assign user management roles, add or remove user management role assignments to a Role Assignment Policy and remove a Role Assignment Policy that is no longer needed.

The User Roles tab is used to manage Role Assignment Policies

Admin Audit Log

The ECP provides the primary graphical interface for quickly accessing Exchange 2010 SP1 auditing reports. Using the ECP you can search the admin audit logs to discover who made configuration changes in an organization. The Auditing Reports page in ECP has several reports that you can run to review various types of compliance and administrative configuration changes. You have the ability to run reports on non-owner mailbox access, litigation hold settings, role group changes, and also mailbox and administrator audit logs. Admin Audit Logging must be enabled for audit log entries to be stored in the audit log.

MRM Tasks in EMC

In Exchange 2010 SP1, the MRM tasks which were a part of the 2010 RTM console have been taken out and can only be configured using the Shell. Managed Default Folders, Managed Custom Folders and Managed Folder Mailbox Policies are part of Message Records Management (MRM 1.0), whereas Retention Policies and Retention Policy Tags are part of MRM 2.0. Both MRM 1.0 and 2.0 are available in 2010 RTM, but Managed Default Folders, Managed Custom Folders and Managed Folders Mailbox Policies are exposed in the console. Exchange 2010 SP1 provides management tools and workflows for migrating users from managed folders to retention tags. The features exposed in the 2010 SP1 console are Retention Policies and Retention Policy Tags.

When focused on the Mailbox node, there are two tabs for managing MRM that appear in the Result pane (center): Retention Policy Tags and Retention Policies.

The EMC also includes a wizard to aid administrators in creating a new retention tag that applies the retention functionality of a specified managed folder.

Public Folder Management Console

The Manage Public Folder Settings wizard is a new feature available from the Exchange 2010 SP1 Public Folder Management Console that makes it possible to accomplish updating client permissions on a selected folder and optionally update the permissions on all subfolders to match. There is also an option to propagate public folder settings from a parent folder to all subfolders.

The wizard is started by selecting the public folder to manage from the public folder tree, and then by clicking the Manage Setting link from the Actions pane, or by right-clicking the public folder and selecting the link from the contextual menu. This opens the Introduction page as shown below. These options are mutually exclusive, meaning you can only select one or the other, and contextual, meaning the options change depending on the public folder that has been selected.

The purpose of this is that you can, like you could in Exchange 2003 ESM, modify permissions on let’s say a parent folder, and then use the wizard to propagate the changes down the Public Folder tree.

The Specify Action page allows you to select two options:

Lastly, the Assign Permissions page allows you to grant access to public folders.

Additionally, similarly to functionality in Exchange 2003 ESM, if you pull up properties of any public folder now, the permissions tab is exposed there too.

DAG

SP1 includes EMC enhancements for managing DAGs. New fields and controls have been added to DAG properties. To access the properties for a DAG, from the EMC, navigate to the Mailbox node in the console tree. From the Result pane, select the Database Availability Group tab. From the list of DAGs displayed in the result, select the DAG to manage. From the Actions pane, select the Properties link or right-click the DAG and select the link from the contextual menu. The "General" tab exposes the option to specify an Alternate Witness Server and directory. The IP Addresses tab makes it possible to manage IP Addresses for the underlying DAG cluster as shown below. The "Operational Servers" tab gives us the list of servers that are operational in the DAG. It’s a read-only tab.

Archiving

Many of the new features and functionality for Exchange 2010 SP1 centers on changes required to support Exchange service offerings through Microsoft Online Services. The EMC includes several wizards and controls for managing archive mailboxes

  • New Mailbox Wizard – includes a page to specify archive mailbox and the location of the mailbox
  • Enable Archive control – makes it possible to archive mailbox enabled an existing mailbox enabled account
  • Disable Archive control – makes it possible to disable the archive mailbox for a mailbox enabled account
  • Disconnected Mailboxes – makes it possible to reconnect an archive mailbox to the owning mailbox enabled account
  • Mailbox properties – used to manage the related properties of an archive mailbox enabled account
  • New Move Request wizard – makes it possible to move the primary and archive mailboxes together or independently

These wizards and tasks are available from the Mailbox node under Recipient Configuration in the console tree (except for Disconnected Mailboxes which is a separate node under Recipient Configuration). They appear in the Actions pane on the right, or are available by selecting and right-clicking the object to manage.

Many archive mailbox properties can be managed from the property pages of the associated primary mailbox. To open the property pages, select the mailbox to manage and the select Properties from the Actions menu, or right-click the mailbox and select Properties from the contextual menu. This opens the property pages starting on the General tab.

From the Mailbox Features tab you can access the Archive feature as well as see its current status. From the Mailbox Settings tab you can access the Archive Quota settings.

The Exchange 2010 SP1 version of the New Local Move Request wizard makes it possible to move the archive mailbox independently of the primary mailbox. Exchange 2010 SP1 supports:

  • Primary and Archive On-Premises (Same DB)
  • Primary and Archive On-Premises (Different DBs)
  • Primary and Archive in the Cloud
  • Primary On-Premises and Archive in the Cloud

Start the wizard by selecting the mailbox object that owns the archive mailbox to move and then select New Local Move Request from the Actions menu. You can also right-click the mailbox and select New Local Move Request from the contextual menu.

Resetting Client Access Virtual Directory

In Exchange 2010 SP1, you can use the new Reset Client Access Virtual Directory wizard to reset one or more Client Access server virtual directories. The wizard is available from the Client Access node under Server Configuration in the console tree. In addition to resetting virtual directories, the wizard creates a log file that includes the settings for each virtual directory that you choose to reset.

Unified Messaging

You can launch the UM Reporting features via EMC Toolbox. Call Statistics and User Call Logs are the 2 features that have been added.

Below is a screenshot of the Call Statistics report:

The below screenshot depicts a User Call logs report:

In SP1, we have made a change to allow the admin to set the UM server for the dial plan during the creation of the dial plan (wizard).

There are a ton of additional features in Exchange 2010 SP1 that are worth reviewing, some of which may jump out as being more important in your environment than many of the ones that are listed here.

Source: Nagesh Mahadev

Kind Regards
Catastrophic Failure “JV”Nerd smile

Office 365 and Exchange


You may have seen some of the press coverage today on Office 365, which brings all of Microsoft’s business productivity software together into one cloud service. Exchange Server 2010 Service Pack 1 (SP1) will be the engine that powers Exchange Online in Office 365, lighting up slick new features such as:

  • Voice mail with Unified Messaging: Integrate your on-premises PBX with hosted voicemail provided by Exchange Online, to replace your on-premises voicemail system.
  • Rich cross-premises coexistence (hybrid or split domain scenario): Drop an Exchange 2010 SP1 CAS/Hub Transport server into your Exchange 2003/2007 environment to enable advanced coexistence with Exchange Online, including the following capabilities:
    • Cross-premises management: Use the Exchange Management Console to manage mailboxes for both your hosted and on-premises Exchange deployments.
    • Calendar sharing: Enable free/busy sharing between hosted and on-premises users using the calendar federation capabilities of Exchange 2010.
    • Smooth migration: Move users to Exchange Online in just a few clicks using the Exchange Management Console or PowerShell. And, if the need arises, move them back on-premises just as easily.
    • No OST resync: The same Mailbox Replication Service used in on-premises mailbox moves also powers migrations to Exchange Online. It performs a mailbox move, not a mailbox copy, so mailbox GUIDs are preserved and Outlook doesn’t waste network bandwidth by rebuilding users’ OST files.
  • Advanced mail routing options: Route outbound e-mail through your on-premises infrastructure or other hosted services. This lets you integrate data loss prevention (DLP) appliances, perform custom post-processing of outbound e-mail, and deliver e-mail to business partners via private networks.

The service will also have all of the newest Exchange 2010 features that you’d expect, including good stuff for end users (MailTips, Conversation View, instant messaging in OWA, Personal Archive…) and administrators (Remote PowerShell, RBAC, retention policies, auditing reports, multi-mailbox search…).

Live@edu customers have been enjoying Exchange 2010 as a cloud service since October 2007 via the Outlook Live offering, and have been providing important feedback to the Exchange team all along the way. We look forward to providing these new capabilities to the rest of you when Office 365 launches.

For more information on the Office 365 beta, go to www.office365.com. And check out the blog post by Julia White, Senior Director of Exchange Product Management, for links to Exchange Online case studies.

Source: Jon Orton

Kind Regards
Catastrophic Failure “JV”Nerd smile

New HA Design Guidance Articles


Last week we updated our Exchange TechNet articles.  Within that update are two new articles that I wanted to call out:

Hope you enjoy this new information.  If you have any questions, please let us know.

Source: Ross Smith IV

Kind Regards
Ctatsrophic Failure “JV”Nerd smile