Jump to content

Promoting Windows 2003 R2 to Domain Controller


Recommended Posts

Guest H. Hudson
Posted

We have a Windows 2003 Server Std with Exchange 2003. We are looking to

promote an addition server (Windows 2003 R2).

 

We tried to run adprep.exe /forestprep on the current domain controller from

the Windows 2003 R2 installation disk 2, but receive the following error:

 

'schupgr.exe' is not recognized as an internal or external command,

operable program or batch file.

Adprep was unable to upgrade the schema on the schema master.

[status/Consequence]

The schema will not be restored to its original state.

[user Action]

Check the Ldif.err log file in the

C:\WINDOWS\system32\debug\adprep\logs\2007083110756 directory for detailed

information.

 

Adprep was unable to update forest-wide information.

[status/Consequence]

Adprep requires access to existing forest-wide information from the schema

maste

r in order to complete this operation.

[user Action]

Check the log file, Adprep.log, in the

C:\WINNT\system32\debug\adprep\logs\20070831100756 directory for more

information.

 

Adprep.log is as follows:

Adprep created the log file ADPrep.log under

C:\WINDOWS\system32\debug\adprep\logs\20070831100756 directory.

 

 

 

Adprep copied file d:\cmpnents\r2\adprep\schema.ini from installation point

to local machine under directory C:\WINDOWS.

 

 

 

Adprep copied file d:\cmpnents\r2\adprep\sch31.ldf from installation point

to local machine under directory C:\WINDOWS\system32.

 

 

 

Adprep copied file d:\cmpnents\r2\adprep\dcpromo.csv from installation point

to local machine under directory C:\WINDOWS\system32\debug\adprep\data.

 

 

 

Adprep copied file d:\cmpnents\r2\adprep\409.csv from installation point to

local machine under directory C:\WINDOWS\system32\debug\adprep\data.

 

 

 

Adprep successfully made the LDAP connection to the local domain controller

MACOREIS.

 

 

 

Adprep was about to call the following LDAP API. ldap_search_s(). The base

entry to start the search is (null).

 

 

 

LDAP API ldap_search_s() finished, return code is 0x0

 

 

 

Adprep successfully retrieved information from the local directory service.

 

 

 

Adprep successfully initialized global variables.

 

[status/Consequence]

 

Adprep is continuing.

 

 

 

 

 

ADPREP WARNING:

 

 

 

Before running adprep, all Windows 2000 domain controllers in the forest

should be upgraded to Windows 2000 Service Pack 1 (SP1) with QFE 265089, or

to Windows 2000 SP2 (or later).

 

 

 

QFE 265089 (included in Windows 2000 SP2 and later) is required to prevent

potential domain controller corruption.

 

 

 

For more information about preparing your forest and domain see KB article

Q331161 at http://support.microsoft.com.

 

 

 

[user Action]

 

If ALL your existing Windows 2000 domain controllers meet this requirement,

type C and then press ENTER to continue. Otherwise, type any other key and

press ENTER to quit.

 

 

 

Adprep was about to call the following LDAP API. ldap_search_s(). The base

entry to start the search is

CN=UID,CN=Schema,CN=Configuration,DC=macore,DC=local.

 

 

 

LDAP API ldap_search_s() finished, return code is 0x0

 

 

 

Adprep successfully determined whether Microsoft Windows Services for UNIX

(SFU) is installed or not. If adprep detected SFU, adprep also verified that

Microsoft hotfix Q293783 for SFU has been applied.

 

 

 

Adprep was unable to upgrade the schema on the schema master.

 

[status/Consequence]

 

The schema will not be restored to its original state.

 

[user Action]

 

Check the Ldif.err log file in the

C:\WINDOWS\system32\debug\adprep\logs\20070831100756 directory for detailed

information.

 

 

 

Adprep set the value of registry key

System\CurrentControlSet\Services\NTDS\Parameters\Schema Update Allowed to 0

 

 

 

Adprep was unable to update forest-wide information.

 

[status/Consequence]

 

Adprep requires access to existing forest-wide information from the schema

master in order to complete this operation.

 

[user Action]

 

Check the log file, Adprep.log, in the

C:\WINDOWS\system32\debug\adprep\logs\20070831100756 directory for more

information.

 

Also this article has steps to take for Microsoft Exchange 2000 in Windows

2000 forests - http://support.microsoft.com/kb/325379

 

Are there any steps to take for Exchange 2003?

 

Any help would be appreciated.

 

Thanks

  • Replies 2
  • Created
  • Last Reply
Guest Danny Sanders
Posted

Re: Promoting Windows 2003 R2 to Domain Controller

 

> We tried to run adprep.exe /forestprep on the current domain controller

 

Does this server have SP 2 installed? If so you may have to uninstall SP 2,

run adprep, then reinstall SP2.

 

hth

DDS

 

"H. Hudson" <HHudson@discussions.microsoft.com> wrote in message

