NTDS Replication "Susan" <susan[ at ]smcreynolds.com> 25.06.2007 20:21:05 Event ID 1864 I have a new SBS server in place and migrated from the old. The old server is offline and OFF and all is well....except... I thought I had done everything needed to promote the new server and I cannot find anything still looking for (or any reference to) the old server, but i continue to get daily errors in the event log re: NTDS Replication -- not being able to obtain replication info from the old server. How can i tell it to stop looking? What could be left that's causing this? Any help would be appreciated..i've been ignoring the errors, but finally getting tired of seeing them! Thanks in advance, Susan

Re: NTDS Replication "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> 25.06.2007 20:27:56 Susan wrote: [Quoted Text] > Event ID 1864 > > I have a new SBS server in place and migrated from the old. The old > server is offline and OFF and all is well....except... > > I thought I had done everything needed to promote the new server and I > cannot find anything still looking for (or any reference to) the old > server, but i continue to get daily errors in the event log re: NTDS > Replication -- not being able to obtain replication info from the old > server. > How can i tell it to stop looking? What could be left that's causing > this? > Any help would be appreciated..i've been ignoring the errors, but > finally getting tired of seeing them! > Thanks in advance, > Susan Sounds like an FRS replication partner 'remnant'. See the following for proper cleanup; http://support.microsoft.com/kb/216498/en-us -- /kj

Re: NTDS Replication "Susan" <susan[ at ]smcreynolds.com> 25.06.2007 22:24:31 Even though that KB doesn't specify it applies to SBS? That always confuses me.... will follow this KB and 'hopefully' this will solve my problem. Thanks, Kevin!! "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message news:OefnSd2tHHA.3544[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > Susan wrote: >> Event ID 1864 >> >> I have a new SBS server in place and migrated from the old. The old >> server is offline and OFF and all is well....except... >> >> I thought I had done everything needed to promote the new server and I >> cannot find anything still looking for (or any reference to) the old >> server, but i continue to get daily errors in the event log re: NTDS >> Replication -- not being able to obtain replication info from the old >> server. >> How can i tell it to stop looking? What could be left that's causing >> this? >> Any help would be appreciated..i've been ignoring the errors, but >> finally getting tired of seeing them! >> Thanks in advance, >> Susan > > Sounds like an FRS replication partner 'remnant'. See the following for > proper cleanup; > http://support.microsoft.com/kb/216498/en-us > > > -- > /kj >

Re: NTDS Replication "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> 25.06.2007 22:35:37 Susan wrote: [Quoted Text] > Even though that KB doesn't specify it applies to SBS? > > That always confuses me.... will follow this KB and 'hopefully' this > will solve my problem. > > Thanks, Kevin!! The old server was a domain controller, right? If so, then SBS AD replication is not fundamentally different than any other. Make sure you have verified good backups (more than one, preferably SBS wizard backups) and very carefully follow ntdsutil operation as it very unforgiving and easy to make a critical mistake. > > "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message > news:OefnSd2tHHA.3544[ at ]TK2MSFTNGP03.phx.gbl... >> Susan wrote: >>> Event ID 1864 >>> >>> I have a new SBS server in place and migrated from the old. The old >>> server is offline and OFF and all is well....except... >>> >>> I thought I had done everything needed to promote the new server >>> and I cannot find anything still looking for (or any reference to) >>> the old server, but i continue to get daily errors in the event log >>> re: NTDS Replication -- not being able to obtain replication info >>> from the old server. >>> How can i tell it to stop looking? What could be left that's causing >>> this? >>> Any help would be appreciated..i've been ignoring the errors, but >>> finally getting tired of seeing them! >>> Thanks in advance, >>> Susan >> >> Sounds like an FRS replication partner 'remnant'. See the following >> for proper cleanup; >> http://support.microsoft.com/kb/216498/en-us >> >> >> -- >> /kj -- /kj

