Skip to main content

Force replication of Sysvol contents


In Active Directory domain, in Windows world sysvol folder needs to be consistent all through the domain. If the sysvol is inconsistent a lot of problems will happen. So for a smooth domain operation with less grumpy users "sysvol" folder has to be the same in all DC's.


To force sysvol replication via command line:

DFSRDIAG SyncNow /Partner:other_dc_name /RGName:”Domain System Volume” /Time:5

Check out this link from MS for more info: https://support.microsoft.com/en-us/kb/2218556

Another method is to go to control panel, then click on "Services".

Then find "DFS Replication" service and click on restart.

I did use this method before when I updated some batch file scripts and the script just doesn't sync even though the script is about 2KB in size only.

The moment I restart the "DFS Replication" service, then I was able to see the changes on the other DC.

I never test this command below but I guess it should work.

net stop DFSR

net start DFSR


An alternative to restart DFS Replication service via command line if need to script or automate restarting of the service.

Or just set a task scheduler via a batch file and run the task at a specific time.


Cheers..till next time.. hope it helps..

Linux Android App cheat sheet:
https://play.google.com/store/apps/details?id=com.LinuxMobileKit

Labels:

Comments

  1. AlexMarch 30, 2020 at 7:10 PM

    I get resolver my problem with your tutorial + this vídeo ( https://youtu.be/qVqzJr7LHPk )

    Thank you

    ReplyDelete

Post a Comment

Popular posts from this blog

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

PowerShell Match Drive Letter to Volume ID in AWS

Matching AWS volume ID to its corresponding Windows drive letter is an easy task using PowerShell. Win32_DiskDrive holds the info for the volume-ID. Here’s the script, below enjoy 😊 $get_disks = gwmi -query "SELECT * FROM Win32_DiskDrive" ForEach ( $disk in $get_disks ){         $get_partitions = gwmi -query "ASSOCIATORS OF {Win32_DiskDrive.DeviceID=' $( $disk . DeviceID) '} WHERE AssocClass = Win32_DiskDriveToDiskPartition"     ForEach ( $partition in $get_partitions ){         $get_logicaldisks = gwmi -query "ASSOCIATORS OF {Win32_DiskPartition.DeviceID=' $( $partition . DeviceID) '} WHERE AssocClass = Win32_LogicalDiskToPartition"          ForEach ( $logicaldisk in $get_logicaldisks ){         $insert_the_dash = ( $disk . SerialNumber) . Insert( 3 , "-" ) #insert dash to match AWS v...
Post a Comment
Read more