Solved

Active Directory is taking longer than expected during SBS2008 setup

Posted on 2010-08-25
13
916 Views
Last Modified: 2012-05-10
I mam adding SBS2008 to an existingServer 2003 domain, using the answer file.
I reviewed and followed all recommended procedures.
Setup has been hung with this error for a day; selecting "YES let it wait" has not worked.
I ran AD Replication monitor, only one failure: (Group Policies and Scriots have not replicated to the SYSVOL Folder
Can I assume that replication is working correctly, and choose "NOT TO WAIT" ?
Here is the log for the SBS2003 Server
----------------------------------
     Active Directory Replication Monitor
Printed on 8/25/2010 11:06:44 AM
This report was generated on data from the server: JLP03

***************************************************************************
                               JLP03 Data
***************************************************************************

This server currently has writable copies of the following directory partitions:
---------------------------------------------------------------------------
     DC=jlproler,DC=com
     CN=Configuration,DC=jlproler,DC=com
     CN=Schema,CN=Configuration,DC=jlproler,DC=com
     DC=DomainDnsZones,DC=jlproler,DC=com
     DC=ForestDnsZones,DC=jlproler,DC=com

Because this server is a Global Catalog (GC) server, it also has copies
of the following directory partitions:
---------------------------------------------------------------------------

Current NTDS Connection Objects
-------------------------------
     Houston\JLP02
          Connection Name : 5d056e12-f35c-4d89-ad7b-1eaa15153b6f
          Administrator Generated?: AUTO
          Reasons for this connection:
               Directory Partition (DC=DomainDnsZones,DC=jlproler,DC=com)
                    Replicated because the replication partner is a ring neighbor.

               Directory Partition (DC=ForestDnsZones,DC=jlproler,DC=com)
                    Replicated because the replication partner is a ring neighbor.

               Directory Partition (DC=jlproler,DC=com)
                    Replicated because the replication partner is a ring neighbor.

               Directory Partition (CN=Schema,CN=Configuration,DC=jlproler,DC=com)
                    Replicated because the replication partner is a ring neighbor.

               Directory Partition (CN=Configuration,DC=jlproler,DC=com)
                    Replicated because the replication partner is a ring neighbor.

     Houston\JLP01
          Connection Name : 74985ce2-0656-4dce-ac15-5c391af1b19b
          Administrator Generated?: AUTO
          Reasons for this connection:
               Directory Partition (DC=DomainDnsZones,DC=jlproler,DC=com)
                    Replicated because the replication partner is a ring neighbor.

               Directory Partition (DC=ForestDnsZones,DC=jlproler,DC=com)
                    Replicated because the replication partner is a ring neighbor.

               Directory Partition (DC=jlproler,DC=com)
                    Replicated because the replication partner is a ring neighbor.

               Directory Partition (CN=Schema,CN=Configuration,DC=jlproler,DC=com)
                    Replicated because the replication partner is a ring neighbor.

               Directory Partition (CN=Configuration,DC=jlproler,DC=com)
                    Replicated because the replication partner is a ring neighbor.


Current Direct Replication Partner Status
-----------------------------------------

     Directory Partition: DC=jlproler,DC=com

          Partner Name: Houston\JLP01
               Partner GUID: 7B524845-725C-4551-801B-67F22941764A
               Last Attempted Replication: 8/25/2010 11:04:24 AM (local)
               Last Successful Replication: 8/25/2010 11:04:24 AM (local)
               Number of Failures:  0
               Failure Reason Error Code:  0
               Failure Description: The operation completed successfully.
               Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
               USN of Last Property Updated:  4534173
               USN of Last Object Updated:  4534173
               Transport: Intra-Site RPC

          Partner Name: Houston\JLP02
               Partner GUID: A728F54E-8239-404F-A007-C7A33F054BDA
               Last Attempted Replication: 8/25/2010 11:06:26 AM (local)
               Last Successful Replication: 8/25/2010 11:06:26 AM (local)
               Number of Failures:  0
               Failure Reason Error Code:  0
               Failure Description: The operation completed successfully.
               Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
               USN of Last Property Updated:  5103872
               USN of Last Object Updated:  5103872
               Transport: Intra-Site RPC

          Change Notifications for this Directory Partition
          -------------------------------------------------
               Server Name: Houston\JLP02
                    Object GUID: 7C7BB7D7-CF5D-41A1-8050-BFC4ABC4AB76
                    Time Added:  8/25/2010 11:04:42 AM
                    Flags:       DRS_WRIT_REP
                    Transport:   RPC
               Server Name: Houston\JLP01
                    Object GUID: 7A188E15-C04D-4AE0-B311-81B58F324664
                    Time Added:  8/25/2010 11:02:43 AM
                    Flags:       DRS_WRIT_REP
                    Transport:   RPC

     Directory Partition: CN=Configuration,DC=jlproler,DC=com

          Partner Name: Houston\JLP01
               Partner GUID: 7B524845-725C-4551-801B-67F22941764A
               Last Attempted Replication: 8/25/2010 11:04:24 AM (local)
               Last Successful Replication: 8/25/2010 11:04:24 AM (local)
               Number of Failures:  0
               Failure Reason Error Code:  0
               Failure Description: The operation completed successfully.
               Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
               USN of Last Property Updated:  4534134
               USN of Last Object Updated:  4534134
               Transport: Intra-Site RPC

          Partner Name: Houston\JLP02
               Partner GUID: A728F54E-8239-404F-A007-C7A33F054BDA
               Last Attempted Replication: 8/25/2010 11:04:24 AM (local)
               Last Successful Replication: 8/25/2010 11:04:24 AM (local)
               Number of Failures:  0
               Failure Reason Error Code:  0
               Failure Description: The operation completed successfully.
               Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
               USN of Last Property Updated:  5103838
               USN of Last Object Updated:  5103838
               Transport: Intra-Site RPC

          Change Notifications for this Directory Partition
          -------------------------------------------------
               Server Name: Houston\JLP01
                    Object GUID: 7A188E15-C04D-4AE0-B311-81B58F324664
                    Time Added:  8/25/2010 10:41:16 AM
                    Flags:       DRS_WRIT_REP
                    Transport:   RPC
               Server Name: Houston\JLP02
                    Object GUID: 7C7BB7D7-CF5D-41A1-8050-BFC4ABC4AB76
                    Time Added:  8/25/2010 10:41:13 AM
                    Flags:       DRS_WRIT_REP
                    Transport:   RPC

     Directory Partition: CN=Schema,CN=Configuration,DC=jlproler,DC=com

          Partner Name: Houston\JLP01
               Partner GUID: 7B524845-725C-4551-801B-67F22941764A
               Last Attempted Replication: 8/25/2010 11:04:24 AM (local)
               Last Successful Replication: 8/25/2010 11:04:24 AM (local)
               Number of Failures:  0
               Failure Reason Error Code:  0
               Failure Description: The operation completed successfully.
               Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
               USN of Last Property Updated:  4534134
               USN of Last Object Updated:  4534134
               Transport: Intra-Site RPC

          Partner Name: Houston\JLP02
               Partner GUID: A728F54E-8239-404F-A007-C7A33F054BDA
               Last Attempted Replication: 8/25/2010 11:04:24 AM (local)
               Last Successful Replication: 8/25/2010 11:04:24 AM (local)
               Number of Failures:  0
               Failure Reason Error Code:  0
               Failure Description: The operation completed successfully.
               Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
               USN of Last Property Updated:  5103838
               USN of Last Object Updated:  5103838
               Transport: Intra-Site RPC

          Change Notifications for this Directory Partition
          -------------------------------------------------
               Server Name: Houston\JLP01
                    Object GUID: 7A188E15-C04D-4AE0-B311-81B58F324664
                    Time Added:  8/24/2010 2:55:46 PM
                    Flags:       DRS_WRIT_REP
                    Transport:   RPC
               Server Name: Houston\JLP02
                    Object GUID: 7C7BB7D7-CF5D-41A1-8050-BFC4ABC4AB76
                    Time Added:  8/24/2010 2:55:43 PM
                    Flags:       DRS_WRIT_REP
                    Transport:   RPC

     Directory Partition: DC=DomainDnsZones,DC=jlproler,DC=com

          Partner Name: Houston\JLP01
               Partner GUID: 7B524845-725C-4551-801B-67F22941764A
               Last Attempted Replication: 8/25/2010 11:04:24 AM (local)
               Last Successful Replication: 8/25/2010 11:04:24 AM (local)
               Number of Failures:  0
               Failure Reason Error Code:  0
               Failure Description: The operation completed successfully.
               Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
               USN of Last Property Updated:  4534134
               USN of Last Object Updated:  4534134
               Transport: Intra-Site RPC

          Partner Name: Houston\JLP02
               Partner GUID: A728F54E-8239-404F-A007-C7A33F054BDA
               Last Attempted Replication: 8/25/2010 11:04:24 AM (local)
               Last Successful Replication: 8/25/2010 11:04:24 AM (local)
               Number of Failures:  0
               Failure Reason Error Code:  0
               Failure Description: The operation completed successfully.
               Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
               USN of Last Property Updated:  5103838
               USN of Last Object Updated:  5103838
               Transport: Intra-Site RPC

          Change Notifications for this Directory Partition
          -------------------------------------------------
               Server Name: Houston\JLP02
                    Object GUID: 7C7BB7D7-CF5D-41A1-8050-BFC4ABC4AB76
                    Time Added:  <no value>
                    Flags:       DRS_WRIT_REP
                    Transport:   RPC
               Server Name: Houston\JLP01
                    Object GUID: 7A188E15-C04D-4AE0-B311-81B58F324664
                    Time Added:  <no value>
                    Flags:       DRS_WRIT_REP
                    Transport:   RPC

     Directory Partition: DC=ForestDnsZones,DC=jlproler,DC=com

          Partner Name: Houston\JLP01
               Partner GUID: 7B524845-725C-4551-801B-67F22941764A
               Last Attempted Replication: 8/25/2010 11:04:24 AM (local)
               Last Successful Replication: 8/25/2010 11:04:24 AM (local)
               Number of Failures:  0
               Failure Reason Error Code:  0
               Failure Description: The operation completed successfully.
               Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
               USN of Last Property Updated:  4534134
               USN of Last Object Updated:  4534134
               Transport: Intra-Site RPC

          Partner Name: Houston\JLP02
               Partner GUID: A728F54E-8239-404F-A007-C7A33F054BDA
               Last Attempted Replication: 8/25/2010 11:04:24 AM (local)
               Last Successful Replication: 8/25/2010 11:04:24 AM (local)
               Number of Failures:  0
               Failure Reason Error Code:  0
               Failure Description: The operation completed successfully.
               Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
               USN of Last Property Updated:  5103838
               USN of Last Object Updated:  5103838
               Transport: Intra-Site RPC

          Change Notifications for this Directory Partition
          -------------------------------------------------
               Server Name: Houston\JLP02
                    Object GUID: 7C7BB7D7-CF5D-41A1-8050-BFC4ABC4AB76
                    Time Added:  <no value>
                    Flags:       DRS_WRIT_REP
                    Transport:   RPC
               Server Name: Houston\JLP01
                    Object GUID: 7A188E15-C04D-4AE0-B311-81B58F324664
                    Time Added:  <no value>
                    Flags:       DRS_WRIT_REP
                    Transport:   RPC

Current Transitive Replication Partner Status
---------------------------------------------

     Directory Partition: DC=jlproler,DC=com

          Partner Name: **DELETED SERVER #2
               Partner GUID: 15CA89F1-9204-49F6-82A0-A2699EEFD1CC
               USN:  4251650

          Partner Name: **DELETED SERVER #3
               Partner GUID: 3C1A2058-67E0-499C-B0E0-845F564FE693
               USN:  4830268

          Partner Name: **DELETED SERVER #4
               Partner GUID: 7653A066-E892-4C2D-907C-E1DB08FD9F83
               USN:  348282

          Partner Name: Houston\JLP01
               Partner GUID: 7B524845-725C-4551-801B-67F22941764A
               USN:  4534215

          Partner Name: **DELETED SERVER #5
               Partner GUID: A4FBF803-9F27-4870-A179-FD39F272B3DB
               USN:  11090

          Partner Name: Houston\JLP02
               Partner GUID: A728F54E-8239-404F-A007-C7A33F054BDA
               USN:  5103909

          Partner Name: **DELETED SERVER #6
               Partner GUID: CDC4B618-62F5-4FBD-9F7E-CA8241230F92
               USN:  39082

          Partner Name: Houston\JLP03
               Partner GUID: D6A7FE33-0184-480B-BC85-0EB5888523E6
               USN:  20523

     Directory Partition: CN=Configuration,DC=jlproler,DC=com

          Partner Name: **DELETED SERVER #2
               Partner GUID: 15CA89F1-9204-49F6-82A0-A2699EEFD1CC
               USN:  4251650

          Partner Name: **DELETED SERVER #3
               Partner GUID: 3C1A2058-67E0-499C-B0E0-845F564FE693
               USN:  4830268

          Partner Name: **DELETED SERVER #4
               Partner GUID: 7653A066-E892-4C2D-907C-E1DB08FD9F83
               USN:  348269

          Partner Name: Houston\JLP01
               Partner GUID: 7B524845-725C-4551-801B-67F22941764A
               USN:  4534179

          Partner Name: **DELETED SERVER #5
               Partner GUID: A4FBF803-9F27-4870-A179-FD39F272B3DB
               USN:  11090

          Partner Name: Houston\JLP02
               Partner GUID: A728F54E-8239-404F-A007-C7A33F054BDA
               USN:  5103872

          Partner Name: **DELETED SERVER #6
               Partner GUID: CDC4B618-62F5-4FBD-9F7E-CA8241230F92
               USN:  39076

          Partner Name: Houston\JLP03
               Partner GUID: D6A7FE33-0184-480B-BC85-0EB5888523E6
               USN:  20523

     Directory Partition: CN=Schema,CN=Configuration,DC=jlproler,DC=com

          Partner Name: **DELETED SERVER #2
               Partner GUID: 15CA89F1-9204-49F6-82A0-A2699EEFD1CC
               USN:  4251650

          Partner Name: **DELETED SERVER #3
               Partner GUID: 3C1A2058-67E0-499C-B0E0-845F564FE693
               USN:  4830268

          Partner Name: **DELETED SERVER #4
               Partner GUID: 7653A066-E892-4C2D-907C-E1DB08FD9F83
               USN:  348269

          Partner Name: Houston\JLP01
               Partner GUID: 7B524845-725C-4551-801B-67F22941764A
               USN:  4534179

          Partner Name: **DELETED SERVER #5
               Partner GUID: A4FBF803-9F27-4870-A179-FD39F272B3DB
               USN:  11090

          Partner Name: Houston\JLP02
               Partner GUID: A728F54E-8239-404F-A007-C7A33F054BDA
               USN:  5103872

          Partner Name: **DELETED SERVER #6
               Partner GUID: CDC4B618-62F5-4FBD-9F7E-CA8241230F92
               USN:  39028

          Partner Name: Houston\JLP03
               Partner GUID: D6A7FE33-0184-480B-BC85-0EB5888523E6
               USN:  20523

     Directory Partition: DC=DomainDnsZones,DC=jlproler,DC=com

          Partner Name: **DELETED SERVER #4
               Partner GUID: 7653A066-E892-4C2D-907C-E1DB08FD9F83
               USN:  348271

          Partner Name: Houston\JLP01
               Partner GUID: 7B524845-725C-4551-801B-67F22941764A
               USN:  4534179

          Partner Name: Houston\JLP02
               Partner GUID: A728F54E-8239-404F-A007-C7A33F054BDA
               USN:  5103872

          Partner Name: Houston\JLP03
               Partner GUID: D6A7FE33-0184-480B-BC85-0EB5888523E6
               USN:  20523

     Directory Partition: DC=ForestDnsZones,DC=jlproler,DC=com

          Partner Name: **DELETED SERVER #4
               Partner GUID: 7653A066-E892-4C2D-907C-E1DB08FD9F83
               USN:  348277

          Partner Name: Houston\JLP01
               Partner GUID: 7B524845-725C-4551-801B-67F22941764A
               USN:  4534179

          Partner Name: Houston\JLP02
               Partner GUID: A728F54E-8239-404F-A007-C7A33F054BDA
               USN:  5103872

          Partner Name: Houston\JLP03
               Partner GUID: D6A7FE33-0184-480B-BC85-0EB5888523E6
               USN:  20523

Current Group Policy Object Status
----------------------------------
     Default Domain Policy
          Group Policy Object GUID: {31B2F340-016D-11D2-945F-00C04FB984F9}
          Group Policy Object Version in the DS:  262195
          Group Policy Object Version in SYSVOL: ERROR

     Default Domain Controllers Policy
          Group Policy Object GUID: {6AC1786C-016F-11D2-945F-00C04fB984F9}
          Group Policy Object Version in the DS:  61
          Group Policy Object Version in SYSVOL: ERROR

     Managed Computers
          Group Policy Object GUID: {DF0F2A70-4209-4EDE-9050-EE15AF596574}
          Group Policy Object Version in the DS:  8
          Group Policy Object Version in SYSVOL: ERROR


The server JLP03 knows about the following FSMO roles:
--------------------------------------------------------------------------
     Schema FSMO: Houston\JLP03
     Domain Naming FSMO: Houston\JLP03
     Infrastructure FSMO: Houston\JLP03
     Primary Domain Controller FSMO: Houston\JLP03
     RID Pool FSMO: Houston\JLP03

Performance Statistics at Time of Report
----------------------------------------

Configuration (Registry)
NOTE: an empty value indicates that Windows 2000 will use the internal default
NOTE: all empty values may indicate insufficient permission to retrieve this information from the domain controller
------------------------

     DSA
     ---

          Days per Database Phantom Scan:
          Initialize MAPI interface:
          Enforce LIST_OBJECTS rights:
          DSA Heuristics:
          Max Threads (ExDS+NSP+DRA):
          DSA Database file: C:\Windows\ntds\ntds.dit
          DSA Working Directory: C:\Windows\ntds
          Critical Object Installation:
          DS Drive Mappings:
          DSA Previous Restore Count:

     REPLICATION
     -----------

          Replicator notify pause after modify (secs):
          Replicator notify pause between DSAs (secs):
          Replicator intra site packet size (objects):
          Replicator intra site packet size (bytes):
          Replicator inter site packet size (objects):
          Replicator inter site packet size (bytes):
          Replicator maximum concurrent read threads:
          Replicator operation backlog limit:
          Replicator thread op priority threshold:
          Replicator intra site RPC handle lifetime (secs):
          Replicator inter site RPC handle lifetime (secs):
          Replicator RPC handle expiry check interval (secs):

     LDAP
     ----

          Max objects in LDAP Search (Admin Limit):
          Max concurrent LDAP connections allowed:
          Max time allowed for an LDAP Search:
          Max concurrent LDAP searches allowed:
          Max concurrent threads per LDAP connection allowed:
          Minimum idle seconds before potential \ timeout of LDAP connection (non-authenticated client):
          Minimum idle seconds before potential \ timeout of LDAP connection (authenticated client):

     Database
     --------

          Database backup path: C:\Windows\ntds\dsadata.bak
          Database backup interval (hours):
          Database log files path: C:\Windows\ntds
          Database logging/recovery: ON
          Hierarchy Table Recalculation interval (minutes): 720
          Database restored from backup:
          Pending object ownership conversions:
          EDB max buffers:
          EDB max log buffers:
          EDB log buffer flush threshold:
          EDB buffer flush start:
          EDB buffer flush stop:
          EDB max ver pages (increment over the minimum:
          Circular Logging:
          Server Functionality:
          TCP/IP Port:
          Restore from disk backup:
          Performance Counter Version:

     KCC
     ---

          Repl topology update delay (secs):
          Repl topology update period (secs):
          KCC site generator fail-over (minutes):
          KCC site generator renewal interval (minutes):
          KCC site generator renewal interval (minutes):
          CriticalLinkFailuresAllowed:
          MaxFailureTimeForCriticalLink (sec):
          NonCriticalLinkFailuresAllowed:
          MaxFailureTimeForNonCriticalLink (sec):
          IntersiteFailuresAllowed:
          MaxFailureTimeForIntersiteLink (sec):
          KCC connection failures:
          IntersiteFailuresAllowed:
          IntersiteFailuresAllowed:

***************************************************************************
                            Enterprise Data
***************************************************************************

Globally Unique Identifiers (GUIDs) for each domain controller in the enterprise
NOTE:  the absence of a GUID means that the server has been demoted.
--------------------------------------------------------------------------------

     Site Name:  Houston
     ---------------------------------------
     Site Options           :
     Site Topology Generator: CN=NTDS Settings,CN=JLP01,CN=Servers,CN=Houston,CN=Sites,CN=Configuration,DC=jlproler,DC=com
     Site Topology Renewal  :
     Site Topology Failover :

          HOUSV03
               Server GUID (used for DNS)                                         :
               Replication Database GUID (used to identify partner in replication):
               DSA Options               :
               DSA Computer Path         : CN=HOUSV03,OU=Manged Computers,DC=jlproler,DC=com
               DSA Schema Location       :
               DSA Mail Address          : _IsmService@48616ddb-c99b-4b22-ac49-c5aade446687._msdcs.jlproler.com
               DSA DNS Host Name         : housv03.jlproler.com
               DSA BridgeHead Transports :

          JLP01
               Server GUID (used for DNS)                                         : 7A188E15-C04D-4AE0-B311-81B58F324664
               Replication Database GUID (used to identify partner in replication): 7B524845-725C-4551-801B-67F22941764A
               DSA Options               : NTDSDSA_OPT_IS_GC
               DSA Computer Path         : CN=JLP01,OU=Domain Controllers,DC=jlproler,DC=com
               DSA Schema Location       : CN=Schema,CN=Configuration,DC=jlproler,DC=com
               DSA Mail Address          :
               DSA DNS Host Name         : JLP01.jlproler.com
               DSA BridgeHead Transports :

          JLP02
               Server GUID (used for DNS)                                         : 7C7BB7D7-CF5D-41A1-8050-BFC4ABC4AB76
               Replication Database GUID (used to identify partner in replication): A728F54E-8239-404F-A007-C7A33F054BDA
               DSA Options               : NTDSDSA_OPT_IS_GC
               DSA Computer Path         : CN=JLP02,OU=Domain Controllers,DC=jlproler,DC=com
               DSA Schema Location       : CN=Schema,CN=Configuration,DC=jlproler,DC=com
               DSA Mail Address          : _IsmService@7c7bb7d7-cf5d-41a1-8050-bfc4abc4ab76._msdcs.jlproler.com
               DSA DNS Host Name         : JLP02.jlproler.com
               DSA BridgeHead Transports :

          JLP03
               Server GUID (used for DNS)                                         : B4521947-7343-4B7A-B823-4AD10B7A4137
               Replication Database GUID (used to identify partner in replication): D6A7FE33-0184-480B-BC85-0EB5888523E6
               DSA Options               : NTDSDSA_OPT_IS_GC
               DSA Computer Path         : CN=JLP03,OU=Domain Controllers,DC=jlproler,DC=com
               DSA Schema Location       : CN=Schema,CN=Configuration,DC=jlproler,DC=com
               DSA Mail Address          :
               DSA DNS Host Name         : JLP03.jlproler.com
               DSA BridgeHead Transports :



Site Links and Site Link Bridges
-----------------------------------------------------

     Site Links
     ----------

          DEFAULTIPSITELINK
               Link Type:           : IP
               Distinguished Name   : CN=DEFAULTIPSITELINK,CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=jlproler,DC=com
               Replication Interval : 180
               Cost                 : 100
               Options              :
               Site List            :
                                      Houston

     Site Link Bridges
     ------------------

          Active Directory Replication Monitor determined that no Site Link Bridges are present in the Directory.
     Inter-Site Transports
     ---------------------

          IP
               Options     :
               DLL Name    : ismip.dll
               Address Type: dNSHostName

          SMTP
               Options     : NTDSTRANSPORT_OPT_IGNORE_SCHEDULES
               DLL Name    : ismsmtp.dll
               Address Type: mailAddress

     Subnets
     -------
          10.0.120.0/24
               Associated Site  : CN=Houston,CN=Sites,CN=Configuration,DC=jlproler,DC=com

     Active Directory Configuration Data
     -----------------------------------
          Stay of Execution for Servers: 0
          SPN Mappings                 : host=alerter,appmgmt,cisvc,clipsrv,browser,dhcp,dnscache,replicator,eventlog,eventsystem,policyagent,oakley,dmserver,dns,mcsvc,fax,msiserver,ias,messenger,netlogon,netman,netdde,netddedsm,nmagent,plugplay,protectedstorage,rasman,rpclocator,rpc,rpcss,remoteaccess,rsvp,samss,scardsvr,scesrv,seclogon,scm,dcom,cifs,spooler,snmp,schedule,tapisrv,trksvr,trkwks,ups,time,wins,www,http,w3svc,iisadmin

0
Comment
Question by:cookd47
  • 7
  • 6
13 Comments
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 33523382
In prepping for this migration, did you elevate the Server 2003 funtional level?  Did you run DCPromo on the Server 2003 server using the SBS media to extend the schema?
How many nics in each server and what are they connected to?
0
 

Author Comment

by:cookd47
ID: 33523629
Raised Functional Level; ran DC Romo on Server 2003
The 2003 servers have one card; the SBS 2008 has two
0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 33523747
That may be the problem...SBS can only have 1 enabled NIC..obviously it must be in the same subnet as the Sever 2003
0
 

Author Comment

by:cookd47
ID: 33523818
Since restrting is not an option, should I just unplug one and select "YES let it wait" ?
0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 33523858
it should be unplugged and disabled and then let it wait.
0
 

Author Comment

by:cookd47
ID: 33524034
How do you disable it?
I have no access to the OS; restarting is not n option
0
Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 35

Expert Comment

by:Cris Hanna
ID: 33524181
I don't know of a way to disable it outside the OS
Why is restarting not an option?  If FSMO roles have already gone to the SBS 2008, you should be able to get them back...or do a restore.
You can try unplugging and waiting or tell it to continue...but I suspect you're gonna have issues either way
by chance did you have WSUS running on the Server 2003 box?
0
 

Author Comment

by:cookd47
ID: 33524264
WSUS is not running; if I proceed, or restart, I may not be able to recover without rebuilding the domain.
0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 33524317
well I just attempted a migration from SBS 2008 to SBS v7 (beta) and it failed and I was able to get back and didn't have to do a restore nor rebuild the domain...required transferring the FSMO roles back to SBS 2008, Cleaning up DNS and AD to remove the SBS v7 server and had to reset DHCP on the 08 server...you would simply do that on the 03 server.
If you look at this blog from one of the other MVPs,  who is also a regular contributor on EE, http://blog.mpecsinc.ca/2009/06/sbs-2003-to-2008-migration-stall-event.html  Go to the troubleshooting section and he talks about disabling two services on the 08 box which resolved a similar issue for hime...Your mileage may vary.
0
 

Accepted Solution

by:
cookd47 earned 0 total points
ID: 33550826
Reviewed the event log (was able to launch utilities with Task Ngr); the was a journal wrap error that was preventing replication of the SYSVOL folder; found registry fix; migration completed.
NOTE: The unattended installatin had disabled the secong NIC.
0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 33550916
Journal wrap is a real pain!   Glad you were able to sort it out
0
 

Author Comment

by:cookd47
ID: 33659258
This issue should be closed; I resolved the problem (see comments)
0
 

Author Closing Comment

by:cookd47
ID: 33659268
I soolved the problem myself
0

Featured Post

Shouldn't all users have the same email signature?

You wouldn't let your users design their own business cards, would you? So, why do you let them design their own email signatures? Think of the damage they could be doing to your brand reputation! Choose the easy way to manage set up and add email signatures for all users.

Join & Write a Comment

Because virtualization becomes more and more common, and, with Microsoft Hyper-V included in Windows Server at no additional costs, and, most server hardware nowadays is more than capable of running a physical Small Business Server (SBS) 2008 or 201…
Synchronize a new Active Directory domain with an existing Office 365 tenant
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now