[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 994
  • Last Modified:

Remove Exchange 2007 hub transport role

I upgraded from Exchange 2007 to 2013. My last step is removing Exchange 2007 from the domain. I did the uninstall and it seemed to go through but had an error at the end.

When I go back to uninstall, I get the error "setup was unable to uninstall the server role" "Hub Transport Role"  "Timed out waiting for process to complete."

In 2013 ECP the 2007 server is still listed under servers and shows "Hub Transport"

How can I finish removing 2007 from the domain
0
ajdratch
Asked:
ajdratch
  • 4
  • 2
1 Solution
 
dsnegi_25decCommented:
Could you check what error are you getting on event viewer if its 4999 then below process will definitely help you.  What you need to do is increase the timeout settings & crete local host entry

Issue :-Microsoft Exchange Search Services are showing stop during 2007 SP2  Installation .
Event ID:      4999

Watson report about to be sent to dw20.exe for process id: 2540, with parameters: E12, c-RTL-AMD64, 08.02.0176.000, MSExchangeTransportLogSearch, unknown, unknown,
Answer¿ create d new Dword Value to increase the time setting for MSExchangeTransportLog Search


1.      Start Registry Editor (Regedit.exe).
2.      To change the value data for the ServicesPipeTimeout DWORD value to 60000 in the Control key, follow these steps:
a.      Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
b.      Click the Control subkey
c.      Right-click the ServicesPipeTimeout DWORD value, and then click Modify.
d.      Click Decimal.
e.      Type 60000, and then click OK.
3.      If the ServicesPipeTimeout value is not available, add the new DWORD value, and then set its value data to 60000 in the Control key. To do so, follow these steps:
 .      Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
a.      Click the Control subkey.
b.      On the Edit menu, point to New, and then click DWORD Value.
c.      Type ServicesPipeTimeout, and then press ENTER.
d.      Right-click the ServicesPipeTimeout DWORD value, and then click Modify.
e.      Click Decimal.
f.      Type a value of 60000, and then click OK.

The value is 60000 milliseconds and is equivalent to 60 seconds or to one minute.

2      Create Local host entry under C:\WINDOWS\system32\drivers\etc
127.0.0.1  crl.microsoft.com
0
 
Gareth GudgerCommented:
What was the error you received from the end? If you don't have it, it should be recorded in Event Viewer.
0
 
ajdratchAuthor Commented:
I checked with MS partner forums and finally he had me remove the server using adsiedit
CN=Configuration, DC= Domain Name, DC=com, CN=Services, CN=Microsoft Exchange, CN=<Organization Name>, CN=Administrative Groups, CN= <Exchange Administrative Group>, CN=Servers, CN=<Server Name>

I thought all was good but now email will not come in. The sender gets the error "#< #5.4.4 smtp;554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain> #SMTP#"

Server DNS is set properly to the internal nic. This is a VM.

I found this link http://msexchangeguru.com/2013/11/23/451-4-4-0-dns-query-failed-the-error-was-smtpsend-dns-nonexistentdomain-nonexistent-domain/

Based on that I did confirm that the msExchRoutingMasterDN value is set to the old server.

Seems I need to fix the routing master but I have no idea how to do that
0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 
Gareth GudgerCommented:
Is there any chance that mail from your firewall is still directed at the 2007 server's IP address and not the 2013 server?
0
 
ajdratchAuthor Commented:
no. When I telnet from outside, the new mail server answers
0
 
ajdratchAuthor Commented:
Finally contacted MS support. I am running Exchange 2013 on server 2012 R2. They said this was not supported so i had to bring up Server 2012 (not R2) and install Exchange 2013 on that.

I suspect it would have worked on R2 if i did a clean install.
0
 
ajdratchAuthor Commented:
Re installed Exchange
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now