Fresh Rebuild of a Win2000 Server

[Don]

I have responsibility for a Win2000 Server that hosts a small, stand-alone
(no internet connection) lab network (<10 total machines; <15 users). In
general, the machine does a fine job as a print and file server (with
back-up), and user authentication, so we are not really looking to replace
the computer. However, the machine's disk configuration is bizarre at best
and now causing some limitation. The short story (Mainly because the
installation predates me and no one seems to know the history since the
original builders left!) is the c: drive is 1GB and only has a couple of
licensing files on it; d: is the CD/DVD burner; e: is the 6GB and is almost
full since it has the OS and programs on it; and the remaining two drives
are the shared drives.

What I would like to do is rebuild the machine on a new c: from the ground
up since we have all the original program CDs. The issue I am not sure how
to address is the transfer of the existing user account information. At
first I considered Ghosting the e: to the new c:, but there are some quirks
with the current Win2000 installation, so I would really like to do a fresh
install of the OS.

Is it possible to import user account information onto a freshly built
Win2000 Server?

Any suggestions, comments, pointers to articles, etc would be greatly
appreciated!

Thanks!

Don

 

[Lanwench [MVP - Exchange]]

In

I have responsibility for a Win2000 Server that hosts a small,
stand-alone (no internet connection) lab network (<10 total machines;
<15 users). In general, the machine does a fine job as a print and
file server (with back-up), and user authentication, so we are not
really looking to replace the computer. However, the machine's disk
configuration is bizarre at best and now causing some limitation. The
short story (Mainly because the installation predates me and no
one seems to know the history since the original builders left!) is
the c: drive is 1GB and only has a couple of licensing files on it;
d: is the CD/DVD burner; e: is the 6GB and is almost full since it
has the OS and programs on it; and the remaining two drives are the
shared drives.
What I would like to do is rebuild the machine on a new c: from the
ground up since we have all the original program CDs. The issue I am
not sure how to address is the transfer of the existing user account
information. At first I considered Ghosting the e: to the new c:,
but there are some quirks with the current Win2000 installation, so I
would really like to do a fresh install of the OS.

Is it possible to import user account information onto a freshly built
Win2000 Server?

Any suggestions, comments, pointers to articles, etc would be greatly
appreciated!

Thanks!

Don

Standalone server or domain controller? this makes a big difference - with
AD, you can build a new server (even temporarily on cheapo workstation
hardware), dcpromo it to be a domain controller, install DNS, transfer the
FSMO roles, and then rebuild the old box, make it a domain controller etc
etc etc, and transfer the FSMO roles back ...and then restore your data.

 

[Don]

It is indeed an AD domain controller. It's all that information I am afraid
of losing.

So, if I understand your summary and expanding on it:

1) Build a new temporary server (AD Domain Controller)
Test
Add to domain
Test

2) Transfer domain controller responsibilities
Promote new, temporary Domain Controller to Top Dog (command 'dcpromo'
?)
Install DNS (not currently using DNS)
Transfer the FSMO (?) roles

3) [demote original domain controller, and otherwise render it a simple
machine on the net]

4) Rebuild the old box from the ground up

5) Using same process used to make temporary domain controller Top Dog,
make the newly rebuilt machine Top Dog on the network

6) Restore data and away we go.



Any references on the web that really flesh this process out. In particular
the domain controller promotion and FSMO(?) transfer?


Thanks!!!

Don





"Lanwench [MVP - Exchange]"

 

[Lanwench [MVP - Exchange]]

In

It is indeed an AD domain controller. It's all that information I am
afraid of losing.

So, if I understand your summary and expanding on it:

1) Build a new temporary server (AD Domain Controller)
Test
Add to domain
Test

2) Transfer domain controller responsibilities
Promote new, temporary Domain Controller to Top Dog (command
'dcpromo' ?)
Install DNS (not currently using DNS)

You have to be using some sort of non-public/internal DNS server to have AD
run properly. You need to install it on the new server....or have another
DNS server in house, which it sounds like you don't.

Transfer the FSMO (?) roles

3) [demote original domain controller, and otherwise render it a
simple machine on the net]

4) Rebuild the old box from the ground up

5) Using same process used to make temporary domain controller Top
Dog, make the newly rebuilt machine Top Dog on the network

6) Restore data and away we go.
Yep.



Any references on the web that really flesh this process out. In
particular the domain controller promotion and FSMO(?) transfer?

DCPROMO: start | run
dcpromo <enter>

For FSMO roles:
http://support.microsoft.com/default.aspx?kbid=324801&product=winsvr2003

Thanks!!!

Don





"Lanwench [MVP - Exchange]"

In

Standalone server or domain controller? this makes a big difference
- with AD, you can build a new server (even temporarily on cheapo
workstation hardware), dcpromo it to be a domain controller, install
DNS, transfer the FSMO roles, and then rebuild the old box, make it
a domain controller etc etc etc, and transfer the FSMO roles back
...and then restore your data.

 

[Don]

Thanks!

Don





"Lanwench [MVP - Exchange]"

In

It is indeed an AD domain controller. It's all that information I am
afraid of losing.

So, if I understand your summary and expanding on it:

1) Build a new temporary server (AD Domain Controller)
Test
Add to domain
Test

2) Transfer domain controller responsibilities
Promote new, temporary Domain Controller to Top Dog (command
'dcpromo' ?)
Install DNS (not currently using DNS)

You have to be using some sort of non-public/internal DNS server to have
AD run properly. You need to install it on the new server....or have
another DNS server in house, which it sounds like you don't.

Transfer the FSMO (?) roles

3) [demote original domain controller, and otherwise render it a
simple machine on the net]

4) Rebuild the old box from the ground up

5) Using same process used to make temporary domain controller Top
Dog, make the newly rebuilt machine Top Dog on the network

6) Restore data and away we go.
Yep.



Any references on the web that really flesh this process out. In
particular the domain controller promotion and FSMO(?) transfer?

DCPROMO: start | run
dcpromo <enter>

For FSMO roles:
http://support.microsoft.com/default.aspx?kbid=324801&product=winsvr2003

Thanks!!!

Don





"Lanwench [MVP - Exchange]"

In Don <[email protected]> typed:
I have responsibility for a Win2000 Server that hosts a small,
stand-alone (no internet connection) lab network (<10 total
machines; <15 users). In general, the machine does a fine job as a
print and file server (with back-up), and user authentication, so
we are not really looking to replace the computer. However, the
machine's disk configuration is bizarre at best and now causing
some limitation. The short story (Mainly because the installation
predates me and no one seems to know the history since the original
builders left!) is
the c: drive is 1GB and only has a couple of licensing files on it;
d: is the CD/DVD burner; e: is the 6GB and is almost full since it
has the OS and programs on it; and the remaining two drives are the
shared drives.
What I would like to do is rebuild the machine on a new c: from the
ground up since we have all the original program CDs. The issue I
am not sure how to address is the transfer of the existing user
account information. At first I considered Ghosting the e: to the
new c:, but there are some quirks with the current Win2000
installation, so I would really like to do a fresh install of the
OS. Is it possible to import user account information onto a freshly
built Win2000 Server?

Any suggestions, comments, pointers to articles, etc would be
greatly appreciated!

Thanks!

Don

Standalone server or domain controller? this makes a big difference
- with AD, you can build a new server (even temporarily on cheapo
workstation hardware), dcpromo it to be a domain controller, install
DNS, transfer the FSMO roles, and then rebuild the old box, make it
a domain controller etc etc etc, and transfer the FSMO roles back
...and then restore your data.