Re: Upgrade of 2003 member server in NT domain
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Wed, 15 Feb 2006 19:28:43 -0500
"ReadyForThis??" <ReadyForThis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DB1D6E3A-3CFF-43E6-ADE5-9C516F7E0CCC@xxxxxxxxxxxxxxxx
Could I run this upgrade to Server 2003 during the day whilst all users
are
accessing the network? What issues could I come across?
Slow performance for logons and using that server during
the upgrade. Loss of access during reboots.
I would prefer to do it when they go home or on the
weekend but it PROBABLY could be done without
major disruption.
You do have a backup, right? It is almost never needed
but if you don't have it then that is when it is needed. <grin>
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
"ReadyForThis??" <ReadyForThis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DB1D6E3A-3CFF-43E6-ADE5-9C516F7E0CCC@xxxxxxxxxxxxxxxx
Could I run this upgrade to Server 2003 during the day whilst all users
are
accessing the network? What issues could I come across?
Gary
"Herb Martin" wrote:
"ReadyForThis??" <ReadyForThis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:A79B8E95-D70E-468C-BA5C-9EFBD902BD6A@xxxxxxxxxxxxxxxx
What would happen with the user shares. Each client has various shares
assigned at login. These are setup using Kix????? I guess this wouldn't
carry
on working?
Group policys??
Group policy is cool.
You said in your first message that the PDC/BDC didn't
have anything:
<<The PDC and BDC's have nothing on them.
They are only there to authenticate user logins.>>
....and that the Win2003 was your file server.
Shares assigned at login through Kix will still go to
the same place -- and generally shares are so reliable
these days you can just make them /permanent or write
a login script if you need to figure out or ensure the
connection.
If you have server side profiles or share that will disappear
with the old PDC/BDC then you have to deal with that BEFORE
you remove them.
Remember, you don't HAVE to remove them -- especially if
you can upgrade them to Win2003. An old limping DC can
make a great fault tolerant addition for small to even low-medium
sized domains.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Gary
"Herb Martin" wrote:
"ReadyForThis??" <ReadyForThis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:85E8B67B-1426-446A-94E2-EE9CED5A6C3B@xxxxxxxxxxxxxxxx
Can I not promote a BDC to PDC and then upgrade that machine to
2003,
installing AD during the upgrade.
Yes -- that was in fact one of the options I gave you:
>> If it is a BDC, promote it to PDC.
Once it is in place then dcpromo the
current 2003 machine and then transfer the FSMO, the GC, DNS etc?
After
this
is complete I can turn off the upgraded machine (original BDC)?
Not quite, you should FIRST "DCPromo" the original DC to NON-DC
(DCPromo on a DC does the demotion) so that it will be properly
removed as a DC from the domain.)
THEN you can turn it off.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Gary
"Herb Martin" wrote:
"ReadyForThis??" <ReadyForThis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:8FEC0EC9-3922-4A81-A1D5-6BA1E8384930@xxxxxxxxxxxxxxxx
I currently work for an organisation that has an NT domain
consisting
of
1
NT
PDC, 2 NT BDC's and 1 Windows Server 2003 member.
The PDC and BDC's have nothing on them. They are only there to
authenticate
user logins.
They tried to install NT on the 2003 machine but it wouldn't take
it
so
they
made it a 2003 member of the NT domain.
That is highly unlikely -- any hardware that will run
Win2003 is almost guaranteed to work with NT (with
the possible exception of some drivers which can usually
be worked around.)
BUT, if it is really the case then you need a machine that
can become a WinNT BDC (then promote to PDC) and CAN
be upgraded to Win2003. You only need this machine to
remain temporarily and their is plenty of obsolete hardware
for very little money that can do this.
The 2003 server is the file/print machine with all user shares
and
data
files stored on it along with all network printers.
I need to upgrade the 2003 machine to become the DC and install
AD
on
it
but
You cannot do that. There is no path to upgrade a non-DC under
WinNT nor is their way to upgrade an NT domain EXCEPT by
upgrading the PDC.
Everything else involves a 'migration' to a NEW domain which
is almost always less desirable than the (true) upgrade you
are (correctly) trying to perform.
I don't want to destroy the files or printers already installed.
This
will
then allow me to turn off the NT boxes (I hope)!
How can I go about this without causing too much, if any
disruption
to
the
users?
Get a machine that will run NT AND will run Win2003. Maybe the
current NT PBD (or BDCs) will do that.
If it is a new machine, install NT4 as a BDC (only way to get a DC
into a WinNT domain is to do it at install time.)
If it is a BDC, promote it to PDC.
Once you have a PDC that can run Win2003, perform the upgrade.
NOW the other Win2003 Server can also be promoted (DCPromo)
to another Win2003 DC.
At that point you may keep or remove the original (PDC upgraded)
DC.
Be carefull to make sure the 5-FSMO roles, the GC, and your DNS
are transferred or working on the remaining DC before you do that
though.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Gary
.
- References:
- Re: Upgrade of 2003 member server in NT domain
- From: ReadyForThis??
- Re: Upgrade of 2003 member server in NT domain
- Prev by Date: RE: Users unable to browse trusted domain
- Next by Date: RE: How to put 2003 drivers on 2000 print server
- Previous by thread: Re: Upgrade of 2003 member server in NT domain
- Next by thread: How to put 2003 drivers on 2000 print server
- Index(es):
Relevant Pages
|
