Windows Server - Dfs replication between Windows server 2003 R2 and Windows server
Asked By lenm12
22-May-07 11:45 AM
Every time I try to replicate a folder between a windows server 2003 SP1 and
windows server 2003 R2 I have the fallowing error:
\\servername (server which is a windows server 2003)\share “DFS replication
service is not installedâ€
DFSR
(1)
DC
(1)
Server
(1)
DanielJust
(1)
DDSI
(1)
DanielIf
(1)
CD
(1)
MSFTNGP
(1)
Danny Sanders replied...
To set up R2 replication each server in the replication group must have the
new DFSR installed.
Run setup2 from the second disk of the R2 set on the server that needs R2
installed.
hth
DDS
lenm12 replied...
I do not understand, you mean to update the Windows server 2003 to Windows
server 2003 R2. Because windows server 2003 R2 come with 2 CDs the second CD
is the one with the new components and future, also I do not know if I need
another license. If you can be more explicit.
There is not another way?
lenm12 replied...
I do not understand, you mean to update the Windows server 2003 to Windows
server 2003 R2. Because windows server 2003 R2 come with 2 CDs the second CD
is the one with the new components and future, also I do not know if I need
another license. If you can be more explicit.
There is not another way?
Danny Sanders replied...
Win 2k3 came out. At a later date MS decided to add some updated features to
Win 2k3. Out came R2. If you want to use those updated features of R2 you
MUST install R2 on each server you want to use the updated features on.
You can not use the updated DFS replication that comes with Win 2k R2 on a
server without R2 installed.
Run setup2 from the second disk of the R2 set to install the updated R2
features.
, also I do not know if I need
Check with the people you bought Win 2k3 R2 from.
hth
DDS
Daniel replied...
Danny, in order to use replication between servers is it necessary to use DC
or can use member server and install administration pack ?
Daniel
Danny Sanders replied...
If you mean DFSR, no you do not need to run it on a DC.
Administration Pack has nothing to do with DFSR.
hth
DDS
Daniel replied...
I have 1 R2 server and 2 member servers and i can replicate the root
namespace of DC to the file server ?
Daniel
Jill Zoeller [MSFT] replied...
Just one thing to add here--in addition to the requirement that all servers
using DFSR must run R2, you also need to install a schema update to support
DFSR. This does not mean that your DCs must run R2. It just means that your
domain admin must install the schema update for R2. Otherwise the necessary
DFSR objects won't be in AD.
More information can be found at www.microsoft.com/dfs.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows file and storage technologies? Visit our
team blog at http://blogs.technet.com/filecab/default.aspx.
Daniel replied...
DFSR are not same as root namespace replication ? is it just the normal file
replication that use RDC technology ?
Daniel
AD replication Windows Server I have and exiting 2000 mixed mode domain just added a 2003 server into the mix and promoted it to DC The AD transfer happened but I am not sure everything is operating correctly I am that my AD (long with my AD integrated DNS) should be replicating between these to DC's ?? If so It appears to NOT be happening How canI verify this ? I did create a dummy user ( me hehehe) in the AD on the new DC. . . . . but havent observed the new user over in my 2000 server AD not sure if I am under the correct assumptions that I should see these in a very quick fashion? for that matter before I decommision the old existing w2k DC I should see the AD correclty replicating between the 2 ? thanks Windows Server Active Directory Discussions DC (1) Administration (1) Eriecountygov (1) DNS (1) TCP (1) CN (1
Please Help. . . . Server 2003 and 2008 domain controller problems. . . Windows Server Hi, I'm replacing servers on my network with with new servers running server 2008. I'm removing the 2 old server 2003 domain controllers. One of them crashed and I I seized all rolls and removed all records of that server with ntdsutil. That left me with one 2003 domain controller. I then added 2 new DCs to themselves and eachother for DNS. I then tried to demote the old 2003 DC to a member server to remove it from the network. It fails with and error that says that the last domain controller in domain" check box in not checked, but no other DC could be contacted. I ran dcdiag. . . . it says that no global catalog could be contacted
AD state and dns windows2003r2x64 Windows Server My Company recently upgraded to server2003R2x64 with the help of a Microsoft Partner from Nt4 ago I searched the newsgroups and someone replied with tests I should run on my dc's to check if they are alright. the tests I ran are: -> DCDIAG / V / C D / E / s:yourdcname > c: \ dcdiag.log -> netdiag.exe / v > c: \ netdiag.log (On each dc) -> repadmin.exe / showrepl dc* / verbose / all / intersite > c: \ repl.txt -> dnslint / ad / s "ip address of your dc" I have run these and on the child dc's they contain errors as well as some of the root forest dc's. Now since I am not the greatest AD expert I would like to know I have two main catogoty of issues I would like to resolve. thank you Windows Server DNS Discussions DomainDnsZones.ELLJHB.ELLIESHQ.LOCAL (1) DomainDnsZones.ELLIESHQ.LOCAL (1) ForestDnsZones.ELLIESHQ.LOCAL (1
Error after pdc rebuild Windows Server Hi, This week we had to rebuild our pdc after OS corruption whilst doing a state but to no avail. We have two domain controllers pdc and bdc running Windows server 2003 r2 standard. In the end we rebuilt the pdc manually but could only add it to the domain using dcpromo as another dc, there didn't seem anyway of adding it as a primary domain controller. We seem followed by BDC DCDIAG Domain Controller Diagnosis Performing initial setup: * Connecting to directory service on server highfield-pdc01. * Collecting site info. * Identifying all servers. * Identifying all NC cross-refs. * Found 2 DC(s). Testing 2 of them. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name \ HIGHFIELD-BDC01 Starting test: Connectivity * Active Directory LDAP Services Check * Active Directory RPC Services Check . . . . . . . . . . . . . . . . . . . . . . . . HIGHFIELD-BDC01 passed test Connectivity Testing server: Default-First-Site-Name \ HIGHFIELD-PDC01 Starting test: Connectivity * Active Directory LDAP Services Check * Active Directory RPC Services Check . . . . . . . . . . . . . . . . . . . . . . . . HIGHFIELD-PDC01 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name \ HIGHFIELD-BDC01 Starting test: Replications * Replications Check * Replication Latency Check DC
KRB_APP_ERR_MODIFIED Windows Server Hi there! This is our situation. DC1 Win 2k upgraded to w2k3 DC2 Win 2k naming context is in the process of being removed or is not replicated fromthe specified server. I'm kind of stuck, not sure what else to try. Please help. Thank you dc2 = ho dc3 = ho1 - -- -- -- -- -- -- -- -- -- -- -- -- -- Domain Controller Diagnosis Performing initial setup: * Connecting to directory service on server HO2. * Collecting site info. * Identifying all servers. * Identifying all NC cross-refs. * Found 3 DC(s). Testing 3 of them. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name \ HO1 Starting test: Connectivity * Active Directory LDAP Services Check * Active Directory RPC Services Check . . . . . . . . . . . . . . . . . . . . . . . . . HO1 passed test Connectivity Testing server: Default-First-Site-Name \ HO Starting test: Connectivity * Active Directory LDAP Services Check * Active Directory RPC Services Check . . . . . . . . . . . . . . . . . . . . . . . . . HO passed test Connectivity Testing server: Default-First-Site-Name \ HO2 Starting test: Connectivity * Active Directory LDAP Services Check * Active Directory RPC Services Check . . . . . . . . . . . . . . . . . . . . . . . . . HO2 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name \ HO1 Starting test: Replications * Replications Check * Replication Latency Check DC = ForestDnsZones