Re: Group policy and File Replication Service



Amanda,
Alas, there is no "SLA" on public newsgroups--at least, not that I know of.
But, with respect to your problem, yes, the inability for some DCs to enable
SYSVOL replication will prevent clients from getting GP correctly. Every DC
needs to have shared Netlogon and SYSVOL. If they are not, you will have GP
problems because clients read GP settings from the SYSVOL portion of a GPO.
So, your first order of business is to fix FRS replication between all your
DCs. There are a lot of KB articles on FRS problems, but I would recommend
starting with this one:
http://support.microsoft.com/kb/290762/en-us

--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policy
Check out http://www.gpoguy.com -- The Windows Group Policy Information Hub:
FAQs, Whitepapers and Utilities for all things Group Policy-related
And, the Windows Group Policy Guide is out from Microsoft Press!!! Check it
out at http://www.microsoft.com/mspress/books/8763.asp
GPOGUY Blog: http://blogs.dirteam.com/blogs/gpoguy



"Amanda" <Amanda@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:37E15644-6781-4602-AA57-77E5C0762FE8@xxxxxxxxxxxxxxxx
>I thought that these posts are supposed to be receive a response by next
> business day?
>
> "Amanda" wrote:
>
>> Hello,
>> I'm having a problem with Group policy. We have 5 DC's on our network.
>> The
>> problem is that some of them are only online part time. I'm seeing lots
>> of
>> rile replication and kerberos errors in the event log on the PDC. The
>> servers
>> that that Server1 is having trouble connecting to are the ones that are
>> offline part time. So it isn't surprising to me that these errors are
>> showing
>> up. The problem is that along with the errors there is an issue with a
>> very
>> important group policy replicating to all the clients. A popup is
>> supposed to
>> occur when clients logon to the network and that is not happening on most
>> machines. How do I go about fixing this and are these issues all related?
>> Below is one of the errors I'm getting:
>>
>> Event Type: Warning
>> Event Source: NtFrs
>> Event Category: None
>> Event ID: 13508
>> Date: 1/19/2005
>> Time: 8:20:43 AM
>> User: N/A
>> Computer: Server1
>> Description:
>> The File Replication Service is having trouble enabling replication from
>> Server2 to Server1 for drive:\winnt\sysvol\domain using the DNS name
>> Server2.domainname.suffix FRS will keep retrying.
>> Following are some of the reasons you would see this warning.
>>
>> [1] FRS can not correctly resolve the DNS name martin.here.bates.ctc.edu
>> from this computer.
>> [2] FRS is not running on server2.domainname.suffix.
>> [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.
>>


.



Relevant Pages

  • Re: Unable to decommission a Windows 2008 DC via dcpromo
    ... Server1 has never been restored from backup. ... The File Replication Service Event log test ... SYSVOL has been shared. ... Replica set member name is "server1" ...
    (microsoft.public.windows.server.active_directory)
  • Re: MS ADAM/AD: Absolute simplest repl/sync solution for MS ADAM on 2 or more WinXP machines?
    ... Michael Herman ... Developers of Advanced Business Collaboration Solutions for Microsoft ... > own replication engine. ... >>> "offline access" are these clients writing the database as well as ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows AD problems
    ... You did not mention the WAN link speeds. ... How to configure Site Link Replication ... How WIN2000 clients locate a Domain Controller ... Currently their are two remote locations and my location and we all use the ...
    (microsoft.public.win2000.active_directory)
  • Re: Please ease my terror
    ... Replication manager or get some answers on this topic without it. ... I think at this time, Replication is not the ideal solution for my clients, ... > that server, it can be a hub for replication. ...
    (microsoft.public.access.replication)
  • Re: MS ADAM/AD: Absolute simplest repl/sync solution for MS ADAM on 2 or more WinXP machines?
    ... I would think you could look at it like this: The replication requires ... directory service for clients to query as needed. ... > Each client instance of ADAM will be used by a single user on that WinXP ...
    (microsoft.public.windows.server.active_directory)

Loading