ADSIEdit is a very powerful tool you can access from a domain controller. OK, let’s take a look at ADSIEdit now that you see where I am going. Ask yourself the question, would you like somebody to do a sloppy repair job and hand it over to you to fix and you waste endless hours trying to figure out what was done? Using ADSIEdit Spend the time to complete the job properly. Even though it seems easy to do, doing a quick fix now may create problems later. When you as the IT admin leave the organization, perhaps they hire someone who might be less skilled than you or is still learning. You now have a broken database availability group (DAG), a broken hub transport server, an Exchange server that had mailboxes that you thought were not needed even though you need to keep the data for compliance. While it seems easy to say, “I solved the issue as I removed the server from ADSIEdit or Active Directory,” you did not remove the entire footprint of Exchange in ADSIEdit and from Active Directory. The other challenge is that something goes wrong with an Exchange server and admins find it easier to just remove the server using ADSIEdit. The other Exchange servers then continuously log that they cannot communicate with server X and they are stuck because of an orphaned server. Or people just shut down a server and delete it from Active Directory with a “we don’t need it anymore” kind of attitude. They often get errors that reference a server or servers that were removed by previous admins.
#Remove exchange public folder adsiedit upgrade
Many users and IT staff on the Microsoft TechNet forums run into endless issues when they want to upgrade or remove a server or simply do the normal tasks they need to do. But when they do, they often hit roadblocks on their journey. When recovering an Exchange server, admins typically want to take the fastest route.