news:0179CE5C-913E-49AA-88F5-3C833A536D99@microsoft.com...

> We have a Windows 2003 Server Std with Exchange 2003. We are looking to

> promote an addition server (Windows 2003 R2).

>

> We tried to run adprep.exe /forestprep on the current domain controller

> from

> the Windows 2003 R2 installation disk 2, but receive the following error:

>

> 'schupgr.exe' is not recognized as an internal or external command,

> operable program or batch file.

> Adprep was unable to upgrade the schema on the schema master.

> [status/Consequence]

> The schema will not be restored to its original state.

> [user Action]

> Check the Ldif.err log file in the

> C:\WINDOWS\system32\debug\adprep\logs\2007083110756 directory for detailed

> information.

>

> Adprep was unable to update forest-wide information.

> [status/Consequence]

> Adprep requires access to existing forest-wide information from the schema

> maste

> r in order to complete this operation.

> [user Action]

> Check the log file, Adprep.log, in the

> C:\WINNT\system32\debug\adprep\logs\20070831100756 directory for more

> information.

>

> Adprep.log is as follows:

> Adprep created the log file ADPrep.log under

> C:\WINDOWS\system32\debug\adprep\logs\20070831100756 directory.

>

>

>

> Adprep copied file d:\cmpnents\r2\adprep\schema.ini from installation

> point

> to local machine under directory C:\WINDOWS.

>

>

>

> Adprep copied file d:\cmpnents\r2\adprep\sch31.ldf from installation point

> to local machine under directory C:\WINDOWS\system32.

>

>

>

> Adprep copied file d:\cmpnents\r2\adprep\dcpromo.csv from installation

> point

> to local machine under directory C:\WINDOWS\system32\debug\adprep\data.

>

>

>

> Adprep copied file d:\cmpnents\r2\adprep\409.csv from installation point

> to

> local machine under directory C:\WINDOWS\system32\debug\adprep\data.

>

>

>

> Adprep successfully made the LDAP connection to the local domain

> controller

> MACOREIS.

>

>

>

> Adprep was about to call the following LDAP API. ldap_search_s(). The base

> entry to start the search is (null).

>

>

>

> LDAP API ldap_search_s() finished, return code is 0x0

>

>

>

> Adprep successfully retrieved information from the local directory

> service.

>

>

>

> Adprep successfully initialized global variables.

>

> [status/Consequence]

>

> Adprep is continuing.

>

>

>

>

>

> ADPREP WARNING:

>

>

>

> Before running adprep, all Windows 2000 domain controllers in the forest

> should be upgraded to Windows 2000 Service Pack 1 (SP1) with QFE 265089,

> or

> to Windows 2000 SP2 (or later).

>

>

>

> QFE 265089 (included in Windows 2000 SP2 and later) is required to prevent

> potential domain controller corruption.

>

>

>

> For more information about preparing your forest and domain see KB article

> Q331161 at http://support.microsoft.com.

>

>

>

> [user Action]

>

> If ALL your existing Windows 2000 domain controllers meet this

> requirement,

> type C and then press ENTER to continue. Otherwise, type any other key and

> press ENTER to quit.

>

>

>

> Adprep was about to call the following LDAP API. ldap_search_s(). The base

> entry to start the search is

> CN=UID,CN=Schema,CN=Configuration,DC=macore,DC=local.

>

>

>

> LDAP API ldap_search_s() finished, return code is 0x0

>

>

>

> Adprep successfully determined whether Microsoft Windows Services for UNIX

> (SFU) is installed or not. If adprep detected SFU, adprep also verified

> that

> Microsoft hotfix Q293783 for SFU has been applied.

>

>

>

> Adprep was unable to upgrade the schema on the schema master.

>

> [status/Consequence]

>

> The schema will not be restored to its original state.

>

> [user Action]

>

> Check the Ldif.err log file in the

> C:\WINDOWS\system32\debug\adprep\logs\20070831100756 directory for

> detailed

> information.

>

>

>

> Adprep set the value of registry key

> System\CurrentControlSet\Services\NTDS\Parameters\Schema Update Allowed to

> 0

>

>

>

> Adprep was unable to update forest-wide information.

>

> [status/Consequence]

>

> Adprep requires access to existing forest-wide information from the schema

> master in order to complete this operation.

>

> [user Action]

>

> Check the log file, Adprep.log, in the

> C:\WINDOWS\system32\debug\adprep\logs\20070831100756 directory for more

> information.

>

> Also this article has steps to take for Microsoft Exchange 2000 in Windows

> 2000 forests - http://support.microsoft.com/kb/325379

>

> Are there any steps to take for Exchange 2003?

>

> Any help would be appreciated.

>

> Thanks

  • 2 months later...
Guest Jonathan
Posted

Re: Promoting Windows 2003 R2 to Domain Controller

 

Guess youve sen this but on another forum issue was purely that the scema

upgrade app was not on disk2 but disk 1

copy into place and away you go....


×
×
  • Create New...