However, the remote desktop gateway is likely to still be broken. This should resolve the Kerberos errors in the event logs. Save and close the file then run iisreset in an elevated command prompt. Use the find feature to find the line containing Kerbauth and remove the entire line. Open notepad as administrator and use File > Open to open the nfig file in the following directory. The data is the error.Īfter some searching I found an article by Wayne Small at sbsfaq which was very helpful. However, I have found that if Remote Web Workplace was used for remote access to a terminal server or PC’s this functionality is now likely to be broken.Įxamining the event logs will likely show errors as follows: The Module DLL C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll failed to load. This is where most guides I have found stop, and in some cases this is fine. In one case I needed to kill a process that was locking some of the files and then re-run the setup in uninstall mode.Īt this stage I would highly recommend a reboot. If all went well, this will run through some checks and then proceed to uninstall Exchange. In an elevated command prompt, browse to the Exchange BIN folder and run the setup in uninstall mode: cd “C:\Program Files\Microsoft\Exchange Server\v14\Bin” Having done this I was able to uninstall Exchange as follows: In one case I also had to browse through the Exchange Administrative Group and remove another reference to a previous Public Folder Database that had not been correctly removed. Under this location I deleted the object for the public folder database. IN ADSIedit I browsed to the following location: CN = Configuration > CN =Services > CN =Microsoft Exchange > CN =First Organization > CN =Administrative Groups > CN =Exchange Administrative Group (FYDIBOHF23SPDLT ) > CN =Servers > CN =SERVER > CN =Information Store > CN =Second Storage Group > CN =Public Folder Database Using ADSIedit can be very dangerous, so for the second time, proceed at your own risk. The post by Todd Nelson was very helpful in this regard as ADSIedit was needed to remove the public folder database. Before deleting the public folder database, remove the folders or move the replicas to another public folder database. However, in all cases I have dealt with, the commands to remove the public folder database failed with the following or similar: The public folder database "SERVER\Second Storage Group\Public Folder Database" contains folder replicas. Resolving public folder database removal failure # Remove arbitration mailboxes (SBS 2011/Exchange 2010 Only)Īt this stage Exchange should be fairly bare. Get-Mailbox -Arbitration | Disable-Mailbox -Arbitration -DisableLastArbitrationMailboxAllowed Get-PublicFolderDatabase | Remove-PublicFolderDatabase # Remove the Public Folder database (May fail, see below) Get-OfflineAddressBook | Remove-OfflineAddressBook Get-PublicFolder "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Recurse -ErrorAction:Silentl圜ontinue Get-PublicFolder "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Recurse -ErrorAction:Silentl圜ontinue To go through the initial steps of the Exchange decommissioning, the blog post by ITProMentor was very helpful.Īfter running Exchange Management Shell as Administrator the following commands can be entered, answering prompts with “A” for ALL.
#How to export mailbox exchange windows 2011 sbs full#
(As stated the following is not supported or recommended so proceed at your own risk! I HIGHLY recommend taking a full restorable backup before continuing) Initial Decommissioning That said, the following is what I have found was required to decommission Exchange with minimal breakage. It is generally considered best practice to simply disable all the Exchange services until the SBS is fully decommissioned and I would highly recommend this if at all possible. Additionally disk space was running low and Exchange was an easy-ish target for reclaiming space and allowing the SBS to continue running for a few more months before decommissioning. However, in several cases I have dealt with, the client’s mail has been migrated to a Hosted Exchange platform or to Office 365 and Exchange was no longer required. This is generally not recommended as it can easily break some of the functionality of the SBS. I have recently needed to decommission Exchange on several 2011 Small Business Servers.