• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Exchange server 2013
 

Exchange server 2013

on

  • 2,981 views

 

Statistics

Views

Total Views
2,981
Views on SlideShare
2,981
Embed Views
0

Actions

Likes
0
Downloads
142
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Exchange server 2013 Exchange server 2013 Document Transcript

    • EXCHANGE SERVER 2013Whats New in Exchange 2013 PreviewMicrosoft Exchange Server 2013 Preview brings a new rich set of technologies, features, and services to theExchange Server product line. Its goal is to support people and organizations as their work habits evolve froma communication focus to a collaboration focus. At the same time, Exchange Server 2013 Preview helps lowerthe total cost of ownership whether you deploy Exchange 2013 Preview on-premises or provision yourmailboxes in the cloud. New features and functionality in Exchange 2013 Preview are designed to do thefollowing:Support a multigenerational workforce Social integration and making it easier to find people isimportant to users. Smart Search learns from users communication and collaboration behavior toenhance and prioritize search results in Exchange. Also, with Exchange 2013 Preview, users can mergecontacts from multiple sources to provide a single view of a person, by linking contact informationpulled from multiple locations.Provide an engaging experience Microsoft Outlook 2013 Preview and Microsoft Office Outlook WebApp have a fresh new look. Outlook Web App emphasizes a streamlined user interface that alsosupports the use of touch, enhancing the mobile device experience with Exchange.Integrate with SharePoint and Lync Exchange 2013 Preview offers greater integration with MicrosoftSharePoint 2013 Preview and Microsoft Lync 2013 Preview through site mailboxes and In-PlaceeDiscovery.Help meet evolving compliance needs Compliance and eDiscovery are challenging for manyorganizations. Exchange 2013 Preview helps you to find and search data not only in Exchange, butacross your organization. With improved search and indexing, you can search across Exchange 2013Preview, Lync 2013 Preview, SharePoint 2013 Preview, and Windows file servers.Provide a resilient solution Exchange 2013 Preview builds upon the Exchange Server 2010architecture and has been redesigned for simplicity of scale, hardware utilization, and failure isolation.See the following sections for more information about what’s new in Exchange 2013 Preview:Exchange Administration CenterExchange 2013 Preview provides a single unified management console that allows for ease of use and isoptimized for management of on-premises, online, or hybrid deployments. The Exchange AdministrationCenter (EAC) in Exchange 2013 Preview replaces the Exchange 2010 Exchange Management Console (EMC)and the Exchange Control Panel (ECP). Some of the EAC features include:List view The list view in EAC has been designed to remove limitations that existed in ECP. ECP waslimited to displaying up to 500 objects and, if you wanted to view objects that weren’t listed in thedetails pane, you needed to use searching and filtering to find those specific objects. In Exchange 2013Preview, the viewable limit from within the EAC list view is approximately 20,000 objects. In addition,paging has been added so that you can page to the results. You can also configure page size andexport to a CSV file.Add/Remove columns to the Recipient list view You can choose which columns to view, and youcan save your custom list views.Secure the ECP virtual directory You can partition access from the Internet and Intranets from withinthe ECP IIS virtual directory to allow or disallow management features. With this feature, you can permitor deny access to users trying to access the EAC from the Internet outside of your organizationalenvironment, while still allowing access to an end-user’s Outlook Web App Options.Public Folder management In Exchange 2010 and Exchange 2007, public folders were managedthrough the Public Folder administration console. Public folders are now in the EAC, and you dont needa separate tool to manage them.Notifications In Exchange 2013 Preview, the EAC now has a Notification viewer so that you can viewthe status of long-running processes and, if you choose, receive notification via an email message whenthe process completes.
    • Exchange 2013 architecturePrevious versions of Exchange were optimized and architected with certain technological constraints thatexisted at that time. For example, during development for Exchange 2007, one of the key constraints was CPUperformance. To alleviate that constraint, Exchange 2007 was split into different server roles that allowed scaleout through server separation. However, server roles in Exchange 2007 and Exchange 2010 were tightlycoupled. The tight coupling of the roles had several downsides including version dependency, geo-affinity(requiring all roles in a specific site), session affinity (requiring expensive layer 7 hardware load balancing), andnamespace complexity.Today, CPU horsepower is significantly less expensive and is no longer a constraining factor. With thatconstraint lifted, the primary design goal for Exchange 2013 Preview is for simplicity of scale, hardwareutilization, and failure isolation. With Exchange 2013 Preview, we reduced the number of server roles to two:the Client Access server role and the Mailbox server role. (In addition, Exchange 2013 Preview works with theExchange 2010 Edge server role.)The Mailbox server includes all the traditional server components found in Exchange 2010: the Client Accessprotocols, Hub Transport service, Mailbox databases, and Unified Messaging. The Mailbox server handles allactivity for a given mailbox. The Client Access server provides authentication, redirection, and proxy services.The Client Access server itself doesnt do any data rendering. The Client Access server is a thin and statelessserver. There is never anything queued or stored on the Client Access server. The Client Access server offers allthe usual client access protocols: HTTP, POP and IMAP, and SMTP.With this new architecture, the Client Access server and the Mailbox server have become “loosely coupled”. Allprocessing and activity for a specific mailbox occurs on the Mailbox server that houses the active databasecopy where the mailbox resides. All data rendering and data transformation is performed local to the activedatabase copy, eliminating concerns of version compatibility between the Client Access server and the Mailboxserver.The Exchange 2013 Preview architecture provides the following benefits:Version upgrade flexibility No more rigid upgrade requirements. A Client Access server can beupgraded independently and in any order in relation to the Mailbox server.Geo-flexibility Because all the processing and data transformation takes place on the Mailbox server,were no longer constrained to having both a Client Access server and a Mailbox server in each site. Youcan now choose to have a central Client Access site for all protocol traffic if you want.Session indifference With Exchange 2010, session affinity to the Client Access server role wasrequired for several protocols. In Exchange 2013 Preview, the client access and mailbox componentsreside on the same Mailbox server. Because the Client Access server isnt doing any data rendering, weonly require layer 4 load balancing. Layer 4 load balancing is protocol- unaware and balances trafficbased on IP address and TCP/UDP port.Deployment simplicity With an Exchange 2010 site-resilient design, you needed up to eight differentnamespaces. With Exchange 2013 Preview, the minimum number of namespaces drops to two. If you’recoexisting with Exchange 2007, you still need to create a legacy hostname, but if you’re coexisting withExchange 2010 or you’re installing a new Exchange 2013 Preview organization, the minimum number ofnamespaces you need is two: one for client protocols and one for Autodiscover. You may also need anSMTP namespace.As a result of these architectural changes, there have been some changes to client connectivity. First, RPC is nolonger a supported direct access protocol. This means that all Outlook connectivity must take place using RPCover HTTPS (also known as Outlook Anywhere). At first glance, this may seem like a limitation, but it actuallyhas some added benefits. The most obvious benefit is that there is no need to have the RPC client accessservice on the Client Access server. This results in the reduction of two namespaces that would normally berequired for a site-resilient solution. In addition, there is no longer any requirement to provide affinity for theRPC client access service. Second, Outlook clients no longer connect to a server FQDN as they have done in allprevious versions of Exchange. Outlook uses AutoDiscover to create a new connection point comprised ofmailbox GUID, @ symbol, and UPN suffix. This simple change results in a near elimination of the unwelcomemessage of “Your administrator has made a change to your mailbox. Please restart.” Only Outlook 2007 andhigher versions are supported with Exchange 2013 Preview.
    • The high availability model of the mailbox component has not changed significantly since Exchange 2010. Theunit of high availability is still the database availability group (DAG). The DAG still uses Windows 2008clustering. Continuous replication still supports both file mode and block mode replication. However, therehave been some improvements. Failover times have been reduced as a result of transaction log codeimprovements and deeper checkpoint on the passive nodes. The Exchange Store service has been re-written inmanaged code (see the "Managed Store" section later in this topic). Now, each database runs under its ownprocess, allowing for isolation of store issues to a single database.Managed StoreIn Exchange 2013 Preview, the Managed Store is the name of the newly rewritten Information Store processes,Microsoft.Exchange.Store.Service.exe and Microsoft.Exchange.Store.Worker.exe. The new Managed Store iswritten in C# and tightly integrated with the Microsoft Exchange Replication service (MSExchangeRepl.exe) toprovide higher availability through improved resiliency. In addition, the Managed Store has been architectedto enable more granular management of resource consumption and faster root cause analysis throughimproved diagnostics.The Managed Store works with the Microsoft Exchange Replication service to manage mailbox databases,which continues to use Extensible Storage Engine (ESE) as the database engine. Exchange 2013 Previewincludes significant changes to the mailbox database schema that provide many optimizations over previousversions of Exchange. In addition to these changes, the Microsoft Exchange Replication service is responsiblefor all service availability related to Mailbox servers. The architectural changes enable faster database failoverand better physical disk failure handling.The Managed Store is also integrated with the FAST search engine (the same search engine used bySharePoint 2013 Preview) to provide more robust indexing and searching.Certificate managementManaging digital certificates is one of the most important security-related tasks for your Exchangeorganization. Ensuring that certificates are appropriately configured is key to delivering a secure messaginginfrastructure for the enterprise. In Exchange 2010, the Exchange Management Console was the primarymethod of managing certificates. In Exchange 2013 Preview, certificate management functionality is providedin the Exchange Administration Center, the new Exchange 2013 Preview administrator user interface.The work in Exchange 2013 Preview related to certificates focused around minimizing the number ofcertificates that an Administrator must manage, minimizing the interaction the Administrator must have withcertificates, and allowing management of certificates from a central location. Benefits resulting from thechanges in certificate management are:All certificate management is performed on the Client Access server. The Mailbox server has a self-signed certificate installed by default. The Client Access server automatically trusts the self-signedcertificate on the Exchange 2013 Preview Mailbox server, so clients will not receive warnings about aself-signed certificate not being trusted provided that the Exchange 2013 Preview Client Access serverhas a non-self-signed certificate from either a Windows certificate authority (CA) or a trusted thirdparty.In previous versions of Exchange, it was difficult to see when a digital certificate was nearing expiration.In Exchange 2013 Preview, the Notifications center will display warnings when a certificate stored onany Exchange 2013 Preview Client Access servers is about to expire.Messaging policy and complianceData loss prevention (DLP) is a new feature in Exchange 2013 Preview. DLP capabilities help you protect yoursensitive data and inform users of internal compliance policies. DLP can also help to keep your organizationsafe from users mistakenly sending sensitive information to unauthorized people. DLP helps you identify,monitor, and protect sensitive data through deep content analysis. Exchange 2013 Preview offers built-in DLP
    • policies based on regulatory standards such as personally identifiable information (PII) and payment cardindustry data security standards (PCI), and is extensible to support other policies important to your business.Additionally, the new PolicyTips in Outlook 2013 Preview inform users about policy violations before sensitivedata is sent.In-place archiving, retention, and eDiscoveryExchange 2013 Preview includes the following improvements to In-Place Archiving, Retention, and eDiscoveryto help your organization meet its compliance needs:In-Place Hold In-Place Hold allows you to:Preserve the results of the query (query-based hold), which allows for scoped immutability acrossmailboxes.Place a time-based hold to meet retention requirements (for example, retain all items in amailbox for seven years, a scenario that required the use of Single Item Recovery/Deleted ItemRetention in Exchange 2010).Place a mailbox on indefinite hold (known as a litigation hold in Exchange 2010).In-Place eDiscovery In-Place eDiscovery allows you to search and preserve data across multiple datarepositories. Exchange 2013 Preview exposes the ability to perform In-Place eDiscovery search acrossExchange, SharePoint 2013 Preview, and Lync 2013 Preview. You can use the eDiscoveryCenter inSharePoint 2013 Preview to perform In-Place eDiscovery search and hold. Query-based In-Place Holdallows you to preserve the results of the query, which allows for scoped immutability across mailboxes.If SharePoint 2013 Preview isnt available, a subset of the discovery functionality is available in theExchange Administration Center (EAC). In addition, Discovery Managers can export mailbox content to a.pst file from the SharePoint 2013 Preview eDiscovery Console. Mailbox export request cmdlets are nolonger required to export a mailbox to a .pst file.Keyword statistics Search statistics are offered on a per search term basis. This feature enables aDiscovery Manager to quickly make intelligent decisions about how to further refine the search query toprovide better results. eDiscovery search results are sorted by relevance.Search across primary and archive mailboxes in Outlook Web Access In Exchange 2013 Preview,users can search across their primary and archive mailboxes in Outlook Web App. Two separatesearches are no longer necessary.Apply personal tags to default folders using Outlook Web App With Outlook Web App, users canapply Personal Tags to default folders such as Inbox and Deleted Items.Transport rulesTransport rules in Exchange Server 2013 Preview are a continuation of the features that were available inExchange Server 2010. However, several improvements have been made to transport rules in Exchange 2013Preview. The most important change is the support for data loss prevention (DLP). There are also newpredicates and actions, enhanced monitoring, and a few architectural changes.Mail flowThe transport pipeline in Exchange 2013 Preview is now made up of several different services: the Front EndTransport service on Client Access servers, the Hub Transport service on Mailbox servers, and the MailboxTransport service on Mailbox servers. For more information, see Mail Flow.Mail routing in Exchange 2013 Preview recognizes DAG boundaries as well as Active Directory site boundaries.Also, mail routing has been improved to queue messages more directly for internal recipients.RecipientsThe EAC includes auditing functionality so that you can run reports or export entries from the mailbox auditlog and the administrator audit log. The mailbox audit log records whenever a mailbox is accessed by
    • someone other than the person who owns the mailbox. This can help you determine who has accessed amailbox and what they have done. The administrator audit log records any action, based on a WindowsPowerShell cmdlet, performed by an administrator. This can help you troubleshoot configuration issues oridentify the cause of problems related to security or compliance. For more information, see Auditing Reports.Administrators can also use the EAC to track delivery information for email messages sent to or received byany user in your organization. You just select a mailbox, and then search for messages sent to or received by adifferent user. You can narrow the search by searching for specific words in the subject line. The resultingdelivery report tracks a message through the delivery process and specifies if the message was successfullydelivered, pending delivery, or if it wasnt delivered.Sharing and collaborationThis section describes the sharing and collaboration enhancements in Exchange 2013 Preview.Public foldersPublic folders in Exchange 2013 Preview now take advantage of the existing high availability and storagetechnologies of the mailbox store. The public folder architecture uses specially designed mailboxes to storeboth the hierarchy and the public folder content. This new design also means that there is no longer a publicfolder database. Public folder replication now uses the continuous replication model. High availability for thehierarchy and content mailboxes is provided by the DAG. With this design, were moving away from a multi-master replication model to a single-master replication model.Site mailboxesEmail and documents are traditionally kept in two unique and separate data repositories. Most teams wouldnormally collaborate using both mediums. The challenge is that both email and documents are accessed usingdifferent clients, which usually results in a reduction in user productivity and a degraded userexperience.The site mailbox is a new concept in Exchange 2013 Preview that attempts to solve these problems.Site mailboxes improve collaboration and user productivity by allowing access to both documents in aSharePoint site and email messages in an Exchange mailbox, using the same client interface. A site mailbox isfunctionally comprised of SharePoint site membership (owners and members), shared storage through anExchange mailbox for email messages and a SharePoint site for documents, and a management interface thataddresses provisioning and lifecycle needs.Integration with SharePoint and LyncExchange 2013 Preview offers greater integration with SharePoint 2013 Preview and Lync 2013 Preview.Benefits of this enhanced integration include:Users collaborate more effectively by using site mailboxes.Lync Server 2013 Preview can archive content in Exchange 2013 Preview and use Exchange 2013Preview as a contact store.Discovery Managers can perform In-Place eDiscovery and Hold searches across SharePoint 2013Preview, Exchange 2013 Preview, and Lync 2013 Preview data.Oauth authentication allows partner applications to authenticate as a service or impersonate userswhere required.Clients and mobile devicesThe Outlook Web App user interface is new and optimized for tablets and smartphones as well as desktop andlaptop computers. New features include apps for Outlook, which allow users and administrators to extend the
    • capabilities of Outlook Web App, Contact linking, the ability for users to add contacts from their LinkedInaccounts, and updates to the look and features of the calendar.Unified MessagingUnified Messaging in Exchange 2013 Preview contains essentially the same voice mail features included inExchange 2010. However, some new and enhanced features and functionality have been added to thoseexisting features. More importantly, architectural changes in Exchange 2013 Preview Unified Messagingresulted in components, services, and functionality that were included with the Unified Messaging server rolein Exchange 2010 to be divided between the Exchange 2013 Preview Client Access and Mailbox server roles.Batch movesExchange 2013 Preview introduces the concept of batch moves. The new move architecture is built on top ofMRS (Mailbox Replication service) moves with enhanced management capability. The new batch movearchitecture in Exchange 2013 Preview features the following enhancements:Ability to move multiple mailboxes in large batches.Email notification during move with reporting.Automatic retry and automatic prioritization of moves.Primary and personal archive mailboxes can be moved together or separately.Option for manual move request finalization, which allows you to review a move before you completeit.Periodic incremental syncs to migrate the changes.High availability and site resilienceExchange 2013 Preview continues to make use of the database availability group (DAG) platform introduced inExchange 2010 for both high availability and site resilience. Exchange 2013 Preview also includesenhancements to the DAG platform that improve manageability and reduce costs. These features include:Managed availability.Managed Store.Automatic configuration and management of DAG networks.Management via the Exchange Administration Center.Enhancements to DAG-related cmdlets to introduce new scenarios.Exchange workload managementAn Exchange workload is an Exchange server feature, protocol, or service that has been explicitly defined forthe purposes of Exchange system resource management. Each Exchange workload consumes system resourcessuch as CPU, mailbox database operations, or Active Directory requests to execute user requests or runbackground work. Examples of Exchange workloads include Outlook Web App, Exchange ActiveSync, mailboxmigration, and mailbox assistants.There are two ways to manage Exchange workloads: by monitoring the health of system resources or bycontrolling how resources are consumed by individual users (sometimes called user throttling in Exchange2010). Managing workloads based on the health of system resources is new in Exchange 2013 Preview.Controlling how resources are consumed by individual users was possible in Exchange 2010, and this capabilityhas been expanded for Exchange 2013 Preview.Whats New for Outlook Web App in Exchange 2013 Preview
    • For Microsoft Exchange Server 2013 Preview, we’ve added several new features to Microsoft Office OutlookWeb App and updated its design.Apps in Outlook Web AppWe’ve added several apps for Outlook: Bing Maps, Suggested Appointments, and Action Items. These apps areintegrated with Outlook and Outlook Web App and extend the information and functionality of messages andcalendar items.Apps in Outlook attempt to anticipate your needs and automatically propose actions you might want to takeby using the contents of the email message. For example, if an email message contains a street address, theBing Maps app offers you a Bing tab with a quick link to a map and directions. Or, if a phrase in the emailmessage suggests a possible action item, the Action Items app creates a suggested Task for your review. Anoffer to meet is suggested as an Appointment to be added to your calendar, thanks to the SuggestedAppointments app.Apps for Outlook aren’t dependent on the version of Exchange Server that you’re using. You won’t have toworry about breaking or losing any apps for Outlook that you have added when you upgrade Exchangeservers or move to a new Exchange version.Administrators can use the Exchange Administration Center (EAC) to manage the apps available to users in theorganization. Users can then manage their apps. Administrators can also allow users to download apps fromOffice.com.In addition, we encourage third-party developers to create additional apps for Outlook and then offer them atOffice.com. To learn more, see Build Apps for Office for background information and Mail apps for Outlook fordetailed information about building apps for Outlook.PeopleNow, users can link multiple entries for the same person and view the information in a single contactcard. For example, if a user has two entries for Holly Holt in his Contacts folder, one entry copied fromthe organization’s address list and one entry that he added manually, he can link the two entries in hisContacts folder and view all the information in one place. Contact linking is done automatically, but theuser can also manually link and unlink contacts.Connected accounts have been extended to include the ability to connect to a user’s LinkedIn account.After the link is established, Outlook Web App automatically adds the user’s LinkedIn contacts to theContacts folder.CalendarUsers can now view multiple calendars in a merged view. Entries from each calendar have their owncolor, making it easy for users to identify which calendar an entry belongs to. In the day view, users canview multiple calendars in a merged view or in separate columns.The month view now includes an agenda for the selected day, providing users with helpful informationas they review the days activities.In all calendar views, users can click an item to view a pop-up of the items details. In addition to thedetails, controls are now available to accept or decline the item if it’s a meeting, to edit or delete if it’san appointment, or, if a meeting item, to join the meeting if an online meeting link is included.
    • Tablets and smartphonesOutlook Web App emphasizes a streamlined user interface that also supports the use of touch, enhancing themobile device experience with Exchange.Supported browsersTo experience all Outlook Web App features, use one of the operating system and browser combinationslabeled “Best”, as noted in the tables below. Outlook Web App is supported by many operating system andweb browser combinations, but not all Outlook Web App features are available in all combinations. Somebrowsers support only the light version of Outlook Web App.Supported browsers on desktop and laptop computersIn the table below, the following definitions apply:Best: All Outlook Web App features are supported.Good: Most Outlook Web App features are supported.Light: The browser displays the light version of Outlook Web App.Desktops and laptops: Outlook Web App features available by Windows operating system and browsercombinationWeb browser Windows XP andWindows Server 2003Windows Vista andWindows Server 2008Windows 7 Windows 8Release PreviewInternetExplorer 7Good Not available Not available Not availableInternetExplorer 8Good Good Good Not availableInternetExplorer 9Not available Best Best Not availableInternetExplorer 10 orlaterNot available Not available Best - plusoffline accessBest – plusoffline accessFirefox 12 orlaterGood Good Best BestSafari 5.1 orlaterGood – plus offlineaccessGood – plus offlineaccessGood – plusoffline accessGood – plusoffline accessChrome 18 orlaterGood – plus offlineaccessGood – plus offlineaccessBest – plusoffline accessBest – plusoffline accessNote:
    • In previous versions, Outlook Web App had a built-in spell checker. In Exchange Server 2013 Preview, OutlookWeb App relies on the web browser for spell checking, which Internet Explorer prior to version 10 doesn’tprovide.Desktops and laptops: Outlook Web App features available by non-Windows operating system andbrowser combinationWeb browser Mac OX X v10.5 Mac OX X v10.6 and v10.7 LinuxFirefox 12 or later Best Best BestSafari 5.0.6 Best – plus offline access Best – plus offline access Not availableSafari 5.1 or later Not available Best – plus offline access Not availableChrome 18 or later Best – plus offline access Best – plus offline access Best – plus offline accessNote:Operating system and browser combinations not listed display the light version of Outlook Web App.Supported browsers for tablets and smartphonesYou can use the web browser on a tablet or smartphone to sign in to Outlook Web App. The available OutlookWeb App features depends on the operating system and browser combination in use, as follows:Best: All Outlook Web App features for smartphones and tablets are supported.Light: The browser displays the light version of Outlook Web App.Tablets and smartphones: Outlook Web App features available by operating system and browsercombinationDevice Minimum memory Application SupportWindows 8 Release Preview tablet 512 MB Web browser BestiOS 5 or later for iPhone 512 MB Web browser BestiOS 5 or later for iPad 512 MB Web browser BestAndroid 4.0 smartphone or later 512 MB Web browser BestAndroid 4.0 tablet or later 512 MB Web browser BestAll other smartphones and tablets Not applicable Web browser LightNote:iPad version 1 devices have 256 MB of memory. Outlook Web App requires 512 MB of memory; therefore, itsnot supported on version 1 iPads.
    • Whats New for Unified Messaging in Exchange 2013 PreviewIn Microsoft Exchange Server 2013 Preview, were enhancing earlier releases of Exchange by introducing newfeatures and architectural changes. Unified Messaging (UM) in Exchange 2013 Preview includes the samefeature set as Exchange 2010 and Exchange 2007; however, Unified Messaging is no longer a separate serverrole. It’s now a component of the voice-related features offered in Exchange 2013 Preview.Changes in the Voice architectureThe architecture of Exchange 2013 Preview is different than it was in Exchange 2010 and Exchange 2007. Inprevious versions of Exchange UM, all the components for Unified Messaging were included on a server withthe UM server role installed. In Exchange 2013 Preview, all the Unified Messaging components are splitbetween a Client Access server running the Microsoft Exchange Unified Messaging Call Router service and aMailbox server running the Microsoft Exchange Unified Messaging service. All of the functionality, includingthe services and worker processes for Unified Messaging, is located on each Mailbox server, other than theClient Access server running the Microsoft Exchange Unified Messaging Call Router service that proxiesincoming calls to the Mailbox server. For details, see Voice Architecture Changes.Support for IPv6Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP). IPv6 is intended tocorrect many of the shortcomings of IPv4, which was the previous version of the IP. Just as with Exchange2010, Exchange 2013 Preview Client Access and Mailbox servers fully support IPv6 networks. For details,see IPv6 Support in Unified Messaging.Support for UCMA 4.0 APISince Service Pack 1 for Exchange 2010, the Unified Messaging role has relied on Unified CommunicationsManaged API v2.0 (UCMA) for signaling and media. Therefore, UCMA 2.0 is a prerequisite for Exchange 2010UM setup. UCMA 2.0 is downloaded separately and deployed manually by administrators on existing Exchange2010 SP1 or later UM servers. For Exchange 2013 Preview, UCMA 4.0 is required. However, given that the UMserver is no longer a separate server role in Exchange 2013 Preview, now it’s the Client Access and Mailboxservers that require UCMA 4.0.UCMA 4.0 supports new features in Unified Messaging, such as using the same version of the Speech Enginefor both TTS and Automatic Speech Recognition (ASR). The platform that’s used for Exchange 2013 Preview,.NET 4.0, includes a single installer file and enables backward compatibility with Exchange 2010 and Exchange2007 UM servers.In Exchange 2010 SP2 and SP1, UCMA 2.0 installation is required prior to installing the service pack on aUnified Messaging server. However, UCMA 2.0 had several limitations. UCMA 4.0 corrects many of theshortcomings of UCMA 2.0. In Exchange Server 2013 Preview, UM continues to use UCMA. However, movingto the newest version of UCMA gives you these multiple benefits:The newest build of UCMA incorporates hotfixes and patches.UCMA requires .NET 4.0, which is the platform used by Exchange Server 2013 Preview. (UCMA 2.0doesn’t support .NET 4.0.)UCMA 4.0 supports IPv6.Simplified and automated deployment of UCMA 4.0. Exchange 2013 Preview Setup performs a singlecheck for UCMA 4.0.UCMA 4.0 setup includes all prerequisites for Exchange 2013 Preview.Note:UCMA 4.0 is installed when youre installing Exchange 2013 Preview. For details about UCMA
    • 4.0 and setup requirements, see Exchange 2013 Prerequisites. To upgrade to the most recentversion of UCMA, you must first uninstall any previous versions of UCMA that are installedusing Add/Remove programs.Improvements to Voice Mail PreviewSome enhancements to the speech-related services are offered for Exchange Server 2013 Preview UM via theSpeech Engine 11.0 and UCMA 4.0. Grammar generation and language improvements are included. Inaddition, Exchange Server 2013 Preview UM includes several enhancements to the UI and improvements forconfidence and accuracy for Voice Mail Preview. For details, see Voice Mail Preview Enhancements.Enhanced caller ID supportIn previous releases of Exchange Unified Messaging, a UM server that took a call used caller ID to look up thepossible identity of the calling party. This search extended across Active Directory and the UM user’s personalcontacts stored in their mailbox.Exchange users are often annoyed by failures to identify Exchange or personal contacts from their caller ID.Until now, only the default contact folder in Exchange UM has been used for this search. But, Exchange Server2013 Preview users are likely to have contacts aggregated from external social networks or contacts for whichthe users may have manually created unique folders to organize their contacts. Now, the features in Exchange2013 Preview UM extend the scope of the search to include the user’s other Exchange and personal contactfolders that are manually created. Exchange 2013 Preview also supports contact aggregation from externalsocial networks, provides intelligence to link multiple contacts referring to the same person, and uses that datato present person-centric (rather than contact-centric) views. Those contacts that are aggregated from externalnetworks are placed in contact folders including any additional contact folders that users created.Caller ID look-up is integrated with contact aggregation, so that it searches across external contacts, and alsoso that its output can be presented by Exchange Server 2013 Preview clients with a person-centric userinterface.The PersonID property, where present and with a non-null value, improves the user experience for caller IDresolution by suppressing duplicate matches to contacts that are associated with the same person. Becausethe PersonID property is the same on both results, UM treats this as a match to a single contact.Enhancements to speech platform and speech recognitionExchange Server 2013 Preview UM introduces some enhancements to the speech platform and speechrecognition including the following:Enhancements and improved accuracy for Voice Mail Preview.Support for the Microsoft Speech Platform – Runtime (Version 11.0).Speech grammar generation using the system mailbox for an organization.Exchange Unified Messaging uses static and dynamic speech grammars to recognize commands, names ofcontacts in the global address list (GAL), and names of personal contacts in the user’s mailbox. Today, inExchange Server 2013 Preview, every Mailbox server running the Microsoft Exchange Unified Messagingservice generates grammars for all UM languages installed on it and stores them in directories. Thus, creatinggrammar files is done by every Mailbox server. Every Mailbox server stores every possible grammar, which itgenerates based on the number of dial plans, auto attendants and the UM languages that are installed.Grammar files are used as inputs to the speech recognition process and are generated on a periodic basis. TheGGG.exe command in Exchange 2007 and Exchange 2010 allowed you to manually update the grammar fileswithout waiting for the scheduled update. In Exchange Server 2013 Preview, to address ASR grammargeneration scalability issues for UM, the speech GAL grammar generation no longer happens on the serverwith the Unified Messaging server role installed. Instead, it happens periodically using the Mailbox Assistant,on the Mailbox server running the Microsoft Exchange Unified Messaging service that hosts the organization’s
    • arbitration mailbox. The GAL speech grammar file is stored in the arbitration mailbox for an organization andthen later downloaded to all Mailbox servers in that Exchange organization. By default, the Mailbox Assistantruns every 24 hours. You can adjust the frequency by using the Set-MailboxServer cmdlet.Cmdlet updatesFor Exchange 2013 Preview, many UM cmdlets have been brought over from Exchange 2010, but there havebeen changes in some of those cmdlets, and new cmdlets have been added for new functionality. For details,see Unified Messaging Cmdlet Updates.Note:Similar to the products themselves, content for the next version of Exchange Server and ExchangeOnline is still being developed. If our Preview documentation doesn’t contain the information you’relooking for, there’s a good chance the content from previous releases may still apply. Browseour Exchange Server 2010 and Exchange Online documentation. If you still can’t find answers, pleasesend feedback to Exchange 2013 Preview Help Feedback. Your comments will help us provide youwith the most useful content.Whats New for Transport RulesIn Microsoft Exchange Server 2013 Preview, several improvements have been made to transport rules. Thistopic provides a brief overview of some of the key changes and enhancements. To learn more about transportrules, see Transport Rules.Support for data loss prevention policiesData loss prevention (DLP) features in Exchange 2013 Preview can help organizations reduce unintentionaldisclosure of sensitive data. Transport rules have been updated to support creating rules that accompany andenforce DLP policies. To learn more about DLP support in transport rules, see the following topics:Integrating Sensitive Information Rules with Transport RulesData Loss PreventionNew predicates and actionsThe functionality of transport rules has been extended via the addition of new predicates and actions. Eachpredicate listed below can be used as a condition or an exception when youre creating transport rules.For detailed information about using these new predicates and actions, see New-TransportRule.New predicatesMessageContainsDataClassifications Used to detect sensitive information in the message body andany of the attachments. For a list of data classifications available, see Sensitive Information TypesInventory.HasSenderOverride Used to detect messages where the sender has chosen to override a DLP policyrestriction.SenderIPRanges Used to detect messages sent from a specific set of IP address ranges.AttachmentExtensionMatchesWords Used to detect messages that contain attachments withspecific extensions.
    • AttachmentHasExecutableContent Used to detect messages that contain attachments withexecutable content.MessageSizeOver Used to detect messages whose overall size is greater than or equal to thespecified limit.New actionsNotifySender Controls how the sender of a message that goes against a DLP policy is notified. Youcan choose to simply inform the sender and route the message normally, or you can choose to rejectthe message and notify the sender.StopRuleProcessing Stops the processing of all subsequent rules on the message.RouteMessageOutboundRequireTLS Requires TLS encryption when routing this message outsideyour organization. If TLS encryption isnt supported, the message is rejected and not delivered.ReportSeverityLevel Sets the specified severity level in the incident report. Values for the action are:Informational, Low, Medium, High, and Off.GenerateIncidentReport Generates an incident report that is sent to a specified SMTP address. Theaction also has a parameter called IncidentReportOriginalMail that accepts one of two values:IncludeOriginalMail or DoNotIncludeOriginalMail.Other changes in Transport rulesSupport for extended regular expression syntax Transport rules in Exchange 2013 Preview arebased on the Microsoft.NET Framework regular expression (regex) functionality and now supportextended regular expression syntax.Transport rules agent invocation The key architectural change in Exchange 2013 Preview forTransport rules is the Transport Rules Agent is invoked on onResolvedMessage. In previous versions ofExchange, the Rules Agent was invoked on onRoutedMessage. This change allowed us to add newactions, such as requiring TLS, that can change how a message is routed. To learn more about thetransport rules architecture in Exchange 2013 Preview, see Transport Rules.Detailed Transport rule information in message tracking logs Detailed information aboutTransport rules are now included in message tracking logs. The information includes which rules weretriggered for a specific message and the actions taken as a result of processing those rules.New rule monitoring functionality Exchange 2013 Preview monitors Transport rules that areconfigured and measures the cost of running these rules both when youre creating the rule and alsoduring regular operation. Exchange can detect and generate alerts for rules that are causing delays inmail delivery.
    • New Features in Exchange 2013 Transport RulesMicrosoft has published a list of changes and improvements to transport rules on this TechNet page.Support for data loss prevention policies is one of the major new features in Exchange Server 2013, and this integrateswith transport rules.Exchange 2013 also has a number of new predicates (conditions) and actions for transport rules. A few of the highlightsare: Ability to take action on messages that have been sent from specific IP address ranges Ability to take action on messages that have attachments with specific extensions, or that contain executable content Ability to stop subsequent rules from processing a message (this will make the order of rules important for someenvironments) Ability to generate incident reports to an email address at varying severity levels Transport rule information is now included in message tracking logs Rule monitoring to detect and alert on rules that are delaying email deliveryManaging Transport RulesTransport rules in Exchange Server 2013 can be managed in two ways. The first is by using the Exchange ManagementShell cmdlets:[PS] C:>get-command -Noun *TransportRule*CommandType Name----------- ----Function Disable-TransportRuleFunction Enable-TransportRuleFunction Export-TransportRuleCollectionFunction Get-TransportRuleFunction Get-TransportRuleActionFunction Get-TransportRulePredicateFunction Import-TransportRuleCollectionFunction New-TransportRuleFunction Remove-TransportRuleFunction Set-TransportRuleThe second is by using the Exchange Administration Center, in the Mail Flow section under Rules.
    • Managing Transport Rules in the Exchange Admin CenterCreating New Transport RulesThe New Rule wizard behaves in an interesting way in Exchange Server 2013. If you simply click the + button the NewRule wizard begins and exposes a limited subset of the available conditions and actions in the drop down lists.Creating a new transport rule in Exchange Server 2013However, there is also a More options link in the wizard start screen.
    • Exposing more options for transport rulesClicking that link expands the options available in the wizard to a much more granular set, as well as the ability to setmultiple conditions and actions.Fine-grain controls for transport rules in Exchange Server 2013Creating New Transport Rules Based on TemplatesIn addition to the New Rule wizard behavior shown above you can also create a new rule based on a template of sorts. Byclicking the little arrow next to the + icon a menu of common rule types is presented to get you started.
    • Transport rule templatesFor example, choosing the “Apply signature or disclaimers” option from the list the new rule starts with the “Append adisclaimer to the message” action already selected.Transport rule to append a disclaimer to a messageOther templates present different subsets of actions depending on the general purpose that the rule is for. However in allcases it appears you can still click More options to get access to all of the conditions and actions if needed.Time-Based Transport RulesAnother useful capability of Exchange 2013 transport rules is the ability to set specific dates for the rule to be activatedand deactivated.
    • This could be useful for businesses that need to align their disclaimers with specific events such as a marketing campaign,a holiday period, or corporate merger/acquisition.Transport Rules Audit ModeExchange 2013 transport rules also have an audit mode so that they can be tested without impacting message delivery. Inthe New Rule wizard these options are visible as the two “Test rule…” modes.Exchange 2013 transport rule test/audit modesAlthough they are referred to as “Test” in the Exchange Admin Center the modes are referred to as “Audit” in theNew-TransportRule cmdlet parameters.So in effect a rule can be placed in one of three modes: Enforce – the rule is active and all the actions you have specified will be taken Audit (Test rule with notifications disabled) – the rule is active, and the actions are logged to the message trackinglogs, but not actually enforced on the message Audit and Notify (Test rule with notifications enabled) – same as Audit mode except any “Notify…” actions on the ruleare takenSummaryAs you can see a number of improvements have been made to transport rules in Exchange Server 2013 that add morepower and flexibility to this feature, which will no doubt help many organizations who rely on transport rules today or whohave specific needs that aren’t quite met by the transport rules functionality in previous versions of Exchange.
    • Exchange Server 2013 Server RolesExchange Server 2013 has only two server roles: Client Access server Mailbox serverExchange 2013 Server Role selection during setupThe two roles can co-exist on the same host, or be installed separately. At least one of each server role is required in anyActive Directory site where Exchange 2013 is running.Exchange Server 2013 Client Access ServerAs the name suggests, the Client Access server role is the server that clients (eg Outlook, Outlook Web App, ActiveSync)connect to for mailbox access. The Client Access server authenticates, and redirects or proxies those requests to theappropriate Mailbox server.Client Access servers can be made highly available through the use of a load balancer.There are two main components: Client Access service – this handles the client connections to mailboxes Front End Transport service – this performs various email traffic filtering functions, as well as email routing betweenthe Exchange servers and the outside worldExchange Server 2013 Mailbox ServerMailbox servers host the databases that contain mailbox and public folder data. As with Exchange 2010 the Exchange2013 Mailbox server role can be made highly available by configuring a Database Availability Group.The Mailbox server also runs two Transport services: Hub Transport service – similar to the Exchange 2007/2010 Hub Transport server role, this service provides emailrouting within the organization, and connectivity between the Front End transport service and the Mailbox Transportservice Mailbox Transport service – this service passes email messages between the Hub Transport service and themailbox databaseOther Server Roles from Exchange 2007/2010With the reduction in server roles to just two in Exchange Server 2013 you may be wondering what has happened to theremaining server roles that existed in Exchange Server 2007 and 2010: Hub Transport server – this functionality has been divided between the Client Access server (Front End Transportservice) and Mailbox server (Hub Transport and Mailbox Transport services) and is no longer a dedicated server role Unified Messaging – this functionality has been divided between the Client Access and Mailbox server and is nolonger a dedicated server role Edge Transport – Exchange 2013 Preview does not contain an Edge Transport server role, however it will functionwith an Exchange 2007 or 2010 Edge Transport. There have been hints that the Edge Transport server role will not bein future versions of Exchange server.
    • How to Install Exchange Server 2013inShareJuly 22, 2012 By Paul Cunningham 2 CommentsThis article is based on the Exchange 2013 Preview release, and is subject to change when it reaches RTM. Do notattempt to install pre-release software in a production environment.Deployment of an Exchange Server 2013 server goes through three main stages.1. Preparing Active Directory (if you are installing Exchange Server 2013 for the first time)2. Installing the Exchange Server 2013 pre-requisites on the server3. Running Exchange Server 2013 setupPreparing Active Directory for Exchange Server 2013When you are installing Exchange Server 2013 for the first time the Active Directory needs to be prepared.There are a series of requirements for Active Directory preparation to be successful: Schema master running Windows Server 2003 with SP2, or a later version of Windows Server At least one Global catalog server per site that Exchange will be installed in that is running Windows Server 2008 orlater At least one Domain controller per site that Exchange will be installed in that is running Windows Server 2008 or later Forest functional mode of Windows Server 2003 or higher An account with Schema Admins, Domain Admins, and Enterprise Admins permissions to run Exchange setupAlthough Active Directory preparation can occur as part of the installation of the first Exchange Server 2013 server, youcan also run the Active Directory preparation as a separate task beforehand on a 64-bit server running Windows Server2008 or higher.Because the Active Directory preparation requires the RSAT-ADDS tools I am running it on the domain controller in mytest lab.Alternatively, you can install the tools on a member server to run Exchange 2013 Active Directory preparation.For Windows Server 2008 R2 (SP1 or later), in PowerShell run:Import-Module ServerManagerAdd-WindowsFeature RSAT-ADDSFor Windows Server 2012, in PowerShell run:Install-WindowsFeature RSAT-ADDSFor an Active Directory forest with a single domain run the following Exchange 2013 setup command to prepare ActiveDirectory:setup /PrepareAD [/OrganizationName: "your organization name"/IAcceptExchangeServerLicenseTermsNote: if your organization name contains spaces then it must be enclosed in quotes as shown above.For other Active Directory preparation scenarios, such as multiple forests or multiple domains, refer to this article onTechNet.Installing the Exchange Server 2013 Pre-RequisitesExchange Server 2013 can be installed on either Windows Server 2008 R2 (SP1 or later) or Windows Server 2012.Depending on the server roles you are installing the pre-requisites vary. Installing Exchange Server 2013 Pre-Requisites on Windows Server 2008 R2 Installing Exchange Server 2013 Pre-Requisites on Windows Server 2012
    • Installing Exchange Server 2013 Using the Setup WizardFrom the location where you have stored your Exchange 2013 files run Setup.exe.The first dialog gives you the opportunity to check for updates to the setup files before you proceed.Checking for updates during Exchange 2013 setupAfter the setup files have updated click Next to continue.Setup files updated successfullyClick Next to continue past the Introduction message.Exchange 2013 Setup IntroductionAccept the license agreement and click Next to continue.
    • Exchange 2013 License AgreementChoose whether or not to enable Error Reporting and click Next to continue.Error Reporting option for Exchange 2013After a check that all the pre-requisites are installed the setup wizard will move on to the next step automatically (if thecheck was successful).Now we can choose the server roles to install. If this is the first server youre installing Microsoft recommends you installthe Mailbox server role first (this can be either a Mailbox-only server or a combined Mailbox/Client Access server).For the Exchange Server 2013 Preview uncheck the box to automatically install server roles and features required forExchange.
    • Choosing Exchange 2013 server roles to installVerify that you have enough disk space for the installation, or choose a path that does have enough disk space, andclick Next to continue.Choose the installation path for Exchange 2013If there is no existing Exchange organization in Active Directory, and you havent already prepared Active Directory forExchange, you will be prompted to enter an Exchange organization name.
    • Choose a name for the Exchange organizationWhen installing the Mailbox server role you are given the option to disable malware protection. If you disable it now youcan enable it again later.Choose whether to disable malware protection or leave it enabledWhen installing the Client Access server role you can choose to enter an external domain name if you are planning tomake the server internet-facing. This will pre-configure the virtual directories for services such as OWA with the externalname that you enter here.Configure the external name for internet-facing Client Access serversParticipation in the Customer Experience Improvement program is optional.
    • Optional participation in the CEIPSome readiness checks are performed, and then if everything is okay you can click Install to begin.Readiness checks complete and ready to install Exchange 2013When setup has finished click Complete.Exchange 2013 setup complete
    • Upgrading to Exchange Server 2013inShareOctober 14, 2012 By Paul Cunningham 1 CommentWith the news that Exchange Server 2013 has reached RTM a lot of customers are now asking for guidance on upgradingtheir existing organizations to Exchange 2013.Although all of the upgrade guidance is not publicly available yet, here is what we know so far.Supported Co-Existence Scenarios for Exchange 2013Exchange Server 2013 will support co-existence with the following versions: Exchange Server 2010 SP3 Exchange Server 2007 SP3 + an update rollupNeither Exchange 2010 Service Pack 3 nor the required update rollup for Exchange 2007 SP3 have been released yet, soas it stands right now there is no co-existence possible.Microsoft has announced that Exchange 2010 SP3 will be released some time in the first half of 2013. This leaves openthe possibility that Exchange 2013 will reach general availability (announced for Q1 2013 and rumoured to be in February)before the Exchange 2010 SP3 release. Personally I hope they arrive at the same time.No word yet on the next update rollup for Exchange 2007 SP3, which it has been suggested will be the one to meet therequirements for co-existence with Exchange 2013. However based on typical release cadence we may see this inJanuary/February 2013 as well.There will be no co-existence support for Exchange Server 2003. If you’re still running Exchange 2003 and are looking toupgrade to Exchange 2013 you’ll need to do an interim upgrade to Exchange 2010 (or 2007) first.Client Support for Exchange Server 2013During a TechEd Australia session on Exchange 2013 deployment and co-existence, Scott Schnoll showed us thefollowing list of compatible clients for Exchange Server 2013. Outlook 2013, Outlook 2010, and Outlook 2007 Entourage 2008 for Mac, Web Services Edition Outlook 2011 for MacOutlook 2013 will support Exchange 2013 as-is, but an update will be required for Outlook 2010 and 2007.There will be no support for Outlook 2003. If you’re still running Office 2003 in your environment and intend to upgrade toExchange 2013 then now would be a good time to begin looking at upgrading your Office installations.Active Directory Requirements for Exchange Server 2013In what may be a relief for some customers, Exchange 2013 will support a Windows Server 2003 Forest/Domain functionallevel, and Windows Server 2003 SP2 domain controllers, according to the information presented at TechEd.A schema update will be required as usual, and this is expected to be delivered in the same service pack/update rollupthat will provide co-existence support.A Look at Exchange Server 2013 Resource MailboxesinShare13August 22, 2012 By Paul Cunningham 1 CommentResource mailboxes have been around for a few versions of Exchange Server, and Exchange Server 2013brings us a fewimprovements in how they are managed.There are two types of resource mailboxes: Room mailboxes are for fixed locations such as meeting rooms or conference facilities
    •  Equipment mailboxes are for items that are not fixed to a location, such as laptops or vehiclesExchange 2013 puts resource mailboxes under their own section of the Exchange Administration Center. Both room andequipment mailboxes are managed in this same section.One of the immediate improvements is that you are able to set the booking policy or assign delegates during the creationof the resource mailbox, rather than as a secondary task after the mailbox is created.After the mailbox has been created there are a few additional properties you can customize. The booking options can befurther tuned with regards to recurring meetings, booking horizon, and custom replies.
    • You can also easily configure a MailTip for the resource mailbox.The text that you place in the MailTip will appear automatically when people add the room or resource mailbox to ameeting request in Outlook. Although in my opinion the MailTip needs some color to draw the person’s attention to it.Finally, an interesting default setting is the disabling of email address policies. This does make sense as most resourcemailboxes are for internal use only, so having email address policies assigning multiple SMTP addresses to resourcemailboxes is usually not necessary.
    • Overall it appears that room and resource mailboxes are a feature that has matured over the previous versions ofExchange Server and now receive just a few minor improvements to make them simpler to manage.Changes to Test Cmdlets in Exchange Server 2013Each new version of Exchange Server usually brings with it some new PowerShell cmdlets, and Exchange Server 2013 isno different.According to a quick check of my test systems, the Test-* cmdlet count for each of the current versions of Exchange is asfollows: Exchange 2007, 17 cmdlets Exchange 2010, 29 cmdlets Exchange 2013, 32 cmdletsBetween Exchange 2010 and Exchange 2013 the changes are as follows.New cmdlets in Exchange Server 2013: Test-MigrationServerAvailability – relates to migrations to Exchange online Test-OAuthConnectivity – tests OAuth authentication to an application Test-SiteMailbox – tests connectivity between the site mailbox and SharePoint, as well as verifying correct permissions Test-TeamMailbox – I can’t find information on this one yet but it appears to perform similar tests to Test-SiteMailboxCmdlets removed in Exchange Server 2013: Test-ExchangeSearch – presumably this is no longer required with the switch to FAST search in the 2013 serversUsers do not receive quota warning messagesWe all know that, for better or for worse, the way Exchange calculates and sends Quota Messages changedwith Exchange 2010 SP1. We also know that this has caused nothing but confusion for many Administratorsout there…In this post I will try to give an overview of the new behaviour for normal mailboxes and, more important,explain when users will actually receive these messages.Pre Exchange 2010 SP1In Exchange environments previous to Exchange 2010 SP1, Exchange sends a quota message to mailboxowners when a:1. Mailbox exceeds its IssueWarningQuota limit (the lowest storage quota);2. Mailbox exceeds its ProhibitSendQuota limit (the middle storage quota);3. Mailbox exceeds its ProhibitSendReceiveQuota limit (the highest storage quota).Remember that:quota messages are sent to mailbox owners, so if a mailbox is owned by a security group (sharedmailbox), quota messages are sent to the security group;quota messages are sent with high importance and are not subject to storage quotas, which meansthey are always delivered even if the recipient’s mailbox is full;quotas can be configured at a mailbox or database level.
    • These quota messages are sent during the QuotaNotificationSchedule specified for each mailboxdatabase, which would normally be something like every day from 4AM to 6AM:Get-MailboxDatabase | Set-MailboxDatabase -QuotaNotificationSchedule “Mon.04:00-Mon.06:00, Tue.04:00-Tue.06:00, Wed.04:00-Wed.06:00, Thu.04:00-Thu.06:00, Fri.04:00-Fri.06:00, Sat.04:00-Sat.06:00, Sun.04:00-Sun.06:00″During this period, Exchange goes through every mailbox in the database(s) and if any has exceeded thequota threshold, it sends the owner an e-mail. No matter if the schedule was 1h, 2h or 10h, as long asExchange has enough time to go through every mailbox, everyone over quota receives one warningmessage.Exchange 2010 SP1 OnwardsNow comes SP1 and all hell breaks loose… We still have:the same 3 levels of quotas;quotas configurable at the user or database level;Quota messages sent during the QuotaNotificationSchedule.BUT…. The way these messages are generated has changed… Now, every mailbox has a flag that controlswhether it is checked to see if it has exceed a quota threshold. This flag is only set if the mailbox size ismore than 50% of the ProhibitSendQuota limit! Unfortunately, this flag is a system property (part ofthe code) and therefore not visible using MFCMapi…Let’s take an example and imagine a mailbox currently 450MB in size. This mailbox (or its database)has IssueWarningQuota set to 400MB andProhibitSendQuota set to 1GB. We can see the mailbox isover its warning limit but because 450MB is not over 50% of the ProhibitSendQuota (500MB), it will not bechecked and will not receive a quota warning message!On top of this, once a mailbox has been checked during the QuotaNotificationSchedule, the flag is clearedand the mailbox will not be checked again until the flag is reset. Now, here’s the problem I found: accordingto Microsoft documentation, this flag is reset when “either a message is saved in the mailbox or a message issubmitted“. When this happens, if the mailbox size is more than 50% of the ProhibitSendQuota, the flag isreset and the mailbox will be checked during the next QuotaNotificationSchedule.But what exactly is a saved message?! I assumed that if a user drafted a message and saved it withoutsending it, the flag would be reset. However, from my tests this is not the case… So far, only sending e-mails from a mailbox seems to reset this flag. This means that if you have a mailbox that only receivese-mails, it will never receive the warning message. Again, this is what I am seeing in the environment I workat and from my tests!You might be asking why I previously emphasised the “1″ in “everyone over quota receives one warningmessage“. By default, with SP1 theQuotaNotificationSchedule is set to run for 15 minutes every day at1AM. If you increase this to 2h, for example, your users might receive more than one message at a time! Ihad cases where I had this set to run over 3h for testing purposes, and some users received 3 quotamessages…TroubleshootingIf you would like to see if/which mailboxes are over quota or received a quota message, you have a fewmethods:Increase the diagnostic logging on the mailbox server you want to check:1. Open the Exchange Management Console;2. Choose Server Configuration;3. Select the the server name under Server Configuration for which you want to increase logging ;4. Choose Manage Diagnostic Logging Properties… under the Actions pane;5. Expand MSExchangeIS;6. Expand 900 Private;7. Choose Storage Limits;8. Select the Expert radio button and click Configure;9. You don’t need to restart the MSExchangeIS service or dismount and remount the database stores;10. The next time the QuotaNotificationSchedule runs, look for the EventID 1077 inthe Application log.Use PowerShell to check mailbox statistics:
    • Get-MailboxStatistics -Database MDB01 | ? {$_.StorageLimitStatus -eq “IssueWarning” -OR $_.StorageLimitStatus -eq “ProhibitSend” -OR $_.StorageLimitStatus -eq“ProhibitSendReceive”} | Select DisplayName, Alias, StorageLimitStatusUse PowerShell to see which users received a quota message:Get-TransportServer | Get-MessageTrackingLog -ResultSize Unlimited -Start“08/08/2012″ -MessageSubject “your mailbox is” –EventID DELIVER | SelectTimeStamp, Recipients, MessageSubjectExchange 2013I have been doing some tests with Exchange 2013 to check if the behaviour is the same, but for some reasonExchange doesn’t seem to check my mailbox for quotas…From the screenshot below, you will see that:1. Database DB1 has ProhibitSendQuota set to 400MB and IssueWarningQuota to 200MB;2. My mailbox is using the database’s quota defaults;3. My mailbox is over the IssueWarningQuota limit with a size of 246MB4. Exchange has not set the StorageLimitsStatus for my mailbox which should say IssueWarning (ifit’s the same as 2007 and 2010).It was only when I set quota limits at the mailbox level that I started to get warning messages, so I am stilltrying to understand exactly what is going on with Exchange 2013…ConclusionTo reiterate, from Exchange 2010 SP1 onwards:Every mailbox has a flag to control if the mailbox’s quota is checked;This flag is only set if the mailbox size is more than 50% of the ProhibitSendQuota limit;If the flag is set, Exchange will send a quota message duringthe QuotaNotificationSchedule interval and then clear the flag;The flag is reset only when a message is sent from the mailbox;Hope this helps clarifying the new behavior regarding quota messages!
    • Exchange 2013 mailflow explainedI’ve been playing with Exchange 2013 for a while now and overall – I love all the new features.Let’s take a closer look at mailflow architecture in Exchange 2013…The Exchange team calls the overall mailflow happening through a transport pipeline. A transport pipeline isnothing but a collection of windows services, some connections and some components and messages queuesthat act together to make the overall email flow through the categorizer in the Hub transport Service whichnow reside on the Mailbox server.I thought of creating a chart to help you understand various services, where they are homed and theirfunction:Server role Service Name FunctionsMailbox ServerRoleHub Transport service Handles all incoming and outgoing SMTP email messagesMessage content inspectionMessage CategorizationActs as a middle man and routes messages between MailboxTransport service and the Front End Transport serviceIs identical to the Hub Transport Server role in Exchange 2010Never contacts the mailbox databases directlyAccepts external messages from the front end transport serviceMailbox ServerRoleMailbox Transport service 2 services treated like one – Mailbox Transport Submissionservice and Mailbox Transport Delivery serviceThe Mailbox Transport Delivery service receives SMTPmessages from the Hub Transport service, andconnects to the mailbox database using anExchange remote procedure call (RPC) to deliver the messageThe Mailbox Transport Submission service connectsto the mailbox database using RPC toretrieve messages, and submits the messagesover SMTP to the Hub Transport serviceMailbox Transport service doesn’t queue any messages locallyCommunicates directly with mailbox databasesCAS Server Role Front End TransportserviceRuns on all Client Access serversActs like a proxy for all inbound and outbound external SMTP trafficCan filter messages based on connections, domains, senders, andrecipientsCannot read the message contentOnly communicates with the Hub Transport service
    • Accepts external messages through a receive connectorMessages inside the organization enter the Hub Transport service on a Mailbox server in one of the followingways:Through a Receive connector.From the Pickup directory or the Replay directory.From the Mailbox Transport service.Through agent submission.Every message that’s sent or received in an Exchange 2013 Preview organization must be categorized in theHub Transport service on a Mailbox server before it can be routed and delivered. After a message has beencategorized, it’s put in a delivery queue for delivery to the destination mailbox database, the destinationdatabase availability group (DAG), Active Directory site, or Active Directory forest, or to the destinationdomain outside the organization.The Hub Transport service on a Mailbox server consists of the following components and processes:SMTP Receive:When messages are received by the Hub Transport service, message content inspection is performed,transport rules are applied, and anti-spam and anti-malware inspection is performed if they are enabled. TheSMTP session has a series of events that work together in a specific order to validate the contents of amessage before it’s accepted. After a message has passed completely through SMTP Receive and isn’trejected by receive events, or by an anti-spam and anti-malware agent, it’s put in the Submission queue.Submission:Submission is the process of putting messages into the Submission queue. The categorizer picks up onemessage at a time for categorization.Submission happens in three ways:Through an SMTP Receive connector.Through the Pickup directory or the Replay directory. These directories exist on the Mailbox server. Correctlyformatted message files that are copied into the Pickup directory or the Replay directory are put directly intothe Submission queue.Through an agent.Categorizer:The categorizer picks up one message at a time from the Submission queue. The categorizer completes thefollowing steps:Recipient resolution, which includes top-level addressing, expansion, and bifurcation.Routing resolution.Content conversion.Additionally, mail flow rules that are defined by the organization are applied. After messages have beencategorized, they’re put into a delivery queue that’s based on the destination of the message. Messages arequeued by the destination mailbox database, DAG, Active Directory site, Active Directory forest or externaldomain.SMTP Send: How messages are routed from the Hub Transport service depends on the location of themessage recipients relative to the Mailbox server where categorization occurred. The message could berouted to the Mailbox Transport service on the same Mailbox server, the Mailbox Transport service on adifferent Mailbox server that’s part of the same DAG, the Hub Transport service on a Mailbox server in adifferent DAG, Active Directory site, or Active Directory forest, or to the Front End Transport service on a
    • Client Access server for delivery to the Internet.Most of the content in this article is taken from the E2013 help file. I just thought of formatting in a way easyto understand.“Could not send your message.Error 421.” – Meaning of the NumbersHave you ever tried wondering what the codes actually mean? Or have you thought, if these numbers domake some sense? Or if they might mean something which could help you identify with the issue. Very oftenyou encounter this in your mailbox. I intend just giving a small heads-up in understanding the meaning orinterpreting the error codes which might help in making sense as to where the trouble could be.Primarily you will get the error code with three numbers as I showed above Error 421.First Number: This lets you know whether the server has accepted the command and wascapable to handle it or not. Let me address you the possible meanings of the first number in theerror now.1: The server has taken the command, but it’s not executing it. Here you need a confirmation message.2: The server was able to complete the task.3: The server was able to understand the request but feels it needs more information to complete it.4: The server faces a temporary failure here. If you try executing the command again, it may complete. Attimes, mail servers use such temporary failures to keep security higher.5: The server actually has the error and you should attempt it.Second Number: This gives a little more information. Let me address you the possible meaningsof the second number in the error now:0: This indicates that a syntax error has taken place.1: This indicates an informational reply, for example to a HELP request.
    • 2: This indicates your connection status.3 and 4 are unspecified.5: This indicates your status of the mail system as a whole and the mail server in particular.Third Number: The last number is the key. It pertains more to mail transfer status. This actuallyrelates to the detailed list of ESMTP server response codes, as laid down in RFC 821 and laterextensions.211 - This indicates a system status message.214 - This indicates that a help message for a human reader follows.220 - This indicates that SMTP Service ready.221 - This indicates that service is closing.250 - This indicates that requested action taken and completed.251 - This indicates that the server will accept and forward the message though the recipient is not localto the server.252 - This indicates the server accepts the message, tries delivering it inspite of the recipient not beingVRFYed.354 - Start message input and end with <CRLF>.<CRLF>. This indicates that the server is ready to acceptthe message.421 - This indicates that the service is not available and the connection will be closed.450 - This indicates to try again later as the requested command failed due to unavailability of user’smailbox.451 - This indicates server error.452 - This indicates insufficient system storage.The following error messages (500-504) usually tell you that your email client is broken. It’s probably bestto let the program’s author know.500 - This indicates syntax error.501 - A syntax error was encountered in command arguments.502 - This command is not implemented.503 - This indicates that the server has encountered a bad sequence of commands.504 - This indicates that command parameter is not implemented.550 - This indicates that the user’s mailbox was unavailable (for example because it was not found, orbecause the command was rejected for policy reasons).551 - The recipient is not local to the server. The server then gives a forward address to try.552 - This indicates that storage allocation was exceeded.553 - This indicates invalidity of the mailbox name.554 - The transaction failed.
    • Microsoft Exchange Server 2013 Preview InstallationThe preview version of Microsoft Exchange is out now and available for download:Grab a copy here: http://technet.microsoft.com/en-US/evalcenter/hh973395Once you click the link, you will be asked to sign in with your Hotmail or Live id and once you install theActiveX control, it will let you download the preview.The downloaded exe file is about 1.35GB and about 3.35GB post extraction.Let’s take a look at Whats new with Microsoft exchange 2013:1. Exchange 2013 Server Roles2. Operating System requirements3. Exchange server 2013 pre-requisites4. Preparing Active Directory domains5. A look at unattended and GUI installation6. A look at mailflow in Exchange 2013 – the Front End Transport service on Client Access servers, theHub Transport service on Mailbox servers, and the Mailbox Transport service on Mailbox serversSteps in detail:1. Exchange 2013 Server Roles: One of the major changes in server roles is that the Hub TransportServer role is long gone.Exchange server 2013 server roles consist of just:Client Access server roleMailbox server roleCAS servers proxies connectivity for all clients through IIS so – Microsoft Office Outlook, Outlook Web App,Exchange ActiveSync mobile devices, POP, and SMTP and also accepts mail from and delivers mail toother mail hosts on the Internet.Client access servers can be organized into Client Access server arrays.Mailbox role stores mailbox data performs processing, acknowledging and rendering for client connectionsproxied by the Client Access server, and handles Unified Messaging requests.DAG’s are still intact and Mailbox servers will be organized into back-end clusters that use DAG’s.2. Operating System requirements: Exchange server 2013 is only supported on x64 bit architecture.Server Role OS RequirementMailbox and Client Access server roles Windows Server 2012Windows Server 2008 R2 Standard with SP1Windows Server 2008 R2 Enterprise with SP1Windows Server 2008 R2 Datacenter RTM or laterSupport for Outlook as follows:Outlook 2013 PreviewOutlook 2010 SP1 with April 2012 Cumulative UpdateOutlook 2007 SP3 with July 2012 Cumulative UpdateEntourage 2008 for Mac, Web Services EditionOutlook for Mac 20113. Exchange server 2013 pre-requisites:Forest functional level should be at least Windows Server 2003
    • Schema master is running Windows Server 2003 with SP1 or laterDifferent from other version, MS suggests installing MBX role firstThe machine which you use to Prepare Active Directory should have the following:Microsoft .NET Framework 4.5Windows Management Framework 3.0Windows Server 2012 ships with these already. So no need to install separately.Now install the following on the server:Component Operating System Command PlatformRemote ToolsAdministration PackWindows Server 2012 Install-WindowsFeature RSAT-ADDSPowershellW2K8 2008 R2 SP1 Add-WindowsFeature RSAT-ADDSOn Windows Server 2012 – If you are installing both MBX and CAS role or MBX role ONLY on thesame server:Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth,Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console,Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server,Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-FoundationNow install:1. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit2. Microsoft Office 2010 Filter Pack 64 bit3. Microsoft Office 2010 Filter Pack SP1 64 bitNow, uninstall Microsoft Visual C++ 11 Beta Redistributable (x64):1. Open Control Panel > Programs and Features.2. Select Visual C++ 11 Beta Redistributable (x64) – 11.0.50531 and then click Uninstall.3. In Microsoft Visual C++ 11 Beta setup, click Uninstall.4. When Microsoft Visual C++ 11 Beta is uninstalled, click Close.On Windows Server 2012 – If you are installing CAS role ONLY:Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth,Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console,Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server,Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-FoundationNow install:Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bitNow, uninstall Microsoft Visual C++ 11 Beta Redistributable (x64):1. Open Control Panel > Programs and Features.2. Select Visual C++ 11 Beta Redistributable (x64) – 11.0.50531 and then click Uninstall.3. In Microsoft Visual C++ 11 Beta setup, click Uninstall.4. When Microsoft Visual C++ 11 Beta is uninstalled, click Close.On Windows Server 2008 R2 SP1 – If you are installing both MBX and CAS role or MBX role ONLYon the same server:Import-Module ServerManagerAdd-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy,RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth,
    • Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase,Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMINow install these in the order which is shown:Microsoft .NET Framework 4.5 RCWindows Management Framework 3.0Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bitMicrosoft Office 2010 Filter Pack 64 bitMicrosoft Office 2010 Filter Pack SP1 64 bitMicrosoft Knowledge Base article KB974405 (Windows Identity Foundation)Knowledge Base article KB2619234 (Enable the Association Cookie/GUID that is used by RPC over HTTP toalso be used at the RPC layer in Windows 7 and in Windows Server 2008 R2)Knowledge Base article KB2533623 (Insecure library loading could allow remote code execution)Now, uninstall Microsoft Visual C++ 11 Beta Redistributable (x64):1. Open Control Panel > Programs and Features.2. Select Visual C++ 11 Beta Redistributable (x64) – 11.0.50531 and then click Uninstall.3. In Microsoft Visual C++ 11 Beta setup, click Uninstall.4. When Microsoft Visual C++ 11 Beta is uninstalled, click Close.On Windows Server 2008 R2 SP1 – If you are installing CAS role ONLY:Import-Module ServerManagerAdd-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy,RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth,Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase,Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMINow install these in the order which is shown:Microsoft .NET Framework 4.5Windows Management Framework 3.0Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bitKnowledge Base article KB974405 (Windows Identity Foundation)Knowledge Base article KB2619234 (Enable the Association Cookie/GUID that is used by RPC over HTTP toalso be used at the RPC layer in Windows 7 and in Windows Server 2008 R2)Knowledge Base article KB2533623 (Insecure library loading could allow remote code execution)Now, uninstall Microsoft Visual C++ 11 Beta Redistributable (x64):1. Open Control Panel > Programs and Features.2. Select Visual C++ 11 Beta Redistributable (x64) – 11.0.50531 and then click Uninstall.3. In Microsoft Visual C++ 11 Beta setup, click Uninstall.4. When Microsoft Visual C++ 11 Beta is uninstalled, click Close.Preparing Active Directory domains: At least one domain controller running any of the following:Windows Server 2012Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)Windows Server 2008 R2 Standard or EnterpriseOn Windows Server 2008 R2 SP1, run “Add-WindowsFeature RSAT-ADDS”On Windows Server 2012 computers, run “Install-WindowsFeature RSAT-ADDS”
    • Now type this in an elevated command prompt:setup /PrepareAD [/OrganizationName: <organization name> ] or setup /p [/on:<organizationname>]Post upgrades confirm if it was successful by:objectVersion property in Active Directory.The objectVersion property is in the CN=<your organization>,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=<domain> container.The objectVersion value for Exchange 2013 is 15448.Schema container, verify that the rangeUpper property on ms-Exch-Schema-Verision-Pt is set to 15132Let’s take a look at the installation now:Things to look for:If you are installing one role ONLY, install the MBX role firstInstall at least one Mailbox and one Client Access server in an Active Directory site. AMailbox server is required for the Client Access server to work correctlyInstall all pre-requisites mentioned aboveEnterprise admins and Schema admins group permissionsIf you are installing the CAS server alone, set the “Net.Tcp Port Sharing Service” type toAutomaticTo install in unattended mode:Setup.exe /mode:Install /role:ClientAccess,Mailbox /OrganizationName:EXCHGURU/IAcceptExchangeServerLicenseTermsTo install using the GUI mode:
    • Accept the license and Error reporting and click next
    • Now the setup will check to ensure all prerequisites are in place:As you can see, I got a bunch of errors so I am going to install all pre-requisites now:
    • Error:This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://support.microsoft.com/kb/2619234).Without this update, the Outlook Anywhere feature may not work reliably.This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://support.microsoft.com/kb/2619234).Without this update, the Outlook Anywhere feature may not work reliably.http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.aspxError:This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Download it fromhttp://go.microsoft.com/fwlink/?LinkId=238142.This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Download it fromhttp://go.microsoft.com/fwlink/?LinkId=238142.http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspxError:This computer requires the update described in Microsoft Knowledge Base article KB974405 (http://support.microsoft.com/kb/974405).Please install the update and restart setup.This computer requires the update described in Microsoft Knowledge Base article KB974405 (http://support.microsoft.com/kb/974405).Please install the update and restart setup.http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7WindowsIdentityFoundationUpdateNotInstalled.aspxError:All Exchange 2010 servers in the organization need to be at Exchange 2010 SP3 orlater.All Exchange 2010 servers in the organization need to be at Exchange 2010 SP3 orlater.http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.E15E14CoexistenceMinVersionRequirement.aspxWarning:
    • This computer requires the Microsoft Office 2010 Filter Packs – Version 2.0. Please install the software fromhttp://go.microsoft.com/fwlink/?LinkID=191548. For more information see the help link:http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.MSFilterPackV2NotInstalled.aspxWarning:This computer requires the Microsoft Office 2010 Filter Packs – Service Pack 1. Please install the software fromhttp://www.microsoft.com/download/en/details.aspx?id=26604. For more information see the help link:http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.MSFilterPackV2SP1NotInstalled.aspxThis error did give me a hard time:Error:All Exchange 2010 servers in the organization need to be at Exchange 2010 SP3 orlater.All Exchange 2010 servers in the organization need to be at Exchange 2010 SP3 orlater.http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.E15E14CoexistenceMinVersionRequirement.aspxThis means that you cannot install Exchange 2013 Preview in mixed mode.So, I had to perform the installation in a brand new AD forest Once I completed all pre-requisite installation, setup completed successfully.Exchange Server 2013 PreviewA new star has appeared on the horizon: Microsoft announced the preview edition of ExchangeServer 2013 on July 16 along with the other servers and clients that collectively form the Office2013 “wave.” The pace will increase at the Microsoft Exchange Conference (MEC) in Orlandoon September 24 when Microsoft will release a mass of detail about Exchange 2013 en route toshipping the product in early 2013. One problem that always faces software vendors with verymature products is trying to build a case to convince customers to upgrade. Exchange Server5.5 did a fine job of processing email when it was launched in 1998. Every version of Exchangesince then has continued to add new features that respond to customer demands, reflect thecurrent market, or give Exchange a competitive edge. For example, the Exchange Server 2010story is focused on high availability because thats a compelling feature for many customers.Exchange 2013 represents three years of output from a large engineering group and includesnumerous changes, improvements, and tweaks that I could discuss; however, I dont have thespace to cover everything in detail. Instead, lets concentrate on the features that mightconvince CIOs to approve an upgrade. Understanding the value that the new features providewill help you decide whether and when to upgrade your environment. Keep in mind thatMicrosoft is still working on Exchange 2013, and some details might change between thepreview edition discussed here and general availability.
    • Deployment BasicsAs in Exchange 2010 and Exchange Server 2007, Microsoft doesnt support in-place upgradesfor Exchange 2013. Instead, you must deploy on new or reused hardware. Because of achange in the way that Client Access servers process user credentials to comply with a new"serialized common security context" and the need to update Exchange 2010 with new code tointeroperate with Exchange 2013, you must upgrade your Exchange 2010 servers to ServicePack 3 (SP3), which isnt scheduled for release until early 2013. You also must install an ActiveDirectory (AD) schema update to prepare the way for new functionality such as "modern" publicfolders (which I discuss later). If youre still running Exchange 2007, you need to update thoseservers with a patch that Microsoft has yet to finalize. Exchange Server 2003 servers are nolonger supported in an organization after you upgrade to Exchange 2013.Exchange 2013 supports Windows Server 2008 R2 (SP1 or later) or Windows Server 2012.Although components such as PowerShell 3.0 are exploited, its not yet clear whetherExchange 2013 will take advantage of some of the advanced new features of Server 2012. Forexample, database availability groups (DAGs) use Windows failover clustering, which supportsup to 64 servers on Server 2012. It would be nice if Exchange 2013 supported more than thecurrent 16-server limit in a DAG. Every AD site into which you deploy Exchange 2013 musthave at least one Server 2008 (or higher) Global Catalog (GC) and domain controller (DC), andthe overall forest must be at Windows Server 2003 functional level or higher. Exchange 2013doesnt support read-only DCs (or GCs), nor is it possible to run Exchange 2013 on Server2012 Server Core.When you install Exchange 2013, youll see that server roles have been simplified. We nowhave Client Access servers and Mailbox servers, both of which are different from theirExchange 2010 or Exchange 2007 equivalents, and both of which have taken over someaspects of the work previously done by Hub Transport servers. Client Access servers aredesigned to be stateless servers that proxy incoming connections from all protocols, includingSMTP. Unlike older Client Access servers, Exchange 2013 Client Access servers support TCP(layer 4) affinity to make load balancing easier. By comparison, Exchange 2010 and Exchange2007 load balancing is based on layer 7 affinity, so if you use hardware load balancers, youneed to check with your vendor to establish whether changes are required to support Exchange2013. The upshot is that these changes dramatically reduce the complexity of load balancing inan Exchange environment.Although they appear similar to their predecessors, Exchange 2013 Mailbox servers represent amajor evolution of the Exchange 2010 model. All rendering and other processing of messagesoccurs on Mailbox servers. (Client Access servers perform some of this work in Exchange2010.) This simplifies processing if a failure occurs because everything switches to the Mailboxserver that activates the failed databases. Client Access servers now focus solely on makingsure that client connections get to the correct Mailbox server.Communication between Client Access servers and Mailbox servers is through either HTTP(MAPI RPCs are wrapped in HTTP) for client traffic or SMTP for transport. Exchange 2013doesnt yet have an Edge Transport server role, but you can continue to use Exchange 2010(SP3) Edge servers until Microsoft updates these servers.Microsoft recommends upgrading Internet-facing sites first, followed by internal sites. Thisapproach allows Exchange 2013 Client Access servers to take over the organizations
    • namespace and support incoming connections for both down-level Exchange 2010 andExchange 2013 servers. Microsoft also recommends that you either install both roles on the firstExchange 2013 server installed or make sure that at least one server of each type is deployed.The reason for this is that PowerShell cmdlets are executed only on Mailbox servers, so youneed to have an Exchange 2013 Mailbox server available to be able to manage theenvironment.I think most administrators will find it natural to install both roles on all servers. Role separationis most commonly encountered in larger deployments that require this level of flexibility andcontrol. Microsofts goal is that you should be able to update Client Access servers and Mailboxservers independently. In the future, it should be possible to mix and match Client Accessservers and Mailbox servers running different software versions without any problems. SplittingExchange into thin protocol servers and thick compute engines addresses some of the currentcomplexity, in which all of the Exchange components that interact with a users mailbox must beupgraded together. The new architecture also delivers a useful benefit for Office 365 becauseExchange 2013 will be much easier for Microsoft to deploy and update in its data centers thanits predecessors are.Database UpdatesExchange 2013 continues to use the Extensible Storage Engine (ESE) for its databases, whichare populated by moving mailboxes from Exchange 2010 or Exchange 2007 servers. You cantmove mailboxes directly from Exchange 2003 servers; these moves must go through anintermediate Exchange 2010 or Exchange 2007 server.For the third version in succession, Microsofts Exchange engineers have focused on theefficiency of the Exchange Information Store. All Exchange 2010 and Exchange 2007 Storecode has been rewritten in new managed code modules, resulting in a further reduction in theI/O footprint per active mailbox. More memory is used to cache data to avoid expensive diskI/O.Microsoft learned a lot from Exchange 2010 customer deployments, as well as from thecompanys own experience running Exchange Online for millions of mailboxes. Multiple diskfailures in JBOD arrays (approximately 5 percent for 7.2K rpm SATA drives and 2.75 percent for7.2K rpm SAS disks) resulted in the frequent need to reseed database copies on replaceddisks. Because reseeding operations from a single source is slow, Exchange 2013 can nowreseed a database copy from all available copies. According to Microsoft, its now possible tocomplete a reseed operation for a 2TB database in approximately 10 hours rather than the 23hours previously required if three healthy database copies are available. Although not manyinstallations operate 2TB+ databases, I appreciate the fact that operational experience fromOffice 365 is driving improvements that benefit on-premises customers.Because of a change in the way mailbox properties and other overhead are more accuratelyincluded in the calculation of mailbox size, you can expect to see mailbox sizes grow byapproximately 30 percent. No increase in physical database size occurs, but you might have toadjust some assigned mailbox quotas to accommodate the new overhead.Exchanges Transport Dumpster feature captures and holds copies of messages in transit untilthe messages are safely committed. Exchange can recover copies of messages from theTransport Dumpster if data loss occurs as a result of a database outage. Exchange 2013
    • updates the Transport Dumpster feature to better support lagged database copies. A laggeddatabase copy is designed to remain a predefined time period (up to 7 days) behind the livedatabase copy and is intended to provide a backup for database recovery in case a problemoccurs that corrupts the live database and its other copies. Exchange 2013 expands theTransport Dumpster feature so that the Transport Dumpster understands when a serversupports lagged copies and therefore keeps copies of messages until theyre committed into thelagged copy. This change is small but important.A New Era of AdministrationPrevious versions of Exchange include a Windows-based administration console. A centraltheme in Server 2012 is remote administration. Exchange 2010 demonstrates the effectivenessof this approach by using remote PowerShell as the underlying foundation for all of itsmanagement interfaces, including the Microsoft Management Console (MMC)-based ExchangeManagement Console (EMC).Exchange 2010 also includes a browser-based administration console, the Exchange ControlPanel (ECP), which is used as the primary management tool for Exchange Online. The ECP iseffective in many respects. For example, its interface is built from "slabs," each of which revealsthe necessary UI for specific functionality, such as executing multi-mailbox discovery searches.The ECP exposes slabs based on users Role Based Access Control (RBAC) membership. Forexample, a user who is a member of the Discovery Management role group will see the UI tocreate, execute, and examine mailbox searches. If youre not a member of this role group, theECP simply rearranges UI elements to disguise the fact that mailbox searches even exist.Exchange 2013 management is performed through a much-enhanced version of the ECP calledthe Exchange Administration Center (EAC), which Figure 1 shows.Figure 1: Exchange 2013s Exchange Administration Center (Click image for larger view)The EAC uses the same UI framework as the ECP but expands its functionality to include all ofthe management components that the ECP doesnt support, such as DAG management (seeFigure 2) and the wizards that automate many aspects of Exchange server management.
    • Figure 2: Adding a new server to a DAG (Click image for larger view)The EAC follows the design principles for Metro-style interfaces, as does the upgraded versionof Outlook Web App (OWA). In addition to being more approachable for inexperiencedadministrators than the EMCs complex layout is, Microsoft notes that the EAC is far moreefficient than the EMC at dealing with a large number of objects and is therefore capable ofhandling even the largest Exchange deployment.Few will shed many tears at the demise of the EMC. Despite its richness in features, the EMCwas slow and unwieldy and had suffered some recent problems when Internet Explorer 9.0changed an underlying component. It makes more sense for Microsoft to concentrate its effortson browser-based management tools that can be used on almost any PC, as well as on otherdevices such as iPads. In addition, the EAC provides the basis for a common administrativeplatform shared between on-premises and cloud deployments. The only downside is the loss ofthe EMCs three PowerShell learning tools. Many administrators used the EMCs ability todisplay the PowerShell code it executed as a way to become accustomed to PowerShell syntaxand constructs.Modern Public FoldersMicrosoft describes the Exchange 2013 implementation of public folders as "modern publicfolders." Given that the public folder implementation in Exchange 2010 is based on the samedesign as originally implemented in Exchange Server 4.0 (circa 1996), its fair to describe thenew approach as "modern," especially because the storage model now uses mailbox databasesthat let public folders take advantage of the development tweaks Microsoft put into refiningmailbox databases over the past three releases.In Exchange 2013, every public folder mailbox holds a copy of the public folder hierarchy. Asingle public folder mailbox, which is always the first public folder created in the organization,
    • stores a writeable copy of the hierarchy (the master hierarchy). Changes made to the mastercopy are replicated to the other mailboxes. Access to public folder content is thereforeaccomplished by first interrogating the hierarchy, followed by a redirect to the specific publicfolder mailbox holding the content. Unlike in previous versions of Exchange, content isntreplicated to multiple public folder replicas. It always remains in a single distinct location whoseintegrity is protected by standard Exchange high-availability features.Moving to this model has many advantages. Public folders have long been the cockroaches ofExchange -- unloved but ever-present. As such, they havent received much attention; somewould argue that Microsoft dedicated just enough effort to public folders to keep them alive.Modern public folders are stored in mailbox databases and are therefore maintained as a corecomponent. Another major advantage is that public folders now enjoy the high-availabilityfeatures of DAGs. Of course, public folders have enjoyed a multi-copy replication model eversince Exchange 4.0. However, although public folder replication works, it doesnt offer the samekind of advanced replication and problem-solving features that are available in a DAG, such asblock mode replication or single page patching.Exchange 2013 public folder deployment and management will require different techniques. Itstoo soon to offer a definitive assessment of possible fault lines, but because of the variousmethods available for deploying public folders, some hiccups are sure to happen along the way-- possibly related to electronic forms or to other applications that use public folders for storage.The migration path to modern public folders goes something like this:1. Move all user mailboxes to Exchange 2013 servers. Users will still continue to accesspublic folders on an Exchange 2010 server. Users whose mailboxes are on Exchange 2010or Exchange 2007 servers cant access Exchange 2013 public folders.2. Run the public folder migration script (PublicFolderToMailboxMapGenerator.ps1) toanalyze the existing public folder hierarchy and folder content. You can use this scriptsoutput to create an initial set of Exchange 2013 public folder mailboxes.3. Initiate the process to move public folders to Exchange 2013. The Mailbox ReplicationService (MRS) creates public folder mailboxes in the target database and performs theinitial population.4. Background synchronization by the MRS continues to keep two sets of public folderssynchronized for up to 30 days. Administrators use this time period to prepare for the finalswitchover.5. Administrators trigger the final replication phase. This is similar to the existing functionalityin Exchange 2010 where an administrator can resume a suspended mailbox move. TheMRS then performs a final incremental synchronization to ensure that all of the content inthe public folders is completely up-to-date, then switches the AD configuration so that usersbegin to access the Exchange 2013 public folders. All versions of Outlook supported byExchange 2013 can access public folders in their new location.6. After the switchover is complete, an organization cant revert to Exchange 2010 publicfolders.Although the new public folders are contained in mailbox databases, their content isnt exposedto discovery searches, nor is it possible to apply mailbox retention policies. Microsoft will offermodern public folders as a new feature for Office 365 subscribers. However, because OWAwont support access to public folders until Exchange 2013 SP1, you’ll have to use Outlook2013 to access the new repository.
    • Data Leak ProtectionMicrosoft did an enormous amount of work on a broad set of compliance features in Exchange2010, with archive mailboxes, multi-mailbox discovery searches, an upgraded dumpster, andretention policies. Exchange 2013 adds Data Leak Protection (DLP) to its compliancecapabilities.A simple way to describe DLP is that it stops users from doing stupid things such as includingdata that they shouldnt share in email messages. For example, its usually a bad idea to send acredit card number in an email message because this data can be misused if the message isintercepted or ends up with an unintended recipient. DLP tries to identify confidential data inemail messages and prevent such data from leaving the organization.DLP works through policies defined on an organizational level. These policies identify thehallmarks of confidential data that should be protected. DLP is very similar to transport rules inthat Exchange examines messages as they pass through the transport pipeline to identify policyviolations and then takes whatever action is defined by the policy. For example, messages canbe suppressed, sent to an authorized intermediary such as a manager, protected againstunauthorized access with Rights Management Services (RMS), or returned to the sender withan explanation of why a policy has been violated. Code is built in to Outlook 2013 to make itDLP-aware so that potential policy violations can be flagged as messages are composed.Exchange 2013 includes a set of DLP policies, such as policies that protect Gramm-Leach-Bliley Actdata (for financial services), Payment Card Industry–Data Security Standard (PCI-DSS) data (credit card information), and US personally identifiable information (PII) (data thatcould identify an individual, such as a Social Security number). Custom policies can be createdfrom scratch or imported from a file. Microsoft believes that ISVs will develop market-specificDLP policies that can be sold to companies.DLP will be very important for some customers, especially those who work in highly regulatedindustries. Other companies wont regard DLP as important. Adoption will likely be slowbecause only Outlook 2013 fully supports DLP, much like Outlook 2010 was the only client thatcould display MailTips when Exchange 2010 debuted.Site MailboxesIn some respects, site mailboxes complicate Exchanges collaboration story, if only becauseeven more choices exist for how the sharing needs of groups of users can be met. Sitemailboxes are based on SharePoint 2013 and require Outlook 2013 Professional Plus (orOWA). Cynics might ask why site mailboxes havent appeared before, because manycustomers have asked for better integration between SharePoint and Exchange. In thisimplementation, documents reside in SharePoint, and Exchange looks after calendaring andemail. A tight link is maintained between Exchange and SharePoint to ensure that new contentis synchronized correctly between the two repositories. No hybrid configurations are supportedfor site mailboxes, which means that the Exchange and SharePoint servers must be deployedon premises.Setting up site mailboxes is easy. After theyre created, new site mailboxes appear in Outlook2013 as soon as Autodiscover refreshes the set of resources available to a user. Site mailboxesappear much like shared mailboxes or PSTs, with the obvious difference that any access to adocument is processed by SharePoint. The transfer between SharePoint and Exchange is
    • seamless and users can perform all the operations youd expect, such as dragging anddropping messages from a mailbox to SharePoint or vice versa.Creating software that meets all possible requirements is difficult in a first release, and sitemailboxes are no exception. Several issues exist that could make site mailboxes lesssuccessful when deployed. Like archive mailboxes, documents associated with a site mailbox that are stored inSharePoint are available only when youre working online. This restriction might not be ahuge problem in todays always-connected world; however, there will be times when itsimpossible to be online and you might need a document. You can copy documents fromSharePoint into a mailbox folder for later use offline -- but how likely will you be to rememberto do so before a road trip? SharePoint supports document versioning, which is a useful feature for teams thatcollaborate on complex documents. Outlook doesnt support versioning and can display onlythe latest version of a document. This isnt necessarily a problem unless you need access toan earlier version, in which case you must access documents in the SharePoint site directlyrather than going through Outlook. Site mailboxes dont respect Exchange retention policies; in addition, site mailboxes canthave archive mailboxes in the same way that a shared mailbox can. Microsoft designed theretention policy and tag model to deal with personal mailboxes. The Managed FolderAssistant (MFA), which is the Exchange component that processes mailboxes to applyretention policies, has no knowledge of the SharePoint sites that underpin site mailboxes. Itwould be nice if Microsoft extended the retention model to accommodate site mailboxes inthe future so that all of the information available to users could be managed in a single way.Client Upgrade: A Necessary EvilLike previous versions of Exchange, you need to upgrade client desktops to the latest version ofOutlook to be able to exploit all the features that Exchange 2013 supports. Features such asDLP and site mailboxes simply wont surface in earlier versions. Although Outlook 2013 hassome useful new features that make sense (such as the ability to reply to a message within thereading pane) and enhance the user interface (such as the ability to display expanded contactinformation using data retrieved from multiple social networking sources or the ability to displayweather information for meetings), the upgrade to Outlook 2013 will be a hard sell within manycompanies -- particularly because the new Metro-style UI will provoke worries about usertraining and support similar to those when Office 2007 introduced the Ribbon interface.Older clients can connect to Exchange 2013, but this release marks the end of the road forOutlook 2003. Microsoft did a lot of work to retrofit support for Outlook 2003 into Exchange2010 but hasnt brought that work forward into Exchange 2013. Equipped with the latestpatches, Outlook 2010 and Outlook 2007 work just fine as long as you dont want to use thenew Exchange 2013 features. It remains to be seen whether Microsoft will issue a service packor other update to reveal features such as DLP in Outlook 2010 and Outlook 2007 in the sameway that the company eventually supported Exchange 2010 archive mailboxes for Outlook2007.OWA continues to get better and better. Although some might be enthused by the addition ofinline editing for new messages, which Figure 3 shows, the OWA headline feature for Exchange2013 is the addition of offline access, which OWA switches into if a network connection is
    • unavailable. To some degree, adding offline access is a nod to Gmail, which introduced offlineaccess mode in 2011. Offline storage is standards-based and is managed by the browser youuse. If your browser supports HTML5 IDB, OWA will use it for storage; if not, OWA willuse WebSQL. You need to be running IE 10.0, Chrome 16.0 or later, or Safari 5.1 or later touse offline access because these are the only browsers that currently support the storagemechanism.Figure 3: Exchange 2013 Outlook Web App (Click image for larger view)Even more interesting is the way OWA morphs itself to support three distinct screen formfactors (phone, slate, and traditional PC). The UI is Metro-based and touch/gesture-capableacross the width of the screen; it has an advanced HTML5-based mode that facilitates videodisplay. The two traditional modes (premium and reach) continue to let OWA support the widestpossible range of browsers. Although the OWA support matrix is a tad more complex becauseof the multiple form factors, IE, Chrome, Firefox, and Safari all support the premium interface.Exchange OnlineExchange Online is a major part of the Office 365 value proposition, so its no surprise to learnthat Exchange Online will include the new features enabled by Exchange 2013 soon aftergeneral availability. Microsoft hasnt set a firm date for the update yet but will advise tenantadministrators when to expect upgrades to commence. The company will allow tenantadministrators to select the most appropriate upgrade time within a window spanning a coupleof months. Tenants can even opt to run a pilot deployment for a select group of users before fulldeployment begins. This feature is based on scheduling batches of mailbox moves. Exchange2013 marks the first time that Office 365 has been through a major application functionalityupgrade -- so its good that Microsoft has considered how to minimize disruption for customersduring the transition.The Big Upgrade QuestionExchange 2013 includes numerous improvements that I havent discussed here. For example,the Exchange content-indexing subsystem is replaced by a FAST-based search engine thatextends over Exchange 2013, SharePoint 2013, and Lync 2013 to provide a single enterprise-class search capability across multiple data sources. This upgrade would certainly merit muchdiscussion in another release -- but such are the changes in Exchange 2013 that thisimprovement is merely mentioned in passing.As always, when Microsoft releases a brand-new version of a popular server application, wemust ask whether theres a compelling reason to upgrade. In this case, the answer forcompanies running Exchange 2010 is probably No -- unless they have a pressing need to useone of Exchange 2013s new features and the necessary financial and technical resources to
    • deploy new hardware and new software (Exchange and SharePoint), upgrade clients, train andsupport users, and so on. But if youre running Exchange 2003, its definitely time to move tonew technology, and it makes sense to consider an early upgrade to Exchange 2013. The sameargument can be made for Exchange 2007 deployments. Although these servers did a good jobin their time, that time is quickly running out.Of course, companies faced with the complexity and cost of migrating to Exchange 2013 mightsimply conclude that now is a good time to move some or all of their user population to Office365. Moving to Office 365 isnt free of charge; costs will be incurred to plan, prepare, andexecute all the steps necessary to set up a new tenant domain, establish interoperability withon-premises Exchange, establish single sign-on (SSO) using Active Directory FederationServices (AD FS), move mailboxes to the cloud, and figure out details such as the effect onother applications. But the whole point of going through this pain is that after you migrate toOffice 365, Microsoft will take care of the heavy lifting of server and software maintenance fromthat point on and youll be able to take advantage of new features and functionality soon afterrelease without having to go through a traditional migration. The steadily improving reliabilityrecord of Office 365, combined with the release of Office 2013 apps, will create a real decisionpoint for companies as they chart their long-term future for email services.Old Habits Die HardIf you can cope with the migration and can make use of the new features, Exchange 2013 willbe worth the effort. The implementation seems solid, and Microsoft has tested the heck out ofthis release to prepare for its introduction in the Office 365 cloud service. Still, I think mostExchange admins will opt to wait for SP1. After all, in the past three major versions, Microsofthas substantially improved the initial Exchange release with the first service pack. Why spoilwhat has become such a long-standing habit?