Re: Adprep Fails

I have double checked the registry key location and it is correct (the key
was already there, I just change the value from 0 to 1).

Are you still with me? Anyone?

"TimeTraveller" <TimeTraveller@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:e%23UD0nKDGHA.3992@xxxxxxxxxxxxxxxxxxxxxxx
> Please check your registry key location.
>
> To Enable Schema Updates by Means of the Registry:
>
> It is not recommended to enable schema updates by directly editing the
> "Schema Update Allowed" registry key. Schema updates should be enabled
> through the console method, whenever possible. If for some reason the
> console method cannot be used, the following registry key may be edited
> directly:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
>
> To directly edit this registry key, perform the following steps:
> 1. Click Start, click Run, and then in the Open box, type: regedit
> Then press ENTER.
> 2. Locate and click the following registry key:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
> 3. On the Edit menu, click New, and then click DWORD Value.
> 4. Enter the value data when the following registry value is
> displayed:
>
> Value Name: Schema Update Allowed
> Data Type: REG_DWORD
> Base: Binary
> Value Data: Type 1 to enable this feature, or 0 (zero) to disable it.
>
>
> TT
>
>
> "Bill" <billyg1943@xxxxxxxxxxx> wrote in message
> news:%23qwCHKFDGHA.1028@xxxxxxxxxxxxxxxxxxxxxxx
>> Trying to Extend the Schema of SBS 2000 SP4/Exchange 2000 SP3 and am
>> geting the following error in ADPREP.LOG:
>>
>> Adprep created the log file ADPrep.log under
>> C:\WINNT\system32\debug\adprep\logs\20051229160747 directory.
>>
>> Adprep copied file d:\i386\schema.ini from installation point to local
>> machine under directory C:\WINNT.
>>
>> Adprep copied file d:\i386\sch19.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\sch20.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\sch21.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\sch22.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\sch23.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\sch24.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\sch25.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\sch26.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\sch27.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\sch28.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\sch29.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\sch30.ldf from installation point to local
>> machine under directory C:\WINNT\system32.
>>
>> Adprep copied file d:\i386\dcpromo.cs_ from installation point to local
>> machine under directory C:\WINNT\system32\debug\adprep\data.
>>
>> Adprep copied file d:\i386\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 HI-TECH-SERVER.
>>
>> 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=Hitechagencies,DC=com,DC=au.
>>
>> 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:\WINNT\system32\debug\adprep\logs\20051229160747 directory for detailed
>> 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\20051229160747 directory for more
>> information.
>>
>> LDIF.ERR says:
>> Entry DN:
>> CN=ms-DS-DnsRootAlias,CN=Schema,CN=Configuration,DC=Hitechagencies,DC=com,DC=au
>> Add error on line 4: Busy
>> The server side error is "A database error has occurred."
>> An error has occurred in the program
>>
>> There is also one Windows 2000 server DC in the domain and it is also
>> SP4.
>>
>> I have used Q325379 as my how-to. I have checked with adseit for phantom
>> DCs and run dcdiag without errors. I couldn't get adprep to run at all
>> until I applied KB Q325379 "Exchange schema conflict" and edited
>> HKLM\CCS\Services\NTDS\parameters\schema updates allowed=1.
>>
>> I thought this would be one of the easier steps in a swing migration!
>> Any ideas, anyone?
>>
>>
>>
>
>


.

Relevant Pages

  • Re: Adprep Fails
    ... Please check your registry key location. ... To Enable Schema Updates by Means of the Registry: ... > Adprep copied file d:\i386\schema.ini from installation point to local ...
    (microsoft.public.windows.server.sbs)
  • Re: Adprep Fails
    ... Not sure what you mean here: I already made this change to the registry ... > To Enable Schema Updates by Means of the Registry: ... >> Adprep copied file d:\i386\schema.ini from installation point to local ...
    (microsoft.public.windows.server.sbs)
  • RE: Adprep /Forestprep errors
    ... |point to local machine under directory C:\WINNT\system32. ... The base entry to start the search is ...
    (microsoft.public.windows.server.migration)
  • Re: 2000 AD to 2003 adprep
    ... Sounds like you need to do a metabase cleanup of the remnants of your former Exchange server. ... Adprep copied file D:\I386\schema.ini from installation point to local ... The schema conflict must be resolved before running adprep. ...
    (microsoft.public.windows.server.active_directory)
  • RE: Adprep /Forestprep errors
    ... The machine that I took offline was the shema master as I ... >|point to local machine under directory C:\WINNT. ...
    (microsoft.public.windows.server.migration)