Link to home
Start Free TrialLog in
Avatar of WitoldRyba
WitoldRybaFlag for Afghanistan

asked on

Server 2008 as domain controller in 2003 domain

Hi experts,

I currently run Server 2003 domain.. 2 DCs.
I have aquired server 2008, and am trying to promote the server to DC.

i have run adprep /forestprep
adprep /domainprep on the schema and infrastructure master (1of the DCs).
However as I try to dcpromo the server 2008, I get the message:
"to install domain controller into this active directory forest, you must first prepare the forest using adprep /forest prep"

I have looked through the debug logs, and

"Log on to the schema master primary for this forest, run the following command from the installation media to complete the forest update first:
adprep.exe /forestprep
and then rerun adprep.exe /domainprep on infrastructure master again. "
I do this, however I am still unable to promote server 2008.

Further info
Server 2008 is 64 bit.
Server 2003 DCs are 32 bit (1 DC is a global catalog), the other the primary infrastructure and schema server.

Please help

Avatar of Brian Pierce
Brian Pierce
Flag of United Kingdom of Great Britain and Northern Ireland image

Can I just clarify
Did you :-
       Place the the 2008 DVD on the Windows 2003 DC  
       Run  adprep from the SOURCES folder on the 2008 DVD.
       Run
          adprep /forestprep    and
          adprep /domainprep   and
          adprep /gpprep

Avatar of WitoldRyba

ASKER

Hi,

I will attempt to, I ve been running it through UNC, as the server 2003 does not have a DVD drive.
does that matter ?

WR
It shouldn't...
Don't know if you've noticed or whether it's a typo, but you've got an unwanted space in your original post. It should be /domainprep and /forestprep which you have to run on your existing DCs.

For clarity I've included the entire procedure for adding the second DC below.

--
Install Windows Server 2008 onto the new server which is intended to be promoted as a Domain Controller. Ensure the new server is assigned a routable static IP address on your IP subnet. Ensure the IP address is not included in any of your existing DHCP scopes. The only DNS server entry at this stage should be the IP address of the existing domain controller on your network.

After installation, join the new machine to the existing domain as a member server. This procedure is exactly the same as joining a workstation to the domain.

Since you are upgrading the Operating System on the new Domain Controller, you will need to add some values to the existing Active Directory schema, in order for the new server to become a Domain Controller. Windows Server 2008 supports more functionality than before, so a schema upgrade for the domain and forest is required to facilitate this and make this new feature set fully functional on the domain. To make the necessary changes, you must be logged on as the built-in Administrator user account, or a user with Domain, Schema and Enterprise Admin privileges.

Insert the Windows Server 2008 media into your current server (or connect remotely to the drive in another server as you please) . Open a command prompt and browse to sources\adprep folder within the Windows Server 2008 DVD media. Execute the command adprep /forestprep.

Next, execute adprep /domainprep . You must be logged on as a Domain Admin user for these steps to work correctly. Once these commands have run your Active Directory schema will have been extended to support Windows Server 2008 as a Domain Controller.

The next step is to promote the new server as a Domain Controller for the domain. Enter dcpromo at a command prompt and follow the wizard. When prompted, select the option for an additional domain controller in an existing domain. After the wizard completes, the new server will be acting as a Domain Controller for your domain. It is necessary at this point to restart the server for these changes to be applied.

In a single-domain Active Directory forest, all servers should also be Global Catalog servers. The Global Catalog is a required component of Active Directory which is used during logins to establish universal group membership for a user account. To promote the new server as a Global Catalog, open Active Directory Sites and Services from the Administrative Tools container within Control Panel or on the Start Menu. Double-click Sites, then Servers, followed by the name of the new server. Next, right-click "NTDS Settings" and select Properties. On the General tab, check the Global Catalog checkbox. Restart the new Domain Controller for changes to take effect.

If you wish the new server to become the holder of one or more Operations (FSMO) roles, you will need to transfer these roles to the new server. In a single-domain environment, you gain no benefits from spreading FSMO roles between Domain Controllers

The current FSMO role configuration for your network can be found by running the command "netdom query fsmo" at a command prompt on a Domain Controller.

To transfer one or more of these FSMO roles to the new domain controller, follow the information detailed in the following Microsoft Support article: http://support.microsoft.com/kb/324801. Please ensure any other information you follow is information regarding the TRANSFER of FSMO roles. Seizing FSMO roles is an emergency operation which should not be performed during this procedure.

DNS is a critical component of your Active Directory network. The easiest way to install the DNS role onto the new server is to follow the instructions outlined at http://technet2.microsoft.com/WindowsServer2008/en/library/3cf4d1b1-7a6e-4438-bf4f-22d9468c17321033.mspx You should be already using Active Directory-integrated DNS zones, which is the easiest method of allowing DNS replication to occur - DNS information is stored in Active Directory and replicates with Domain Controller replication traffic. To check if your DNS zones are AD-integrated (and convert them if not), please follow http://support.microsoft.com/kb/227844.

You probably want to enable DNS forwarding in the DNS console on the server, too. This forwards lookups for external domains to a DNS server at your ISP, which allows the server to effectively resolve DNS for external domains. More information on forwarders can be found at http://technet2.microsoft.com/WindowsServer/en/Library/ee992253-235e-4fd4-b4da-7e57e70ad3821033.mspx.

To move DHCP to the new server, you will need to first install the role. To install the role in Windows Server 2008, check the DHCP Server role option within the Add Roles wizard in the Server Manager. To correctly configure DHCP after the role is installed on your new server, you will need to ensure you configure it to distribute IP addresses which are in a different range to the IP scope defined on the other DHCP server. You should also ensure the correct DNS and WINS servers are entered into the scope options. Remember that the only DNS servers which should be configured on workstations are the Domain Controllers which are also acting as DNS servers - no ISP DNS server should ever be set through DHCP.

-tigermatt
hi all,

i have run: adprep /forestprep and /domainprep on both DCs
These were dome via RDP domain admin account.

the schema and infrastructure master, stills says
"Forest-wide information needs to be updated before the domain-wide information can be updated.
[User Action]
Log on to the schema master primary.westcourts.com.au for this forest, run the following command from the installation media to complete the forest update first:
adprep.exe /forestprep
and then rerun adprep.exe /domainprep on infrastructure master again.
"
And the 08 box is still unable to be promoted via DCPROMO

help..
W

well, it turned out that Mcafee Antivirus 8.5i was the problem, locking some files.
I uninstalled the antivirus app, and viola.

thanks for your help

W
can we have a point refund please - moderator

W
ASKER CERTIFIED SOLUTION
Avatar of Computer101
Computer101
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial