I've posted previously about this but now Its causing an issue.
We have and old server called TUBE1 running on Windows NT. This server ran Active Directory for the company and had Exchange 5.5 installed.
A about two years ago a new server was put into place called TLSVR02, this machine was given a new Active Directory Forest called APO. Then an Active Directory Connector was installed and all users accounts were migrated.
After that Exchange 2003 was installed on TLSVR02 in APO but due to ADC the new Exchange Server was published into the TUBE1\First Administrative Groups.
So the ADC was never turned off and a few years later I am not working with the system.
When ever a user account is created in APO and given a mailbox it is in turned created on TUBE1 and their mailbox is placed under the TUBE1\First Admin Group all of their internal routing
Information is generated and put into the old TUBE1 domains recipient containers.
I found this all today when I had to create a new user for an employee we just hired. All of his info while being created on the APO domain was pushed to TUBE1.
At first we had an issue sending the new employee mail, when looking on the TLSVR02 (APO) there were alot of EVENT ID 8026's
LDAP Bind was unsuccessful on directory tlsvr02.apo.tl.com for distinguished name 'TUBE1\exchange_apo'. Directory returned error:[0x51] Server Down. (Connection Agreement 'Config CA_TUBELITE_TLSVR02' #2920)
I think this is all tied back to the two domains being intertwined and exchange in the APO domain being installed into the TUBE1 admin group and then having the ADC continuously sync between the domains.
1. We want to get rid of these errors and our email issue with the new employee
2. We want to decomission the old TUBE1 domain and get rid of this connector
3. We don't want any issue with exchange after we get rid of TUBE1.