Re: NTDS Replication "Susan" <susan[ at ]smcreynolds.com> 25.06.2007 23:21:01 Yikes...that's quite a warning there.... i knew it wouldnt be easy! Warning taken and will heed. THANK YOU. "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message news:OHM6Do3tHHA.1768[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > Susan wrote: >> Even though that KB doesn't specify it applies to SBS? >> >> That always confuses me.... will follow this KB and 'hopefully' this >> will solve my problem. >> >> Thanks, Kevin!! > > The old server was a domain controller, right? If so, then SBS AD > replication is not fundamentally different than any other. > > Make sure you have verified good backups (more than one, preferably SBS > wizard backups) and very carefully follow ntdsutil operation as it very > unforgiving and easy to make a critical mistake. > >> >> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >> news:OefnSd2tHHA.3544[ at ]TK2MSFTNGP03.phx.gbl... >>> Susan wrote: >>>> Event ID 1864 >>>> >>>> I have a new SBS server in place and migrated from the old. The old >>>> server is offline and OFF and all is well....except... >>>> >>>> I thought I had done everything needed to promote the new server >>>> and I cannot find anything still looking for (or any reference to) >>>> the old server, but i continue to get daily errors in the event log >>>> re: NTDS Replication -- not being able to obtain replication info >>>> from the old server. >>>> How can i tell it to stop looking? What could be left that's causing >>>> this? >>>> Any help would be appreciated..i've been ignoring the errors, but >>>> finally getting tired of seeing them! >>>> Thanks in advance, >>>> Susan >>> >>> Sounds like an FRS replication partner 'remnant'. See the following >>> for proper cleanup; >>> http://support.microsoft.com/kb/216498/en-us >>> >>> >>> -- >>> /kj > > -- > /kj >

Re: NTDS Replication "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> 25.06.2007 23:30:43 Susan wrote: [Quoted Text] > Yikes...that's quite a warning there.... i knew it wouldnt be easy! > > Warning taken and will heed. THANK YOU. Yes. Very powerful usually equates to very dangerous (if misused.) Print out the article, find a nice quiet setting with no interruptions or disturbances and follow the steps with all due care and caution. - You'll be fine. (SP1 servers are much easier) The good thing is the article is well written and detailed. > > "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message > news:OHM6Do3tHHA.1768[ at ]TK2MSFTNGP04.phx.gbl... >> Susan wrote: >>> Even though that KB doesn't specify it applies to SBS? >>> >>> That always confuses me.... will follow this KB and 'hopefully' this >>> will solve my problem. >>> >>> Thanks, Kevin!! >> >> The old server was a domain controller, right? If so, then SBS AD >> replication is not fundamentally different than any other. >> >> Make sure you have verified good backups (more than one, preferably >> SBS wizard backups) and very carefully follow ntdsutil operation as >> it very unforgiving and easy to make a critical mistake. >> >>> >>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>> news:OefnSd2tHHA.3544[ at ]TK2MSFTNGP03.phx.gbl... >>>> Susan wrote: >>>>> Event ID 1864 >>>>> >>>>> I have a new SBS server in place and migrated from the old. The >>>>> old server is offline and OFF and all is well....except... >>>>> >>>>> I thought I had done everything needed to promote the new server >>>>> and I cannot find anything still looking for (or any reference to) >>>>> the old server, but i continue to get daily errors in the event >>>>> log re: NTDS Replication -- not being able to obtain replication >>>>> info from the old server. >>>>> How can i tell it to stop looking? What could be left that's >>>>> causing this? >>>>> Any help would be appreciated..i've been ignoring the errors, but >>>>> finally getting tired of seeing them! >>>>> Thanks in advance, >>>>> Susan >>>> >>>> Sounds like an FRS replication partner 'remnant'. See the following >>>> for proper cleanup; >>>> http://support.microsoft.com/kb/216498/en-us >>>> >>>> >>>> -- >>>> /kj >> >> -- >> /kj -- /kj

