Download Adprep

 admin
-->

Applies To: Windows Server

For a better understanding of what will occur running the ADPREP /Domainprep command, I have referenced the KB article Enhancements to ADPREP.exe in Windows Server 2003 Service Pack 1(Q324392). The More Information section describes the functionality post-Windows 2003 SP1, including the Windows 2008 ADPREP. 2) ADPrep /ForestPrep needs to be run once in the forest. ADPrep can be found on the Windows Server 2012 R2 DVD. It only needs to be run once before the first Windows Server 2012 R2 Domain.

ADPREP.exe is a command-line tool that is available on the Windows Server 2008 installation disc in the ‘sources’adprep folder. When you run it, it must be run ADPREP from an elevated command. Adprep (plural adpreps) ( grammar ) A word that functions both as an adverb and as a preposition. 2000, Claudia Claridge, Multi-word Verbs in Early Modern English: A Corpus-based Study. Changes Made by Adprep.exe.; 2 minutes to read Contributors. In this article. Applies To: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012. Describes a problem in which the 'Adprep /rodcprep' command is not completed successfully because the infrastructure master for one or more active directory NDNCs is not reachable. A resolution is provided.

This topic provides background information about Active Directory DomainServices in Windows Server 2016 and explains the process for upgrading domain controllers from Windows Server 2012 or Windows Server 2012 R2.

Pre-requisites

The recommended way to upgrade a domain is to promote domain controllers that run newer versions of Windows Server and demote the older domain controllers as needed. That method is preferable to upgrading the operating system of an existing domain controller. This list covers general steps to follow before you promote a domain controller that runs a newer version of Windows Server:

  1. Verify the target server meets system requirements.
  2. Verify Application compatibility.
  3. Review Recommendations for moving to Windows Server 2016
  4. Verify security settings. For more information, see Deprecated features and behavior changes related to AD DS in Windows Server 2016.
  5. Check connectivity to the target server from the computer where you plan to run the installation.
  6. Check for availability of necessary operation master roles:
    • To install the first DC that runs Windows Server 2016 in an existing domain and forest, the machine where you run the installation needs connectivity to the schema master in order to run adprep /forestprep and the infrastructure master in order to run adprep /domainprep.
    • To install the first DC in a domain where the forest schema is already extended, you only need connectivity to the infrastructure master.
    • To install or remove a domain in an existing forest, you need connectivity to the domain naming master.
    • Any domain controller installation also requires connectivity to the RID master.
    • If you are installing the first read-only domain controller in an existing forest, you need connectivity to the infrastructure master for each application directory partition, also known as a non-domain naming context or NDNC.

Installation steps and required administrative levels

The following table provides a summary of the upgrade steps and the permission requirements to accomplish these steps

Installation actionCredential requirements
Install a new forestLocal Administrator on the target server
Install a new domain in an existing forestEnterprise Admins
Install an additional DC in an existing domainDomain Admins
Run adprep /forestprepSchema Admins, Enterprise Admins, and Domain Admins
Run adprep /domainprepDomain Admins
Run adprep /domainprep /gpprepDomain Admins
Run adprep /rodcprepEnterprise Admins

For additional information on new features in Windows Server 2016, see What's new in Windows Server 2016.

Supported in-place upgrade paths

Domain controllers that run 64-bit versions of Windows Server 2012 or Windows Server 2012 R2 can be upgraded to Windows Server 2016. Only 64-bit version upgrades are supported because Windows Server 2016 only comes in a 64-bit version.

If you are running this edition:You can upgrade to these editions:
Windows Server 2012 StandardWindows Server 2016 Standard or Datacenter
Windows Server 2012 DatacenterWindows Server 2016 Datacenter
Windows Server 2012 R2 StandardWindows Server 2016 Standard or Datacenter
Windows Server 2012 R2 DatacenterWindows Server 2016 Datacenter
Windows Server 2012 R2 EssentialsWindows Server 2016 Essentials
Windows Storage Server 2012 StandardWindows Storage Server 2016 Standard
Windows Storage Server 2012 WorkgroupWindows Storage Server 2016 Workgroup
Windows Storage Server 2012 R2 StandardWindows Storage Server 2016 Standard
Windows Storage Server 2012 R2 WorkgroupWindows Storage Server 2016 Workgroup

For more information about supported upgrade paths, see Supported Upgrade Paths

Adprep and Domainprep

If you are doing an in-place upgrade of an existing domain controller to the Windows Server 2016 operating system, you will need to run adprep /forestprep and adprep /domainprep manually. Adprep /forestprep needs to be run only once in the forest. Adprep /domainprep needs to be run once in each domain in which you have domain controllers that you are upgrading to Windows Server 2016.

Download the free and latest full version of Nero StartSmart 15.0 for Windows PC, which is a project launcher. The application lets you easily access the Nero premium application all features by converting your Computer to a digital media workstation. /nero-7-free-download-for-windows-10.html.

If you are promoting a new Windows Server 2016 server you do not need to run these manually. These are integrated into the PowerShell and Server Manager experiences.

For more information on running adprep see Running Adprep

Functional level features and requirements

Windows Server 2016 requires a Windows Server 2003 forest functional level. That is, before you can add a domain controller that runs Windows Server 2016 to an existing Active Directory forest, the forest functional level must be Windows Server 2003 or higher. If the forest contains domain controllers running Windows Server 2003 or later but the forest functional level is still Windows 2000, the installation is also blocked.

Windows 2000 domain controllers must be removed prior to adding Windows Server 2016 domain controllers to your forest. In this case, consider the following workflow:

  1. Install domain controllers that run Windows Server 2003 or later. These domain controllers can be deployed on an evaluation version of Windows Server. This step also requires running adprep.exe for that operating system release as a prerequisite.
  2. Remove the Windows 2000 domain controllers. Specifically, gracefully demote or forcibly remove Windows Server 2000 domain controllers from the domain and used Active Directory Users and Computers to remove the domain controller accounts for all removed domain controllers.
  3. Raise the forest functional level to Windows Server 2003 or higher.
  4. Install domain controllers that run Windows Server 2016.
  5. Remove domain controllers that run earlier versions of Windows Server.

Rolling back functional levels

After you set the forest functional level (FFL) to a certain value, you cannot roll back or lower the forest functional level, with the following exceptions:

  • If you are upgrading from Windows Server 2012 R2 FFL, you can lower it back to Windows Server 2012 R2.
  • If you are upgrading from Windows Server 2008 R2 FFL, you can lower it back to Windows Server 2008 R2.

After you set the domain functional level to a certain value, you cannot roll back or lower the domain functional level, with the following exceptions:

  • When you raise the domain functional level to Windows Server 2016 and if the forest functional level is Windows Server 2012 or lower, you have the option of rolling the domain functional level back to Windows Server 2012 or Windows Server 2012 R2.

For more information about features that are available at lower functional levels, see Understanding Active Directory Domain Services (AD DS) Functional Levels.

AD DS interoperability with other server roles and Windows operating systems

AD DS is not supported on the following Windows operating systems:

  • Windows MultiPoint Server
  • Windows Server 2016 Essentials

AD DS cannot be installed on a server that also runs the following server roles or role services:

  • Microsoft Hyper-V Server 2016
  • Remote Desktop Connection Broker

Administration of Windows Server 2016 servers

Use the Remote Server Administration Tools for Windows 10 to manage domain controllers and other servers that run Windows Server 2016. You can run the Windows Server 2016 Remote Server Administration Tools on a computer that runs Windows 10.

Step-by-Step for Upgrading to Windows Server 2016

The following is a simple example of upgrading the Contoso forest from Windows Server 2012 R2 to Windows Server 2016.

  1. Join the new Windows Server 2016 to your forest. Restart when prompted.

  2. Sign in to the new Windows Server 2016 with a domain admin account.

  3. In Server Manager, under Add Roles and Features, install Active Directory Domain Services on the new Windows Server 2016. This will automatically run adprep on the 2012 R2 forest and domain.

  4. In Server Manager, click the yellow triangle, and from the drop-down click Promote the server to a domain controller.

  5. On the Deployment Configuration screen, select Add a domain controller to an existing forest and click next.

  6. On the Domain Controller options screen, enter the Directory Services Restore Mode (DSRM) password and click next.

  7. For the remainder of the screens click Next.

  8. On the Prerequisite Check screen, click install. Once the restart has completed you can sign back in.

  9. On the Windows Server 2012 R2 server, in Server Manager, under tools, select Active Directory Module for Windows PowerShell.

  10. In the PowerShell windows use the Move-ADDirectoryServerOperationMasterRole to move the FSMO roles. You can type the name of each -OperationMasterRole or use numbers to specify the roles. For more information see Move-ADDirectoryServerOperationMasterRole

  11. Verify the roles have been moved by going to the Windows Server 2016 server, in Server Manager, under tools, select Active Directory Module for Windows PowerShell. Use the Get-ADDomain and Get-ADForest cmdlets to view the FSMO role holders.

  12. Demote and remove the Windows Server 2012 R2 domain controller. For information on demoting a dc, see Demoting Domain Controllers and Domains

  13. Once the server is demoted and removed you can raise the forest functional and domain functional levels to Windows Server 2016.

Next Steps

Adprep 2016

Compatible with Windows 10, 8, 7, Vista, XP and 2000

Optional Offer for WinThruster by Solvusoft EULA Privacy Policy Terms Uninstall

Overview of ADPREP.EXE

What Is ADPREP.EXE?

ADPREP.EXE is a type of EXE file associated with MSDN Disc 2465 developed by Microsoft for the Windows Operating System. The latest known version of ADPREP.EXE is 1.0.0.0, which was produced for Windows. This EXE file carries a popularity rating of 1 stars and a security rating of 'UNKNOWN'.

What Are EXE Files?

EXE ('executable') files, such as ADPREP.EXE, are files that contain step-by-step instructions that a computer follows to carry out a function. When you 'double-click' an EXE file, your computer automatically executes these instructions designed by a software developer (eg. Microsoft) to run a program (eg. MSDN Disc 2465) on your PC.

Every software application on your PC uses an executable file - your web browser, word processor, spreadsheet program, etc. - making it one of the most useful kinds of files in the Windows operating system. Without executable files like ADPREP.EXE, you wouldn't be able to use any programs on your PC.

Why Do I Have EXE Errors?

Because of their usefulness and ubiquity, EXE files are commonly used as a method of delivery for virus / malware infection. Often, viruses will be disguised as a benign EXE file (such as ADPREP.EXE) and distributed through SPAM email or malicious websites, which can then infect your computer when executed (eg. when you double-click the EXE file).

In addition, viruses can infect, replace, or corrupt existing EXE files, which can then lead to error messages when MSDN Disc 2465 or related programs are executed. Thus, any executable files that you download to your PC should be scanned for viruses before opening - even if you think it is from a reputable source.

When Do EXE Errors Occur?

EXE errors, such as those associated with ADPREP.EXE, most often occur during computer startup, program startup, or while trying to use a specific function in your program (eg. printing).


Common ADPREP.EXE Error Messages

The most common ADPREP.EXE errors that can appear on a Windows-based computer are:

Download Adprep Tool

  • 'ADPREP.EXE Application Error.'
  • 'ADPREP.EXE is not a valid Win32 application.'
  • 'ADPREP.EXE has encountered a problem and needs to close. We are sorry for the inconvenience.'
  • 'Cannot find ADPREP.EXE.'
  • 'ADPREP.EXE not found.'
  • 'Error starting program: ADPREP.EXE.'
  • 'ADPREP.EXE is not running.'
  • 'ADPREP.EXE failed.'
  • 'Faulting Application Path: ADPREP.EXE.'

These EXE error messages can appear during program installation, while a ADPREP.EXE-related software program (eg. MSDN Disc 2465) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your ADPREP.EXE error occurs is a critical piece of information in troubleshooting the problem.