Steve,
A little of column A and a little of column B.
DFSR is what you'd use if you were running R2. DFS is standard to
Win2K3, and uses FRS to do the replication (if used). Don't be afraid -
it's easier than FRS alone... although, I can tell you that you'd be
1000% better off replicating using DFSR (FRS is kludgy at best).
My $0.02 inc GST.
themolk.
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Egan
(Temp)
Sent: Tuesday, 16 January 2007 1:38 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] File replication setup problem
If I'm reading the Microsoft instructions correctly, all you
have to run FRS is 2003 with SP1. Am I wrong, people? I am aware that
DFS will require R2...
FYI, none of the servers in question are running 2003R2.
Steve Egan
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond
Sent: Monday, January 15, 2007 6:15 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] File replication setup problem
Steve-
Is the box running R2? You need to upgrade to schema v31 (r2) if
so.
If not I tend to think your DNS is busted.
Thanks,
Brian Desmond
[EMAIL PROTECTED]
c - 312.731.3132
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Egan
(Temp)
Sent: Monday, January 15, 2007 8:51 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] File replication setup problem
Howdy, Brain Trust:
I have two servers, one on Poland, the other in Sweden, that I
want to install FRS on (and later "upgrade" to DFS) so that I can back
up these remote location files locally on a high-speed offsite backup
here in the States. I'm attempting to go slow and do a little bit at a
time.
When I Run the New Replication Group Wizard and name the
replication group and hit Next, the following error happens:
"<company.com>: The Active Directory schema on domain controller
<ftp server>.<domain.com> cannot be read. This error might be caused by
a schema that has not been extended, or was extended improperly. See
Help and Support Center for information about extending the Active
Directory schema. A class schema object cannot be found."
I've tried and tried to extend the schema, the results are
normal (no errors), and still the AD schema is broken. It swears up and
down that it is a 2003 schema. I can't install AD on the Sweden server
because something ain't right with it (schema), and now this. I have
two servers running here in the states as DC's, and they both think they
are the "top dog" controller because whenever I try to do something like
this it tells me the schema is broken. The FTP server and the mail
server are both set up as DC's, both have AD on them. How do I tell one
of them that they are no longer the master? Can I just delete (remove)
the AD schema from the ftp server and reinstall it without serious
breakage? I'm not sure that a simple demote will do the trick. I'm
enough of a thumb-fingered idiot when it comes to AD that I live in fear
of really screwing the pooch if I do something like this - but I have to
get it solved somehow.
Somebody got a life preserver?
Steve Egan (temp)
Systems/Network Engineer
Occasional AD fumble-fingered idiot
This email (including any attachments) contains confidential information and
is intended only for the named addressee. If you are not the named addressee
you should not disseminate, distribute or copy this email. Please notify the
sender immediately by email if you have received this email by mistake and
delete this email from your system and destroy any copies.
This email is also subject to copyright. No part of it should be reproduced,
adapted or communicated without the written consent of the copyright owner.
Email transmission cannot be guaranteed to be secure or error-free and emails
may be interfered with, may contain computer viruses or other defects and may
not be successfully replicated on other systems. The sender does not give any
warranties nor accepts any liability in relation to any of these matters. If
you have any doubt about the authenticity of an email purportedly sent by us,
please contact us immediately.
