Major changes with Exchange Server 2013 – Part 2


This is the documentation for the Online discussion we conducted on Major changes with Exchange Server 2013.
Recording of this session is available on
https://www.youtube.com/playlist?list=PLQupF2rE3mCdLvO6AMEBmF0nKg1LWVNxy

Here we discussed about.

PART 2 of 2
Changes in Clients and Mobiles
Changes in Sharing and collaboration
Changes in Unified Messaging
Changes in Batch mailbox moves
Changes to High availability and site resilience
What is Exchange workload management?
Exchange 2013 Setup
Finally, What’s Removed in Exchange 2013?

Changes in Clients and Mobiles

ActiveSync
  1. There is no new EAS version or hidden ActiveSync features in the Exchange 2013.
  2. Only difference I can find is New-ActiveSyncMailboxPolicy is replaced by New-MobileMailboxPolicy.
Outlook
  1. No more MAPI
  2. No offline access to Archive Mailbox
  3. Outlook 2013 can control the size of the OST file
  4. Outlook 2013 not longer connects to Server using FQDN
  5. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the user’s primary SMTP address.
Optimized for touch devices.

  1. Apps in Outlook Web App.
  2. Apps for Outlook aren’t dependent on the version of Exchange Server that you’re using.
  3. Administrators can also allow users to download apps from Office.com.
  4. Third-party developers can create additional apps for Outlook and offer them at Office.com.
  5. Contacts a.k.a People
  6. Users can link multiple entries for the same person and view the information in a single contact card.
  7. Calendar - Users can now view multiple calendars in a merged view.
  8. Calendar - The month view now includes an agenda for the selected day.
  9. Calendar - In all calendar views, users can click an item to view a pop-up of the item's details.
  10. Calendar - The month view now includes an agenda for the selected day.
  11. Calendar - In all calendar views, users can click an item to view a pop-up of the item's details.
  12. Outlook Web App Offline
  13. Does not include Archive Mailbox Still. Its still Online Archive Mailbox.

Changes in Sharing and collaboration

Site mailboxes

Site mailboxes require Exchange 2013 and SharePoint Server 2013 integration and configuration.



Managed availability

In this monitoring and recovery-oriented features are tightly integrated to help prevent failures

  1. Proactively restore services
  2. Initiate server failovers automatically
  3. Alert administrators to take action.
What is New?
  1. The Managed Store is the name of the newly rewritten Information Store processes in Exchange 2013.
  2. Support for multiple databases per disk
  3. Automatic reseed
  4. Automatic recovery from storage failures
  5. Lagged copy enhancements
  6. Lagged copies can invoke auto replay feature when a low disk space threshold has been reached
  7. Single copy alert enhancements
  8. Is no longer a separate scheduled script, now a part of Managed availability
  9. DAG network auto-configuration

What is Exchange workload management?

  1. Monitor the health of system resources
  2. Control how resources are consumed by individual users
 
  • First we need to create workload management policy
  • New-WorkloadManagementPolicy
  • Then create a new workload policy and assign it to the above new workload management policy
  • New-WorkloadPolicy
  • Apply the custom workload management policy to a specific server
  • Set-ExchangeServer -WorkloadManagementPolicy Workload_Management_Policy_Name -Server ServerName
 
  • Change workload management policy settings for all servers in your organization
  • create a new workload policy and assign it to GlobalOverwrittenWorkloadManagementPolicy

Exchange 2013 Setup

Active Directory preparation
Install the following software on the computer that will be used to prepare Active Directory:
  1. Microsoft .NET Framework 4.5
  2. Windows Management Framework 3.0
  3. Remote Tools Administration Pack
Prerequisites required on the server.
Mailbox server role or combined Mailbox and Client Access server roles
  • Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, 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-Foundation

Client Access server role
  • 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-Foundation
Active Directory preparation
Prepare Active Directory and Domains
Prepare Active Directory Schema
  • setup /PrepareSchema or setup /ps
  • Sets the schema version (ms-Exch-Schema-Verision-Pt) to 15137
Prepare Active Directory
  • setup /PrepareAD [/OrganizationName:<organization name>] or setup /p [/on:<organization name>]
  • Sets the objectVersion to 15449.
  • CN=<your organization>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain>
Prepare Active Directory Domain
  • setup /PrepareDomain or setup /pd
Verify Active Directory preparation
  • In the Configuration naming context, verify that the msExchProductId property in the CN=<your organization>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain> container is set to 15.00.516.032.
  • In the Schema naming context, verify that the rangeUpper property on ms-Exch-Schema-Verision-Pt is set to 15137.
  • In the Configuration naming context, verify that the objectVersion property in the CN=<your organization>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain> container is set to 15449.
  • In the Default naming context, verify that the objectVersion property in the Microsoft Exchange System Objects container under DC=<root domain is set to 13236.
What's Discontinued in Exchange 2013
Architecture
  • No more Hub Transport server Role
  • No more Unified Messaging server Role
Management interfaces
  • No more Exchange Management Console
  • No more Exchange Control Panel
Client access
  • Outlook 2003 is no longer supported
  • RPC/TCP access for Outlook clients
Outlook Web App (Removed)
  • Access to shared email folders
  • Distribution list moderation
  • S/MIME
  • Inability to apply messaging policies
  • Antivirus software is unable to scan encrypted message content
  • Impact to custom transport agents
  • Taken care by Information Rights Management
  • Spell check
  • Reading pane at the bottom of the page
  • Cannot reply to emails that are sent as attachments
Mail flow (Removed)
  • Linked connectors
  • Anti-spam and anti-malware
  • Anti-spam agent management only availble in Exchange Management Shell
  • No more Connection Filtering agent
  • The Connection Filtering agent provides IP Allow List and IP Block List capabilities.
  • Messaging policy and compliance
  • Retention policies replace Managed Folders

Tools (Removed)
  • Exchange Best Practice Analyzer
  • Mail flow troubleshooter
  • Performance monitor
  • Performance troubleshooter
  • Routing Log Viewer

Please find the slides as attached.
Thanks you all for spending your valuable time.

[Video]

Microsoft Exchange Server 2013 - PART 2.pdf

Comments (1)

  1. Charles Derber says:

    Book-marked Hero 🙂

Skip to main content