Thanks Michael. I found several Google threads pertaining to this. It is my
perception that Exchange 2010 integration with Exchange 2003 is not fully
baked. Exchange signature errors, validation errors, nominated Recipient Update
Service errors, home MDB errors etc. etc. and everything seems to point back to
the 2003 server. Lots of chasing my tail and never catching it.
- Original Message -
From: Michael B. Smith michael @ smithcons .com
To: MS-Exchange Admin Issues exchangelist @ lyris .sunbelt-software.com
Sent: Wednesday, March 10, 2010 8:40:06 AM GMT -05:00 US/Canada Eastern
Subject: RE: Domain has unknown Exchange signature
This is a known issue. Ignore it. 12639 is the correct signature value.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http :// TheEssentialExchange .com
From: Chipshead @comcast.net [ mailto : Chipshead @comcast.net]
Sent: Wednesday, March 10, 2010 6:50 AM
To: MS-Exchange Admin Issues
Subject: Domain has unknown Exchange signature
Slowly doing a migration from Exchange 2003 SP2 to Exchange 2010. Using the MS
Exchange Best Practices analyzer returns the Domain has an unknown Exchange
signature. Ref: http :// technet . microsoft .com/en-us/library/aa997081( EXCHG
.80). aspx . My objectVersion is 12639.
Exchange 2003 was NOT installed using a pre-release version. Additionally, when
installing Exchange 2010, part of the install process was a domain prep. I'm
trying to determine why this error occurs and if it is something I should take
steps to try and correct knowing that the Exchange 2003 server (which is a
domain controller) will eventually be retired from the network. If I leave it
as it is what are the potential issues this may cause moving forward? Thanks.
Steve