Re: NTDS Replication "Susan" <susan[ at ]smcreynolds.com> 25.06.2007 23:43:01 Yes, I've been in trouble before, so I know how that goes. Too bad it won't just quit trying to find the old server -- heck, i was told the 2 couldnt coexist for more than 14 days anyway (microsoft support during my migration) so why is it bothering? Oh well. "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message news:OXtMbD4tHHA.680[ at ]TK2MSFTNGP05.phx.gbl... [Quoted Text] > Susan wrote: >> Yikes...that's quite a warning there.... i knew it wouldnt be easy! >> >> Warning taken and will heed. THANK YOU. > > Yes. Very powerful usually equates to very dangerous (if misused.) > > Print out the article, find a nice quiet setting with no interruptions or > disturbances and follow the steps with all due care and caution. - You'll > be fine. (SP1 servers are much easier) The good thing is the article is > well written and detailed. > >> >> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >> news:OHM6Do3tHHA.1768[ at ]TK2MSFTNGP04.phx.gbl... >>> Susan wrote: >>>> Even though that KB doesn't specify it applies to SBS? >>>> >>>> That always confuses me.... will follow this KB and 'hopefully' this >>>> will solve my problem. >>>> >>>> Thanks, Kevin!! >>> >>> The old server was a domain controller, right? If so, then SBS AD >>> replication is not fundamentally different than any other. >>> >>> Make sure you have verified good backups (more than one, preferably >>> SBS wizard backups) and very carefully follow ntdsutil operation as >>> it very unforgiving and easy to make a critical mistake. >>> >>>> >>>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>>> news:OefnSd2tHHA.3544[ at ]TK2MSFTNGP03.phx.gbl... >>>>> Susan wrote: >>>>>> Event ID 1864 >>>>>> >>>>>> I have a new SBS server in place and migrated from the old. The >>>>>> old server is offline and OFF and all is well....except... >>>>>> >>>>>> I thought I had done everything needed to promote the new server >>>>>> and I cannot find anything still looking for (or any reference to) >>>>>> the old server, but i continue to get daily errors in the event >>>>>> log re: NTDS Replication -- not being able to obtain replication >>>>>> info from the old server. >>>>>> How can i tell it to stop looking? What could be left that's >>>>>> causing this? >>>>>> Any help would be appreciated..i've been ignoring the errors, but >>>>>> finally getting tired of seeing them! >>>>>> Thanks in advance, >>>>>> Susan >>>>> >>>>> Sounds like an FRS replication partner 'remnant'. See the following >>>>> for proper cleanup; >>>>> http://support.microsoft.com/kb/216498/en-us >>>>> >>>>> >>>>> -- >>>>> /kj >>> >>> -- >>> /kj > > -- > /kj >

Re: NTDS Replication "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> 25.06.2007 23:51:37 Susan wrote: [Quoted Text] > Yes, I've been in trouble before, so I know how that goes. > > Too bad it won't just quit trying to find the old server -- heck, i > was told the 2 couldnt coexist for more than 14 days anyway > (microsoft support during my migration) so why is it bothering? Oh > well. AD Replication isn't one of the things SBS restricts. NTFRS orphaned replication is also not something that is time crucial to get fixed. > "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message > news:OXtMbD4tHHA.680[ at ]TK2MSFTNGP05.phx.gbl... >> Susan wrote: >>> Yikes...that's quite a warning there.... i knew it wouldnt be easy! >>> >>> Warning taken and will heed. THANK YOU. >> >> Yes. Very powerful usually equates to very dangerous (if misused.) >> >> Print out the article, find a nice quiet setting with no >> interruptions or disturbances and follow the steps with all due care >> and caution. - You'll be fine. (SP1 servers are much easier) The >> good thing is the article is well written and detailed. >> >>> >>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>> news:OHM6Do3tHHA.1768[ at ]TK2MSFTNGP04.phx.gbl... >>>> Susan wrote: >>>>> Even though that KB doesn't specify it applies to SBS? >>>>> >>>>> That always confuses me.... will follow this KB and 'hopefully' >>>>> this will solve my problem. >>>>> >>>>> Thanks, Kevin!! >>>> >>>> The old server was a domain controller, right? If so, then SBS AD >>>> replication is not fundamentally different than any other. >>>> >>>> Make sure you have verified good backups (more than one, preferably >>>> SBS wizard backups) and very carefully follow ntdsutil operation as >>>> it very unforgiving and easy to make a critical mistake. >>>> >>>>> >>>>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>>>> news:OefnSd2tHHA.3544[ at ]TK2MSFTNGP03.phx.gbl... >>>>>> Susan wrote: >>>>>>> Event ID 1864 >>>>>>> >>>>>>> I have a new SBS server in place and migrated from the old. The >>>>>>> old server is offline and OFF and all is well....except... >>>>>>> >>>>>>> I thought I had done everything needed to promote the new server >>>>>>> and I cannot find anything still looking for (or any reference >>>>>>> to) the old server, but i continue to get daily errors in the >>>>>>> event log re: NTDS Replication -- not being able to obtain >>>>>>> replication info from the old server. >>>>>>> How can i tell it to stop looking? What could be left that's >>>>>>> causing this? >>>>>>> Any help would be appreciated..i've been ignoring the errors, >>>>>>> but finally getting tired of seeing them! >>>>>>> Thanks in advance, >>>>>>> Susan >>>>>> >>>>>> Sounds like an FRS replication partner 'remnant'. See the >>>>>> following for proper cleanup; >>>>>> http://support.microsoft.com/kb/216498/en-us >>>>>> >>>>>> >>>>>> -- >>>>>> /kj >>>> >>>> -- >>>> /kj >> >> -- >> /kj -- /kj

