Search the Community

Hello, We have about 20 separate sites all on server 2012 or 2012 r2. Before we was on 2012 they were on 2008 R2. We have been problems across many sites with two or more domain controllers replicating Sysvol and group policys. We started all the domain from scratch and added the additional domain controllers afterwards. We never had a problem with this in 20082. Just wondering has anything changed and requires to be done a different way and has anyone else come across this ? We have followed all the guides on the internet but no luck. Sometimes it works for a bit but after a couple of months stops replicating. Does everyone still use more than one Domain controller ?

Group Policy Management shows 3 out of 4 DCs (Not FSMO role holder as Authoritative DC) "Replication in progress" for recently edited policies (longer than 24 hours). DFS Management diagnostic reporting shows propagation test data replication status "Arrival pending" and has since test was started 4 days ago. Event log has no extra information. DCDiag shows no issues aside from DFSRevent which are reports that service stops due to backups (at correct time for DC backups). Some policies are several versions out of date, so likely this has been going on for some time. Anyone know how I can further troubleshoot this issue?

I have a problem when i try to log on from my pc to AD in the domain. When i boot the pc, and enter username, password and domain to which i want to log on, i need to wait 3-4 minutes, at Applying your personal settings... pop up. After that i can log on, but when i check logs on my pc, at Application logs i fount thise two logs: -----> LOG1 Event Type: Error Event Source: Userenv Event Category: None Event ID: 1030 Date: 1/27/2011 Time: 10:05:29 AM User: DOMAIN\user1 Computer: user1pc Description: Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine. For more information, see Help and Support Center at Events and Errors Message Center: Basic Search. ----> LOG2 Event Type: Error Event Source: Userenv Event Category: None Event ID: 1006 Date: 1/27/2011 Time: 10:05:29 AM User: DOMAIN\user1 Computer: user1pc Description: Windows cannot bind to domain.com domain. (Local Error). Group Policy processing aborted. For more information, see Help and Support Center at Events and Errors Message Center: Basic Search. I log off and log on back several times, and its the same situation, 3-4 minutes waiting at log on, and always this two logs. The DFS service is started at DC. ------------- About sysvol: ------------- I have the following path: c:\Windows\sysvol\sysvol\domain.com\ For the File permisions: ******************** C:\Windows\sysvol\ Folder is not shared. Authenticated users and Server Operators have Read&Execute Administrators, Creator Owners and System have Full Control In the column Inherited From: they all have In the column Apply To: Creator Owner: Subfolders and Files only Others: This foler, subfolders and files Check box: Allow inheritable permissions from the parrent to propagate... is Unchecked Check box: Replace permmision enttries on all child objects... is unchecked ************************ C:\Windows\sysvol\sysvol\ Folder is shared. Administrators: Full control Authenticated users: Read & Execute, List Folder Contents, Read Creator Owner: Full control SYSTEM: Full control Server Operators: Read and Execute Everyone: Read & Execute Domain users: Read & Execute In the column Inherited from for Domain users and Everyone is For the rest is "inherited from C:\\Windows\sysvol\" In the column Apply to For Creator Owner: Subfolders and files only For Everyone: This folder only For all the rest: This folder, subfolders and files Check box: Allow inheritable permissions from the parrent to propagate... is Unchecked for all Check box: Replace permmision enttries on all child objects... is unchecked ********************************* Any ideas, solutions?

Hi All I'm having few issues getting sysvol to replicate after I dcpromo a server 2008 machine into a 2003 domain, but having no problems with replication if I dcpromo another 2003 machine into the domain. I have noticed that the link folders within Sysvol (2008 machine) are incorrect, and folder linking path is incorrect, but 2003 is spot on. I've changed the paths using HardLinkShellExt_win32.exe, to rectify the link folder problem, but still no replication..... help:confused:, Any idea's? Thanks in advance

Does anyone keep their Mandatory Profiles in sysvol? Or tried and ended up regreting it? The reason I'm asking is I'm trying to eliminate single points of failure in our network, if the profile can be loaded from any domain controller this should make things more reliable.

I'm trying to add a 2019 DC to my existing 2012r2 DCs, they've done the DRFS migration "eliminated" (and are all in the same state, dfs is happy with no errors) and now have sysvol_DRFS as the sysvol share on the 2012r2s When I go to add a new 2019 DC and promote it, it creates a sysvol NOT sysvol_DRFS and DFS will not sync correctly the new server. (dfs has a timeout error with new server, possible error) I've tried with a second (new) DC and I'm getting the same result... (it want to make a sysvol not sysvol_DRFS) what gives? The new server does create a sysvol folder with files in it, so it is syncing... so it is doing something. is sysvol_DRFS only for migrated servers? and it is the share name that is important not the location on a given server? Then why does dfs get upset?