[THIN] Re: OT: NT4 Domain to W2k AD upgrade PART 2 (Exchange twist)
- From: Vince Tan <VinceT@xxxxxxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Wed, 27 Nov 2002 12:07:19 -0500
Yeah, I was going with that scenario at first. But it is no biggie, I can
always rebuilt the BDC since they are all spare machine for now. I'm just
wondering if the whole issue with the PDC and BDC is the cause of my
Exchange not starting.
Vince
-----Original Message-----
From: Joe Shonk [mailto:JShonk@xxxxxxxxxxxxxx]
Sent: Wednesday, November 27, 2002 12:09 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: OT: NT4 Domain to W2k AD upgrade PART 2 (Exchange twist)
Actually there is a "Demote" option... Anyways, here are two Q Article =
detailing how to demote a PDC to a BDC when there are two PDCs
http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;167248
http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;112549
-----Original Message-----
From: Pavlo Ignatusha [mailto:pignatusha@xxxxxxxxxxxxx]
Sent: Wednesday, November 27, 2002 9:53 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: OT: NT4 Domain to W2k AD upgrade PART 2 (Exchange
twist)
Yep Chris was definitely right.
but I think you could still correct your "multiple PDC" problem without
going back too far. I never had this problem myself but here what I'd =
do:
Because there is no option to "Demote to BDC" in Server Manager you need =
to have a BDC around to do the promotion and this way have your PDC =
demoted. At the worst case scenario you can take your exchange PDC out to
the other physical network (perhabs a hub) take a PC workstation, build a
quick = BDC with same name and IP as your current (new) PDC and promote this
PC BDC = to be a PDC on this little network. As a result of this your
exchange box = will become a BDC and you may try to plug it back into your
real network.
Hope this helps
Pav
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Vince Tan
Sent: Wednesday, November 27, 2002 11:30 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: OT: NT4 Domain to W2k AD upgrade PART 2 (Exchange
twist)
Hi Pav, I think Chris pointed out the mistake that I made. I should = have
left the old PDC running when I promoted the new BDC to a PDC. That = might
be the caused of the problem.
Vince
-----Original Message-----
From: Pavlo Ignatusha [mailto:pignatusha@xxxxxxxxxxxxx]
Sent: Wednesday, November 27, 2002 11:24 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: OT: NT4 Domain to W2k AD upgrade PART 2 (Exchange =
twist)
Vince,
Did you power your old PDC on being hooked up to the network or not? If =
you were plugged in you had 2 PDC on your network at a time. One of these 2
should became a PDC or your network is screwed. Check it in the Server
Manager and demote your old PDC to BDC for sure. Check the Event Viewer = on
your exchange box for services that did not start as well to find the
dependancy.
Now I think you could demote your exchange to BDC pretty safely for a =
couple of reasons: 1. You can always promote it back if something does't
work = 2. Exchange 5.5 doesn't need to run on PDC. Moreover I don't think it
is recommended. You have it like that only because of small Business =
Server.
Hope this helps
Pav
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Vince Tan
Sent: Wednesday, November 27, 2002 10:35 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] OT: NT4 Domain to W2k AD upgrade PART 2 (Exchange twist)
Hello again,
After getting all the advise (by the way, thanks to all), I decided to
start my upgrade process. I installed 2 new BDC (machine b and c) to my =
NT4 domain, then shut down my PDC which is also my exchange server. I then
promoted one of the new BDC (machine C) to a PDC, then took it off line =
and just stored it. The next step was promoting the other new BDC (machine
=
B)
to a PDC. Everything works so far. So I proceeding turning on my old = PDC
(the one with exchange running on it) thinking that I could get exchange
running again and then demote the machine to a BDC. After it started,
Exchange did not start at all. It gave me an Event ID 7001 error for = all
5 exchange services.
Event ID: 7001
Source: Service Control Manager
Type: Error
Description:
The Microsoft Exchange Event Service service depends on the Microsoft
Exchange Information Store service which failed to start because of the
following error:
The dependency service or group failed to start.
Event ID: 7001
Source: Service Control Manager
Type:Error
Description:
The Microsoft Exchange Message Transfer Agent service depends on the
Microsoft Exchange Directory service which failed to start because of = the
following error:
The dependency service or group failed to start.
Event ID: 7001
Source: Service Control Manager
Type: Error
Description:
The Microsoft Exchange Information Store service depends on the = Microsoft
Exchange Directory service which failed to start because of the = following
error:
The dependency service or group failed to start.
Event ID: 7001
Source: Service Control Manager
Type:Error
Description:
The Microsoft Directory service depends on the Microsoft Exchange System
Attendant service which failed to start because of the following error:
The dependency service or group failed to start.
Event ID: 7001
Source: Service Control Manager
Type:Error
Description:
The Microsoft Exchange System Attendant service depends on the Netlogon
service which failed to start because of the following error: The = service
have returned a service specific error code.
I have not demoted this machine so there are 2 PDC. I am afraid to = demote
this because I can't really afford to have exchange down. Could having =
the 2 PDC be the cause of the exchange problem?
Below was my original message.
Thanks again and Happy Thanksgiving everyone.
Vince
From: Vince Tan [mailto:VinceT@xxxxxxxxxxxx]
Sent: Tuesday, November 26, 2002 9:14 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] OT: NT4 Domain to W2k AD upgrade advise
Hi everyone, I'm taking the leap to active directory finally so I'm =
trying to plan out what is the best strategy to approach this task. My
network consist of only one NT4 domain, a PDC (NT4 Small Business Edition
with
Exchange) and a BDC (NT4 Server). I also have a few NT4 Servers and a
couple of W2k servers running as member server. I also plan to upgrade = my
Exchange 5.5 to 2000. So here is what I am thinking of doing:
1. Because the PDC and BDC are both running in old HP LC3 boxes, I can =
not reuse them or upgrade them so I am going to get a couple of new boxes. =
2. Plan to making one of the new box (machine A) a new BDC to the NT4 =
Domain 3. Promote the new BDC to a PDC 4. Upgrade this new PDC to Win2K DC
5. Install the 2nd new box (machine B) and make it a Win2K DC and sync with
= the other DC 6. Demote machine A from being a DC and then remove it from
= the network completely 7. Install fresh W2k server on machine A and make
it = a DC, then sync to machine B 8. Install exchange in machine A
Is this the right approach? Do I need to take it off my production =
network while doing all the upgrade or can I just do the upgrade on my
actual network since none of my existing server will be touched except for
the = old PDC which will have to be taken off line and demote to BDC
Thanks for any advise
Vince
***********************************************
This Weeks Sponsor
OneApp Total Control
Control, Secure and Audit your Thin Client Systems = http://www.oneapp.co.uk
***********************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link.
http://thethin.net/citrixlist.cfm
***********************************************
This Weeks Sponsor
OneApp Total Control
Control, Secure and Audit your Thin Client Systems = http://www.oneapp.co.uk
***********************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link.
http://thethin.net/citrixlist.cfm
***********************************************
This Weeks Sponsor
OneApp Total Control
Control, Secure and Audit your Thin Client Systems http://www.oneapp.co.uk
***********************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link.
http://thethin.net/citrixlist.cfm
***********************************************=20
This Weeks Sponsor
OneApp Total Control
Control, Secure and Audit your Thin Client Systems http://www.oneapp.co.uk
***********************************************=20
For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link.
http://thethin.net/citrixlist.cfm
***********************************************
This Weeks Sponsor
OneApp Total Control
Control, Secure and Audit your Thin Client Systems http://www.oneapp.co.uk
***********************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link.
http://thethin.net/citrixlist.cfm
***********************************************
This Weeks Sponsor
OneApp Total Control
Control, Secure and Audit your Thin Client Systems
http://www.oneapp.co.uk
***********************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link.
http://thethin.net/citrixlist.cfm
Other related posts:
