We've migrated to Server 2016 with Exchange 2016. I followed the instructions to remove Exchange 2010, but it failed half way through the uninstall. I then tried following the ADSI Edit instructions, but I don't want to proceed as they remove anything exchange related from the domain, which I don't want to do. How do I make sure Exchange 2010 gets fully removed from my AD?
Thanks.
Ah this is related to your other question I guess, see https://server-essentials.com/community/discussions/extra-step-in-dns-config. THere is no need to create an autodiscover record on the SBS. As a matter of fact the only place you need an autodiscover record is in public DNS and Outlook 2016 clients on your local network use SCP (Service Connection Point) to find your on-premise Exchange Server.
Can you post the error message you got and name the step where you got the problem?
Ha, yes :) Here's the end of the exchange setup log. I believe it errored at "removing exchange files." Unfortunately it also removed the setup.com file so I can't re-run it.
02/17/2018 23:32:15.0300] [0] Setup will run the task 'uninstall-msipackage' [02/17/2018 23:32:15.0300] [1] Setup launched task 'uninstall-msipackage -logfile 'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode '4934d1ea-be46-48b1-8847-f1af20e892c1' -PropertyValues 'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU'' [02/17/2018 23:32:15.0448] [1] Active Directory session settings for 'Uninstall-MsiPackage' are: View Entire Forest: 'True', Configuration Domain Controller: 'LSYDC.architects.local', Preferred Global Catalog: 'LSYDC.architects.local', Preferred Domain Controllers: '{ LSYDC.architects.local }' [02/17/2018 23:32:15.0448] [1] Beginning processing uninstall-msipackage -LogFile:'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode:'4934d1ea-be46-48b1-8847-f1af20e892c1' -PropertyValues:'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU' [02/17/2018 23:32:15.0464] [1] Removing MSI package with code '4934d1ea-be46-48b1-8847-f1af20e892c1'. [02/17/2018 23:34:13.0022] [1] Ending processing uninstall-msipackage [02/17/2018 23:34:13.0023] [0] ************** [02/17/2018 23:34:13.0023] [0] Setup will run the task 'Start-MidFileCopy' [02/17/2018 23:34:13.0023] [1] Setup launched task 'Start-MidFileCopy -IsServerSbs $true -PreviousVersion '14.3.123.4' -Mode 'BuildToBuildUpgrade' -Roles 'BridgeheadRole','ClientAccessRole','MailboxRole','AdminToolsRole'' [02/17/2018 23:34:13.0181] [1] Active Directory session settings for 'Start-MidFileCopy' are: View Entire Forest: 'True', Configuration Domain Controller: 'LSYDC.architects.local', Preferred Global Catalog: 'LSYDC.architects.local', Preferred Domain Controllers: '{ LSYDC.architects.local }' [02/17/2018 23:34:13.0181] [1] Beginning processing Start-MidFileCopy -IsServerSbs:'True' -PreviousVersion:'14.3.123.4' -Mode:'BuildToBuildUpgrade' -Roles:'BridgeheadRole','ClientAccessRole','MailboxRole','AdminToolsRole' [02/17/2018 23:34:13.0214] [1] Loaded component 'All Roles MidFileCopy' with 2 task information blocks from 'res://AllRolesMidFileCopyComponent.xml' [02/17/2018 23:34:13.0215] [1] Loaded component 'Datacenter All Roles MidFileCopy' with 2 task information blocks from 'res://DatacenterAllRolesMidFileCopyComponent.xml' [02/17/2018 23:34:13.0231] [1] Loaded component 'Bridgehead MidFileCopy' with 1 task information blocks from 'res://BridgeheadMidFileCopyComponent.xml' [02/17/2018 23:34:13.0233] [1] Loaded component 'Datacenter Bridgehead MidFileCopy' with 1 task information blocks from 'res://DatacenterBridgeheadMidFileCopyComponent.xml' [02/17/2018 23:34:13.0236] [1] Loaded component 'Client Access MidFileCopy' with 1 task information blocks from 'res://ClientAccessMidFileCopyComponent.xml' [02/17/2018 23:34:13.0242] [1] Loaded component 'Datacenter Client Access MidFileCopy' with 1 task information blocks from 'res://DatacenterClientAccessMidFileCopyComponent.xml' [02/17/2018 23:34:13.0244] [1] Loaded component 'Mailbox MidFileCopy' with 1 task information blocks from 'res://MailboxMidFileCopyComponent.xml' [02/17/2018 23:34:13.0246] [1] Loaded component 'Datacenter Mailbox MidFileCopy' with 1 task information blocks from 'res://DatacenterMailboxMidFileCopyComponent.xml' [02/17/2018 23:34:13.0254] [1] Loaded component 'Admin Tools MidFileCopy' with 1 task information blocks from 'res://AdminToolsMidFileCopyComponent.xml' [02/17/2018 23:34:13.0256] [1] Loaded component 'Datacenter Admin Tools MidFileCopy' with 1 task information blocks from 'res://DatacenterAdminToolsMidFileCopyComponent.xml' [02/17/2018 23:34:13.0332] [1] Exception : Microsoft.Exchange.Configuration.Tasks.WriteErrorException: Unexpected Error at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl) at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target) at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.PopulateContextVariables() at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.GenerateAndExecuteTaskScript(InstallationCircumstances installationCircumstance) [02/17/2018 23:34:13.0365] [1] [ERROR] Unexpected Error [02/17/2018 23:34:13.0398] [1] [ERROR] Could not find file 'C:\Program Files\Microsoft\Exchange Server\V14\bin\EnterpriseServiceEndpointsConfig.xml'. [02/17/2018 23:34:13.0719] [1] Ending processing Start-MidFileCopy [02/17/2018 23:34:13.0857] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder. [02/17/2018 23:34:13.0871] [0] End of Setup [02/17/2018 23:34:13.0871] [0] **********************************************
One more: the exchangesetup.msilog seems to indicate that exchange uninstalled successfully, but I'm still seeing traces of our old sbs server everywhere on AD.
MSI (s) (BC:98) [18:34:12:870]: Transforming table Error.
MSI (s) (BC:98) [18:34:12:870]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (BC:98) [18:34:12:870]: Product: Microsoft Exchange Server -- Removal completed successfully.
MSI (s) (BC:98) [18:34:12:871]: Windows Installer removed the product. Product Name: Microsoft Exchange Server. Product Version: 14.3.123.4. Product Language: 1033. Manufacturer: Microsoft Corporation. Removal success or error status: 0.
MSI (s) (BC:98) [18:34:12:876]: Deferring clean up of packages/files, if any exist MSI (s) (BC:98) [18:34:12:876]: MainEngineThread is returning 0 MSI (s) (BC:58) [18:34:12:880]: RESTART MANAGER: Session closed. MSI (s) (BC:58) [18:34:12:880]: No System Restore sequence number for this installation. MSI (s) (BC:58) [18:34:12:882]: User policy value 'DisableRollback' is 0 MSI (s) (BC:58) [18:34:12:882]: Machine policy value 'DisableRollback' is 0 MSI (s) (BC:58) [18:34:12:882]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (BC:58) [18:34:12:882]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (BC:58) [18:34:12:883]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (BC:58) [18:34:12:897]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (s) (BC:58) [18:34:12:897]: Post-install cleanup: removing installer file 'C:\Windows\Installer\1ac041.msi' MSI (s) (BC:58) [18:34:12:916]: Post-install cleanup: removing installer file 'C:\Windows\Installer\{4934D1EA-BE46-48B1-8847-F1AF20E892C1}\PowerShell.exe' MSI (s) (BC:58) [18:34:12:935]: Post-install cleanup: removing installer folder 'C:\Windows\Installer\{4934D1EA-BE46-48B1-8847-F1AF20E892C1}\' (if empty) MSI (s) (BC:58) [18:34:12:936]: Note: 1: 2318 2: MSI (s) (BC:58) [18:34:12:936]: Post-install cleanup: removing installer file 'C:\Windows\Installer\{4934D1EA-BE46-48B1-8847-F1AF20E892C1}\LPowerShell.exe' MSI (s) (BC:58) [18:34:12:939]: Post-install cleanup: removing installer folder 'C:\Windows\Installer\{4934D1EA-BE46-48B1-8847-F1AF20E892C1}\' (if empty) MSI (s) (BC:58) [18:34:12:939]: Note: 1: 2318 2: MSI (s) (BC:58) [18:34:12:939]: Post-install cleanup: removing installer file 'C:\Windows\Installer\{4934D1EA-BE46-48B1-8847-F1AF20E892C1}\HelpQMark' MSI (s) (BC:58) [18:34:12:944]: Post-install cleanup: removing installer folder 'C:\Windows\Installer\{4934D1EA-BE46-48B1-8847-F1AF20E892C1}\' (if empty) MSI (s) (BC:58) [18:34:12:944]: Note: 1: 2318 2: MSI (s) (BC:58) [18:34:12:946]: Post-install cleanup: removing installer file 'C:\Windows\Installer\77d2d4e.msp' MSI (s) (BC:58) [18:34:12:948]: Restoring environment variables MSI (s) (BC:58) [18:34:12:963]: Destroying RemoteAPI object. MSI (s) (BC:58) [18:34:12:963]: Custom Action Manager thread ending. MSI (c) (6C:B0) [18:34:13:014]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (6C:B0) [18:34:13:014]: MainEngineThread is returning 0 === Verbose logging stopped: 2/17/2018 18:34:13 ===
At what service pack level was your Exchange Server 2010 before you started the migration? I am wondering why this happens because in all of the migrations I have done I have never had this issue before but all of my Exchange Server 2010 were always up to date with the latest service packs and CU.
Of course you will see traces of the old SBS in your AD because it is still a DC I assume but if you mean traces of Exchange Server 2010 you can also be correct because it was once installed. What do you see and where? If you go to the new Exchange Server 2016 and open EAC can you select the old server in the Servers menu for example or the Virtual Directories?
Thanks. We installed Service Pack 3 for Exchange 2010 the night before the migration. Half-way through the migration, we ended up having to install update rollup 18, I wonder if that had something to do with it. Anyway, I don't see the old server under the servers menu in EAC, but I did see all of the old virtual directories listed. I ran the various PowerShell commands to get rid of them. I still have PowerShell (default web site) and Powershell-Proxy (Default web site) listed. Am I safe to get rid of those? Anything else that could be causing our client certificate issues? OWA works very well and we have mail flow. We're just missing the client outlook config.
Can you run the below script on the Exchange Server 2016 and email me the output? You can find my email address on the invoice for your subscription.
Start-Transcript EnvironmentBackup.txt Get-OutlookProvider | Format-List Get-OutlookAnywhere | Format-List Get-ClientAccessServer | Format-List Get-ActiveSyncVirtualDirectory | Format-List Get-AutodiscoverVirtualDirectory | Format-List Get-EcpVirtualDirectory | Format-List Get-OabVirtualDirectory | Format-List Get-OwaVirtualDirectory | Format-List Get-MapiVirtualDirectory | Format-List Get-PowerShellVirtualDirectory | Format-List Get-WebServicesVirtualDirectory | Format-List Get-SendConnector | Where-Object {$_.Enabled -eq $true} | Format-List Get-SendConnector | Where-Object {$_.Enabled -eq $true} | Get-ADPermission | Where-Object { $_.extendedrights -like '*routing*' } | fl identity, user, *rights Resolve-DnsName -Type A -Name mail.domain.com Resolve-DnsName -Type A -Name autodiscover.domain.com Resolve-DnsName -Type A -Name mail.domain.com -Server 8.8.8.8 Resolve-DnsName -Type A -Name autodiscover.domain.com -Server 8.8.8.8 Resolve-DnsName -Type MX -Name domain.com -Server 8.8.8.8 Resolve-DnsName -Type TXT -Name domain.com -Server 8.8.8.8 Resolve-DnsName -Type A -Name i-should-not-exist.domain.com -Server 8.8.8.8 Stop-Transcript
Obviously you need to change domain.com to your own domain name
Thank you, email sent!
Fixed the issue Luis had in a Teamviewer/Skype session. I cleaned out leftovers from old Exchange with ADSIEdit. Not the best way of doing things but there was no other way.
Thank you so much! Mariette took time out of her Sunday to do a remote session and fix our issue. Amazing service!
Thanks Luis!
Your browser doesn't have Flash, Silverlight or HTML5 support.