Exchange World

Released: Exchange 2013 Server Role Requirements Calculator

2013-05-14T13:26:27Z

The long waited , is here :)

http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx

Latest Exchange 2013 downloadable help file

2013-04-05T12:29:19Z

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

Updated Exchange Server 2013 docs on TechNet

2013-03-02T09:06:00Z

Enjoy
http://technet.microsoft.com/en-us/library/bb124558%28v=exchg.150%29.aspx

And make sure you have a look at "Exchange Server 2013 Deployment
Assistant" http://technet.microsoft.com/en-us/library/jj218681(v=exchg.150).aspx

Windows Management Framework 3.0 on Exchange 2007 and Exchange 2010

2012-12-19T12:28:08Z

Our guidance at this time is that Windows
Management Framework 3.0 should not be deployed on servers
running Exchange 2007 or Exchange 2010, or on workstations with the Exchange
Management Tools for either version installed. If you have already deployed
this update, it should be removed. Once you remove the update, functionality
should be restored.

The link for full details http://blogs.technet.com/b/exchange/archive/2012/12/14/windows-management-framework-3-0-on-exchange-2007-and-exchange-2010.aspx

Microsoft Exchange Server 2013 Help

2012-11-01T11:08:51Z

Just in case you are looking for an offline resource to carry with you for Exchange 2013 , the RTM help file is available .

This download contains the Help content for Microsoft Exchange Server 2013 Hybrid Deployments and the Release to Manufacturing (RTM) version of Microsoft Exchange Server 2013.

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

Restart Outlook prompt post Exchange 2010 SP2 rollup 3+

2012-09-04T14:25:00Z

Kindly note the change in RPC Client Access behavior with Exchange 2010 SP2 Rollup 3 and up:

When moving Mailboxes between Active Directory Sites: By default, once you install SP2 RU3 (or the later RU4), and you move mailboxes between Active Directory sites, all versions of Outlook will get prompted to restart and the Outlook profile’s RPC endpoint will be updated ““The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”.

If you want to disable this behavior and move mailboxes between active directory sites without having the outlook profile updated (thus no outlook restart prompt), you can do so using this registry setting on the Client Access server(s):
HKLM\System\CurrentControlSet\Services\MSExchangeRPC\ParametersSystem
Value Name: EnablePreferredSiteEnforcement
Data Type: REG_DWORD
Value: 0

With Cross-Site Database Switchover/Failover (*over) Events
- Prior to this rollup changing the property AllowCrossSiteRPCClientAccess(using Set-DatabaseAvailabilityGroup) to true of false didn’t have any effect on the client behavior.
- The AllowCrossSiteRPCClientAccess property now controls whether cross-site RPC client access is allowed with database switchover/Failover.
- With this rollup the default value of AllowCrossSiteRPCClientAccess property is $False, the Outlook profile’s RPC endpoint will be updated to be the RPC Client Access Server array that is in the same AD site where the database is active and mounted.
- If you set the AllowCrossSiteRPCClientAccess property value to $true, in the event that the database is activated cross site, the users will continue to leverage the RPC Client Access array in the AD site where the mailbox database with the lowest activation preference value resides as their connectivity endpoint.

Some users may get the Restart Outlook prompt if they have accounts mapped in their profile that need to be accessed using a different CAS array than the one they use to access their own mailboxes (EnablePreferredSiteEnforcement = 0 will solve this also)
EnablePreferredSiteEnforcement and AllowCrossSiteRPCClientAccess are Two different settings controlling different things.
In datacenter activation scenario (following http://technet.microsoft.com/en-us/library/dd351049 ), the value of AllowCrossSiteRPCClientAccess doesn’t matter. This only matters when you have a cross-site database *over event and you want to control whether primary CAS still services the request or switch to another CAS/CAS Array.
To get same functionality that you had prior to installing SP2 RU3 with (SP2 RU3& up) in place, you need to do two things:

You have to set AllowCrossSiteRPCClientAccess to $true (no change to RPC endpoint with Cross-Site Database *over Events)
Use the registry entry EnablePreferredSiteEnforcement and set it to 0 on Client Access servers. (no change to RPC endpoint with mailbox moves )

Kindly note the following Outlook Anywhere behavior related to this RPC client access change http://support.microsoft.com/kb/2725008
More information is on Exchange team blog: http://blogs.technet.com/b/exchange/archive/2012/05/30/rpc-client-access-cross-site-connectivity-changes.aspx

Exchange Server 2013 what's new

2012-07-16T20:47:00Z

What’s new on the fly:

Server Roles: Microsoft Exchange Server 2013 Preview consists of
the following two server roles Client Access server role and Mailbox server
role Exchange2013 Server Roles

Exchange Administration Center: No Exchange management console
,Exchange 2013 Preview provides a single unified management console that allows
for ease of use and is optimized for management of on-premises, online, or
hybrid deployments. The Exchange Administration Center (EAC) in Exchange 2013
Preview replaces the Exchange 2010 Exchange Management Console (EMC) and the
Exchange Control Panel (ECP). ExchangeAdministration Center

No Coexistence with Exchange 2003 Planning and deployment

Exchange 2013 architecture RPC is no longer a supported direct access
protocol. This means that all Outlook connectivity must take place using
RPC over HTTPS (also known as Outlook Anywhere).

New public folder design: Public folders in Exchange 2013 Preview
now take advantage of the existing high availability and storage technologies
of the mailbox store. The public folder architecture uses specially designed
mailboxes to store both the hierarchy and the public folder content. This new
design also means that there is no longer a public folder database. Public
folder replication now uses the continuous replication model. Public
Folders.

2013 Preview has *Offline* access in Outlook Web App (OWA).

The transport pipeline in Exchange 2013 Preview is now made up of
several different services: the Front End Transport service on Client
Access servers, the Hub Transport service on Mailbox servers, and the Mailbox
Transport service on Mailbox servers. For more information, see Mail
Flow.

Site mailboxes improve collaboration and user productivity by allowing access to both documents in a SharePoint site and email messages in an Exchange mailbox, using the same client interface. A site mailbox is functionally comprised of SharePoint site membership (owners and members), shared storage through an Exchange mailbox for email messages and a SharePoint site for documents, and a management interface that addresses provisioning and lifecycle needs.see Site Mailboxes

The whole list is here http://technet.microsoft.com/en-us/library/jj150540(EXCHG.150).aspx#BKMK_Share

Welcome Exchange Server 2013

2012-07-16T19:47:15Z

documentation

http://technet.microsoft.com/en-us/library/bb124558(EXCHG.150).aspx

Mailboxes on a database are Quarantined in an environment with System Center Operations Manager

2012-07-02T12:10:29Z

I have started seeing this issue recently while doing my usual customer visits , kindly check the workaround for the time being

http://blogs.technet.com/b/exchange/archive/2012/06/28/mailboxes-on-a-database-are-quarantined-in-an-environment-with-system-center-operations-manager.aspx

Update Rollup 3 for Exchange 2010 Service Pack 2 released

2012-05-29T18:30:39Z

Exchange team blog post: http://blogs.technet.com/b/exchange/archive/2012/05/29/released-update-rollup-3-for-exchange-2010-service-pack-2.aspx

download from here: http://www.microsoft.com/en-us/download/details.aspx?id=29899