Events 1863 and 2093 post 2003 Migration to 2008 R2

Question

I have migrated AD from a 2003 SBS SP2 server to a 2008 R2 SP1 server using the following article: http://technet.microsoft.com/en-us/library/dd379526.aspx
That was 2 days ago, this morning I noticed the following events in the 2008 error log: Error 1863 and Warning 2093
There appears to be no issue with the domain currently, everyone was able to login in without issue this morning. Both servers are continuing to run, although I plan to demote the 2003 and decommission the hardware if there are no issues (as advised by the
post-migration instructions of the above article). I can provide full text of the events, but I have removed identifying information:
Log Name:      Directory Service
Source:        Microsoft-Windows-ActiveDirectory_DomainService
Date:          2/17/2014 4:18:14 AM
Event ID:      1863
Task Category: Replication
Level:         Error
Keywords:      Classic
User:          ANONYMOUS LOGON
Computer:     SERVERNEW.generic.local
Description:
This is the replication status for the following directory partition on this directory server.
Directory partition:
CN=Schema,CN=Configuration,DC=generic,DC=local
This directory server has not received replication information from a number of directory servers within the configured latency interval.
Latency Interval (Hours):
24
Number of directory servers in all sites:
1
Number of directory servers in this site:
1
The latency interval can be modified with the following registry key.
Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours)
To identify the directory servers by name, use the dcdiag.exe tool.
You can also use the support tool repadmin.exe to display the replication latencies of the directory servers.   The command is "repadmin /showvector /latency <partition-dn>".
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS KCC" />
    <EventID Qualifiers="49152">1863</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>5</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-17T09:18:14.599176800Z" />
    <EventRecordID>243</EventRecordID>
    <Correlation />
    <Execution ProcessID="504" ThreadID="660" />
    <Channel>Directory Service</Channel>
    <Computer>SERVERNEW.generic.local</Computer>
    <Security UserID="S-1-5-7" />
  </System>
  <EventData>
    <Data>CN=Schema,CN=Configuration,DC=generic,DC=local</Data>
    <Data>1</Data>
    <Data>1</Data>
    <Data>24</Data>
    <Data>System\CurrentControlSet\Services\NTDS\Parameters</Data>
  </EventData>
</Event>
Log Name:      Directory Service
Source:        Microsoft-Windows-ActiveDirectory_DomainService
Date:          2/17/2014 4:18:14 AM
Event ID:      2093
Task Category: Replication
Level:         Warning
Keywords:      Classic
User:          ANONYMOUS LOGON
Computer:      SERVERNEW.generic.local
Description:
The remote server which is the owner of a FSMO role is not responding.  This server has not replicated with the FSMO role owner recently.
Operations which require contacting a FSMO operation master will fail until this condition is corrected.
FSMO Role: CN=Schema,CN=Configuration,DC=generic,DC=local
FSMO Server DN: CN=NTDS Settings,CN=SERVEROLD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=generic,DC=local
Latency threshold (hours): 24
Elapsed time since last successful replication (hours): 25
User Action:
This server has not replicated successfully with the FSMO role holder server.
1. The FSMO role holder server may be down or not responding. Please address the problem with this server.
2. Determine whether the role is set properly on the FSMO role holder server. If the role needs to be adjusted, utilize NTDSUTIL.EXE to transfer or seize the role. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.
3. If the FSMO role holder server used to be a domain controller, but was not demoted successfully, then the objects representing that server are still in the forest. This can occur if a domain controller has its operating system reinstalled or if a forced
removal is performed.  These lingering state objects should be removed using the NTDSUTIL.EXE metadata cleanup function.
4. The FSMO role holder may not be a direct replication partner. If it is an indirect or transitive partner, then there are one or more intermediate replication partners through which replication data must flow. The total end to end replication latency should
be smaller than the replication latency threshold, or else this warning may be reported prematurely.
5. Replication is blocked somewhere along the path of servers between the FSMO role holder server and this server.  Consult your forest topology plan to determine the likely route for replication between these servers. Check the status of replication using
repadmin /showrepl at each of these servers.
The following operations may be impacted:
Schema: You will no longer be able to modify the schema for this forest.
Domain Naming: You will no longer be able to add or remove domains from this forest.
PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts.
RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.
Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.

Answer 1

Hi,
The guide you are using is not for SBS. If you look at the detailed supported migration scenarios you will see this matrix:
Source server   processor
Source server operating system
Destination server operating system
Destination server processor
x86- or x64-based
Windows Server 2003 with Service Pack 2 (SP2)
Windows Server 2008 R2, both full and Server Core installation   options
x64-based
x86- or x64-based
Windows Server 2003 R2
Windows Server 2008 R2, both full and Server Core installation   options
x64-based
x86- or x64-based
Windows Server 2008, both full and Server Core   installation options
Windows Server 2008 R2, both full and Server Core installation   options
x64-based
x64-based
Windows Server 2008 R2
Windows Server 2008 R2, both full and Server Core installation   options
x64-based
x64-based
Server Core installation option of Windows Server 2008 R2
Windows Server 2008 R2, both full and Server Core installation   options
x64-based
There is no Small Business Server specified.
This forum is not really for SBS migrations and you can also ask on the SBS forums
for better advice about SBS.
And yes, if you want to decommission the SBS server, running as a DC, you will at some point have to transfer the FSMO roles to the destination server. Please follow the steps in the guide I posted earlier to migrate the roles or applications that you need.
And also ask more details on the SBS forums.
Marius
http://mariusene.wordpress.com/