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.
What is ExFolders?
ExFolders is a Microsoft tool that can connect to Exchange 2010 public folders through a GUI and is separate from the Exchange Management Console. This tool has replaced the old PFDavAdmin public folder administration tool that was used with older versions of Exchange. Microsoft has added some backward compatibility within ExFolders and has configured it to work with Exchange 2007, but it must be run from an Exchange 2010 server. This powerful tool can recover deleted public folder items, propagate public folder permissions, manage your public folder replicas, modify public folder size limits, and more. I like to think of using this utility as a way to get “under the hood” to gain additional insight into the configuration of your public folders.
Getting Started with ExFolders
Now that we know what ExFolders can do, you might ask "how do I get started?" Before you begin, if you are running Exchange 2010 SP1 or later you will need to download the latest ExFolders from http://gallery.technet.microsoft.com/office/Exchange-2010-SP1-ExFolders-e6bfd405. This will need to be installed on an Exchange server, preferably the server with your primary public folder database. Download and extract this to "C:\Program Files\Microsoft\Exchange Server\V14\Bin”. If an older version of ExFolders exists in this directory it is ok to overwrite.
Many customers nowadays are running a virtualized Exchange environment, utilizing Database Availability Groups, load balanced Client Access Servers and the works. However, I also see environments where it is up to the Hypervisor of choice on the hosting of virtual machines after a (planned) fail-over. This goes for Exchange servers, but also for redundant infrastructure components like Domain Controllers or Lync Front-End servers for example.
So, leaving it to “default” is not a good idea when you want to achieve the maximum availability potential. Think about what will happen if redundant roles are located on the same host and that host goes down. What you want to do is prevent hosts from becoming the single point of failure, something which can be accomplished by using a feature called anti-affinity. This will distribute virtual machines over as much hosts as possible. Where affinity means to have an preference for, like in Processor Affinity for processes, Anti-Affinity can be regarded as repulsion in magnetism.
As an Exchange administrator I am sure you have received a request from senior management asking to delete an email sent to wrong distribution list or user. Most of you would say, “It’s Crazy!!!” Mistakes tend to happen. I personally have seen very important emails being sent to a wrong DL. Senders may try to recall the message but the success ratio is very small, if not impossible, if the message has already been read. The Exchange administrator’s job is then to delete the email. There can also be situations where spam emails are sent to the DL or there is a requirement to delete emails between specific dates. These are just a few of the various possible scenarios.
How would you go about removing the message from the various users mailbox? Well the answer to that question depends up on the version of Exchange. In this article, while I briefly skim the procedures for Exchange 2000-2007, I focus on Exchange 2010 SP1/ SP2.
In Exchange 2000 and 2003, this can be achieved by using Exmerge. This was a bit complex and a tedious process.
In Part 1 of the Exchange 2010 Migration Guide, we discussed new features, discontinued features, Exchange Server Role Concepts, and Exchange Server 2010 Editions. Part 2 of the guide will provide basic knowledge about the installation of Exchange Server 2010 with co-existence of Exchange 2003, how to move mailboxes, public folders, OAB, creation of a connector in Exchange Server 2010 and how to decommission the Exchange 2003 server from one organization.
This is purely lab environment testing designed to give a basic idea of how to do a transition from Exchange 2003 to Exchange 2010.
My Current Setup:
I have 2 domains: (1) Happy Domain (2) Smile Domain
In Happy Domain I have 2 computers
Computer-1: E2K3 (computer name) : this is DC\GC, DNS and plus it is having Exchange 2003 Server installed with mailboxes, DL & Public Folders.
IP address: 220.127.116.11
Computer-2: Edge (computer name) : This computer is kept in the dmz network which is possessing two nic card, one for happy domain and another for smile domain.
1st nic card : 18.104.22.168 & 2nd nic card : 192.168.0.1