Re: NTDS Replication "Susan" <susan[ at ]smcreynolds.com> 26.06.2007 00:56:42 Ah...you answered my secret question: do i have to do this right now? I like the answer. Thank you! "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message news:ewlXHP4tHHA.3480[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > Susan wrote: >> Yes, I've been in trouble before, so I know how that goes. >> >> Too bad it won't just quit trying to find the old server -- heck, i >> was told the 2 couldnt coexist for more than 14 days anyway >> (microsoft support during my migration) so why is it bothering? Oh >> well. > > AD Replication isn't one of the things SBS restricts. NTFRS orphaned > replication is also not something that is time crucial to get fixed. > >> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >> news:OXtMbD4tHHA.680[ at ]TK2MSFTNGP05.phx.gbl... >>> Susan wrote: >>>> Yikes...that's quite a warning there.... i knew it wouldnt be easy! >>>> >>>> Warning taken and will heed. THANK YOU. >>> >>> Yes. Very powerful usually equates to very dangerous (if misused.) >>> >>> Print out the article, find a nice quiet setting with no >>> interruptions or disturbances and follow the steps with all due care >>> and caution. - You'll be fine. (SP1 servers are much easier) The >>> good thing is the article is well written and detailed. >>> >>>> >>>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>>> news:OHM6Do3tHHA.1768[ at ]TK2MSFTNGP04.phx.gbl... >>>>> Susan wrote: >>>>>> Even though that KB doesn't specify it applies to SBS? >>>>>> >>>>>> That always confuses me.... will follow this KB and 'hopefully' >>>>>> this will solve my problem. >>>>>> >>>>>> Thanks, Kevin!! >>>>> >>>>> The old server was a domain controller, right? If so, then SBS AD >>>>> replication is not fundamentally different than any other. >>>>> >>>>> Make sure you have verified good backups (more than one, preferably >>>>> SBS wizard backups) and very carefully follow ntdsutil operation as >>>>> it very unforgiving and easy to make a critical mistake. >>>>> >>>>>> >>>>>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>>>>> news:OefnSd2tHHA.3544[ at ]TK2MSFTNGP03.phx.gbl... >>>>>>> Susan wrote: >>>>>>>> Event ID 1864 >>>>>>>> >>>>>>>> I have a new SBS server in place and migrated from the old. The >>>>>>>> old server is offline and OFF and all is well....except... >>>>>>>> >>>>>>>> I thought I had done everything needed to promote the new server >>>>>>>> and I cannot find anything still looking for (or any reference >>>>>>>> to) the old server, but i continue to get daily errors in the >>>>>>>> event log re: NTDS Replication -- not being able to obtain >>>>>>>> replication info from the old server. >>>>>>>> How can i tell it to stop looking? What could be left that's >>>>>>>> causing this? >>>>>>>> Any help would be appreciated..i've been ignoring the errors, >>>>>>>> but finally getting tired of seeing them! >>>>>>>> Thanks in advance, >>>>>>>> Susan >>>>>>> >>>>>>> Sounds like an FRS replication partner 'remnant'. See the >>>>>>> following for proper cleanup; >>>>>>> http://support.microsoft.com/kb/216498/en-us >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> /kj >>>>> >>>>> -- >>>>> /kj >>> >>> -- >>> /kj > > -- > /kj >

