• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 905
  • Last Modified:

Removing Excahnge 2003 from AD errors!

Hi all, i just finished migrating our Exchange 2003 to Exchange 2007, had a few issues but all fixed now! Any way when i am finally removing the last exchange 2003 server and am getting errors on the removal. When it tries to remove AD componennts for active syn and OMA it gives me the error(error 0x80005000: An invalid ADSI pathname was passed. Now when i go into adsi edit i still see the old exchange 2003 storage groups and such can i delete this or will this cause more problems?


Detalied errors:
EventType exchangesetuperror, P1 6_5_6944_0, P2 remove, P3 microsoft exchange messaging and collaboration services, P4 install, P5 80005000, P6 exchange activesync, P7 0, P8 NIL, P9 NIL, P10 NIL.

EventType exchangesetuperror, P1 6_5_6944_0, P2 remove, P3 microsoft exchange messaging and collaboration services, P4 install, P5 80005000, P6 microsoft exchange oma browse, P7 1, P8 NIL, P9 NIL, P10 NIL.

Exchange Server component Microsoft Exchange Messaging and Collaboration Services failed.
Error: 0x80005000 - An invalid ADSI pathname was passed.

0
zeroburnfire
Asked:
zeroburnfire
  • 6
  • 5
1 Solution
 
Exchange_GeekCommented:
Are you sure that you have moved everything from this server.

1) Mailboxes
2) Rehomed all Public folders / system folders
3) Connectors, MX Records etc.

If yes. use the article 833396 to remove the server manually from adsiedit tool.

BEFORE DELETING IT PLEASE TAKE A SYSTEM STATE BACKUP.

If you have any further queries, keep us posted.
0
 
zeroburnfireAuthor Commented:
Thanks for the response! Everything has been moved over to exchange 07 since friday of last week and has been running smooth! So ill follow the kb article and see how far that gets me and post back here.
0
 
Exchange_GeekCommented:
Thanks for your response.

In case you face any problems, please do keep us posted.

Take Care.

God bless.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
zeroburnfireAuthor Commented:
Ok that went good! but i have another question. Can i delete the first administrative group using adsi? Or via the exchange 2003 console that i have installed on my workstation? I just want to get all of the exchange 2003 AD stuff gone cause im seeing about every 15 minutes on the exchange 07 server where its trying to lookup the old exchange 03 server.
0
 
Exchange_GeekCommented:
I would recommend do not break the AG group hierarchy. Which event are you facing, this could be because there would some replica instance left on E2k7 box.

Glad to see atleast your issue got solved.
0
 
zeroburnfireAuthor Commented:
This is the error im getting on the exchange 07 box.

Microsoft Exchange couldn't find a certificate that contains the domain name mail.uhca1.local in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Outgoing Mail with a FQDN parameter of mail.uhca1.local. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.

mail.uhca1.local was the old mail server running exchange 03 and this is happening every 15 minutes
0
 
Exchange_GeekCommented:
Do the following

get-ExchangeCertificate | FL

Now, check if there is any referance to mail.uhca1.local

Also, are you using any certificates for OL2k7 or TLS for Exchange 2007 ???
0
 
zeroburnfireAuthor Commented:
This is what i get, but i dont know why i have 2?


AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessCo
                     ntrol.CryptoKeyAccessRule}
CertificateDomains : {mail08, mail08.uhca1.local}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=mail08
NotAfter           : 10/9/2009 10:47:35 AM
NotBefore          : 10/9/2008 10:47:35 AM
PublicKeySize      : 2048
RootCAType         : None
SerialNumber       : 4FD6B374B9F3B29447D370AE579E2F5C
Services           : IMAP, POP, SMTP
Status             : Valid
Subject            : CN=mail08
Thumbprint         : 817D6C3481EA83F5F837DBC1FCF726943241B6ED

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessCo
                     ntrol.CryptoKeyAccessRule}
CertificateDomains : {mail08, mail08.uhca1.local}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=mail08
NotAfter           : 10/8/2009 9:14:44 AM
NotBefore          : 10/8/2008 9:14:44 AM
PublicKeySize      : 2048
RootCAType         : None
SerialNumber       : 1FEB7E5989FE84A14CD0752103823E63
Services           : IMAP, POP, IIS, SMTP
Status             : Valid
Subject            : CN=mail08
Thumbprint         : 6885E70E58C6B64E8DB2AA638A7D4995E852EC69

0
 
Exchange_GeekCommented:
These are self signed certificates created.

Ideally, you should have only one - i find two of them. That is pretty weird.

Oh by the way there is a MSFT solution for this issue.
http://support.microsoft.com/kb/555855

What you may want to do is to remove those certificates and create new ones.
Ref: www.sembee.co.uk/archive/2007/01/21/34.aspx
0
 
zeroburnfireAuthor Commented:
Any idea on which one i should choose? since they both are the exchange 07 server the only difference is IP.S and IP.WS.

Thumbprint                                Services   Subject
----------                                --------   -------
817D6C3481EA83F5F837DBC1FCF726943241B6ED  IP..S      CN=mail08
6885E70E58C6B64E8DB2AA638A7D4995E852EC69  IP.WS      CN=mail08


[PS] C:\Windows\System32>
0
 
Exchange_GeekCommented:
You may remove both and later create a new one as per your requirement.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now