-->
- Windows Server 2008 Adprep Download
- Windows Server 2008 R2 Adprep Download
- Windows Server 2008 Adprep Download
Applies To: Windows Server
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. Microsoft has a link from technet to a download of adprep.exe which comes with the both 32-bit/64-bit/IA versions and you extract it to the root of C: and then through cmd prompt run adprep /forestprep. I type adprep /forestprep and it comes up with a message saying to make sure your Windows 2000 DC's are all at least SP2, blah blah blah.
Windows 2008 R2 Adprep – sivarajan.com I know there are confusions around 32 bit and 64 bit versions of ADPREP. Windows Server 2008 R2 includes a 32-bit version and a 64-bit version of Adprep.exe. Adprep in Windows Server 2012 – Active Directory. Feb 04, 2013. Installation, you can also run Adprep.exe separately in advance of. Run Windows Server 2008 R2 ADPREP. The Windows Server 2008 R2 ADPREP has been modified to prevent antivirus software from interfering with /FORESTPREP. Run the Windows Server 2008 R2 ADPREP if you have the Windows Server 2008 R2 installation media available. Retry running ADPREP with 3rd-party services disabled. 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. In Server Manager, click the yellow triangle, and from the drop-down click Promote the server to a domain controller. Feb 03, 2009 Any edition of Windows Server 2008 may be installed without activation and evaluated for an initial 60 days. If you need more time to evaluate Windows Server 2008, the 60 day evaluation period may be reset (or re-armed) three times, extending the original 60 day evaluation period by up to 180 days for a total possible evaluation time of 240 days.
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:
- Verify the target server meets system requirements.
- Verify Application compatibility.
- Review Recommendations for moving to Windows Server 2016
- Verify security settings. For more information, see Deprecated features and behavior changes related to AD DS in Windows Server 2016.
- Check connectivity to the target server from the computer where you plan to run the installation.
- 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 action | Credential requirements |
|---|---|
| Install a new forest | Local Administrator on the target server |
| Install a new domain in an existing forest | Enterprise Admins |
| Install an additional DC in an existing domain | Domain Admins |
| Run adprep /forestprep | Schema Admins, Enterprise Admins, and Domain Admins |
| Run adprep /domainprep | Domain Admins |
| Run adprep /domainprep /gpprep | Domain Admins |
| Run adprep /rodcprep | Enterprise 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 Standard | Windows Server 2016 Standard or Datacenter |
| Windows Server 2012 Datacenter | Windows Server 2016 Datacenter |
| Windows Server 2012 R2 Standard | Windows Server 2016 Standard or Datacenter |
| Windows Server 2012 R2 Datacenter | Windows Server 2016 Datacenter |
| Windows Server 2012 R2 Essentials | Windows Server 2016 Essentials |
| Windows Storage Server 2012 Standard | Windows Storage Server 2016 Standard |
| Windows Storage Server 2012 Workgroup | Windows Storage Server 2016 Workgroup |
| Windows Storage Server 2012 R2 Standard | Windows Storage Server 2016 Standard |
| Windows Storage Server 2012 R2 Workgroup | Windows 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.
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:
- 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.
- 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.
- Raise the forest functional level to Windows Server 2003 or higher.
- Install domain controllers that run Windows Server 2016.
- 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.
Join the new Windows Server 2016 to your forest. Restart when prompted.
Sign in to the new Windows Server 2016 with a domain admin account.
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.
In Server Manager, click the yellow triangle, and from the drop-down click Promote the server to a domain controller.
On the Deployment Configuration screen, select Add a domain controller to an existing forest and click next.
On the Domain Controller options screen, enter the Directory Services Restore Mode (DSRM) password and click next.
For the remainder of the screens click Next.
On the Prerequisite Check screen, click install. Once the restart has completed you can sign back in.
On the Windows Server 2012 R2 server, in Server Manager, under tools, select Active Directory Module for Windows PowerShell.
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
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-ADDomainandGet-ADForestcmdlets to view the FSMO role holders.Demote and remove the Windows Server 2012 R2 domain controller. For information on demoting a dc, see Demoting Domain Controllers and Domains
Once the server is demoted and removed you can raise the forest functional and domain functional levels to Windows Server 2016.
Next Steps
Before you can introduce Windows Server 2008 domain controllers intoexisting Windows 2000 or Windows Server 2003 domains, you must preparethe forest and domains with the ADPREP utility. ADPREP.exeis a command-line tool that extends the Active Directory schema, andupdates permissions as necessary to prepare a forest and domain for adomain controller that runs the Windows Server 2008 operating system.Note: ADPREP was also available in Windows Server2003 and Windows Server 2003 R2. In Windows Server 2008, ADPREP followsthe same logic and performs similar tasks to prepare for the upgrade toWindows Server 2003 or Windows Server 2003 R2. Please read my 'Windows 2003 ADPREP' article for more information on that.
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 prompt. To open an elevated command prompt, click Start, right-click Command Prompt, and then click Run as administrator.
Where should I run ADPREP?
ADPREP /forestprep must be run on the SchemaMaster of a forest and under the credentials of someone in the SchemaAdmins and Enterprise Admins groups.
ADPREP /domainprep must be run on the Infrastructure Master of a domain and under the credentials of someone in the Domain Admins group.
Important: Since at the time of running ADPREP youstill do not have any Windows Server 2008 Domain Controllers, it shouldbe made clear that these commands MUST be run on EXISTING Windows 2000or Windows Server 2003 Domain Controllers. That is why you MUST makesure you keep a copy of the 32-bit version of the Windows Server 2008installation DVD. You cannot use the 64-bit version of the installationmedia to run ADPREP on 32-bit versions of Windows 2000/2003. BecauseWindows Server 2008 installation media is 64-bit by default, rememberto request the 32-bit version when you get your copy. In case you don'thave the 32-bit version available, you can also use the evaluationversion of Windows Server 2008 32-bit installation media to run ADPREP,so just download the file from Microsoft's website, and use it to run ADPREP on your 32-bit Windows 2000/2003 DCs.
What does ADPREP do?
Before running ADPREP, all Windows 2000 Active Directory DomainControllers in the forest should be upgraded to Windows 2000 ServicePack 4 (SP4) or later.
ADPREP /forestprep command extends the schema withquite a few new classes and attributes. These new schema objects arenecessary for the new features supported by Windows Server 2008. Youcan view the schema extensions by looking at the .ldf files in the 'sources'adprepdirectory on the Windows Server 2008 DVD. These files contain LDIFentries for adding and modifying new and existing classes andattributes.
ADPREP /domainprep creates new containers and objects, modifies ACLs on some objects, and changes the meaning of the Everyone security principal.
Before you can run ADPREP /domainprep, you must be sure that the updates from /forestprep have replicated to all domain controllers in the forest.
You can view detailed output of the ADPREP command by looking at the log files in the %Systemroot%'system32'debug'adprep'logsdirectory. Each time ADPREP is executed, a new log file is generatedthat contains the actions taken during that particular invocation. Thelog files are named based on the time and date ADPREP was run.
Once you’ve run both /forestprep and /domainprep and allowed timefor the changes to replicate to all domain controllers, you can thenstart upgrading your domain controllers to Windows Server 2008 orinstalling new Windows Server 2008 domain controllers.
Running ADPREP
Windows Server 2008 Adprep Download
In order to run ADPREP, insert the DVD media of Windows Server2008 into the DVD drive of the appropriate Windows 2000/2003 DC, which,as noted above, should be the Schema Master of a forest.
Lamer note: You can use a network path or even copy the files locally to the server if you don't have a DVD drive on your DC…
If you're prompted to install Windows Server 2008, do NOT install it. Close the window instead.
Browse to the 'sources'adprep directory.
Open a Command Prompt window (Click Start > Run > CMD > Enter), and drag the ADPREP.exe file to the Command Prompt window.
Lamer note: If you can't drag 'n drop, you can simply type the path… duh…
In the Command Prompt window, type the following command:
In order to prevent accidental running of the command, you must press the 'C' key on your keyboard, then press Enter.Command will begin to load a bunch of LDIF files containing all thenecessary changes to the existing AD and Schema. Process will take afew moments.
When done, you'll be prompted. Make sure you let the existingDomain Controllers replicate all the changes throughout the entireforest BEFORE proceeding to the next step.
Next, go to the Infrastructure Master of eachdomain that you wish to upgrade and insert the DVD media of WindowsServer 2008 into the DVD drive. Repeat the instructions to open the Command Prompt window, and type:
Unlike the /forestprep action which takes some time, the /domainprep action is almost instantaneous.
Note: The existing Windows 2000/2003 domain MUST bein Native mode, as not Windows NT 4.0 BDCs are supported by WindowsServer 2008 DCs. Therefore, if that is not the case, you'll get thiserror:
Switch your domain to Native mode or above, then repeat the operation.
Again, make sure you let the existing Domain Controllersreplicate all the changes throughout the domain BEFORE proceeding tothe next step.
Repeat the /domainprep action for each domain in the forest that requires new Windows Server 2008 Domain Controllers.
Windows 2000 Domain Notes
When upgrading Windows 2000 domains, an additional command must be run before installing the first Windows Server 2008 DC.
Go to the Infrastructure Master of each domain thatyou wish to upgrade and insert the DVD media of Windows Server 2008into the DVD drive. Repeat the instructions to open the Command Promptwindow, and type:
This command performs similar updates as domainprep. However, thiscommand also provides updates that are necessary to enable ResultantSet of Policy (RSOP) Planning Mode functionality. In Active Directoryenvironments that run Microsoft Windows® 2000, this command performsupdates during off-peak hours. This minimizes replication traffic thatis created in those environments by updates to file system permissionsand Active Directory permissions on existing Group Policy objects(GPOs). This command is also available on Microsoft Windows Server 2003with Service Pack 1 (SP1) or later.
Windows 2003 Domain and first RODC Notes
In Windows Server 2008, a new Domain Controller installation optionis available, called Read Only domain Controller. I will not go intodetail about RODCs in this article (search my site for more informationabout RODCs), however, in order to enable the installation of the firstRODC in an existing Windows Server 2003 Active Directory forest, whereyou have already added at least one Windows Server 2008 regular DC, youmust run the following command:
This command updates permissions on application directory partitionsto enable replication of the partitions to RODCs. This operation runsremotely; it contacts the infrastructure master in each domain toupdate the permissions. You need to run this command only once in theforest. You can run this command on any computer in the forest. Youmust be a member of the Enterprise Admins group to run this command.
You are now ready to introduce your first Windows Server 2008 Domain Controller. Read my 'Installing Active Directory on Windows Server 2008' article for more information on that.