Home All Groups Group Topic Archive Search About

All gone to cr*p after removing win 2003 dc

Author
10 Feb 2009 1:58 PM
Resonate
I seem to remember reading that there must be Windows 2003 DC's available
for Exchange 2007?

Is this true?

Ive installed 2008 x64 and Exchange 2007 SP1, after migrating mailboxes and
leaving it all running for a few days I uninstalled Exchange 2003 from the
old 2003 server.

A few more days ive just removed AD from the 2003 box and raised the DFL and
FFL to Win 2008.

This now leaves me with just 1 server Win 2008 with AD running Exchange 2007
SP1 and the Exchange websites.

Now after a reboot its all gone to crap, exchange services wont start, error
logs about missing domain controllers etc etc.

Any Ideas?

Thanks

Res

Author
11 Feb 2009 5:07 AM
Ed Crowley [MVP]
Comments inline below.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"Resonate" <dont@spam.me> wrote in message
news:99142FD6-57CA-4CF5-9B58-6200A0A948CB@microsoft.com...
>I seem to remember reading that there must be Windows 2003 DC's available
>for Exchange 2007?
>
> Is this true?


All versions of Exchange since 2000 require domain controllers and global
catalog servers.

Show quoteHide quote
> Ive installed 2008 x64 and Exchange 2007 SP1, after migrating mailboxes
> and leaving it all running for a few days I uninstalled Exchange 2003 from
> the old 2003 server.
>
> A few more days ive just removed AD from the 2003 box and raised the DFL
> and FFL to Win 2008.
>
> This now leaves me with just 1 server Win 2008 with AD running Exchange
> 2007 SP1 and the Exchange websites.
>
> Now after a reboot its all gone to crap, exchange services wont start,
> error logs about missing domain controllers etc etc.
>
> Any Ideas?

I'd bet your new server isn't a global catalog.

Look in your event logs for this:

Event Type: Information
Event Source: MSExchange ADAccess
Event Category: Topology
Event ID: 2080
Date:  9/28/2007
Time:  11:33:01 AM
User:  N/A
Computer: EXCHANGE
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1188). Exchange Active
Directory Provider has discovered the following servers with the following
characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable |
PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
adsrv.vtunes.net CDG 1 7 7 1 0 1 1 7 1
adsrv2.vtunes.net CDG 1 7 7 1 0 0 1 7 1
Out-of-site:

This KB explains the message:  http://support.microsoft.com/?kbid=316300

That message should tell you what Exchange is looking for and doesn't find.

By the way, having just one domain controller and global catalog server
isn't very fault tolerant.  Having zero global catalogs is even worse!

Show quoteHide quote
> Thanks
>
> Res
Author
11 Feb 2009 2:10 PM
Resonate
So just a windows 2008 DC is sufficient for Exchange 2007?  Im sure I read
there must be a 2003 DC for some reason?

It is/was a GC as that was a requirement to remove AD from the old one.

Ive just realised (after rebuilding the environment with 2003 x64!) that the
DNS was still pointing at the old server as it was for the initial promotion
of the 2008 box! doh

I guess my real question is will Exchange 2007 run with ONLY 2008 domain
controllers?

Cheers



