Re: Event 2116 Windows 2000 DCs and Exchange 2007

Tech-Archive recommends: Fix windows errors by optimizing your registry

I think this can be done the PowerShell using the Set-ExchagneServer cmdlet.
Take a look at Get-ExchangeServer | FL to see the properties you would need
to set. However, it is usually a good idea to let your servers dynamically
pick their DCs.

To the first poster of this message, you need to get your DCs upgraded to
W2K3 SP1 in order for Exchange to use them.


--
Jim McBee
Blog - http://mostlyexchange.blogspot.com
Directory Update - http://www.directory-update.com


"Tom Leslein" <Tom Leslein@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:118AF803-F49E-4E02-B82F-D8F1FD3BFF60@xxxxxxxxxxxxxxxx
I am having this same problem and I have scoured the internet, is there a
way
to point Ex2007 to a certain DC?

"mdgrkb" wrote:

Hi,

We have a single domain with a Windows 2003 SP1 running as DC with all
FSMOs
and Global Catalog. However, there are some Windows 2000 DCs, and the
Exchange 2007 Beta 2 box is logging the following:

Event Type: Warning
Event Source: MSExchangeADAccess
Event Category: (3)
Event ID: 2116
Date: 12/11/2006
Time: 5:39:43 PM
User: N/A
Computer: EXCHANGE2007
Description:
Process IISIPMD5274F6F-E3FC-4A10-A855-21244E592820 -AP
"EXCHANGEAPPLICATIONPOOL (PID=2708). The Domain Controller
w2kdc.mydom.local
is running Windows 5.0 (2195) (Unknown Service Pack). Exchange Active
Directory Provider requires Domain Controllers that run Windows 2003
Service
Pack 1 or later.

For more information, click http://www.microsoft.com/contentredirect.asp.

Only the Windows 2003 DC is Global Catalog.

Is there a way to force Exchange 2007 to use the Windows 2003 DC or is it
a
requirement for Exchange 2007 that all DCs be running Windows 2003 SP1?
Does this behaviour also take place on the Exchange 2007 RTM version?

Thank you very much





.

Relevant Pages

  • RE: Migrating from 2000 AD to 2003 AD
    ... Promote 2003 DCs ... If you've updated the domain schema when you installed exchange 2003 than ... > that is running on Windows 2000. ... Again people who've gone through the migration process can you ...
    (microsoft.public.windows.server.general)
  • Re: What am I missing?
    ... In the Exchange system manager check the recipients update service and change to the new 2003 DC. ... We are running windows 2000 DCs and windows 2003 DCs for over a year. ... open outlook and disconnect from exchange server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Exchange 2007 requires all DCs to be Windows 2003?
    ... Configuration Domain Controller" and select appropriate DC. ... Exchange 2007 installation. ... Active Directory domain which originally was running Windows 2000. ...
    (microsoft.public.exchange.setup)
  • Re: Event 2116 Windows 2000 DCs and Exchange 2007
    ... To the first poster of this message, you need to get your DCs upgraded to ... W2K3 SP1 in order for Exchange to use them. ... is running Windows 5.0 (Unknown Service Pack). ... requirement for Exchange 2007 that all DCs be running Windows 2003 SP1? ...
    (microsoft.public.exchange.admin)
  • Re: Exchange error
    ... Get the facts on Windows and Linux: ... >> You should only modify this if you are running windows 2000 ADVANCED with ... >> Exchange 2000 Advisory Services ... >> Please do not send email to this address, post a reply to this newsgroup. ...
    (microsoft.public.exchange2000.admin)