Hi, I've not yet experienced the issue described in the DFS Replication 4012 Tutorial as my SBS has not been offline for 6 months however I like to plan ahead! The guide is very clear that it is for a single DC environment, is this because this issue will not affect a multi DC environment or is the fix more complex? Thank you Ian
Hi! I'm getting my SBS 2011 ready to migrate to Windows Server 2019. Working through chapters 1 - 5 prior to migrating Exchange, looked at the FRS log and I have a lot of NtFrs Event ID 13508 errors. To give some context, I have the SBS 2011 as the primary DC and a Windows Server 2012 R2 server as a secondary DC. Everything appears to be working as it should, not experienced any apparent FRS errors in the 6 years this setup has been in place. Should I be worried about these or ...
I have an issue with the FRS to DFRS Migration. Setup is 4 sites with a DC on each and 2 sites with a RODC each (so 6 all together). I have checked the AD health etc and all OK so I ran the dfsrmig /setglobalstate 1 command, went away and came back a hour or so later and checked the progress with dfsrmig /getmigrationstate and all had progressed apart from 1 of the RODC servers. I left it over night and the same. dfsrmig /getmigrationstate The following Domain Controllers are not in sync with ...
There is a server share setup by the install called "Shared Folders", now I don't need this share. Under it is a "Company" folder and a "Users" folder that just points to the Users and Company share, neither of which I actually will use anyway as we have our own that will be replicated on the new server. Now the "Shared Folders" share seems to be shared from "C:\DFSRoots\Shared Folders" but I can't turn that share off as it says I have to remove it from DFS or something like that, first. How do I do that? ...
Hi, At step 17 there is a statement for the sysvol location, C:\Windows\SYSVOL, but on the WSE 2016 source it has been moved to c:\WIndows\SYSVOL_DFSR because there was a branch office and we were using DFSR between two servers. Is this location at this step for the SOURCE or DESTINATION? SYSvol replication on the source has tombstoned out and is stale, but otherwise shows ok. I think this is for the Destination, but just checking.
I was following through the migration guide for SBS2011 to Server 2019 ( https://server-essentials.com/support/migrate-sbs-2011-to-windows-server-2019# ) and then under Section 7 Step 21 is to verify that there is a SYSVOL and NETLOGON share on the 2019 server and unfortunately they are not there. How do I resolve this to continue the migration? Thanks for your help.
Dear sir / madam, It is my understanding that Exchange 2010 CU22+ can exist in a 2019 AD environment[ 1 ], furthemore a 2008 R2 DC can be migrated directly to Server 2019[ 2 ] We're running SBS2011, we now have the hardware in place. so i would like to start the migration ASAP. Would it be feasible if i first stand up a new 2019 based DC (which would temporarily coexist with the SBS 2011 DC [feature level 2008 R2] and then - afterwards (within 21 days) - stand up a Server-2016 ...
I'm using the SBS 2011 Essentials migration guide to deploy a new Windows Server 2019 Standard server. I deployed the SBS 2011 Essentials box back in 2011 using Microsoft Open licensing ISO and not Dell OEM versions. Have just started the FRS to DFSR steps by confirming domain level is already at Windows Server 2008 R2 functional level. My next task was to run dfsrmig /getglobalstate and I learned that the state was already "eliminated" but I'm certain I've never performed the migration from FRS to DFSR in the past. Running dfsrmig /getmigrationstate also shows the global state as "eliminated" ...
Is it ok to use the migration guide for SBS 2011 Essentials to Windows Server 2016 with a new Windows Server 2019 setup? I presume most is all of the same considering the migration from FRS to DFSR is consistent with 2016 and 2019. Thanks. Ken
I'm preparing to migrate the domain from using FRS to DFS replication for SYSVOL. In checking up on FRS health, I don't see any journal wrap errors (Event ID 13568), but I am getting regular daily events for ID 13567 in the File Replication Service log on the SBS 2011 box. My other 3 DCs are not having this issue. The description of that Event ID says: "File Replication Service has detected and suppressed an average of 15 or more file updates every hour for the last 3 hours because the updates did not change the contents ...
Finally getting started on my migration ! Up at step 3: Migrate FRS to DFSR replication in SBS 2011 (going to Win2016), just entered command "dfsrmig /getglobalstate" Instead of getting a response like the one in the guide (DFSR migration has not been initialized) I get this : Current DFSR global state: 'Start' Succeeded. Everything before in step 3 went exactly as in the guide. Was Win2003Forest, now Win2008R2... identical Now, in the past, I've configured DFSR for file replication between servers... could this have an impact on the message I'm ...
Hi Mariette, Since your DFS Tutorial My preference on file migration is the DFS method (which has been very successful) Is there any pitfalls or anything I should know before I start this process. JOE HEALY
server essentials 2019 shutdown automatic 7 days. it's not a DC. only user MS SQL & our company ERP software
Good Day - I'm currently at the section 2 #14 - dfsrmig /getglobalstate and it says I'm at 'Eliminated'; however, it should be known here that this is a previously migrated server from 5 years ago going from SBS2003 to SBS2011, so, it probably should say that. Now, I'm asking the question, is it possible to migrate this server again, from SBS2011 to Server 2016 Essentials? Can I get the dfsr state to start again? Thanks Jeff Adzima
Hi Mariette, DFS Management is missing from the Tools List in server manager Do I need to add that role myself. Remote Server Administration Tools > Role Administration Tools > File Services Joe
Mariette Is there any reason why you use (recommend) robocopy and not DFRS to move files and folders to new server? JOE
I'm doing a conversion for a client from an old server running Windows 2012 R2 to a new server running Windows 2016 Essentials using this guide . I'm on "Step 8 - Check Active Directory Health and Replication", and I've completed the following: repadmin /replsummary - OK repadmin /showrepl - OK DCDIAG /test:DNS /DNSALL /e /v - OK DCDIAG /test:RegisterInDNS /DNSDomain: .local - OK However, when I type "net share" on my 2016 Essentials machine, I am not getting a SYSVOL or NETLOGON folder. ...
Several months after a successful migration from SBS2008 to Server 2016 Std we are now getting an error 4012 on the Domain Controller. There is another Server 2012 that is part of the domain which is not a backup domain controller. The error states: The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 69 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server ...
Mariette, I am in the middle of a migration and moving server folders with DFS. I managed to delete the Namespace from the DFS Manager when breaking a replication job from old server to new.( laptop Mouse pad !) While there is no data lost what impact will this have? Can I create a new name space I have one more server folder to migrate to the new server. Thnks in advance JOE
Finished migrating from SBS 2011 to 2016 Essentials completely. Follow up questions re: DFS Management - I followed your process in Chapter 12 to remove the replication folders that we created during Chapter 9. But DFS Management on the 2016 Essentials still has references in the namespace to the two default shared Essentials folders (Company and Users) that we never used for replication purposes, plus one additional shared folder I created from the Essentials dashboard that I also was NOT going to replicate. My question is three-fold: (1) do I need to do anything with ...
Mariette, DFS was running and populating new 2016 server with files. After 24 hours it looked like we were well over 95% of files copied. I ran DFS diagnostic health report. It had one glaring error: "DFS replication service detected that the staging area usage has exceeded its quota size of 4096 MB" . I did some research and found this Microsoft blog post about it, which included PowerShell scripts to calculate total size of 32 largest files. In this case, the customer has over 32 very large PST files, total equaling 42GB. So ...
Source is SBS 2011 (previously migrated from SBS 2003 5 years ago). Target will be 2016 Essentials. Before doing the FSR to DFSR migration in phase 2, I ran "dcdiag /c" on source. It does have some errors, but I'm not sure which ones may be critical that I need to be concerned with and try to cleanup before doing the FRS migration. Results of the dcdiag can be viewed here: http://kwsupport.com/downloads/dcdiag-sbs2011-2.pdf
I started DFSR replication before the server essentials role was completely configured and now I get the error you cannot start the essentials dashboard until configuration is complete. The attempt to complete configuration fails, with reboot and try again. I cannot uninstall the server essential role either?
Good morning. I am migrating a Windows server 2008 R2 server to Server 2016 Essentials. I am on section 2 step 14. When I run "dfsrmig /getglobalstate" it is already in an "eliminated" state. Should I just continue or is this something to be concerned with? The output of the commands are below. Any guidance would be greatly appreciated. Thanks. Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Administrator.MFSVR>dfsrmig /getglobalstate Current DFSR global state: 'Eliminated' Succeeded. C:\Users\Administrator.MFSVR>dfsrmig /setglobalstate 1 Current DFSR global state: 'Eliminated' New DFSR global state: 'Prepared' Invalid state change requested. C:\Users\Administrator.MFSVR>
I am getting this in step 11-7 of the migration tutorial removing the AD Cert Service. At this point should I try to continue or take some other steps such as doing a force removal of the old DC. Also at what point to am I to turn off the DFS between the old and new? Thanks in advance!