This post is about a recent migration of legacy public folders hosted on Exchange Server 2007 to modern public folders hosted on Exchange Server 2013.
Microsoft is constantly updating and improving services; it’s a hallmark of Office 365. The constant Office 365 updates are great for me, providing new content and tips to share with you on a regular basis.
It's Friday! Start your Halloween weekend off right with some of the top Exchange and Office 365 headlines from the week:
Here's your weekly dose of popular Exchange and Office 365 insights:
A healthy Exchange Hybrid environment is vital for any organization looking for a stable and rapid migration and essential for those organizations expecting to stay in Hybrid mode for more than a very short period.
When designing for a migration to Exchange Server 2013, chances are you’ll have to deal with public folders. Given that Exchange 2013 has been around for a while, you might think such a task would be a proverbial walk in the park. Of course, if you are looking at a cookie-cutter environment, you might be right. However, in every design there are elements specific to the customer that require a different approach.
More specifically, consider the scenario in which you have public folders — possibly lots of them. For the sake of this article, let’s assume you have about 500GB worth in public folders spread over several thousand public folders across one or more replicas. For some customers, these numbers are much more than they have. For other customers, 500GB in public folders might just be a fraction of what they have to deal with. Regardless of your situation, public folders raise a rather interesting question: How do you plan for (a migration of) public folders to Exchange 2013?
The Exchange 2013 Server Role Requirement Calculator is a one stop calculation tool for Exchange 2013 design. The tool covers design calculations for both the Mailbox and Client Access server role. Exchange 2013 reduced the number of roles from previous versions of Exchange by making the design and implementation as simple as possible. The Server Role Requirement Calculator helps us to size both physically and virtually and it provides in-depth sizing of every component of the hardware like CPU, Memory, Network, Storage, Backup, servers, datacenter etc.
Exchange 2013 Server Role Requirement is an excel spread sheet with an option to input your requirement. Before doing this, we need to understand the below criteria and input.
User profile: The number of User mailbox, mailbox size and the message profile. You can refer the following articles in order to get the profile details for both exchange 2007 and 2010
In the event you are planning a migration from Windows Server 2003 to Windows Server 2008 R2, the below steps are crucial. The article specifically highlights the steps needed to take for subordinate CA migration from Windows Server 2003 to Windows Server 2008 R2.
This article is published in three parts and in this part we will discuss more in details on about preparing of source and destination server for the migration.
1. Preparing the Source Server
Map network share in source server to copy backup files
Perform/Verify System state backup of Source CA
Open Command promptType certutil.exe – catemplates > catemplates.txt
Verify the contents of catemplates.txt with the templates displayed in Certificate Authority snap-in
After some recent Exchange troubleshooting I decided to do a small write-up on an attribute most people working with Exchange know about, the infamous exchangeLegacyDN.
In the early days of Exchange, the NT world was flat. Exchange utilized its own hierarchical X.400 directory service and to uniquely identify objects it used an attribute called obj-Dist-Name. It contained a constructed value using elements like organization, containers and the canonical name to construct the entry, e.g. /o=Contoso/ou=EMEA/cn=Recipients/cn=User.
For those involved with Exchange migration projects or managing Exchange environments, at some point you probably have experienced a situation where individuals ended up with duplicate items in their mailbox. Duplicate items can be caused by many things, but most common are:
- Synchronization tools or plug-in. Entries from the mailbox are treated as new entries and as a consequence are added to the mailbox when synchronizing information back to the mailbox, creating duplicates. In the past, I’ve seen this happening with Nokia PC Suite and Google Apps Sync for example;
- Importing existing data. Accidental import from – for example – a PST file to a mailbox can lead to duplicate entries.
When looking for a solution, you’ll probably encounter MSKB299349, “How to remove duplicate imported items in Outlook”. This article describes a manual procedure to remove duplicates entries from your calendar, contacts, inbox or other folders. Not very helpful and labor intensive.
When continuing your search, you’ll find lots (I mean lots!) of tools and Outlook add-ins, like Vaita’s DIR or MAPILab’s Duplicate Remover. Not all of this software is free (some even require payment per duplicate removal of appointments, contacts or e-mail) and some might not even work (MAPI-based tools may not work against Exchange 2013).