I completed this step but it's still barking. Here is the output from the
log file. Any help is appreciated.
Adprep created the log file ADPrep.log under
C:\WINNT\system32\debug\adprep\logs\20040303104311 directory.
Adprep copied file C:\temp\schema.ini from installation point to local
machine under directory C:\WINNT.
Adprep copied file C:\temp\dcpromo.cs_ from installation point to local
machine under directory C:\WINNT\system32\debug\adprep\data.
Adprep copied file C:\temp\409.cs_ from installation point to local machine
under directory C:\WINNT\system32\debug\adprep\data.
Adprep successfully made the LDAP connection to the local domain controller
DS3SQL.
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 set the value of registry key
System\CurrentControlSet\Services\NTDS\Parameters\Schema Update Allowed to 1
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to
add is cn=ForestUpdates,CN=Configuration,DC=ds3cs,DC=com.
LDAP API ldap_add_s() finished, return code is 0x44
Adprep attempted to create the directory service object
cn=ForestUpdates,CN=Configuration,DC=ds3cs,DC=com.
[Status/Consequence]
The object exists so Adprep did not attempt to rerun this operation but is
continuing.
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to
add is cn=Operations,cn=ForestUpdates,CN=Configuration,DC=ds3cs,DC=com.
LDAP API ldap_add_s() finished, return code is 0x44
Adprep attempted to create the directory service object
cn=Operations,cn=ForestUpdates,CN=Configuration,DC=ds3cs,DC=com.
[Status/Consequence]
The object exists so Adprep did not attempt to rerun this operation but is
continuing.
Adprep was about to call the following LDAP API. ldap_search_s(). The base
entry to start the search is
cn=3467dae5-dedd-4648-9066-f48ac186b20a,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com.
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=3467dae5-dedd-4648-9066-f48ac186b20a,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com has completed.
[Status/Consequence]
The operation GUID already exists so Adprep did not attempt to rerun this
operation but is continuing.
Adprep was about to call the following LDAP API. ldap_search_s(). The base
entry to start the search is
cn=33b7ee33-1386-47cf-baa1-b03e06473253,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com.
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=33b7ee33-1386-47cf-baa1-b03e06473253,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com has completed.
[Status/Consequence]
The operation GUID already exists so Adprep did not attempt to rerun this
operation but is continuing.
Adprep was about to call the following LDAP API. ldap_search_s(). The base
entry to start the search is
cn=e9ee8d55-c2fb-4723-a333-c80ff4dfbf45,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com.
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=e9ee8d55-c2fb-4723-a333-c80ff4dfbf45,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com has completed.
[Status/Consequence]
The operation GUID already exists so Adprep did not attempt to rerun this
operation but is continuing.
Adprep was about to call the following LDAP API. ldap_search_s(). The base
entry to start the search is
cn=ccfae63a-7fb5-454c-83ab-0e8e1214974e,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com.
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=ccfae63a-7fb5-454c-83ab-0e8e1214974e,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com has completed.
[Status/Consequence]
The operation GUID already exists so Adprep did not attempt to rerun this
operation but is continuing.
Adprep was about to call the following LDAP API. ldap_search_s(). The base
entry to start the search is
cn=ad3c7909-b154-4c16-8bf7-2c3a7870bb3d,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com.
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=ad3c7909-b154-4c16-8bf7-2c3a7870bb3d,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com has completed.
[Status/Consequence]
The operation GUID already exists so Adprep did not attempt to rerun this
operation but is continuing.
Adprep was about to call the following LDAP API. ldap_search_s(). The base
entry to start the search is
cn=26ad2ebf-f8f5-44a4-b97c-a616c8b9d09a,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com.
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=26ad2ebf-f8f5-44a4-b97c-a616c8b9d09a,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com has completed.
[Status/Consequence]
The operation GUID already exists so Adprep did not attempt to rerun this
operation but is continuing.
Adprep was about to call the following LDAP API. ldap_search_s(). The base
entry to start the search is
cn=4444c516-f43a-4c12-9c4b-b5c064941d61,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com.
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=4444c516-f43a-4c12-9c4b-b5c064941d61,cn=Operations,cn=ForestUpdates,CN=Co
nfiguration,DC=ds3cs,DC=com.
[Status/Consequence]
The operation has not run or is not currently running. It will be run next.
Adprep was unable to complete because the call back function (null) failed.
[Status/Consequence]
Error message: Property msDS-FilterContainers was not found in csv file
C:\WINNT\system32\debug\adprep\data\dcpromo.csv. (0x80004005).
[User Action]
Check the log file Adprep.log, in the
C:\WINNT\system32\debug\adprep\logs\20040303104311 directory for more
information.
Adprep set the value of registry key
System\CurrentControlSet\Services\NTDS\Parameters\Schema Update Allowed to 1
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:\WINNT\system32\debug\adprep\logs\20040303104311 directory for more
information.
Regis Thornton said:
On domains running Windows Server 2003, the schema is enabled for updates
by default. In Windows 2000 Server, you must manually enable updates on the
schema master for the Active Directory forest. The account of the
administrator who updates the schema must either be a member of the Schema
Admins group or have been delegated sufficient permissions to modify the
schema.
To enable schema modifications for a Windows 2000 domain
1. At the command prompt, type Regsvr32 schmmgmt.dll.
2. On the taskbar, click the Start button, and then click Run.
3. Type mmc, and then click OK. The MMC Console1 window appears displaying a blank snap-in.
4. On the Console menu, click Add/Remove Snap-in. The Add/Remove Snap-in dialog box appears.
5. Click Add. The Add Standalone Snap-in dialog box appears displaying all
available snap-ins. Under Snap-in, select Active Directory Schema, and then
click Add.
6. Click Close. The Add/Remove Snap-in dialog box appears displaying the
Active Directory Schema snap-in that was added.
7. Click OK. The MMC Console1 window appears displaying the Active Directory Schema snap-in.
8. In the console tree, right-click Active Directory Schema, and then
select Operations Master. The Change Schema Master dialog box appears.
9. Click The Schema may be modified on this Domain Controller, and then
click OK. The MMC Console1 window appears displaying the Active Directory
Schema snap-in.
10. On the Console menu, click Exit. A Microsoft Management Console
message box appears prompting you to save the changes to Console1.
11. Click No. You have now configured the schema so that it can be extended.
----- DS3 wrote: -----
I am trying to upgrade a Windows 2000 server Active Directory to accommodate
Windows 2003 AD. When I run Adprep on the Windows 2000 server I get the
following error:
Adprep was unable to complete because the call back function (null) failed.
[Status/Consequence]
Error message: Property msDS-FilterContainers was not found in csv file
C:\WINNT\system32\debug\adprep\data\dcpromo.csv. (0x80004005).
[User Action]
Check the log file Adprep.log, in the
C:\WINNT\system32\debug\adprep\logs\20040301165729 directory for more
information.
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:\WINNT\system32\debug\adprep\logs\20040301165729 directory for more
information.
Any help is appreciated.
