When it gets to certain percentage it fails with an error exactly like this: So I omitted the Client access and just typed /r:mailbox. Hi Paul, since is an Exchange 2013, I tried reinstalling typing setup.exe /m:install /r:clientaccess,Mailbox /IacceptExchangeServerLicenseTerms but it complained that the Client Access Role was already present. Recovery installs are available for all of the current versions of Exchange, and there’s really no excuse for not doing one if the scenario calls for it.Įxchange Server Exchange Server, Registry, Setup, Uninstall, Watermark
If you did have a server that was beyond repair and wanted to cleanly remove it from your environment in a supported manner, the correct approach is to use a recovery install. Sure, there’s lots of war stories out there where people have gotten away with it and everything has continued to work okay in their environment (as far as they can tell), but I would never recommend it and certainly don’t do it for customers. As you hopefully already know, removing an Exchange server (or really, doing anything at all) in ADSIEdit is an unsupported method.
Now, during all this I was asked whether we could just power off the server and remove it using ADSIEdit. I was then able to run setup again to uninstall the server, which was successful. This time setup was able to complete the installation, which repaired the server.
HOW TO REMOVE OFFICE 365 SHARED WATERMARK INSTALL
Setup is failing on the Front End Transport service in my case (see above), which is the “FrontEndTransportRole” in the registry.Īfter removing the Action and Watermark entries, I tried the Exchange install again. There’s a tip about it here on the Exchange Masters blog. Thinking back to other Exchange setup-related disasters I’ve encountered, I remembered that Exchange stores some information about setup progress in the registry.
0 kommentar(er)
