Introduction 1. 1 There have always been episodes of migration to Britain but, as this paper demonstrates, those episodes were small and demographically. Nonprofit organization that uses ultra light aircraft to return migrating Whooping cranes to eastern North America. Contains facts and information on crane migration. Migration is one of the most amazing feats performed by osprey with distances of 5,000 km or more from breeding to wintering territories. Tracking osprey is nothing. Monarch Watch is a cooperative network of students, teachers, volunteers and researchers dedicated to the study of the Monarch butterfly, Danaus plexippus and its. Migration Watch UK is an independent and nonpolitical body established in October 2001. Our purposes are to monitor migration flows to and from the UK, provide to. Five Exchange 2. 01. Exchange Server 2. Exchange features. By submitting your personal information, you agree that Tech. Watch Migration ' title='Watch Migration ' />Target and its partners may contact you regarding relevant content, products and special offers. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy. Before upgrading to the latest version, its important that youre aware of a few factors that will help ensure a successful migration. Avoiding the five Exchange 2013 migration gotchas detailed here is a good first step toward ensuring a successful deployment. Exchange 2. 01. 3 migration gotcha 1 Clients. Just as Exchange 2. Outlook 2. 00. 0, Exchange 2. Outlook 2. 00. 3. When it comes to Exchange 2. Outlook 2. 00. 7, Outlook 2. Outlook 2. 01. 3. Outlook 2. 00. 7 must run Service Pack 3 along with the November 2. Outlook 2. 01. 0 must run Service Pack 1 along with the November 2. When patching clients, consider Windows Server Update Services. You can also use the Microsoft Assessment and Planning toolkit, as well as the Get Logon. Statistics cmdlet in Exchange 2. Exchange Server User Monitor Ex. Mon in Exchange 2. And its not just Outlook you need to worry about. With Exchange 2. 00. Outlook Web Access in all its glory with a version of Internet Explorer as low as IE6. In Exchange 2. 01. Premium Outlook Web App is IE7. Therefore, it shouldnt surprise anyone that IE8 is necessary for Exchange 2. At the time of writing, however, IE8 suffers from performance issues when running Outlook Web App 2. IE9 the baseline. It will give users the best OWA 2. Vista and above. For Windows XP and other operating systems, third party browsers like Firefox v. Chrome v. 24 and Safari v. Mac also provide great support for Exchange 2. Check out the table of supported clients on Microsofts Tech. Net site for the most up to date information. Exchange 2. 01. 3 migration gotcha 2 Outlook Web App redirection. This one affects companies migrating from Exchange 2. FBA within Exchange. Previously, when a company migrated from Exchange 2. Exchange 2. 00. 7 to Exchange 2. FBA worked very well. When a user logged into OWA, he was redirected to the legacy server, and the username and password were passed along with the redirection request. In a coexistence scenario with Exchange 2. Exchange 2. 01. 3 using FBA the username and password are not passed when an Exchange 2. The user is redirected to an Exchange 2. If youre expecting a lengthy coexistence period, look into how youll work around this issue. If you already use Forefront TMG 2. Alternately, various third party load balancers provide built in pre authentication support. All this said, if youve already implemented Windows Integrated Authentication for Outlook Web App logins, you wont be affected. Exchange 2. 01. 3 migration gotcha 3 Outlook Anywhere. All communication for Outlook clients with Exchange 2. HTTPS rather than the combination of RPCMAPI and HTTPS used in previous versions. Specifically, this means that Outlook Anywhere  is used for internal clients as well as external clients. Mailboxes that still reside on Exchange 2. Exchange 2. 01. 0 during the coexistence period will continue to connect internally via traditional RPCMAPI. If your organization uses Outlook Anywhere externally, ensure that Outlook Anywhere is also enabled on Exchange 2. Exchange 2. 01. 0. This is because Exchange 2. Outlook Anywhere requests to the version of Outlook Anywhere that corresponds to the version of Exchange Server the mailbox is on. Its not quite as simple as just enabling Outlook Anywhere or leaving it enabled. You must make sure that NTLM authentication at the IIS level is enabled for both Exchange 2. Exchange 2. 01. 0. One more thing when it comes to Outlook Anywhere If the Exchange 2. Outlook Anywhere are also running the client access server and mailbox server roles and not a Global Catalog server you must disable IPv. Exchange 2. 01. 3 migration gotcha 4 Sizing and performance. Performance and sizing can certainly prove a contentious aspect of any Exchange 2. Deployment guidance was released in May 2. Microsofts assistance neednt re evaluate their specifications. Others have been incorrectly looking at existing Exchange 2. RAM and CPU. If youve done this, dont panic, but realize you may need to buy additional hardware. Exchange 2. 01. 3 sizing is fundamentally different and its not as easy as giving it a bit more power. Instead, you need to re think the best way to deploy Exchange 2. JBOD just a bunch of disks is a great option for many customers, thanks to the auto reseed features, which allow for massive disk savings. The Exchange Product Group also advocates the use of building blocks, which are servers that only have local storage. For example, you may have 1. TB disks as your Exchange Server base. Consider using these, rather than expensive add on arrays. You might end up with a smaller user count per server, but youll use fewer disks and benefit from improved reliability. As with any Exchange Server 2. Jet. Stress to ensure that the storage subsystem is capable of handling the expected load. Jet. Stress has been updated for Exchange 2. If youre new to Jet. Stress or looking to follow Microsoft best practices, be warned that the updated version of the Jet. Stress Field Guide has not yet been released. Additionally, Load. Gen, the complementary tool that helps test a real world simulation of activity has not been released either. Therefore, if these tools are essential to your deployment, you may have to hold tight at least for the time being. Exchange 2. 01. 3 migration gotcha 5 Ambiguous namespaces and Exchange 2. What exactly are namespaces Well, in the context of Exchange Server, they are the names used to connect to Exchange both internally and externally using HTTPS, as well as connect to Outlook clients internally using RPCMAPI. During the coexistence period of any Exchange 2. Exchange 2. 01. 3 migration, youll need to update the DNS entries for your Internal. URLs and External. URLs to point at your Exchange 2. Clients with Exchange 2. HTTPS services proxied to the Exchange 2. An Exchange implementation that follows Microsofts recommendations will use a single set of names for both internal and external HTTPS URLs for example, mail. RPC client access array for example, outlook. When the HTTPS name is moved to Exchange 2. RPC client access array name remains on Exchange 2. Theres a gotcha here for organizations that have implemented namespaces incorrectly. Some Exchange 2. 01. HTTPS namespace again, call it mail. URLs and RPC client access array for example, using outlook. RPCMAPI and services like OWA. When you move the internal name to Exchange 2. Outlook client connectivity. The trick here is to update your internal HTTPS URLs to use the external HTTPs URLs. You may want to consider potentially implementing split DNS or pinpoint DNS in the process. Free Download Of Rock Dog there. A small number of organizations have implemented a single name, both for internal and external HTTPS URLs and the RPC client access array. If this describes your setup, you likely need to change your RPC client access array name to something unique. Unfortunately, this does not automatically propagate to clients and you may need to either force Outlook clients to update, or do as Microsoft suggests and move internal Outlook clients on Exchange 2. Outlook Anywhere. Final thoughts. Some of these gotchas might sound like serious problems, but dont let them deter you. Armed with the right information, you can easily complete a successful Exchange 2. About the author Steve Goodman is an Exchange MVP and works as a technical architect for one of the UKs leading Microsoft Gold partners, Phoenix IT Group. Goodman has worked in the IT industry for 1. Microsoft Exchange since version 5.