Show quoteHide quote
"Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
news:#8rdvaAjJHA.5588@TK2MSFTNGP03.phx.gbl...
> Comments inline below.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> .
>
> "Resonate" <dont@spam.me> wrote in message
> news:99142FD6-57CA-4CF5-9B58-6200A0A948CB@microsoft.com...
>>I seem to remember reading that there must be Windows 2003 DC's available
>>for Exchange 2007?
>>
>> Is this true?
>
>
> All versions of Exchange since 2000 require domain controllers and global
> catalog servers.
>
>> Ive installed 2008 x64 and Exchange 2007 SP1, after migrating mailboxes
>> and leaving it all running for a few days I uninstalled Exchange 2003
>> from the old 2003 server.
>>
>> A few more days ive just removed AD from the 2003 box and raised the DFL
>> and FFL to Win 2008.
>>
>> This now leaves me with just 1 server Win 2008 with AD running Exchange
>> 2007 SP1 and the Exchange websites.
>>
>> Now after a reboot its all gone to crap, exchange services wont start,
>> error logs about missing domain controllers etc etc.
>>
>> Any Ideas?
>
> I'd bet your new server isn't a global catalog.
>
> Look in your event logs for this:
>
> Event Type: Information
> Event Source: MSExchange ADAccess
> Event Category: Topology
> Event ID: 2080
> Date:  9/28/2007
> Time:  11:33:01 AM
> User:  N/A
> Computer: EXCHANGE
> Description:
> Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1188). Exchange Active
> Directory Provider has discovered the following servers with the following
> characteristics:
> (Server name | Roles | Enabled | Reachability | Synchronized | GC capable
> | PDC | SACL right | Critical Data | Netlogon | OS Version)
> In-site:
> adsrv.vtunes.net CDG 1 7 7 1 0 1 1 7 1
> adsrv2.vtunes.net CDG 1 7 7 1 0 0 1 7 1
> Out-of-site:
>
> This KB explains the message:  http://support.microsoft.com/?kbid=316300
>
> That message should tell you what Exchange is looking for and doesn't
> find.
>
> By the way, having just one domain controller and global catalog server
> isn't very fault tolerant.  Having zero global catalogs is even worse!
>
>> Thanks
>>
>> Res
>
Author
11 Feb 2009 3:45 PM
Ed Crowley [MVP]
Where did you read that it doesn't?
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

Show quoteHide quote
"Resonate" <dont@spam.me> wrote in message
news:8C19E9ED-8DCE-4C07-83EB-1DE0C06F6829@microsoft.com...
> So just a windows 2008 DC is sufficient for Exchange 2007?  Im sure I read
> there must be a 2003 DC for some reason?
>
> It is/was a GC as that was a requirement to remove AD from the old one.
>
> Ive just realised (after rebuilding the environment with 2003 x64!) that
> the DNS was still pointing at the old server as it was for the initial
> promotion of the 2008 box! doh
>
> I guess my real question is will Exchange 2007 run with ONLY 2008 domain
> controllers?
>
> Cheers
>
>
>
> "Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
> news:#8rdvaAjJHA.5588@TK2MSFTNGP03.phx.gbl...
>> Comments inline below.
>> --
>> Ed Crowley MVP
>> "There are seldom good technological solutions to behavioral problems."
>> .
>>
>> "Resonate" <dont@spam.me> wrote in message
>> news:99142FD6-57CA-4CF5-9B58-6200A0A948CB@microsoft.com...
>>>I seem to remember reading that there must be Windows 2003 DC's available
>>>for Exchange 2007?
>>>
>>> Is this true?
>>
>>
>> All versions of Exchange since 2000 require domain controllers and global
>> catalog servers.
>>
>>> Ive installed 2008 x64 and Exchange 2007 SP1, after migrating mailboxes
>>> and leaving it all running for a few days I uninstalled Exchange 2003
>>> from the old 2003 server.
>>>
>>> A few more days ive just removed AD from the 2003 box and raised the DFL
>>> and FFL to Win 2008.
>>>
>>> This now leaves me with just 1 server Win 2008 with AD running Exchange
>>> 2007 SP1 and the Exchange websites.
>>>
>>> Now after a reboot its all gone to crap, exchange services wont start,
>>> error logs about missing domain controllers etc etc.
>>>
>>> Any Ideas?
>>
>> I'd bet your new server isn't a global catalog.
>>
>> Look in your event logs for this:
>>
>> Event Type: Information
>> Event Source: MSExchange ADAccess
>> Event Category: Topology
>> Event ID: 2080
>> Date:  9/28/2007
>> Time:  11:33:01 AM
>> User:  N/A
>> Computer: EXCHANGE
>> Description:
>> Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1188). Exchange Active
>> Directory Provider has discovered the following servers with the
>> following characteristics:
>> (Server name | Roles | Enabled | Reachability | Synchronized | GC capable
>> | PDC | SACL right | Critical Data | Netlogon | OS Version)
>> In-site:
>> adsrv.vtunes.net CDG 1 7 7 1 0 1 1 7 1
>> adsrv2.vtunes.net CDG 1 7 7 1 0 0 1 7 1
>> Out-of-site:
>>
>> This KB explains the message:  http://support.microsoft.com/?kbid=316300
>>
>> That message should tell you what Exchange is looking for and doesn't
>> find.
>>
>> By the way, having just one domain controller and global catalog server
>> isn't very fault tolerant.  Having zero global catalogs is even worse!
>>
>>> Thanks
>>>
>>> Res
>>