Re: NTDS Replication "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> 26.06.2007 01:18:53 Susan wrote: [Quoted Text] > Ah...you answered my secret question: do i have to do this right now? > > I like the answer. Thank you! *if* you have only one remaining DC, it's just an event log inconvenience. If you have other remaining DC's then you may have issues with Sysvol replication that should be attended to soon. I'd make sure it gets corrected so as not to have other developing issues masked with similar discounted errors. > > "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message > news:ewlXHP4tHHA.3480[ at ]TK2MSFTNGP04.phx.gbl... >> Susan wrote: >>> Yes, I've been in trouble before, so I know how that goes. >>> >>> Too bad it won't just quit trying to find the old server -- heck, i >>> was told the 2 couldnt coexist for more than 14 days anyway >>> (microsoft support during my migration) so why is it bothering? Oh >>> well. >> >> AD Replication isn't one of the things SBS restricts. NTFRS orphaned >> replication is also not something that is time crucial to get fixed. >> >>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>> news:OXtMbD4tHHA.680[ at ]TK2MSFTNGP05.phx.gbl... >>>> Susan wrote: >>>>> Yikes...that's quite a warning there.... i knew it wouldnt be >>>>> easy! Warning taken and will heed. THANK YOU. >>>> >>>> Yes. Very powerful usually equates to very dangerous (if misused.) >>>> >>>> Print out the article, find a nice quiet setting with no >>>> interruptions or disturbances and follow the steps with all due >>>> care and caution. - You'll be fine. (SP1 servers are much easier) >>>> The good thing is the article is well written and detailed. >>>> >>>>> >>>>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>>>> news:OHM6Do3tHHA.1768[ at ]TK2MSFTNGP04.phx.gbl... >>>>>> Susan wrote: >>>>>>> Even though that KB doesn't specify it applies to SBS? >>>>>>> >>>>>>> That always confuses me.... will follow this KB and 'hopefully' >>>>>>> this will solve my problem. >>>>>>> >>>>>>> Thanks, Kevin!! >>>>>> >>>>>> The old server was a domain controller, right? If so, then SBS AD >>>>>> replication is not fundamentally different than any other. >>>>>> >>>>>> Make sure you have verified good backups (more than one, >>>>>> preferably SBS wizard backups) and very carefully follow >>>>>> ntdsutil operation as it very unforgiving and easy to make a >>>>>> critical mistake. >>>>>>> >>>>>>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>>>>>> news:OefnSd2tHHA.3544[ at ]TK2MSFTNGP03.phx.gbl... >>>>>>>> Susan wrote: >>>>>>>>> Event ID 1864 >>>>>>>>> >>>>>>>>> I have a new SBS server in place and migrated from the old. >>>>>>>>> The old server is offline and OFF and all is well....except... >>>>>>>>> >>>>>>>>> I thought I had done everything needed to promote the new >>>>>>>>> server and I cannot find anything still looking for (or any >>>>>>>>> reference to) the old server, but i continue to get daily >>>>>>>>> errors in the event log re: NTDS Replication -- not being >>>>>>>>> able to obtain replication info from the old server. >>>>>>>>> How can i tell it to stop looking? What could be left that's >>>>>>>>> causing this? >>>>>>>>> Any help would be appreciated..i've been ignoring the errors, >>>>>>>>> but finally getting tired of seeing them! >>>>>>>>> Thanks in advance, >>>>>>>>> Susan >>>>>>>> >>>>>>>> Sounds like an FRS replication partner 'remnant'. See the >>>>>>>> following for proper cleanup; >>>>>>>> http://support.microsoft.com/kb/216498/en-us >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> /kj >>>>>> >>>>>> -- >>>>>> /kj >>>> >>>> -- >>>> /kj >> >> -- >> /kj -- /kj

