Active Directory DNS
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Active Directory DNS

 
Post new topic   Reply to topic    Windows Server Forum Index -> Migration
Author Message
Matthew Pietz
Guest





Posted: Wed Jan 05, 2005 4:53 am    Post subject: Active Directory DNS Reply with quote

I have a question that deals with installing a 2003 domain controller that
will take the place of a 2000 DC. When I install active directory and tell it
that it is going to be a member server will DNS be installed along with
Active Directory and will it also replicate the DNS information from the 2000
DC to the 2003 DC along with the other Active Directory information at that
time? I am just trying to get my steps in order for the conversion, and I
need to know if I need an extra step for DNS.


Thanks for your help,

Matt
Back to top
Brian Desmond [MVP]
Guest





Posted: Wed Jan 05, 2005 6:07 am    Post subject: Re: Active Directory DNS Reply with quote

Matt,

I'm a bit confused by your terminology, but, I'm pretty sure I follow
nonetheless. So, to answer your question, if the DNS Service is installed on
a server before or after DCpromo'ing it, it will automatically pickup all of
the AD Integrated zones.

--
--
Brian Desmond
Windows Server MVP
desmondb@payton.cps.k12.il.us

Http://www.briandesmond.com


"Matthew Pietz" <MatthewPietz@discussions.microsoft.com> wrote in message
news:B6E4725B-8E80-4B87-B008-1D569833FD1F@microsoft.com...
Quote:
I have a question that deals with installing a 2003 domain controller that
will take the place of a 2000 DC. When I install active directory and tell
it
that it is going to be a member server will DNS be installed along with
Active Directory and will it also replicate the DNS information from the
2000
DC to the 2003 DC along with the other Active Directory information at
that
time? I am just trying to get my steps in order for the conversion, and I
need to know if I need an extra step for DNS.


Thanks for your help,

Matt
Back to top
Herb Martin
Guest





Posted: Wed Jan 05, 2005 10:47 am    Post subject: Re: Active Directory DNS Reply with quote

"Matthew Pietz" <MatthewPietz@discussions.microsoft.com> wrote in message
news:B6E4725B-8E80-4B87-B008-1D569833FD1F@microsoft.com...
Quote:
I have a question that deals with installing a 2003 domain controller that
will take the place of a 2000 DC. When I install active directory and tell
it
that it is going to be a member server will DNS be installed along with
Active Directory ...

No. This only happens for the first DC of a Domain
usually -- even then it is a choice you must

Quote:
...and will it also replicate the DNS information from the 2000
DC to the 2003 DC along with the other Active Directory information at
that
time?

Yes. If the DNS zone is AD-Integrated then it will
replicate to other DCs (in Win2000 this is the only
replication choice for AD-integrated) but that zone
will not automatically be added to the DNS server
etc.

You can setup the DNS server, create the zone,
set AD-integration and the records should be there.

Quote:
I am just trying to get my steps in order for the conversion, and I
need to know if I need an extra step for DNS.

At some point.

You could also just upgrade the current DC. (Even
if that requires moving it to new hardware.)
Back to top
Frances [MSFT]
Guest





Posted: Wed Jan 05, 2005 4:38 pm    Post subject: RE: Active Directory DNS Reply with quote

Hello Matt,

If you want to add a Windows 2003 DC to a Windows 2000 domain, and replace
the Windows 2000 DC, you have to upgrade the Windows 2000 domain to Windows
2003 domain first. Please follow the steps below.

Step 1: upgrade to Windows 2003 domain
============================================================================
You can refer to the following articles for more information.

325379 How to upgrade Windows 2000 domain controllers to Windows Server
2003 <http://support.microsoft.com/default.aspx?scid=KB;EN-US;325379>

Upgrading from Windows 2000 Server to Windows Server 2003
http://www.microsoft.com/windowsserver2003/upgrading/w2k/default.mspx

Upgrading from Windows 2000 Server to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2kto
ws03-2.mspx

Step 2: Install AD-integrated DNS on Windows 2003
============================================================================
===========
Generally, the process of installing AD-integrated DNS on 2k3 will auto
replicate DNS from Windows 2000 to Windows 2003.
You may also have a look at the following articles for more information.

DNS zone replication in Active Directory

http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/p
roddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/stan
dard/proddocs/en-us/sag_DNS_und_Active_Dir_Storage.asp

Any further questions, let us get in touch!


Best regards,

Frances He


Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Back to top
Matthew Pietz
Guest





Posted: Wed Jan 05, 2005 10:51 pm    Post subject: RE: Active Directory DNS Reply with quote

Clarification is in order here I guess. Although I thought my questions were
quite simple. This is what is going to happen. I am adding a brand new 2003
server(new hardware) to my domain that is eventually going to take over for
my 2000 server once Active Directory information and DNS has replicated and
all the of the neccessary promotions and demotions take place. The 2000
server has Active directory with Active Directory Integrated DNS.

