Planning and migrating a small organization from Exchange 2. Part 8)If you would like to read the other parts in this article series please go to: Introduction. In the previous parts to this series we began our journey to migrate from Exchange 2. Exchange 2. 01. 3, and completed the sizing of our new environment, finishing with getting the hardware ready to roll. We’ll now focus on getting ready to deploy Exchange by first ensuring issues within the current environment are corrected, and then install Exchange 2. Pre- Deployment Remediation. While a bit of a mouthful, pre- deployment remediation could be explained better as “things we need to sort out before we install Exchange”. We’ll explain some of these below. Exchange Server Patching. · Dual Delivery Email routing between MS Office 365 Enterprise Exchange Online and Google Business Apps. If you would like to read the other parts in this article series please go to: Planning and migrating a small organization from Exchange 2007 to 2013 (Part 1). As we’ve mentioned before, you must patch Exchange 2. Service Pack and Update Rollup before you attempt to do anything with Exchange 2. Download and install these patches from here: As with all patches, ensure you read the release notes before implementation. Configuring the Offline Address Book setting on existing Mailbox Databases. If you’ve got any Mailbox Databases that look like the example shown below, you’ll need to make sure they’ve got the current default Offline Address Book for your organization hard configured against each database. This is because Exchange 2. Offline Address Book, forcing clients that don’t have this value configured to perform a full Offline Address Book download before we’re actually ready to introduce Exchange 2. Figure 1: Public Folder Database with no Offline Address Book specified. You can correct this against the individual database by selecting the default Offline Address Book by choosing Browse in the Client Settings tab in the window shown above. As you might expect, the Exchange Management Shell is also a great tool to use to quickly correct this across all databases. You can use the following command to perform this change: Get- Mailbox.
Database | Where {$_. Offline. Address. Book - eq $null} | Set- Mailbox. ![]() ![]() Database - Offline. Address. Book (Get- Offline. Address. Book | Where {$_. Is. Default - eq $True})You’ll see this command in action below: Figure 2: Automating configuring the Default Offline Address Book. Active Directory Forest and Domain Level Changes. If you haven’t already, you’ll need to raise the forest and domain functional levels of your Active Directory to a minimum of Windows 2. Exchange 2. 00. 7’s minimum forest and domain functional levels are just Windows 2. Before you do so, make sure you ensure your Active Directory is in good health (for example by using dcdiag), backed up and any Windows 2. Domain Controllers are gone and were correctly removed. We can raise the Domain Functional Level by opening Active Directory Users and Computers and right clicking the domain, and choosing Raise Domain Functional Level: Figure 3: Raising the Domain Functional Level. You’ll find the option to Raise Forest Functional Level over in Active Directory Domains and Trusts. The option is found by right- clicking the root node, as shown below: Figure 4: Raising the Forest Functional Level. Updating Outlook 2. Clients. In part three and part four of this series we looked at the methods available to identify existing clients, and if you haven’t updated clients now is the time to do so. Auto. Discover responses from Exchange 2. Outlook Anywhere, and these updates ensure support for this in addition to other fixes. To recap, the update levels we’ll need to achieve are as follows: Outlook 2. Service Pack 1 with at least the November 2. Build 1. 4. 0. 6. Outlook 2. 00. 7 Service Pack 3 with at least the November 2. Build 1. 2. 0. 6. Naturally if you can update clients to Outlook 2. Apps for OWA and Outlook 2. Windows Server Update Services (as mentioned in part four of this series) to ensure clients meet minimum update levels or higher. With the recent release of Outlook 2. Service Pack 2, there’s even more reason to get clients updated. Removing unsupported clients. If your client discovery identified any clients that aren’t supported with Exchange 2. Remember – Outlook 2. Outlook before we start the upgrade. Configuring Outlook Anywhere. If you’ve not enabled Outlook Anywhere already, you certainly will want to consider enabling it for Exchange 2. If you’ve already enabled Outlook Anywhere and used Basic authentication then you’ll also need to make another change on Exchange 2. Client Access Servers, within the IIS configuration. Exchange 2. 01. 3 can accept Outlook Anywhere connections for Exchange 2. Outlook Anywhere running on the Exchange 2. Client Access Servers. If Basic Authentication is in use, it will also need Windows Authentication enabled to allow Exchange 2. We can accomplish this by opening IIS Manager and navigating to Sites> Default Website> rpc and then choosing Authentication. Right Click Windows Authentication and choose Enable: Figure 5: Enabling Windows Authentication for Outlook Anywhere on Exchange 2. Third Party Software. As well as upgrading Microsoft software to support Exchange 2. In our example organization, we know we’ve got to upgrade our BES Server, so we’ll ensure the pre- requisites are fulfilled in advance. The key to ensuring that you receive support from the third party vendor during your upgrade is to ensure that if a change needs to be made before you implement Exchange 2. Installing Exchange 2. Pre- requisites. We’re finally ready to begin the installation of pre- requisites for Exchange Server 2. However that preparation should be worthwhile as we’ll now expect the installation to progress pretty smoothly. We’ll be installing Exchange onto Windows Server 2. If you’re given the choice between Server 2. R2 SP1 the former does ensure that less pre- requisites are required, and even Standard Edition supports Clustering (and thus the ability to smoothly upgrade to a Database Availability Group at a later date). In the previous part of this series we defined the specifications for our server, E1. M0. 1 and created the supporting virtual machine. After installing Windows Server 2. Windows updates, we’ll open a Power. Shell window as an Administrator and use the following command to install the Operating System pre- requisites: Install- Windows. Feature AS- HTTP- Activation, Desktop- Experience, NET- Framework- 4. Features, RPC- over- HTTP- proxy, RSAT- Clustering, RSAT- Clustering- Cmd. Interface, RSAT- Clustering- Mgmt, RSAT- Clustering- Power. Shell, Web- Mgmt- Console, 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- WMI, Windows- Identity- Foundation, RSAT- ADDS, RSAT- ADDS- Tools. Figure 6: Installing OS Pre requisites. On Windows Server 2. Microsoft Unified Communications Managed API 4. Runtime, available for download from the Microsoft Download website. Install this using the defaults: Figure 7: Installing Unified Messaging Pre requisites. After installation of the above, our server has the required pre- requisites needed before we can install Exchange, and as we’ll see next, prepare Active Directory for Exchange 2. Exchange 2. 01. 3 Active Directory Preparation. Before installing Exchange itself, we’ll also need to prepare Active Directory. Strictly speaking this will be performed automatically if we simply run the Exchange setup; however downloading and unpacking the Exchange setup files ensures we’ve got pre- requisites available for Jet. Stress testing; and because the Exchange 2. Schema update is an irreversible change that may cause large amounts of Active Directory replication, we’ll perform the Active Directory prep separately. First we need the Exchange 2. The latest Exchange 2. Cumulative Update is always the installation source you should use for installation. This is firstly because the update is actually a slipstreamed installer which includes all files required for initial installation; and secondly because installing the RTM version of Exchange 2. Exchange 2. 00. 7 environment is not supported. The Cumulative Update is the same download for all customers – whether it’s a trial, Tech. Net or MSDN subscription, retail licence or volume licence code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |