Install application on domain controller

If you are installing AD DS on a remote server, you need to specify the credentials, by design. If current user credentials are not sufficient to perform the installation, click Change If you are installing a new child domain, click Add a new domain to an existing forest , for Select domain type , select Child Domain , type or browse to the name of the parent domain DNS name for example, corp.

If you are installing a new domain tree, click Add new domain to an existing forest , for Select domain type , choose Tree Domain , type the name of the root domain for example, corp. If you are installing a new forest, click Add a new forest and then type the name of the root domain for example, corp.

For more information about which options on this page are available or not available under different conditions, see Domain Controller Options.

For more information, see Password Replication Policy. If you are adding a domain controller to an existing domain, select the domain controller that you want to replicate the AD DS installation data from or allow the wizard to select any domain controller.

If you are installing from media, click Install from media path type and verify the path to the installation source files, and then click Next.

You cannot use install from media IFM to install the first domain controller in a domain. IFM does not work across different operating system versions. In other words, in order to install an additional domain controller that runs Windows Server by using IFM, you must create the backup media on a Windows Server domain controller.

On the Preparation Options page, type credentials that are sufficient to run adprep. On the Review Options page, confirm your selections, click View script if you want to export the settings to a Windows PowerShell script, and then click Next. On the Prerequisites Check page, confirm that prerequisite validation completed and then click Install.

On the Results page, verify that the server was successfully configured as a domain controller. The server will be restarted automatically to complete the AD DS installation. In the second stage, a server is attached to the RODC account. The second stage can be completed by a member of the Domain Admins group or a delegated domain user or group. In the Tasks Pane right pane , click Pre-create a read-only domain controller account. On the Network Credentials page, under Specify the account credentials to use to perform the installation , click My current logged on credentials or click Alternate credentials , and then click Set.

In the Windows Security dialog box, provide the user name and password for an account that can install the additional domain controller. To install an additional domain controller, you must be a member of the Enterprise Admins group or the Domain Admins group.

When you are finished providing credentials, click Next. On the Select a Site page, select a site from the list or select the option to install the domain controller in the site that corresponds to the IP address of the computer on which you are running the wizard, and then click Next. On the Additional Domain Controller Options page, make the following selections, and then click Next :. If you do not want the domain controller to be a DNS server, clear this option. However, if you do not install the DNS server role on the RODC and the RODC is the only domain controller in the branch office, users in the branch office will not be able to perform name resolution when the wide area network WAN to the hub site is offline.

Global catalog : This option is selected by default. It adds the global catalog, read-only directory partitions to the domain controller, and it enables global catalog search functionality. If you do not want the domain controller to be a global catalog server, clear this option. However, if you do not install a global catalog server in the branch office or enable universal group membership caching for the site that includes the RODC, users in the branch office will not be able to log on to the domain when the WAN to the hub site is offline.

Read-only domain controller. When you create an RODC account, this option is selected by default and you cannot clear it. If you selected the Use advanced mode installation check box on the Welcome page, the Specify the Password Replication Policy page appears. By default, no account passwords are replicated to the RODC, and security-sensitive accounts such as members of the Domain Admins group are explicitly denied from ever having their passwords replicated to the RODC.

To add other accounts to policy, click Add , then click Allow passwords for the account to replicate to this RODC or click Deny passwords for the account from replicating to this RODC and then select the accounts. You can type the name of only one security principal.

To search the directory for a specific user or group, click Set. In Select User or Group , type the name of the user or group. We recommend that you delegate RODC installation and administration to a group. This user or group will also have local administrative rights on the RODC after the installation.

If you do not specify a user or group, only members of the Domain Admins group or the Enterprise Admins group will be able to attach the server to the account. On the Summary page, review your selections. Click Back to change any selections, if necessary. To save the settings that you selected to an answer file that you can use to automate subsequent AD DS operations, click Export settings.

Type a name for your answer file, and then click Save. This second stage can be completed in the branch office where the RODC will be located. The server where you perform this procedure must not be joined to the domain. On the Select features page, select any additional features that you want to install and click Next.

On the Results page, verify Installation succeeded , and click Promote this server to a domain controller to start the Active Directory Domain Services Configuration Wizard. On the Deployment Configuration page, click Add a domain controller to an existing domain , type the name of the domain for example, emea.

On the Additional Options page, if you are installing from media, click Install from media path type and verify the path to the installation source files, select the domain controller that you want to replicate the AD DS installation data from or allow the wizard to select any domain controller and then click Next.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No.

Any additional feedback? Note If you do not run adprep. The credential requirements are as follows: To introduce the first Windows Server domain controller in the forest, you need to supply credentials for a member of Enterprise Admins group, the Schema Admins group, and the Domain Admins group in the domain that hosts the schema master.

Warning As the previous option does not confirm the password, use extreme caution: the password is not visible. Warning Providing or storing a clear text password is not recommended. Note The -credential argument is only required when you are not currently logged on as a member of the Enterprise Admins group. Note In order to manage a domain-joined computer using Server Manager on a workgroup server, or vice-versa, additional configuration steps are needed. Note The name of the domain and current user credentials are supplied by default only if the machine is domain-joined and you are performing a local installation.

Submit and view feedback for This product This page. View all page feedback. In this article. Specifies the account with Enterprise Admins and Schema Admins group membership that can prepare the forest, according to the rules of Get-Credential and a PSCredential object.

Specifies whether to continue installing this writable domain controller, despite the fact that another writable domain controller account with the same name is detected. Specifies the names of user accounts, group accounts, and computer accounts whose passwords can be replicated to this RODC. Specifies whether the AD DS installation operation performs only critical replication before reboot and then continues.

Specifies the name of the user or group that can install and administer the RODC. Any more roles that you add to the Domain Controllers are basically putting the machine at risk for something to happen or to be compromised.

DeChache Supreme [H]ardness. Joined Oct 30, Messages 7, For the most part you shouldn't run anything that isn't necessary on a infrastructure server. If for no other reason that people can at least try to work if an update brings down the app server but if the infrastructure is down they are dead in the water.

Joined Nov 4, Messages 9, DeChache said:. Click to expand Eiolon Gawd. Joined Apr 6, Messages Besides the issues presented above, I prefer not to put all my eggs in one basket. If it can be afforded, I like to dedicate servers to specific apps. Joined Jul 19, Messages 11, The less you do on a DC, the better.

Also, depends on the size of your company, as Sometimes you'll install software that borks up your computer. Imagine installing something on a domain controller Oh boy I remember a couple of years ago If a domain controller cannot be stored in a locked room in branch locations, you should consider deploying RODCs in those locations. Whenever possible, you should run virtual domain controllers in branch offices on separate physical hosts than the other virtual machines in the site.

In branch offices in which virtual domain controllers cannot run on separate physical hosts from the rest of the virtual server population, you should implement TPM chips and BitLocker Drive Encryption on hosts on which virtual domain controllers run at minimum, and all hosts if possible.

Depending on the size of the branch office and the security of the physical hosts, you should consider deploying RODCs in branch locations. If your infrastructure includes locations in which only a single physical server can be installed, a server capable of running virtualization workloads should be installed in the remote location, and BitLocker Drive Encryption should be configured to protect all volumes in the server.

One virtual machine on the server should run an RODC, with other servers running as separate virtual machines on the host.

For more information about deploying and securing virtualized domain controllers, see Running Domain Controllers in Hyper-V. For more detailed guidance for hardening Hyper-V, delegating virtual machine management, and protecting virtual machines, see the Hyper-V Security Guide Solution Accelerator on the Microsoft website. You should run all domain controllers on the newest version of Windows Server that is supported within your organization and prioritize decommissioning of legacy operating systems in the domain controller population.

By keeping your domain controllers current and eliminating legacy domain controllers, you can often take advantage of new functionality and security that may not be available in domains or forests with domain controllers running legacy operating system.

As for any security-sensitive and single-purpose configuration, we recommend that you deploy the operating system in Server Core installation option. It provides multiple benefits, such as minimizing attack surface, improving performance and reducing the likelihood of human error. It is recommended that all operations and management are performed remotely, from dedicated highly secured endpoints such as Privileged access workstations PAW or Secure administrative hosts.

A number of freely available tools, some of which are installed by default in Windows, can be used to create an initial security configuration baseline for domain controllers that can subsequently be enforced by GPOs. These tools are described in Administer security policy settings section of Microsoft operating systems documentation.

Group Policy Objects that link to all domain controllers OUs in a forest should be configured to allow RDP connections only from authorized users and systems for example, jump servers. This can be achieved through a combination of user rights settings and WFAS configuration and should be implemented in GPOs so that the policy is consistently applied. If it is bypassed, the next Group Policy refresh returns the system to its proper configuration. Although it may seem counterintuitive, you should consider patching domain controllers and other critical infrastructure components separately from your general Windows infrastructure.

If you leverage enterprise configuration management software for all computers in your infrastructure, compromise of the systems management software can be used to compromise or destroy all infrastructure components managed by that software.

By separating patch and systems management for domain controllers from the general population, you can reduce the amount of software installed on domain controllers, in addition to tightly controlling their management. One of the checks that is performed as part of an Active Directory Security Assessment is the use and configuration of Internet Explorer on domain controllers.