<div>
Firstly, ensure DNS is functioning on the 2nd DC.<br />
Secondly, set the 2nd DC as a Global Catalogue.<br />
Now, move teh FSMO Roles from one server to another (1st to 2nd) <a href="http://www.petri.co.il/transferring_fsmo_roles.htm" rel="ugc">http://www.petri.co.il/transferring_fsmo_roles.htm</a><br />
<br />
Leave it 90 mins to ensure everything has moved.<br />
<br />
Now the demotion should be safe.<br />
<br />
-BBRazz<br />

</div>


<div>
<br />
What about the DNS there is any need to promote from secondary to &nbsp;primary 
</div>


<div>
Just to add to this, there is no such thing as primary and secondary Domain controllers in AD. &nbsp;As long as you make sure that DNS is functioning on your secondary and you have at least one other Global Catalog server on the network then you can just demote the old server. &nbsp;The FSMO roles will get transferred automatically on demotion. <br />

</div>


<div>
As per waynewilliams note, hence I referred to as 1 and 2 not primary and secondary :P<br />
Manually moving the FSMO roles ensures a cleaner demotion.<br />
To majid_moeir, DNS for an AD network is stored in Active Directory and as such the zone will be an AD Integrated and shouldn't need ammending.<br />
-BBRazz<br />

</div>


<div>
there is secondary dns on the additional domain , shown as secondary dns zone , and i can click to upgrade i know what u said about integrated active directory zone ,but it is secondary integrated active directory zone
</div>


<div>
It looks like you have a standard secondary DNS zone. &nbsp;You can change this to a AD integrated zone in the DNS console.<br />
<br />
There are no secondary AD-integrated zones.<br />

</div>


<div>
As per wayne, we'd recommend changing this to an AD integrated zone.<br />
In DNS Manager, expand the DNS Server object.<br />
Expand the Forward Lookup Zones folder.<br />
Right-click the zone you created, and then click Properties.<br />
On the General tab, the Zone Type value is set to Primary. Click Change to change the zone type.<br />
In the Change Zone Type dialog box, click DS Integrated Primary, and then click OK.<br />
The DNS server writes the zone database into Active Directory. <br />
-BBRazz<br />
&nbsp;<br />

</div>


<div>
to BBrazz<br />
i think what u mean is first <br />
1-Manually moving the FSMO roles ensures <br />
2-then shut down the the primary dns, and change dns zone on the additional domain to primary then to dns integrated <br />
this are &nbsp;the steps<br />

</div>


<div>
Not just shut down the primary DNS, but run DCPROMO to demote the server.<br />
-BBRazz<br />

</div>


<div>
to &nbsp;waynewilliams:<br />
can just demote the old server. &nbsp;The FSMO roles will get transferred automatically on demotion. <br />
how can i do the demote to the old server ????<br />

</div>


<div>
to BBRazz:<br />
can you please tell the steps by order that needs to be done 
</div>


<div>
Configure DNS to be AD integrated as per above post<br />
Move FSMO rolse as per <a href="http://www.petri.co.il/transferring_fsmo_roles.htm" rel="ugc">http://www.petri.co.il/transferring_fsmo_roles.htm</a><br />
Demotion - <a href="http://revver.com/video/1097733/how-to-demote-your-domain-controller-active-directory/" rel="ugc">http://revver.com/video/10<wbr />97733/how-<wbr />to-demote-<wbr />your-domai<wbr />n-controll<wbr />er-active-<wbr />directory/<wbr /></a> &nbsp;DONT TICK &quot;This is the last domain controller&quot;<br />
-BBRazz<br />

</div>


<div>
to BBRazz:<br />
u think by demoting this domain it will not rpelicate the fsmo role autoatically <br />
or fsmo role needs to be done 
</div>


<div>
It will do it automatically, but I personnally move them manually prior to demotion to ensure they are completed successfully.<br />
-BBRazz<br />

</div>


<div>
i will give try now and i will get back to u <br />
last thing when making the dns seandery to primary and intergrated the<br />
&nbsp;old dns intergated zon(old primary domain) &nbsp;is still one line there is no problem in this 
</div>


<div>
<div class="content wysiwyg-content">
We have two windows 2003 server one primary and other additional domain.<br />
Primary with &nbsp;DNS and additional with secondary DNS, and I have 4 child domain after this tow,<br />
The primary has big problem but still on line I want to promote the additional domain as Primary domain.<br />
&nbsp;Reformat the old primary and make additional for promoted one <br />
<br />
<br />
What is the best practice recommended by Microsoft in this scenario needs , and also that there will be no problem in all forest main and child &nbsp;domain and also for the group policy <br />

</div>
</div>


We have two windows 2003 server one primary and other additional domain.
Primary with  DNS and additional with secondary DNS, and I have 4 child domain after this tow,
The primary has big problem but still on line I want to promote the additional domain as Primary domain.
 Reformat the old primary and make additional for promoted one 


What is the best practice recommended by Microsoft in this scenario needs , and also that there will be no problem in all forest main and child  domain and also for the group policy 


How  to Promote the additional domain controller to be the primary domain controller

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).