But if it can be done without using it I often recommend not to do it. Connect to the domain controller, launch the run dialog (Windows Key + R) - Type in the command adsiedit.msc and then press OK - Right click on the console then Connect to:- In the connection dialog select Well known Naming Context - In the drop down.
#Remove exchange public folder adsiedit how to
It wouldn’t be the first time ADSI Edit saves an Exchange Consultants proverbial bacon. How to remove a dead Exchange server from Active Directory. The described solution/work around in these blogs get the job done perfectly, using ADSI Edit to delete the offending Exchange 2007 public folder database. I got a couple of warnings (source MSExchange ADAccess, Event ID 2937) after removing a Exchange 2007 server at the end of a Exchange 2007 > 2013 migration. This error has been described in some blogs as early as October 2009 on and later on as recently as October 2010 on
Trying to remove the public folder database manually using the Exchange 2007 GUI confirms this, you’ll get the same error. But the public folder is not visible in the Exchange 2010 GUI (EMC) as it lives on an Exchange 2007 server. The issue is that due to the coexistence of Exchange 2007 & Exchange 2010 we can no longer remove the public folder database with the Exchange 2007 GUI (EMC). As you can tell the public folder information is stored on the EX2 public folder database. There is a Routing Group between the two administative groups called test. We will EX1 to re-import the public folder data. We will be using EX as our test server to remove the public folder data. During the removal of the last Exchange 2007 SP3 Mailbox server after completing the transition of Exchange 2007 to Exchange 2010 SP1 we ran into the following well known error: Object is read only because it was created by a future version of Exchange: 0.10 (14.0.100.0). EX2 holds the public folder content for all users.