Re: ADPREP issue - Migration

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

True - Should not assume Swing SBSMigration BUT this is SBS NG and you would
assume that it would be an SBS box which leads to .... :>) Glad you got it
sorted. Good work!

--
Frank McCallister SBS MVP
COMPUMAC
"TimeTraveller" <TimeTraveller@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OaqL9I56FHA.1864@xxxxxxxxxxxxxxxxxxxxxxx
> OK Just fixed the issue.
>
> Step 2 here
>
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;325379#XSLTH4158120122120121120120
>
> Syntax is not obvious but sorted ok now.
>
> Yes Straight 2000 with exchange
>
> I am adding a second server which is a 2003.
>
> Assumption should not be made when the word MIGRATION is used thats it has
> anything to do with SBSMIGRATION, they didnt invent migration.
>
> Its a very straight forward thing that I need to do here.
>
> TT
> "Frank McCallister SBS MVP" <anonymous> wrote in message
> news:%23P2wV446FHA.4012@xxxxxxxxxxxxxxxxxxxxxxx
>> TT
>>
>> Is this Standard 2000 with Standard Exchange or SBS 2000?
>>
>> --
>> Frank McCallister SBS MVP
>> COMPUMAC
>> "TimeTraveller" <TimeTraveller@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:uK0izG36FHA.3232@xxxxxxxxxxxxxxxxxxxxxxx
>>> Update on messages
>>>
>>> C:\Documents and Settings\Administrator\My Documents>ldifde -i -f
>>> inetorgpersonp
>>> revent.ldf -v -c DC=X "dc=jdarecruitment,dc=com"
>>> Connecting to "pheonix.jdarecruitment.com"
>>> Logging in as current user using SSPI
>>> Importing directory from file "inetorgpersonprevent.ldf"
>>> Loading entries
>>> 1:
>>> CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=jdarecruitment,dc=com
>>>
>>>
>>> Add error on line 1: Unwilling To Perform
>>> The server side error is "Schema update is not allowed on this DC.
>>> Either the re
>>> gistry key is not set or the DC is not the schema FSMO Role Owner."
>>> 0 entries modified successfully.
>>> An error has occurred in the program
>>> "TimeTraveller" <TimeTraveller@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>>> message news:uzIleC36FHA.3684@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Its not a swing its the update of objects prior to a Windows 2003
>>>> upgrade from Windows 2000 Server
>>>>
>>>>
>>>> "Frank McCallister SBS MVP" <anonymous> wrote in message
>>>> news:eaQcNy26FHA.1188@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> Hi TT
>>>>>
>>>>> You need to contact Jeff directly by email on this. Did you use his
>>>>> Domain Audit Guide before startiing the Swing?
>>>>>
>>>>> --
>>>>> Frank McCallister SBS MVP
>>>>> COMPUMAC
>>>>> "TimeTraveller" <TimeTraveller@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>>>>> message news:%23gdyKi26FHA.252@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>> Hello All,
>>>>>>
>>>>>> In the middle of a migration to new DC.
>>>>>>
>>>>>> I have a Windows 2000 Server SP4 running Exchange 2000 SP4
>>>>>>
>>>>>> Need to extend the schema in preparation for Windows 2003 using.
>>>>>> ADPREP from the SBS1 CD1 I386 directory.
>>>>>>
>>>>>> This is what I get next.
>>>>>>
>>>>>> Anyone with experience of how to tackle this please.
>>>>>>
>>>>>> H:\I386>adprep /forestprep
>>>>>>
>>>>>> 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 poten
>>>>>> tial domain controller corruption.
>>>>>>
>>>>>> For more information about preparing your forest and domain see KB
>>>>>> article Q3311
>>>>>> 61 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 ENT
>>>>>> ER to quit.
>>>>>>
>>>>>>
>>>>>> c
>>>>>> Adprep was unable to extend the schema.
>>>>>> [Status/Consequence]
>>>>>> There is a schema conflict with Exchange 2000. The schema is not
>>>>>> upgraded.
>>>>>> [User Action]
>>>>>> The schema conflict must be resolved before running adprep. Resolve
>>>>>> the schema c
>>>>>> onflict, allow the change to replicate between all replication
>>>>>> partners, and the
>>>>>> n run Adprep. For information on resolving the conflict, see
>>>>>> Microsoft Knowledge
>>>>>> Base article Q325379.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: ADPREP issue - Migration
    ... Is this Standard 2000 with Standard Exchange or SBS 2000? ... >>> Frank McCallister SBS MVP ... >>> COMPUMAC ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook / Exchange / sender
    ... Instead of Aliases create actual user ids and this will work ... >> Frank McCallister SBS MVP ... >> COMPUMAC ...
    (microsoft.public.windows.server.sbs)
  • Re: Process (inetinfo.exe) Alert on SBSServer
    ... > OWA and put my username and password then as soon as I click logon button ... >> Frank McCallister SBS MVP ... >> COMPUMAC ...
    (microsoft.public.windows.server.sbs)
  • Re: Process (inetinfo.exe) Alert on SBSServer
    ... username to the internal domain name and forward slash /myusername. ... >>> Frank McCallister SBS MVP ... >>> COMPUMAC ...
    (microsoft.public.windows.server.sbs)
  • Re: Internet Connection
    ... >> Frank McCallister SBS MVP ... >> COMPUMAC ... As for the ICW, a router would be ...
    (microsoft.public.windows.server.sbs)