Uninstall Exchange 2010 Some Controls Aren T Valid
- Home
- Collaboration
- Microsoft Exchange
Hey SW community,
I have a small issue with our Exchange 2016. Quick backstory:
We recently migrated from Exchange 2010 to Exchange 2016. The migration went fine, we didn't have any errors, all mailboxes were moved correctly and the new server was working great. We turned off the old Exchange 2010 after the migration and everything worked as expected. After 2 weeks we thought we could maybe uninstall our Exchange 2010.
So I did the following:
2. We got the error "Some controls aren't valid. Please specify an existing server role(s) to uninstall." during role selection (Mailbox, Client Access and Hub Transport selected).
3. I've read on Technet that you have to uninstall the Mailbox role after you've uninstalled the Client Access and Hub role.
4. So I've uninstalled it again with just the two roles selected but got the following error "This Mailbox server is responsible for generating an Offline Address Book. Removal of the Mailbox role is not permitted."
5. Outlook couldn't establish a connection to Exchange 2016 from this moment on.
6. I noticed that all Exchange services have been deactivated on the new Exchange 2016 server. Outlook started working again after I restarted all Exchange 2016 services, however OWA and ECP didn't.
7. After searching around for a while, I rolled back to a backup from the night before (both servers, Exchange 10 + 16). Outlook, OWA and ECP worked fine again.
Now we have the following issue. Existing Outlooks work fine, however, if we try to configure a new profile, Outlook will say that it can't find the Exchange server. We can only configure new profiles now if our old Exchange 2010 is turned on. I think that the Exchange 2010 setup changed some values back to the old server in our Active Directory but I don't know too much about Exchange so I didn't want to change anything without asking you guys.
I feel like there might be an "easy" or obvious fix for this issue, maybe someone had this before.
Thanks and hope you have a good day!
Max
Alright guys, everything works again!
After finding the old server when running Test-OutlookWebServices I just ran the following command and 'deleted' the old autodiscover directory. The issue was caused by a Service Connection Point in Active Directory that still had the old URL in it.
Set-ClientAccessServer – Identity ServerName-AutoDiscoverServiceInternalUri $null
More about this: http://jetzemellema.blogspot.com/2015/10/how-to-remove-exchange-autodiscover-scp.html
Max
7 Replies
from a working Outlook that is online, do a test email autoconfiguration. check where autodiscover, OOF, OAB are pointing to.
Heybadbanana,
thanks for the quick reply!
The Auto config test connects to the right URLs for:
- Internal / External OWA URL
- MAPI HTTP Mailstore
- MAPI HTTP Addressbook Internal / External
- EWS
- OOF URL
- OAB URL
- UMS URL
There's only one time where it tries to connect to our old server. If I switch to the Log tab, it'll show:
- "Attempting URL https://exchange2010/Autodiscover/Autodiscover.xml found through SCP"
- "Autodiscover to https://exchange2010/Autodiscover/Autodiscover.xml starting"
- "GetLastError=0; httpStatus=401."
- "Autodiscover to https://exchange2010/Autodiscover/Autodiscover.xml Failed (0x800C8204)"
- "Autodiscover URL redirection to https://exchange2016:443/Autodiscover/email@company.com/Autodiscover.xml"
- "Autodiscover to https://exchange2016:443/Autodiscover/email@company.com/Autodiscover.xml starting"
- "GetLastError=0; httpStatus=401."
- "GetLastError=0; httpStatus=401."
- "GetLastError=0; httpStatus=200."
- "Autodiscover to https://exchange2016:443/Autodiscover/email@company.com/Autodiscover.xml Succeeded (0x00000000)"
It sounds like it wasn't a complete migration.
QJust like AD, Exchange has roles. Check all roles.
Also check all settings one by one because some might have the 2010 server, for example the offline address book.
AutoDiscover is also a pain. I haven't had to work on it, but a co-worker has to fix it for 2 clients recently.
Finally, you want to use ADEdit to check the AD. There should be an TechNet article with the location of the settings.
I'll check Exchange and ADSIEdit. Autodiscover was working great until we attempted to uninstall the old Exchange server. I'll update as soon as I know more!
dehcbad25 wrote:
It sounds like it wasn't a complete migration.
QJust like AD, Exchange has roles. Check all roles.
Also check all settings one by one because some might have the 2010 server, for example the offline address book.
AutoDiscover is also a pain. I haven't had to work on it, but a co-worker has to fix it for 2 clients recently.
Finally, you want to use ADEdit to check the AD. There should be an TechNet article with the location of the settings.
agree with this.
Hey guys,
so I've been searching around for the last hour and I think I found the cause of the issue, I don't know how to fix it yet but I'm working on it.
If I run Test-OutlookWebServices | fl on my Exchange 2016 server, it will show the new Server as 'source' but the old server as 'ServiceEndpoint'. All virtual directories and OABs are configured correctly.
I'll see how I can change that and update after that.
Alright guys, everything works again!
After finding the old server when running Test-OutlookWebServices I just ran the following command and 'deleted' the old autodiscover directory. The issue was caused by a Service Connection Point in Active Directory that still had the old URL in it.
Set-ClientAccessServer – Identity ServerName-AutoDiscoverServiceInternalUri $null
More about this: http://jetzemellema.blogspot.com/2015/10/how-to-remove-exchange-autodiscover-scp.html
Max
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Uninstall Exchange 2010 Some Controls Aren T Valid
Source: https://community.spiceworks.com/topic/2225067-broke-exchange-2016-by-uninstalling-exchange-2010
0 Response to "Uninstall Exchange 2010 Some Controls Aren T Valid"
Post a Comment