 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Design / January 2005Exchange 2003 Migration Headache
Hello, I had 2 NT4 Servers running exchange - a local and remote server across a T1. 1) Migrated an NT4 PDC with Exchange 5.5 to Server 2003 and Exchange 2003. Installed ADC and linked to server #2. This is the remote server. 2) The BDC at the main location is still running NT4 and Exchange 5.5. It has all the primary connectors to the Internet still. At this point, all works great. However, in preparation to move to all 2003: 3) Installed a new server with Server and Exchange 2003 at the primary location as AD and here is what happens: The #3 (new server) sees all 3 servers in Exchange Server Manager, but the #1 server only sees #1 and #2. Any help would be GREATLY appreciated. Dan Did you check replication already? How are you verifying that #3 can see the others? ESM? Al > Hello, > [quoted text clipped - 19 lines] > > Dan Hi Al, If you mean Site Replication Services in ESM, then yes I cjhecked it on both #1 and #3. They both show #1. Is there a tool or another place I should check? Thank you. Dan In this case, AD replication is what I'm after first. The SRS is for 5.5 backwards compatibility, so you'll want to check that with the 5.5 admin tools. Al > Hi Al, > [quoted text clipped - 5 lines] > > Dan Al, Hmmm, on #3 the AD Users and Computers -> System -> File Replication Object shows both #1 and #3. However, on the #1 system the System Object does not even show in the AD Users and Computers window. All DC's do show up in the Domain Controllers object. SRS seems to be fine. Thanks. Dan That's most likely due to the advanced view settings if I had to wager a guess. Are you familiar with Replmon? It's a tool used to visually show the replication of all your domain controllers. It would be a good idea to double check the replication of your AD to ensure that it's all working as expected. DCDIAG and NETDIAG from each DC is a good idea to help look for issues that may not be obvious until such a situation. Netdiag on the Exchange servers would also be helpful in troubleshooting this. -Al > Al, > [quoted text clipped - 10 lines] > > Dan Al, OK, you were right about the advanced view settings. So, #1 only shows #1 under File Replication. #3 shows #1 and #3 under File Replication. Yes, I have run netdiag /fix and dcdiag /fix on #1 and #3 servers. I ran ReplMon on #1 Server and added both #1 and #3 servers to it. Replmon shows an odd thing: #1 Server (FMGNTF) shows it's site as: Default-First-Site-Name #3 Server (FMG-OAS3) shows it's site as: FMG What's up with that and how do I get them syncronized? Following this is the Status Report from ReplMon run on #1 Server. Thanks again. Dan ***************************************** ReplMon Status Report: Active Directory Replication Monitor Printed on 1/25/2005 10:53:11 AM This report was generated on data from the server: FMGNTF *************************************************************************** FMGNTF Data *************************************************************************** This server currently has writable copies of the following directory partitions: --------------------------------------------------------------------------- DC=Matrix,DC=local CN=Configuration,DC=Matrix,DC=local CN=Schema,CN=Configuration,DC=Matrix,DC=local DC=DomainDnsZones,DC=Matrix,DC=local DC=ForestDnsZones,DC=Matrix,DC=local Because this server is a Global Catalog (GC) server, it also has copies of the following directory partitions: --------------------------------------------------------------------------- Current NTDS Connection Objects ------------------------------- Default-First-Site-Name\FMG-OAS3 Connection Name : 952823cf-7b4e-4cab-957d-5e0fb8a49679 Administrator Generated?: AUTO Reasons for this connection: Directory Partition (CN=Schema,CN=Configuration,DC=Matrix,DC=local) This replication connection is created because another replication partner has surpassed the allowed failure limit. Directory Partition (DC=Matrix,DC=local) This replication connection is created because another replication partner has surpassed the allowed failure limit. Directory Partition (CN=Configuration,DC=Matrix,DC=local) This replication connection is created because another replication partner has surpassed the allowed failure limit. Current Direct Replication Partner Status ----------------------------------------- Directory Partition: DC=Matrix,DC=local Change Notifications for this Directory Partition ------------------------------------------------- Server Name: Default-First-Site-Name\FMG-OAS3 Object GUID: 8CE71067-C054-444E-BCEE-81758378AF5A Time Added: <no value> Flags: DRS_WRIT_REP Transport: RPC Directory Partition: CN=Configuration,DC=Matrix,DC=local Change Notifications for this Directory Partition ------------------------------------------------- Server Name: Default-First-Site-Name\FMG-OAS3 Object GUID: 8CE71067-C054-444E-BCEE-81758378AF5A Time Added: <no value> Flags: DRS_WRIT_REP Transport: RPC Directory Partition: CN=Schema,CN=Configuration,DC=Matrix,DC=local Change Notifications for this Directory Partition ------------------------------------------------- Server Name: Default-First-Site-Name\FMG-OAS3 Object GUID: 8CE71067-C054-444E-BCEE-81758378AF5A Time Added: <no value> Flags: DRS_WRIT_REP Transport: RPC Directory Partition: DC=DomainDnsZones,DC=Matrix,DC=local Change Notifications for this Directory Partition ------------------------------------------------- Server Name: Default-First-Site-Name\FMG-OAS3 Object GUID: 8CE71067-C054-444E-BCEE-81758378AF5A Time Added: <no value> Flags: DRS_WRIT_REP Transport: RPC Directory Partition: DC=ForestDnsZones,DC=Matrix,DC=local Change Notifications for this Directory Partition ------------------------------------------------- Server Name: Default-First-Site-Name\FMG-OAS3 Object GUID: 8CE71067-C054-444E-BCEE-81758378AF5A Time Added: <no value> Flags: DRS_WRIT_REP Transport: RPC Current Transitive Replication Partner Status --------------------------------------------- Directory Partition: DC=Matrix,DC=local Partner Name: Default-First-Site-Name\FMGNTF Partner GUID: E0202A7D-D9AC-4CF1-909C-774AA21F5D7C USN: 165575 Directory Partition: CN=Configuration,DC=Matrix,DC=local Partner Name: Default-First-Site-Name\FMGNTF Partner GUID: E0202A7D-D9AC-4CF1-909C-774AA21F5D7C USN: 165575 Directory Partition: CN=Schema,CN=Configuration,DC=Matrix,DC=local Partner Name: Default-First-Site-Name\FMGNTF Partner GUID: E0202A7D-D9AC-4CF1-909C-774AA21F5D7C USN: 165575 Directory Partition: DC=DomainDnsZones,DC=Matrix,DC=local Partner Name: Default-First-Site-Name\FMGNTF Partner GUID: E0202A7D-D9AC-4CF1-909C-774AA21F5D7C USN: 165575 Directory Partition: DC=ForestDnsZones,DC=Matrix,DC=local Partner Name: Default-First-Site-Name\FMGNTF Partner GUID: E0202A7D-D9AC-4CF1-909C-774AA21F5D7C USN: 165575 Current Group Policy Object Status ---------------------------------- Default Domain Policy Group Policy Object GUID: {31B2F340-016D-11D2-945F-00C04FB984F9} Group Policy Object Version in the DS: 65539 Group Policy Object Version in SYSVOL: 65539 Default Domain Controllers Policy Group Policy Object GUID: {6AC1786C-016F-11D2-945F-00C04fB984F9} Group Policy Object Version in the DS: 10 Group Policy Object Version in SYSVOL: 10 The server FMGNTF knows about the following FSMO roles: -------------------------------------------------------------------------- Schema FSMO: Default-First-Site-Name\FMGNTF Domain Naming FSMO: Default-First-Site-Name\FMGNTF Infrastructure FSMO: Default-First-Site-Name\FMGNTF Primary Domain Controller FSMO: Default-First-Site-Name\FMGNTF RID Pool FSMO: Default-First-Site-Name\FMGNTF 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:\WINNT\NTDS\ntds.dit DSA Working Directory: C:\WINNT\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:\WINNT\NTDS\dsadata.bak Database backup interval (hours): Database log files path: D:\WINNT\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: 17 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: Default-First-Site-Name --------------------------------------- Site Options : Site Topology Generator: CN=NTDS Settings,CN=FMGNTF,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Matrix,DC=local Site Topology Renewal : Site Topology Failover : FMG-OAS3 Server GUID (used for DNS) : 8CE71067-C054-444E-BCEE-81758378AF5A Replication Database GUID (used to identify partner in replication): B3D50557-DB08-497C-85AA-A1AC3DFB716C DSA Options : DSA Computer Path : CN=FMG-OAS3,OU=Domain Controllers,DC=Matrix,DC=local DSA Schema Location : CN=Schema,CN=Configuration,DC=Matrix,DC=local DSA Mail Address : DSA DNS Host Name : DSA BridgeHead Transports : FMGNTF Server GUID (used for DNS) : E0202A7D-D9AC-4CF1-909C-774AA21F5D7C Replication Database GUID (used to identify partner in replication): E0202A7D-D9AC-4CF1-909C-774AA21F5D7C DSA Options : NTDSDSA_OPT_IS_GC DSA Computer Path : CN=FMGNTF,OU=Domain Controllers,DC=Matrix,DC=local DSA Schema Location : CN=Schema,CN=Configuration,DC=Matrix,DC=local DSA Mail Address : _IsmService@e0202a7d-d9ac-4cf1-909c-774aa21f5d7c._msdcs.Matrix.local DSA DNS Host Name : fmgntf.Matrix.local 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=Matrix,DC=local Replication Interval : 180 Cost : 100 Options : Site List : Default-First-Site-Name 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 ------- Active Directory Replication Monitor determined that no Subnets are present in the Directory. 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,msdtc Al, Oh yeah, here are the Netdiag and dcdiag results: On #1 Server: all tests passed (or skipped) On #3 Server: all netdiag passed, all dcdiag (/fix) passed except for the following: Testing server: FMG\FMG-OAS3 Starting test: Replications REPLICATION LATENCY WARNING ERROR: Expected notification link is missing. Source FMGNTF Replication of new changes along this path will be delayed. This problem should self-correct on the next periodic sync. ......................... FMG-OAS3 passed test Replications Starting test: frsevent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. So, I went to the event viewer and have noticed that the following errors are happening: Event Type: Warning Event Source: NtFrs Event Category: None Event ID: 13508 Date: 1/25/2005 Time: 1:02:06 AM User: N/A Computer: FMG-OAS3 Description: The File Replication Service is having trouble enabling replication from FMGNTF to FMG-OAS3 for c:\windows\sysvol\domain using the DNS name fmgntf.Matrix.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name fmgntf.Matrix.local from this computer. [2] FRS is not running on fmgntf.Matrix.local. [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Thanks! Dan Dan it would probably be easier if we could see the entire dcdiag and netdiag results for each of the servers. In the meantime, have you seen this: http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/active directory/maintain/opsguide/part1/adogd11.mspx#EMAA > Al, > [quoted text clipped - 53 lines] > > Dan Al, So, using ReplMon, I figured I had the DNS setup incorrectly on #1 server. I change that and (eventually) all replication started to work correctly. Thanks again for your assistance. Dan Glad it worked out for you. Thanks for posting the answer. -Al > Al, > [quoted text clipped - 7 lines] > > Dan Al, Hey no problem - hopefully some else can use this solution as well. Speaking of that, I made another post about another system I am working on and no one has replied as of yet. Can you take a look? It's at: http://groups-beta.google.com/group/microsoft.public.win2000.dns/browse_frm/thre ad/5af08f4fa7db1f9f Thanks! Dan My first pass is that it would be something to do with the way you dual-homed the machines. DC's don't tend to like that out of the box. How'd you configure them and why have DC's as web servers like that? > Al, > [quoted text clipped - 8 lines] > > Dan |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.