Re: NTDS Replication "Susan" <susan[ at ]smcreynolds.com> 26.06.2007 13:33:44 only one DC remaining... the Sysvol replication worked itself out -- although was throwing errors until just the other day. "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message news:eONK5$4tHHA.668[ at ]TK2MSFTNGP05.phx.gbl... [Quoted Text] > Susan wrote: >> Ah...you answered my secret question: do i have to do this right now? >> >> I like the answer. Thank you! > > *if* you have only one remaining DC, it's just an event log inconvenience. > If you have other remaining DC's then you may have issues with Sysvol > replication that should be attended to soon. > > I'd make sure it gets corrected so as not to have other developing issues > masked with similar discounted errors. > >> >> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >> news:ewlXHP4tHHA.3480[ at ]TK2MSFTNGP04.phx.gbl... >>> Susan wrote: >>>> Yes, I've been in trouble before, so I know how that goes. >>>> >>>> Too bad it won't just quit trying to find the old server -- heck, i >>>> was told the 2 couldnt coexist for more than 14 days anyway >>>> (microsoft support during my migration) so why is it bothering? Oh >>>> well. >>> >>> AD Replication isn't one of the things SBS restricts. NTFRS orphaned >>> replication is also not something that is time crucial to get fixed. >>> >>>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>>> news:OXtMbD4tHHA.680[ at ]TK2MSFTNGP05.phx.gbl... >>>>> Susan wrote: >>>>>> Yikes...that's quite a warning there.... i knew it wouldnt be >>>>>> easy! Warning taken and will heed. THANK YOU. >>>>> >>>>> Yes. Very powerful usually equates to very dangerous (if misused.) >>>>> >>>>> Print out the article, find a nice quiet setting with no >>>>> interruptions or disturbances and follow the steps with all due >>>>> care and caution. - You'll be fine. (SP1 servers are much easier) >>>>> The good thing is the article is well written and detailed. >>>>> >>>>>> >>>>>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>>>>> news:OHM6Do3tHHA.1768[ at ]TK2MSFTNGP04.phx.gbl... >>>>>>> Susan wrote: >>>>>>>> Even though that KB doesn't specify it applies to SBS? >>>>>>>> >>>>>>>> That always confuses me.... will follow this KB and 'hopefully' >>>>>>>> this will solve my problem. >>>>>>>> >>>>>>>> Thanks, Kevin!! >>>>>>> >>>>>>> The old server was a domain controller, right? If so, then SBS AD >>>>>>> replication is not fundamentally different than any other. >>>>>>> >>>>>>> Make sure you have verified good backups (more than one, >>>>>>> preferably SBS wizard backups) and very carefully follow >>>>>>> ntdsutil operation as it very unforgiving and easy to make a >>>>>>> critical mistake. >>>>>>>> >>>>>>>> "kj" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> wrote in message >>>>>>>> news:OefnSd2tHHA.3544[ at ]TK2MSFTNGP03.phx.gbl... >>>>>>>>> Susan wrote: >>>>>>>>>> Event ID 1864 >>>>>>>>>> >>>>>>>>>> I have a new SBS server in place and migrated from the old. >>>>>>>>>> The old server is offline and OFF and all is well....except... >>>>>>>>>> >>>>>>>>>> I thought I had done everything needed to promote the new >>>>>>>>>> server and I cannot find anything still looking for (or any >>>>>>>>>> reference to) the old server, but i continue to get daily >>>>>>>>>> errors in the event log re: NTDS Replication -- not being >>>>>>>>>> able to obtain replication info from the old server. >>>>>>>>>> How can i tell it to stop looking? What could be left that's >>>>>>>>>> causing this? >>>>>>>>>> Any help would be appreciated..i've been ignoring the errors, >>>>>>>>>> but finally getting tired of seeing them! >>>>>>>>>> Thanks in advance, >>>>>>>>>> Susan >>>>>>>>> >>>>>>>>> Sounds like an FRS replication partner 'remnant'. See the >>>>>>>>> following for proper cleanup; >>>>>>>>> http://support.microsoft.com/kb/216498/en-us >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> /kj >>>>>>> >>>>>>> -- >>>>>>> /kj >>>>> >>>>> -- >>>>> /kj >>> >>> -- >>> /kj > > -- > /kj >