<div>
I would personally just add an additional DC to your current abc domain. Have two domains is administration<br />
ovehead<br />

</div>


I would personally just add an additional DC to your current abc domain. Have two domains is administration
ovehead


<div>
1.as of now there is only 10=15 users. but in future it may increase up to 100-150<br />
<br />
please explain why you suggest to have additional domain of abc.com instead of a child domain xyz.com<br />
<br />
just to understand &nbsp;and contribute solutions to future EE queries<br />
<br />

</div>


1.as of now there is only 10=15 users. but in future it may increase up to 100-150

please explain why you suggest to have additional domain of abc.com instead of a child domain xyz.com

just to understand  and contribute solutions to future EE queries



<div>
the answer to this is why would you need a child domain in the first place<br />
<br />
and it's as i said above if you would require a different administration module (i.e OU structure , Group Policies.. etc) , and you already have your administrators there.<br />
<br />
so even for a 100 or 200 users , why complicate it ? <br />
<br />
a single domain 2 sites topology will suite you fine.
</div>


the answer to this is why would you need a child domain in the first place

and it's as i said above if you would require a different administration module (i.e OU structure , Group Policies.. etc) , and you already have your administrators there.

so even for a 100 or 200 users , why complicate it ?

a single domain 2 sites topology will suite you fine.

<div>
Thanks for your reply.<br />
<br />
Please advice how to deploy the additional domain of adc.com as all the PCs in the new office are added to xyz.com domain.<br />
<br />
Any easy way ? or demote and promote and add these PCs again.<br />
<br />
Thanks again<br />
<br />

</div>


Thanks for your reply.

Please advice how to deploy the additional domain of adc.com as all the PCs in the new office are added to xyz.com domain.

Any easy way ? or demote and promote and add these PCs again.

Thanks again



<div>
demote , promote as additional , and rejoin the PCs to the ABC.com domain.
</div>


demote , promote as additional , and rejoin the PCs to the ABC.com domain.

<div>
I am sorry for not mentioning about DNS. You are right we should have additional DNS in the remote location.<br />
<br />
I think there is a script to add PCs to the specified domain.<br />
<br />
If you are know that please send me the URL
</div>


I am sorry for not mentioning about DNS. You are right we should have additional DNS in the remote location.

I think there is a script to add PCs to the specified domain.

If you are know that please send me the URL

<div>
If you've only 10-15 workstations to join I would do them manually.
</div>


If you've only 10-15 workstations to join I would do them manually.

<div>
Beacause I am doing it remotely using pcanywhere connections speed is only 512kb. users there does not how to add and remove from domain. They only knows office. &nbsp;If I have a script I will try here in one PC and send it to them to run there.<br />
<br />
But that is not important. if you have please send me otherwise I will manage.
</div>


Beacause I am doing it remotely using pcanywhere connections speed is only 512kb. users there does not how to add and remove from domain. They only knows office.  If I have a script I will try here in one PC and send it to them to run there.

But that is not important. if you have please send me otherwise I will manage.

<div>
<a href="http://support.microsoft.com/kb/150493" rel="ugc">http://support.microsoft.com/kb/150493</a>
</div>


http://support.microsoft.com/kb/150493 [http://support.microsoft.com/kb/150493]

<div>
Use RDP to connect, its much quicker
</div>


<div>
<br />
what about DC replication?<br />
<br />
how often it will replication?<br />
<br />
Is it possibel to schedule the replication?<br />
<br />
<br />

</div>



what about DC replication?

how often it will replication?

Is it possibel to schedule the replication?




<div>
When you create a site link, by default replication occurs every 15mins, you can change this to a longer period if you wish
</div>


When you create a site link, by default replication occurs every 15mins, you can change this to a longer period if you wish

<div>
My manager asked me why you decided to go for ADC not child domain.<br />
Your answer for that is highly appreciated.
</div>


My manager asked me why you decided to go for ADC not child domain.
Your answer for that is highly appreciated.

<div>
Only use a child domain if you require security to be controlled by another team, or if you require separate security boundaries
</div>


Only use a child domain if you require security to be controlled by another team, or if you require separate security boundaries

<div>
<div class="content wysiwyg-content">
I have a domain controller &nbsp;abc.com. installed in my office with 250 users<br />
we have started one new office out of the country. right now we have a dc installed xyz.com.<br />
we have data line to that office.<br />
<br />
Which is the recommended way to have DC in the new office?<br />
<br />
make xyz.com as a child domain of adc.com?<br />
or remove the current DC and install an additional DC?<br />
or other good idea.<br />
<br />
Could anyone help<br />
<br />

</div>
</div>


I have a domain controller  abc.com. installed in my office with 250 users
we have started one new office out of the country. right now we have a dc installed xyz.com.
we have data line to that office.

Which is the recommended way to have DC in the new office?

make xyz.com as a child domain of adc.com?
or remove the current DC and install an additional DC?
or other good idea.

Could anyone help



Suggestion on installing domain controller

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

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).

Windows Server 2003

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.