![remove exchange public folder adsiedit remove exchange public folder adsiedit](https://www.alitajran.com/wp-content/uploads/2020/05/Remove-Exchange-Server-from-Active-Directory-ADSI-Edit-remove-Exchange.png)
![remove exchange public folder adsiedit remove exchange public folder adsiedit](https://www.petenetlive.com/KB/Media/0000227/00002.jpg)
But if it can be done without using it I often recommend not to do it.
![remove exchange public folder adsiedit remove exchange public folder adsiedit](https://i0.wp.com/www.itxperience.net/wp-content/uploads/2015/01/msexchange_logo.jpg)
It wouldn’t be the first time ADSI Edit saves an Exchange Consultants proverbial bacon. 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. 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. 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#
But the public folder is not visible in the Exchange 2010 GUI (EMC) as it lives on an Exchange 2007 server. How to remove a dead Exchange server from Active Directory. But be careful, it will ruin your public folder stores if you have not successfully and verifiably replicated the public folders to your new server. Since it contained no vaild public folders, I didn’t care if any data was lost. 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). All set I successfully uninstalled Exchange 2007 from this server as soon as that was done. 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).