{"id":1424,"date":"2017-04-16T16:12:24","date_gmt":"2017-04-16T15:12:24","guid":{"rendered":"http:\/\/www.michaelm.info\/blog\/?p=1424"},"modified":"2017-04-16T17:32:00","modified_gmt":"2017-04-16T16:32:00","slug":"when-frs-file-replications-service-has-a-melt-down","status":"publish","type":"post","link":"http:\/\/www.michaelm.info\/blog\/?p=1424","title":{"rendered":"When FRS (file replications service) has a melt down"},"content":{"rendered":"<p>Monitoring alerted me to a couple of servers which had lost the ability to replicate SYSVOL using FRS. Microsft KB290762 (<a href=\"https:\/\/support.microsoft.com\/en-us\/help\/290762\/using-the-burflags-registry-key-to-reinitialize-file-replication-service\" target=\"_blank\">https:\/\/support.microsoft.com\/en-us\/help\/290762\/using-the-burflags-registry-key-to-reinitialize-file-replication-service<\/a>) provided instructions on how to recover.<\/p>\n<p>In summary, on all members of the replication set (in this instance all DCs) stop the ntfrs service using:<\/p>\n<pre>net stop ntfrs<\/pre>\n<p>The choose one server which will be the authoritative copy and set <em>BurFlags<\/em> to <em>0xd4<\/em>:<\/p>\n<pre>reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\NtFrs\\Parameters\\Backup\/Restore\\Process at Startup\" \/v BurFlags \/t REG_DWORD \/d 0xd4 \/f<\/pre>\n<p>On the other servers, set <em>BurFlags<\/em> to <em>0xd2<\/em>:<\/p>\n<pre>reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\NtFrs\\Parameters\\Backup\/Restore\\Process at Startup\" \/v BurFlags \/t REG_DWORD \/d 0xd2 \/f<\/pre>\n<p>On the authoritative server, start the ntfrs service and watch for event 13516 in the &#8220;File Replication Service&#8221; event log. Once that event is logged, start the ntfrs service on the next server and again wait for the 13516 event log. Repeat this on the remaining servers.<\/p>\n<p>EDIT: I have since discovered FRS was being used due to upgrades from Windows 2003. Followed <a href=\"https:\/\/blogs.technet.microsoft.com\/filecab\/2008\/02\/08\/sysvol-migration-series-part-1-introduction-to-the-sysvol-migration-process\/\" target=\"_blank\">https:\/\/blogs.technet.microsoft.com\/filecab\/2008\/02\/08\/sysvol-migration-series-part-1-introduction-to-the-sysvol-migration-process\/<\/a>\u00a0to migrate from FRS to DFSR. In future, if replication breaks it can be reinitialised by following this doc:\u00a0<a href=\"https:\/\/support.microsoft.com\/en-ie\/help\/2218556\/how-to-force-an-authoritative-and-non-authoritative-synchronization-for-dfsr-replicated-sysvol-like-d4-d2-for-frs\" target=\"_blank\">https:\/\/support.microsoft.com\/en-ie\/help\/2218556\/how-to-force-an-authoritative-and-non-authoritative-synchronization-for-dfsr-replicated-sysvol-like-d4-d2-for-frs<\/a><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Monitoring alerted me to a couple of servers which had lost the ability to replicate SYSVOL using FRS. Microsft KB290762 (https:\/\/support.microsoft.com\/en-us\/help\/290762\/using-the-burflags-registry-key-to-reinitialize-file-replication-service) provided instructions on how to recover. In summary, on all members of the replication set (in this instance all DCs) stop the ntfrs service using: net stop ntfrs The choose one server which will [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[35,238,237,236],"class_list":["post-1424","post","type-post","status-publish","format-standard","hentry","category-technical","tag-error","tag-eventid","tag-ntfrs","tag-windows"],"_links":{"self":[{"href":"http:\/\/www.michaelm.info\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1424","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.michaelm.info\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.michaelm.info\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.michaelm.info\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.michaelm.info\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1424"}],"version-history":[{"count":3,"href":"http:\/\/www.michaelm.info\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1424\/revisions"}],"predecessor-version":[{"id":1427,"href":"http:\/\/www.michaelm.info\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1424\/revisions\/1427"}],"wp:attachment":[{"href":"http:\/\/www.michaelm.info\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1424"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.michaelm.info\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1424"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.michaelm.info\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1424"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}