Q1. With Windows 2003 server when you install Active directory does it
automatically install DNS or ask you to install DNS.

Q2. If so when I install Active directory on the 2003 server and make it a
member server of my existing domain will it auto replicate the DNS
information when it replicates the Active Directory?

I am not going to upgrade my 2000 server to 2003 because it is getting
removed from the domain and my 2003 server is going to be renamed to what my
2000 server was after the function levels have been raised. My 2000 server
is going to be reloaded.

Q3. If DNS does not replicate with the rest of Active Directory, how do you
replicate DNS information to the 2003 server? Yes my zones are Active
Directory integrated.
Back to top
Herb Martin
Guest





Posted: Thu Jan 06, 2005 2:04 am    Post subject: Re: Active Directory DNS Reply with quote

"Matthew Pietz" <MatthewPietz@discussions.microsoft.com> wrote in message
news:181011CB-11E8-46D4-B02E-528CD3AFB83E@microsoft.com...
Quote:
Clarification is in order here I guess. Although I thought my questions
were
quite simple. This is what is going to happen. I am adding a brand new
2003
server(new hardware) to my domain that is eventually going to take over
for
my 2000 server once Active Directory information and DNS has replicated
and
all the of the neccessary promotions and demotions take place. The 2000
server has Active directory with Active Directory Integrated DNS.

Q1. With Windows 2003 server when you install Active directory does it
automatically install DNS or ask you to install DNS.

Only in the case of the FIRST one does it definitely
install the DNS for you. When you install a second
on the existing domain it expects you already have
(dynamic DNS). This was in my previous response
above.

Quote:
Q2. If so when I install Active directory on the 2003 server and make it
a
member server of my existing domain will it auto replicate the DNS
information when it replicates the Active Directory?

Yes. In my previous message as well.

BUT the data will be virtually useless until
you configure the DNS server and CREATE
the zone AND make it AD-integrated.

It is perfectly possible to have a DC with the
data that is still a secondary (and therefore
pullin the zone transfer the traditional DNS way.)

Quote:
I am not going to upgrade my 2000 server to 2003 because it is getting
removed from the domain and my 2003 server is going to be renamed to what
my
2000 server was after the function levels have been raised. My 2000
server
is going to be reloaded.

That is a very bad idea. It almost always goes wrong,
first because you cannot generally rename a DC.

You should UPGRADE the existing DC to Win2003 if
that is you goal.

You can perform such upgrades AND change hardward
if you must.

Quote:
Q3. If DNS does not replicate with the rest of Active Directory, how do
you
replicate DNS information to the 2003 server? Yes my zones are Active
Directory integrated.

Yes, it replicates but otherwise you just make it a Secondary,
pull the date (zone transfer) and then change it to Primary or
AD-Integrate -- then you remove or change the existing DNS
as needed.

--
Herb Martin


Quote:


Back to top
Matthew Pietz
Guest





Posted: Thu Jan 06, 2005 4:45 am    Post subject: Active Directory DNS Reply with quote

I already have a new server with W2k3 installed on it. It is not part of any
domain yet becasue I am waiting on more hardware. My plan on the 2k DC is to
run adprep /forest and /domain. Once that is complete I was going to run the
configure my server tool on the 2k3 server and make it a member server of the
domain in this process I understand that Active Directory is supposed to
replicate that is why I asked the DNS question. Once Active Directory and DNS
has been replicated I am going to move the FSMO roles to the 2k3 server and
then demote the 2k server and shut it down. Then promote the 2k3 server to
be a the DC, and make sure that there are no ghost entries of the 2k server
in Active Directory. After that is complete I planned on raising the
functional level of the forest and domain to 2003, this gives the capablitity
to rename the 2k3 domain controller with the netdom tool, and hopefully that
would wrap up conversion. Then all I would have to worry about is my
antivirus and making sure my clients are pointing to the correct parent
server. This is the current plan. The reason I don't want to upgrade the 2k
server is because I going to be essentially breaking the raid configuration
(after a period of time) when I take out drives to put in my NAS. The 2k
sever with the remaining drives is going to be reloaded and become a web
server that will not be part of the domain.
Back to top
Frances [MSFT]
Guest





Posted: Thu Jan 06, 2005 2:57 pm    Post subject: RE: Active Directory DNS Reply with quote

Hello Matthew,

I think now I have a clear picture of you plan. You want to make a new
Windows 2003 DC take the place of the original Windows 2000 DC. You also
plan to name the new DC the original name of Windows 2000 DC.

I suggest you use the following steps to achieve this goal. There are some
differences compared with your original plan.

1. Run adprep /forest and /domain.

2. Install win2k3 on a new box and join it to win2k domain to be a member
server.

3. Promote Windows 2003 box to be a DC.

