| Home | Register | Members | Search | Links |
 |
| Thread Tools | Display Modes |
|
Guest
Posts: n/a
|
|
|
|
||
|
|
| |
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
Hi Jorge. Thanks for confirming the application partition replication for
me. If you have any advice on the replication periods described below I would really appreciate it. The one area I'm still slightly concerned about is the "Last attempt @ (never) was successful" statement on the Schema replication. I have forced replication in both directions using the GUI and repadmin, both of these appear successful but have no impact on this one descriptive entry. What is still a little confusing is why replmon shows the Schema replication regularly during all other normal replications but the date and time never get listed in repadmin. On my test network I have moved the FSMO roles to the 2003 DC and on then examining the repadmin output it then changes from Last attempt @ (never) to a recent time period and appears to replicate normally. My only concern is that the Schema on the 2000 DC may be different to the 2003 DC and when the FSMO roles are transferred, there may be differences between the two DCs. The Last attempt @ (never) is only listed on the 2003 DC under OUTBOUND NEIGHBORS, the 2000 DC shows INBOUND and OUTBOUND replications although the last OUTBOUND NEIGHBORS for this 2000 DC are all around the time when the 2003 DC was added i.e. over 2 days ago, even though the 2003 DC shows recent replications within the last few hours. I'm not overly familiar with the expected regularity of the replications that should be shows in repadmin, does these time periods sound correct ? There are no event errors or anything else to suggest anything is wrong but I want to be sure before I transfer the FSMO roles on the live network and demote and replace the 2000 DC. I was just about to post the message above when I noticed one other difference  . On my test network the DomainDnsZones and ForestDnsZoneshave been created which you clarified in your previous posting. I have just checked this on the live network which currently has only had adprep executed on the 2000 DC and the new 2003 DC added. The 2003 DC does not have the DomainDnsZones and ForestDnsZone listed in replmon. Is this becuase I have not transferred the FSMO roles, I remember reading that for the new Partitions to be created the Domain Naming Master had to be on a 2003 server, on the live network it is currently still on the 2000 ? Thanks again for your help, Alex. "Jorge de Almeida Pinto [MVP - DS]" <SubstituteThisWithMyFullNameSeparatedByDots@gmail .com> wrote in message news:(E-Mail Removed)... > it should be OK.... have you forced replication both ways? > > application partitions can only be hosted on w2k3 DCs and later. w2k dcs > do not understand the concept of application partitions > > -- > > Cheers, > (HOPEFULLY THIS INFORMATION HELPS YOU!) > > # Jorge de Almeida Pinto # MVP Windows Server - Directory Services > > BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx > BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx > ------------------------------------------------------------------------------------------ > * This posting is provided "AS IS" with no warranties and confers no > rights! > * Always test before implementing! > ------------------------------------------------------------------------------------------ > ################################################# > ################################################# > ------------------------------------------------------------------------------------------ > "Alex" <(E-Mail Removed)> wrote in message > news:eLB8%(E-Mail Removed)... >> Hi Jorge. Thanks for the links, I've had a quick read through one of >> those links before but didn't have any of the scenarios that were listed. >> I'll have any read through them in case I missed something. I have a >> test network setup which mirrors the upgrade of the DCs and was built >> from an image of the DC on the live network. There are currently no >> errors appearing in the event logs and no system problems to suggest >> there are any issues. I have also used the replmon tool and if I look at >> CN=Schema,CNConfiguration,DC=DOMAIN,DC=LOCAL on both the DC1 and DC2 they >> both have entries to say successfully replication regularly as expected, >> but the repadmin tool still shows "Last attempt @ (never) was successful" >> on the new 2003 DC. >> >> I have also noticed that the new 2003 DC2 has two extra directory >> partitions, DC=DomainDnsZones,DC=DOMAIN,DC=LOCAL and >> DC=ForestDnsZones,DC=DOMAIN,DC=LOCAL, they partitions are not on the >> older 2000 DC1, both DCs are setup as AD-Integrated DNS Servers. >> >> Thanks, >> Alex. >> >> >> >> >> "Jorge de Almeida Pinto [MVP - DS]" >> <SubstituteThisWithMyFullNameSeparatedByDots@gmail .com> wrote in message >> news:(E-Mail Removed)... >>> http://blogs.dirteam.com/blogs/jorge...on-Issues.aspx >>> >>> -- >>> >>> Cheers, >>> (HOPEFULLY THIS INFORMATION HELPS YOU!) >>> >>> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services >>> >>> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx >>> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx >>> ------------------------------------------------------------------------------------------ >>> * This posting is provided "AS IS" with no warranties and confers no >>> rights! >>> * Always test before implementing! >>> ------------------------------------------------------------------------------------------ >>> ################################################# >>> ################################################# >>> ------------------------------------------------------------------------------------------ >>> "User" <(E-Mail Removed)> wrote in message >>> news:%(E-Mail Removed)... >>>> Hi. We currently have a single domain with one DC (Windows 200 Srv >>>> Std) and are currently in the process of upgrading to 2003 R2 Ent. We >>>> have added a second DC with 2003 R2 Ent and there have been no >>>> unexpected errors in the Event Logs (just the expected replication >>>> notifications etc), no errors in DCDiag and similarly no obvious errors >>>> in repadmin. On running "repadmin /showrepl /all /verobose [DCName]" >>>> against the original 2000 DC all entries for inbound and outbound >>>> neighbours have successful replication results and valid times. But, >>>> on running the same command against the new 2003 DC all inbound and >>>> neighbours have similar results apart from >>>> "CN=Schema,CN=Configuration,DC=domain,DC=local " which has the result >>>> "Last attempt @ (never) was successful". >>>> >>>> I have searched online and found some documentation and postings with >>>> this same entry but have not been able to determine whether this is an >>>> acceptable result or whether this should have been replicated and >>>> therefore if we have a problem to resolve before we continue. Just in >>>> case this has any relevance the original 2000 DC with all successful >>>> results is currently holding all 5 FSMO roles, both DCs are GC. We >>>> were planning on transferring the FSMO roles to the new DC, demoting >>>> the 2000 DC to a member server and replacing it with a new 2003 R2 Ent >>>> server with the same name, dcpromo that to a DC with GC and eventually >>>> transfer the FSMO roles back. >>>> >>>> Can anyone give me any advice regarding this repadmin entry and what I >>>> should be doing with it ? >>>> >>>> Thanks for any help, >>>> Alex. >>>> >>> >>> >> >> > > |
|
|
|
|
|||
|
Guest
Posts: n/a
|
Hi Jorge. I've been thinking about the issues over the weekend and I think
so far everything is alright. The 2003 DC adds the DomainDnsZones and ForestDnsZones automatically when it is given the Domain Naming Master role and the DNS service is restarted. My understanding of the 'Last attempt @ (never) was successful' for the Schema should be acceptable because the 2000 DC Schema was updated with adprep to match the new 2003 R2 schema. Since the 2000 DC and 2003 DCs should now having matching schemas and therefore no replication is required. The 'Last attempt @' then changes to a more recent date and time when the Schema master role is transferred to the 2003 DC, I'm not quite sure why this is the case but it seems to make sense ?  I have left the live and test systems running unchanged now for 24 hours to be on the safe side. There have been no errors in the event logs and replication appears to be working correctly. The only unusual entry which I haven't seen before is with dcdiag. On running dcdiag against the 2000 DC the Replication latency check is listed as 'Not available on this DC' which is expected for a 2000 DC. But the 2003DC has the following replication results : Starting Test: Replication * Replications Check * Replications Latency Check CN=Schema, CN=Configuration,DC=DOMAIN,DC=NET Latency information for 1 entries in the vector were ignored. 1 were retired invocations. 0 were either: read-only replicas and are not verifiable latent, or dc's no longer replicating this nc. 0 had no latency information (Win2k DC). CN=Configuration,DC=DOMAIN,DC=NET Latency information for 1 entries in the vector were ignored. 1 were retired invocations. 0 were either: read-only replicas and are not verifiable latent, or dc's no longer replicating this nc. 0 had no latency information (Win2k DC). DC=DOMAIN,DC=NET Latency information for 1 entries in the vector were ignored. 1 were retired invocations. 0 were either: read-only replicas and are not verifiable latent, or dc's no longer replicating this nc. 0 had no latency information (Win2k DC). * Replication Site Latency Check .......................................DC2 Passed test Replications I haven't seen this type of output on a dcdiag check before from a 2003 DC, do you have any advice on whether this is normal ? I suspect this is related to the 2000 and 2003 DC combination, I have searched to try and find an explanation for these entries but so far haven't been able to find any documentation. Hopefully this is most of the issues now covered and I can finally demote the 2000 DC Thanks again, Alex. "Alex" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)... > Hi Jorge. Thanks for confirming the application partition replication for > me. If you have any advice on the replication periods described below I > would really appreciate it. > > The one area I'm still slightly concerned about is the "Last attempt @ > (never) was successful" statement on the Schema replication. I have > forced replication in both directions using the GUI and repadmin, both of > these appear successful but have no impact on this one descriptive entry. > What is still a little confusing is why replmon shows the Schema > replication regularly during all other normal replications but the date > and time never get listed in repadmin. > On my test network I have moved the FSMO roles to the 2003 DC and on then > examining the repadmin output it then changes from Last attempt @ (never) > to a recent time period and appears to replicate normally. My only > concern is that the Schema on the 2000 DC may be different to the 2003 DC > and when the FSMO roles are transferred, there may be differences between > the two DCs. The Last attempt @ (never) is only listed on the 2003 DC > under OUTBOUND NEIGHBORS, the 2000 DC shows INBOUND and OUTBOUND > replications although the last OUTBOUND NEIGHBORS for this 2000 DC are all > around the time when the 2003 DC was added i.e. over 2 days ago, even > though the 2003 DC shows recent replications within the last few hours. > > I'm not overly familiar with the expected regularity of the replications > that should be shows in repadmin, does these time periods sound correct ? > There are no event errors or anything else to suggest anything is wrong > but I want to be sure before I transfer the FSMO roles on the live network > and demote and replace the 2000 DC. > > I was just about to post the message above when I noticed one other > difference . On my test network the DomainDnsZones and ForestDnsZones> have been created which you clarified in your previous posting. I have > just checked this on the live network which currently has only had adprep > executed on the 2000 DC and the new 2003 DC added. The 2003 DC does not > have the DomainDnsZones and ForestDnsZone listed in replmon. Is this > becuase I have not transferred the FSMO roles, I remember reading that for > the new Partitions to be created the Domain Naming Master had to be on a > 2003 server, on the live network it is currently still on the 2000 ? > > Thanks again for your help, > Alex. > > > "Jorge de Almeida Pinto [MVP - DS]" > <SubstituteThisWithMyFullNameSeparatedByDots@gmail .com> wrote in message > news:(E-Mail Removed)... >> it should be OK.... have you forced replication both ways? >> >> application partitions can only be hosted on w2k3 DCs and later. w2k dcs >> do not understand the concept of application partitions >> >> -- >> >> Cheers, >> (HOPEFULLY THIS INFORMATION HELPS YOU!) >> >> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services >> >> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx >> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx >> ------------------------------------------------------------------------------------------ >> * This posting is provided "AS IS" with no warranties and confers no >> rights! >> * Always test before implementing! >> ------------------------------------------------------------------------------------------ >> ################################################# >> ################################################# >> ------------------------------------------------------------------------------------------ >> "Alex" <(E-Mail Removed)> wrote in message >> news:eLB8%(E-Mail Removed)... >>> Hi Jorge. Thanks for the links, I've had a quick read through one of >>> those links before but didn't have any of the scenarios that were >>> listed. I'll have any read through them in case I missed something. I >>> have a test network setup which mirrors the upgrade of the DCs and was >>> built from an image of the DC on the live network. There are currently >>> no errors appearing in the event logs and no system problems to suggest >>> there are any issues. I have also used the replmon tool and if I look >>> at CN=Schema,CNConfiguration,DC=DOMAIN,DC=LOCAL on both the DC1 and DC2 >>> they both have entries to say successfully replication regularly as >>> expected, but the repadmin tool still shows "Last attempt @ (never) was >>> successful" on the new 2003 DC. >>> >>> I have also noticed that the new 2003 DC2 has two extra directory >>> partitions, DC=DomainDnsZones,DC=DOMAIN,DC=LOCAL and >>> DC=ForestDnsZones,DC=DOMAIN,DC=LOCAL, they partitions are not on the >>> older 2000 DC1, both DCs are setup as AD-Integrated DNS Servers. >>> >>> Thanks, >>> Alex. >>> >>> >>> >>> >>> "Jorge de Almeida Pinto [MVP - DS]" >>> <SubstituteThisWithMyFullNameSeparatedByDots@gmail .com> wrote in message >>> news:(E-Mail Removed)... >>>> http://blogs.dirteam.com/blogs/jorge...on-Issues.aspx >>>> >>>> -- >>>> >>>> Cheers, >>>> (HOPEFULLY THIS INFORMATION HELPS YOU!) >>>> >>>> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services >>>> >>>> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx >>>> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx >>>> ------------------------------------------------------------------------------------------ >>>> * This posting is provided "AS IS" with no warranties and confers no >>>> rights! >>>> * Always test before implementing! >>>> ------------------------------------------------------------------------------------------ >>>> ################################################# >>>> ################################################# >>>> ------------------------------------------------------------------------------------------ >>>> "User" <(E-Mail Removed)> wrote in message >>>> news:%(E-Mail Removed)... >>>>> Hi. We currently have a single domain with one DC (Windows 200 Srv >>>>> Std) and are currently in the process of upgrading to 2003 R2 Ent. We >>>>> have added a second DC with 2003 R2 Ent and there have been no >>>>> unexpected errors in the Event Logs (just the expected replication >>>>> notifications etc), no errors in DCDiag and similarly no obvious >>>>> errors in repadmin. On running "repadmin /showrepl /all /verobose >>>>> [DCName]" against the original 2000 DC all entries for inbound and >>>>> outbound neighbours have successful replication results and valid >>>>> times. But, on running the same command against the new 2003 DC all >>>>> inbound and neighbours have similar results apart from >>>>> "CN=Schema,CN=Configuration,DC=domain,DC=local " which has the result >>>>> "Last attempt @ (never) was successful". >>>>> >>>>> I have searched online and found some documentation and postings with >>>>> this same entry but have not been able to determine whether this is an >>>>> acceptable result or whether this should have been replicated and >>>>> therefore if we have a problem to resolve before we continue. Just in >>>>> case this has any relevance the original 2000 DC with all successful >>>>> results is currently holding all 5 FSMO roles, both DCs are GC. We >>>>> were planning on transferring the FSMO roles to the new DC, demoting >>>>> the 2000 DC to a member server and replacing it with a new 2003 R2 Ent >>>>> server with the same name, dcpromo that to a DC with GC and eventually >>>>> transfer the FSMO roles back. >>>>> >>>>> Can anyone give me any advice regarding this repadmin entry and what I >>>>> should be doing with it ? >>>>> >>>>> Thanks for any help, >>>>> Alex. >>>>> >>>> >>>> >>> >>> >> >> > > |
|
|
|
|
|||
|
Guest
Posts: n/a
|
yes, it is true, the app NCs will be created as soon as the domain naming
FSMO is on a w2k3 DC -- Cheers, (HOPEFULLY THIS INFORMATION HELPS YOU!) # Jorge de Almeida Pinto # MVP Windows Server - Directory Services BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx ------------------------------------------------------------------------------------------ * This posting is provided "AS IS" with no warranties and confers no rights! * Always test before implementing! ------------------------------------------------------------------------------------------ ################################################# ################################################# ------------------------------------------------------------------------------------------ "Alex" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)... > Hi Jorge. Thanks for confirming the application partition replication for > me. If you have any advice on the replication periods described below I > would really appreciate it. > > The one area I'm still slightly concerned about is the "Last attempt @ > (never) was successful" statement on the Schema replication. I have > forced replication in both directions using the GUI and repadmin, both of > these appear successful but have no impact on this one descriptive entry. > What is still a little confusing is why replmon shows the Schema > replication regularly during all other normal replications but the date > and time never get listed in repadmin. > On my test network I have moved the FSMO roles to the 2003 DC and on then > examining the repadmin output it then changes from Last attempt @ (never) > to a recent time period and appears to replicate normally. My only > concern is that the Schema on the 2000 DC may be different to the 2003 DC > and when the FSMO roles are transferred, there may be differences between > the two DCs. The Last attempt @ (never) is only listed on the 2003 DC > under OUTBOUND NEIGHBORS, the 2000 DC shows INBOUND and OUTBOUND > replications although the last OUTBOUND NEIGHBORS for this 2000 DC are all > around the time when the 2003 DC was added i.e. over 2 days ago, even > though the 2003 DC shows recent replications within the last few hours. > > I'm not overly familiar with the expected regularity of the replications > that should be shows in repadmin, does these time periods sound correct ? > There are no event errors or anything else to suggest anything is wrong > but I want to be sure before I transfer the FSMO roles on the live network > and demote and replace the 2000 DC. > > I was just about to post the message above when I noticed one other > difference . On my test network the DomainDnsZones and ForestDnsZones> have been created which you clarified in your previous posting. I have > just checked this on the live network which currently has only had adprep > executed on the 2000 DC and the new 2003 DC added. The 2003 DC does not > have the DomainDnsZones and ForestDnsZone listed in replmon. Is this > becuase I have not transferred the FSMO roles, I remember reading that for > the new Partitions to be created the Domain Naming Master had to be on a > 2003 server, on the live network it is currently still on the 2000 ? > > Thanks again for your help, > Alex. > > > "Jorge de Almeida Pinto [MVP - DS]" > <SubstituteThisWithMyFullNameSeparatedByDots@gmail .com> wrote in message > news:(E-Mail Removed)... >> it should be OK.... have you forced replication both ways? >> >> application partitions can only be hosted on w2k3 DCs and later. w2k dcs >> do not understand the concept of application partitions >> >> -- >> >> Cheers, >> (HOPEFULLY THIS INFORMATION HELPS YOU!) >> >> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services >> >> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx >> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx >> ------------------------------------------------------------------------------------------ >> * This posting is provided "AS IS" with no warranties and confers no >> rights! >> * Always test before implementing! >> ------------------------------------------------------------------------------------------ >> ################################################# >> ################################################# >> ------------------------------------------------------------------------------------------ >> "Alex" <(E-Mail Removed)> wrote in message >> news:eLB8%(E-Mail Removed)... >>> Hi Jorge. Thanks for the links, I've had a quick read through one of >>> those links before but didn't have any of the scenarios that were >>> listed. I'll have any read through them in case I missed something. I >>> have a test network setup which mirrors the upgrade of the DCs and was >>> built from an image of the DC on the live network. There are currently >>> no errors appearing in the event logs and no system problems to suggest >>> there are any issues. I have also used the replmon tool and if I look >>> at CN=Schema,CNConfiguration,DC=DOMAIN,DC=LOCAL on both the DC1 and DC2 >>> they both have entries to say successfully replication regularly as >>> expected, but the repadmin tool still shows "Last attempt @ (never) was >>> successful" on the new 2003 DC. >>> >>> I have also noticed that the new 2003 DC2 has two extra directory >>> partitions, DC=DomainDnsZones,DC=DOMAIN,DC=LOCAL and >>> DC=ForestDnsZones,DC=DOMAIN,DC=LOCAL, they partitions are not on the >>> older 2000 DC1, both DCs are setup as AD-Integrated DNS Servers. >>> >>> Thanks, >>> Alex. >>> >>> >>> >>> >>> "Jorge de Almeida Pinto [MVP - DS]" >>> <SubstituteThisWithMyFullNameSeparatedByDots@gmail .com> wrote in message >>> news:(E-Mail Removed)... >>>> http://blogs.dirteam.com/blogs/jorge...on-Issues.aspx >>>> >>>> -- >>>> >>>> Cheers, >>>> (HOPEFULLY THIS INFORMATION HELPS YOU!) >>>> >>>> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services >>>> >>>> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx >>>> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx >>>> ------------------------------------------------------------------------------------------ >>>> * This posting is provided "AS IS" with no warranties and confers no >>>> rights! >>>> * Always test before implementing! >>>> ------------------------------------------------------------------------------------------ >>>> ################################################# >>>> ################################################# >>>> ------------------------------------------------------------------------------------------ >>>> "User" <(E-Mail Removed)> wrote in message >>>> news:%(E-Mail Removed)... >>>>> Hi. We currently have a single domain with one DC (Windows 200 Srv >>>>> Std) and are currently in the process of upgrading to 2003 R2 Ent. We >>>>> have added a second DC with 2003 R2 Ent and there have been no >>>>> unexpected errors in the Event Logs (just the expected replication >>>>> notifications etc), no errors in DCDiag and similarly no obvious >>>>> errors in repadmin. On running "repadmin /showrepl /all /verobose >>>>> [DCName]" against the original 2000 DC all entries for inbound and >>>>> outbound neighbours have successful replication results and valid >>>>> times. But, on running the same command against the new 2003 DC all >>>>> inbound and neighbours have similar results apart from >>>>> "CN=Schema,CN=Configuration,DC=domain,DC=local " which has the result >>>>> "Last attempt @ (never) was successful". >>>>> >>>>> I have searched online and found some documentation and postings with >>>>> this same entry but have not been able to determine whether this is an >>>>> acceptable result or whether this should have been replicated and >>>>> therefore if we have a problem to resolve before we continue. Just in >>>>> case this has any relevance the original 2000 DC with all successful >>>>> results is currently holding all 5 FSMO roles, both DCs are GC. We >>>>> were planning on transferring the FSMO roles to the new DC, demoting >>>>> the 2000 DC to a member server and replacing it with a new 2003 R2 Ent >>>>> server with the same name, dcpromo that to a DC with GC and eventually >>>>> transfer the FSMO roles back. >>>>> >>>>> Can anyone give me any advice regarding this repadmin entry and what I >>>>> should be doing with it ? >>>>> >>>>> Thanks for any help, >>>>> Alex. >>>>> >>>> >>>> >>> >>> >> >> > > |
|
|
|
|
|||
|
Guest
Posts: n/a
|
> the 2000 DC and 2003 DCs should now having matching schemas and therefore
> no replication is required. The 'Last attempt @' then changes to a more > recent date and time when the Schema master role is transferred to the > 2003 DC, I'm not quite sure why this is the case but it seems to make > sense ? that is because the transfer of the schema FSMO triggers a change in the schema NC and because of that the DC notifies other DCs in the same site on the other thing.... it is OK. nothing to worry about. -- Cheers, (HOPEFULLY THIS INFORMATION HELPS YOU!) # Jorge de Almeida Pinto # MVP Windows Server - Directory Services BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx ------------------------------------------------------------------------------------------ * This posting is provided "AS IS" with no warranties and confers no rights! * Always test before implementing! ------------------------------------------------------------------------------------------ ################################################# ################################################# ------------------------------------------------------------------------------------------ "Alex" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)... > Hi Jorge. I've been thinking about the issues over the weekend and I > think so far everything is alright. The 2003 DC adds the DomainDnsZones > and ForestDnsZones automatically when it is given the Domain Naming Master > role and the DNS service is restarted. My understanding of the 'Last > attempt @ (never) was successful' for the Schema should be acceptable > because the 2000 DC Schema was updated with adprep to match the new 2003 > R2 schema. Since the 2000 DC and 2003 DCs should now having matching > schemas and therefore no replication is required. The 'Last attempt @' > then changes to a more recent date and time when the Schema master role is > transferred to the 2003 DC, I'm not quite sure why this is the case but it > seems to make sense ? > > I have left the live and test systems running unchanged now for 24 hours > to be on the safe side. There have been no errors in the event logs and > replication appears to be working correctly. The only unusual entry which > I haven't seen before is with dcdiag. On running dcdiag against the 2000 > DC the Replication latency check is listed as 'Not available on this DC' > which is expected for a 2000 DC. But the 2003DC has the following > replication results : > > Starting Test: Replication > * Replications Check > * Replications Latency Check > CN=Schema, CN=Configuration,DC=DOMAIN,DC=NET > Latency information for 1 entries in the vector were ignored. > 1 were retired invocations. 0 were either: read-only > replicas and are not verifiable latent, or dc's no longer replicating this > nc. 0 had no latency information (Win2k DC). > CN=Configuration,DC=DOMAIN,DC=NET > Latency information for 1 entries in the vector were ignored. > 1 were retired invocations. 0 were either: read-only > replicas and are not verifiable latent, or dc's no longer replicating this > nc. 0 had no latency information (Win2k DC). > DC=DOMAIN,DC=NET > Latency information for 1 entries in the vector were ignored. > 1 were retired invocations. 0 were either: read-only > replicas and are not verifiable latent, or dc's no longer replicating this > nc. 0 had no latency information (Win2k DC). > * Replication Site Latency Check > .......................................DC2 Passed test Replications > > I haven't seen this type of output on a dcdiag check before from a 2003 > DC, do you have any advice on whether this is normal ? I suspect this is > related to the 2000 and 2003 DC combination, I have searched to try and > find an explanation for these entries but so far haven't been able to find > any documentation. Hopefully this is most of the issues now covered and I > can finally demote the 2000 DC > > Thanks again, > Alex. > > > "Alex" <(E-Mail Removed)> wrote in message > news:(E-Mail Removed)... >> Hi Jorge. Thanks for confirming the application partition replication >> for me. If you have any advice on the replication periods described below >> I would really appreciate it. >> >> The one area I'm still slightly concerned about is the "Last attempt @ >> (never) was successful" statement on the Schema replication. I have >> forced replication in both directions using the GUI and repadmin, both of >> these appear successful but have no impact on this one descriptive entry. >> What is still a little confusing is why replmon shows the Schema >> replication regularly during all other normal replications but the date >> and time never get listed in repadmin. >> On my test network I have moved the FSMO roles to the 2003 DC and on then >> examining the repadmin output it then changes from Last attempt @ (never) >> to a recent time period and appears to replicate normally. My only >> concern is that the Schema on the 2000 DC may be different to the 2003 DC >> and when the FSMO roles are transferred, there may be differences between >> the two DCs. The Last attempt @ (never) is only listed on the 2003 DC >> under OUTBOUND NEIGHBORS, the 2000 DC shows INBOUND and OUTBOUND >> replications although the last OUTBOUND NEIGHBORS for this 2000 DC are >> all around the time when the 2003 DC was added i.e. over 2 days ago, even >> though the 2003 DC shows recent replications within the last few hours. >> >> I'm not overly familiar with the expected regularity of the replications >> that should be shows in repadmin, does these time periods sound correct ? >> There are no event errors or anything else to suggest anything is wrong >> but I want to be sure before I transfer the FSMO roles on the live >> network and demote and replace the 2000 DC. >> >> I was just about to post the message above when I noticed one other >> difference . On my test network the DomainDnsZones and ForestDnsZones>> have been created which you clarified in your previous posting. I have >> just checked this on the live network which currently has only had adprep >> executed on the 2000 DC and the new 2003 DC added. The 2003 DC does not >> have the DomainDnsZones and ForestDnsZone listed in replmon. Is this >> becuase I have not transferred the FSMO roles, I remember reading that >> for the new Partitions to be created the Domain Naming Master had to be >> on a 2003 server, on the live network it is currently still on the 2000 ? >> >> Thanks again for your help, >> Alex. >> >> >> "Jorge de Almeida Pinto [MVP - DS]" >> <SubstituteThisWithMyFullNameSeparatedByDots@gmail .com> wrote in message >> news:(E-Mail Removed)... >>> it should be OK.... have you forced replication both ways? >>> >>> application partitions can only be hosted on w2k3 DCs and later. w2k dcs >>> do not understand the concept of application partitions >>> >>> -- >>> >>> Cheers, >>> (HOPEFULLY THIS INFORMATION HELPS YOU!) >>> >>> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services >>> >>> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx >>> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx >>> ------------------------------------------------------------------------------------------ >>> * This posting is provided "AS IS" with no warranties and confers no >>> rights! >>> * Always test before implementing! >>> ------------------------------------------------------------------------------------------ >>> ################################################# >>> ################################################# >>> ------------------------------------------------------------------------------------------ >>> "Alex" <(E-Mail Removed)> wrote in message >>> news:eLB8%(E-Mail Removed)... >>>> Hi Jorge. Thanks for the links, I've had a quick read through one of >>>> those links before but didn't have any of the scenarios that were >>>> listed. I'll have any read through them in case I missed something. I >>>> have a test network setup which mirrors the upgrade of the DCs and was >>>> built from an image of the DC on the live network. There are currently >>>> no errors appearing in the event logs and no system problems to suggest >>>> there are any issues. I have also used the replmon tool and if I look >>>> at CN=Schema,CNConfiguration,DC=DOMAIN,DC=LOCAL on both the DC1 and DC2 >>>> they both have entries to say successfully replication regularly as >>>> expected, but the repadmin tool still shows "Last attempt @ (never) was >>>> successful" on the new 2003 DC. >>>> >>>> I have also noticed that the new 2003 DC2 has two extra directory >>>> partitions, DC=DomainDnsZones,DC=DOMAIN,DC=LOCAL and >>>> DC=ForestDnsZones,DC=DOMAIN,DC=LOCAL, they partitions are not on the >>>> older 2000 DC1, both DCs are setup as AD-Integrated DNS Servers. >>>> >>>> Thanks, >>>> Alex. >>>> >>>> >>>> >>>> >>>> "Jorge de Almeida Pinto [MVP - DS]" >>>> <SubstituteThisWithMyFullNameSeparatedByDots@gmail .com> wrote in >>>> message news:(E-Mail Removed)... >>>>> http://blogs.dirteam.com/blogs/jorge...on-Issues.aspx >>>>> >>>>> -- >>>>> >>>>> Cheers, >>>>> (HOPEFULLY THIS INFORMATION HELPS YOU!) >>>>> >>>>> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services >>>>> >>>>> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx >>>>> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx >>>>> ------------------------------------------------------------------------------------------ >>>>> * This posting is provided "AS IS" with no warranties and confers no >>>>> rights! >>>>> * Always test before implementing! >>>>> ------------------------------------------------------------------------------------------ >>>>> ################################################# >>>>> ################################################# >>>>> ------------------------------------------------------------------------------------------ >>>>> "User" <(E-Mail Removed)> wrote in message >>>>> news:%(E-Mail Removed)... >>>>>> Hi. We currently have a single domain with one DC (Windows 200 Srv >>>>>> Std) and are currently in the process of upgrading to 2003 R2 Ent. >>>>>> We have added a second DC with 2003 R2 Ent and there have been no >>>>>> unexpected errors in the Event Logs (just the expected replication >>>>>> notifications etc), no errors in DCDiag and similarly no obvious >>>>>> errors in repadmin. On running "repadmin /showrepl /all /verobose >>>>>> [DCName]" against the original 2000 DC all entries for inbound and >>>>>> outbound neighbours have successful replication results and valid >>>>>> times. But, on running the same command against the new 2003 DC all >>>>>> inbound and neighbours have similar results apart from >>>>>> "CN=Schema,CN=Configuration,DC=domain,DC=local " which has the result >>>>>> "Last attempt @ (never) was successful". >>>>>> >>>>>> I have searched online and found some documentation and postings with >>>>>> this same entry but have not been able to determine whether this is >>>>>> an acceptable result or whether this should have been replicated and >>>>>> therefore if we have a problem to resolve before we continue. Just >>>>>> in case this has any relevance the original 2000 DC with all >>>>>> successful results is currently holding all 5 FSMO roles, both DCs >>>>>> are GC. We were planning on transferring the FSMO roles to the new >>>>>> DC, demoting the 2000 DC to a member server and replacing it with a >>>>>> new 2003 R2 Ent server with the same name, dcpromo that to a DC with >>>>>> GC and eventually transfer the FSMO roles back. >>>>>> >>>>>> Can anyone give me any advice regarding this repadmin entry and what >>>>>> I should be doing with it ? >>>>>> >>>>>> Thanks for any help, >>>>>> Alex. >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > |
|
|
|
|
|||
|
|
| |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Network Schema | Marco Pais | Windows Networking | 0 | 04-11-2006 01:08 PM |
| Network schema | Marco Pais | Windows Networking | 0 | 03-30-2006 01:18 PM |
| WINS replication issue - periodic replication not occurring | arrowman | Windows Networking | 0 | 05-26-2005 02:25 PM |
| Modifying router's IP schema | Mercedes | Broadband Hardware | 1 | 12-14-2004 06:15 PM |
| MN-740's has anyone updated them successful? | faustus | Broadband Hardware | 12 | 01-16-2004 07:02 PM |
Linear Mode
