Re: DFS Replication setup in Server2k3 R2

I imagine the first fact is I never extended the schema. I installed
Server2k3 from the R2 cd's. I never upgraded from R1 to R2. If you install
the OS from R2, do you still need to extend the schema or does this happen by
default when you put cd2 in during the install?


Next thing would be how do I confirm in the schema if the correct entries
are there to support DFSR?
Here are some event entries from the DFS Replication logs on one of the
participating servers:

Event Type: Information
Event Source: DFSR
Event Category: None
Event ID: 1002
Date: 5/5/2006
Time: 3:35:53 PM
User: N/A
Computer: HQFS1
Description:
The DFS Replication service is starting.

Event Type: Information
Event Source: DFSR
Event Category: None
Event ID: 1314
Date: 5/5/2006
Time: 3:35:53 PM
User: N/A
Computer: HQFS1
Description:
The DFS Replication service successfully configured the debug log files.

Additional Information:
Debug Log File Path: C:\WINDOWS\debug

Event Type: Information
Event Source: DFSR
Event Category: None
Event ID: 1004
Date: 5/5/2006
Time: 3:35:53 PM
User: N/A
Computer: HQFS1
Description:
The DFS Replication service has started.

Event Type: Information
Event Source: DFSR
Event Category: None
Event ID: 1210
Date: 5/5/2006
Time: 3:35:53 PM
User: N/A
Computer: HQFS1
Description:
The DFS Replication service successfully set up an RPC listener for incoming
replication requests.

Additional Information:
Port: 0.

Event Type: Information
Event Source: DFSR
Event Category: None
Event ID: 6102
Date: 5/5/2006
Time: 3:35:53 PM
User: N/A
Computer: HQFS1
Description:
The DFS Replication service has successfully registered the WMI provider.

Event Type: Information
Event Source: DFSR
Event Category: None
Event ID: 1206
Date: 5/5/2006
Time: 3:41:20 PM
User: N/A
Computer: HQFS1
Description:
The DFS Replication service successfully contacted domain controller
\\xxxx.xxxx.xxxx.xxx to access configuration information.

Thanks for the reply and help!
--
Chris


"Jorge de Almeida Pinto [MVP]" wrote:

before even being able to setup DFS-R you need to extend the schema
otherwise you will not succeed.

If you have configured DFS-R then the schema has already been updated

I installed the services according to articles on the WindowsIT Pro
website

that does not mean much to me because I don't know what articles you are
talking about and what is in them. If available, I always prefer MS
docs/articles.

Tell us what YOU did. don't forget any details

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
-----------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
-----------------------------------------------------------------------------


-----------------------------------------------------------------------------
"aclouden" <aclouden@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:37281EE4-F6F3-486C-A9D2-B51391948498@xxxxxxxxxxxxxxxx
Hello all.

I hope I haven't made a serious mistake with my DC but here goes. I
installed Server 2003 R2 on three servers and setup users, groups shares
etc
in a brand new environment. I went to setup DFSR between the two file
servers
on the local LAN. I installed the services according to articles on the
WindowsIT Pro website. This seems to work except for lag when one of the
servers is shut down. I just saw that I was supposed to extend the schema
first before setting up DFSR..? I thought that it was all done because I
installed R2 from the get go and did not upgrade from R1, right?? If not,
how
do I go about correcting the situation where DFSR was setup without first
extending the schema in R2? Could this explain the lag when one of the two
replicating servers is down?

Any input appreciated!
--
Chris



.

Relevant Pages

  • Re: Domain Controller?
    ... ERROR: Failed to transfer the schema FSMO role: 52 ... I generally install the resource kit ... >> servers are just workstation servers. ...
    (microsoft.public.win2000.general)
  • Re: 2003 Member Servers in 2000 Active Directory Domain
    ... you can install the server and join the domain without having to do anything ... > member servers in this structure. ... Does the schema need updating? ...
    (microsoft.public.windows.server.setup)
  • Re: 2003 Member Servers in 2000 Active Directory Domain
    ... > the schema only needs to be extended if you install AD on the 2003 box ... >> member servers in this structure. ... Does the schema need updating? ...
    (microsoft.public.windows.server.setup)
  • Re: 2008 or 2003
    ... To install a 2008 DC in a 2003 domain the schema has to be upgraded to version 44. ... The schema is the same in your complete domain, the schema upgrade will add additional AD objects which are needed for 2008. ... 2008 ad schema instead of setting it up as a 2003 AD server I need all ...
    (microsoft.public.windows.server.setup)
  • Re: SP1 Installation on CAS - [WP]
    ... Source: NTDS Replication ... consistent schema but last attempt to sync the schema had failed. ... And I am installing Exchange in mydomain.com where all the users reside. ... Now trying to install Exchange 2007 SP1 it gave me error ... ...
    (microsoft.public.exchange.setup)