4. Transfer GC from 2k to 2k3:
816105 HOW TO: Create or Move a Global Catalog in Windows Server 2003
http://support.microsoft.com/?id=816105

5. Transfer FSMO from 2k to 2k3:
Using Ntdsutil.exe to seize or transfer FSMO roles to a domain controller
http://support.microsoft.com/default.aspx?scid=kb;en-us;255504

Note: You cannot transfer FSMO to 2003 member server. Only DC can hold FSMO.

You can refer to the following article for more information.
223787 Flexible Single Master Operation Transfer and Seizure Process
http://support.microsoft.com/?id=223787

6. Demote 2000 DC.

Please take a close look at the article 325379 as I have mentioned before
you upgrade win2k DC to win2k3 DC.
325379 How to upgrade Windows 2000 domain controllers to Windows Server 2003
http://support.microsoft.com/?id=325379

7. Raise domain functional level to rename DC.

Note: Is there any particular reason to change the DC name? If it is not
necessary, I suggest you don't rename the DC name since the rename process
is very complicated and may raise some issues.

The following article has detailed how to rename the name of DC.

814589 HOW TO: Rename a Windows 2003 Domain Controller
http://support.microsoft.com/?id=814589

With regards to the DNS, you can install AD-integrated DNS on win2k3.
During this process, win2k3 will replicate all DNS information from win2k.
After the process, you can transfer FSMO, take win2k offline, and rename
DC.

Any questions, let us get in touch!


Best regards,

Frances He


Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Back to top
Matthew Pietz
Guest





Posted: Thu Jan 06, 2005 10:23 pm    Post subject: RE: Active Directory DNS Reply with quote

Well the reason I want to rename the domain controller is becasue we have a
relatively simple domain structure and it is fairly small, like maybe 50
computers total and we only have this one server at this point in time. The
other reason I would like to rename the DC is because of shares and printers.
Everyone on the domain is used to \\Servername\mappeddrive or
\\servername\printer. This way hopefully we won't have to go to every single
computer and reconnect all of the mapped drives and reconnect to all of the
printers.
Back to top
Herb Martin
Guest





Posted: Fri Jan 07, 2005 12:50 pm    Post subject: Re: Active Directory DNS Reply with quote

"Matthew Pietz" <MatthewPietz@discussions.microsoft.com> wrote in message
news:56747877-0134-457E-8D08-EABF326FF52B@microsoft.com...
Quote:
Well the reason I want to rename the domain controller is becasue we have
a
relatively simple domain structure and it is fairly small, like maybe 50
computers total and we only have this one server at this point in time.
The
other reason I would like to rename the DC is because of shares and
printers.


Why not fix the problem permantently by making a DFS root
with or without (sub)Links.

Most people get overfocused on the work "Distributed"
in DFS but it can easily do the effective rename for
file share access and later you can add replicas without
having to re-educated the users or remap the shares.

Quote:
Everyone on the domain is used to \\Servername\mappeddrive or
\\servername\printer. This way hopefully we won't have to go to every
single
computer and reconnect all of the mapped drives and reconnect to all of
the
printers.

You can do the mappings from a Logon batch file
from a GPO.


--
Herb Martin
Back to top
Frances [MSFT]
Guest





Posted: Fri Jan 07, 2005 2:25 pm    Post subject: RE: Active Directory DNS Reply with quote

Hello Matthew,

You can use the netdom command to rename the DC since there are only 50
clients in the network.


Alternatively, you can use the following method to handle shares and
printers issue:

1. Printer migration tool
You may use a tool called Print Migrator to facilitate the migration. The
following website/documents contain very good information for this tool:

Print Server Upgrade, Migration, and Interoperability
http://www.microsoft.com/windows2000/technologies/fileandprint/print/miginte
rop.asp

Print Migrator 3.1 Download
http://www.microsoft.com/downloads/details.aspx?FamilyID=9b9f2925-cbc9-44da-
b2c9-ffdbc46b0b17&displaylang=en

Microsoft Print Migrator Document
http://www.microsoft.com/windows2000/docs/PrintMigrator3.doc

2. Use logon script and GPO to remap the shared files
You can use Net use command to re-map the driver. Use logon script and
startup script via GPO deploy. This way, the end users will not know what
has happened while continuing using the shared files.

2.1 Net use command to re-map the drive.
The article below tells you how to use the net use command.
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/p
roddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/stan
dard/proddocs/en-us/net_use.asp

2.2 Assign startup script and logon script
Assigning computer startup scripts
http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windo
ws2000/en/advanced/help/gptext_assigncomputerstartupscripts.htm

Assigning logon scripts to user or group accounts
http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windo
ws2000/en/advanced/help/sag_lsconcepts_1.htm

2.3 Use GPO to deploy the scripts


A kind reminder, it is better to have 2 DCs in a domain for fault tolerance
requirements and overloading issues.

Any updates, welcome to contact me!


Best regards,

Frances He


Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Migration All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB