Re: Questions regarding configuring Windows Server 2003 as a DC

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I'm thinking of tweaking my plan here a little by doing the following:
1. Install Windows 2000 Server SP4 + all updates, and join the domain.
2. Install AD integrated DNS, and wait for replication to occur
3. Move all FSMO Roles over
4. Configure a Global Catalog Server

This should leave me with a functioning DC, correct? At this point if my
PDC FSMO failed what else would I need to do other than seize the FSMO roles
to make sure this new DC can become the PDC FSMO and run my network?

Thank you.

"Jorge Silva" wrote:

also take a look
Considerations when creating an AD Test environment - Part 1
http://blogs.dirteam.com/blogs/jorge/archive/2005/11/19/105.aspx
Considerations when creating an AD Test environment - Part 2
http://blogs.dirteam.com/blogs/jorge/archive/2005/11/19/107.aspx
Building of a copy of the production Active Directory
http://71.214.145.52:443/windows/articles/TestDomain.html

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator
"mike dunphy" <mikedunphy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:985400B8-5606-4E89-9A61-9BFE0E805AF6@xxxxxxxxxxxxxxxx
I have not done anything with VM yet. However, I could add a temp DC to
the
network as a Windows 2000 Server, transfer the roles to it, etc and then
take
it off-line to try the upgrade.

"Jorge Silva" wrote:

Are you aware of VM you can do some decent tests before going to
production
(MS Virtual Server R2 is free).

There other ways, for example isolate the DC from network (backup it
first),
or disabling replication, then enabling it first only with one partner
then
another, etc.

Adding a tem DC to network, then transferring the roles to it, isolate it
from network, upgrade it then if everything ok start by replicating only
with one DC in network, then another, etc.

If everything wrong you can always shutdown the Temp DC , and seize the
roles to the other available DCs.

Etc.. etc.. there many options to do this you can google to some
suggestions
and different scenarios.


--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator
"mike dunphy" <mikedunphy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B621460F-A3C5-4817-9F8F-14D741DF4E93@xxxxxxxxxxxxxxxx
Thanks Jorge. In a perfect environment with a big budget and resources
available this would be an option. I'll do the best with what I have.
:)

"Jorge Silva" wrote:

I as all updates process you should make a lab duplicating your
environment
and test it first, by using this method you can have sure if you'll
run
into
issues.



--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator
"mike dunphy" <mikedunphy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C85B128-35E0-4682-AB33-29EA2DD6F10B@xxxxxxxxxxxxxxxx
It already has helped me, and I'm sure it will continue to.

Is there any way to estimate how long running Inetorgpersonfix.ldf
will
take? Also, do I risk corrupting anything in my IS or AD by running
this?
I
know these questions are difficult to answer, but hopefully this
information
will help quantify things.
IS == 20GB
System Mailboxes == 38

Since there are multiple steps associated with moving my DC to a
2003
server
I'll need to spread this project across several days / weeks and I
plan
on
doing most of the work in the mornings.

Thank you!

"Jorge Silva" wrote:

That's right.
--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator
"mike dunphy" <mikedunphy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:8576066E-CBE9-46E4-9121-69BE5C91770E@xxxxxxxxxxxxxxxx
Thanks for the link to KB 314649. In our scenario I added
Exchange
2000
to
an existing Windows 2000 forest. As a result all I really need
to
do
is
run
Inetorgpersonfix.ldf before running the Windows Server 2003
adprep /
forestprep command, correct?

Thank you.

"Jorge Silva" wrote:

Hi

Basic rules are:

Because you have exchange first take a look at:
http://support.microsoft.com/kb/314649/

Then you need to prepare the Forest and the domain where you're
adding
the
2003 DCs.
dcpromo /forestprep on schema master and /domainprep on IM.
Promote the Windows 2003 to additional DCs in the existent
domain.
- Make the Servers DNS servers (configure the DNS servers as AD
Integrated).
- Make sure that everything is replicated across existent DCs.
- Transfer the Fsmo roles to the new servers.
- Make the 2 new W2K3 servers GCs.
- Transfer any other role that you might have in the Windows
2000
(like:DHCP, Wins, Apps, etc.)
- Make sure that the clients use the NEW DNS servers in their
TCP/IP
Primary
and secondary DNS server.
- After everything is in place, disconnect the DCs to be
removed- a
week
or
so... if everything Ok, connect the 2000 servers again and use
DC
promo
to
remove them from AD.
- Note: you need to remove them manually from Active Directory
Sites
and
Services.
Voilá you're Done.

Lots of info here:
http://www.microsoft.com/windowsserver2003/upgrading/w2k/default.mspx
http://support.microsoft.com/kb/555040/en-us
http://support.microsoft.com/?kbid=325379
--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator
"mike dunphy" <mikedunphy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:E6AC4D07-3C2D-4726-A73A-13CDAAE7E4B2@xxxxxxxxxxxxxxxx
Hello. I'm the release engineer of a small software company,
and
also
assume
all system administration responsibilities. Our network
consists
of
14
servers, among those servers we have (2) Windows 2000 Server
domain
controllers, each having a copy of the global catalog.
Additionally
each
of
these DC servers is also a DNS server. The remaining servers
run
Windows
Server 2003 with the exception of our Exchange 2000 server
that
runs
on
Windows 2000 Advanced Server.

These domain controllers are running on hardware that is over
5
years
old,
and beyond backing these systems up there is no real
redundancy
built
in.
I
would like to install Windows Server 2003 on two new servers,
so
that I
can
retire the domain controllers running on this old equipment.
Beyond
configuring these new servers as domain controllers during the
initial
installation what other steps need to be taken? I'll also
configure
these
servers as DNS servers, and replicate the global catalog over,
but
it
seems
to me there must be more that has to happen.

If my existing hardware wasn't so old I would look to upgrade
these
systems
to Windows Server 2003 and upgrade the schema master using
adprep.
However,
in this case it makes more sense to start with new hardware.

I appreciate any comments, tips and criticisms that can point
me
in
the
right direction.

Thank you.
















.

Relevant Pages

  • Re: Linux DHCP updating Windows 2000 DNS
    ... > We are looking at alternatives to our Windows DHCP servers as they do ... > I have it clustering fine and giving out IP's ... I haven't tried with Windows DNS servers. ...
    (comp.os.linux.networking)
  • Re: Need help with DNS design and settings
    ... about forest root and tree root domains. ... The name servers box is usually populated automatically (at least I ... thought so) with the DNS servers you have the AD integrated zones on. ... > forwarders for internet queries, I put the address of my 2 external DNS ...
    (microsoft.public.win2000.dns)
  • Re: Need help with DNS design and settings
    ... we often point all servers at the ... provided all DNS servers have a consistent copy of the zone. ... Name server box is only the servers authoritative for that zone. ... >>> forwarders for internet queries, I put the address of my 2 external DNS ...
    (microsoft.public.win2000.dns)
  • Re: How to host email using Exchange 2003
    ... > You Own SMTP Mail using Exchange 2000" and think the instructions will ... So their DNS your company is using is Internet "facing". ... record specific Emails servers. ... The ISP DNS servers will do the job of sending Internet mails out. ...
    (microsoft.public.exchange.setup)
  • Re: Questions regarding configuring Windows Server 2003 as a DC
    ... Systems Administrator ... My goal now is to have a DC in place capable of being the PDC FSMO in the ... an existing Windows 2000 forest. ... Make the Servers DNS servers (configure the DNS servers ...
    (microsoft.public.windows.server.active_directory)