discoveranother Posted July 15, 2019 Posted July 15, 2019 Hello Have a Windows 2008 R2 Server which will be being replaced with Windows 2016. Will be transferring the FSMO roles over. 1) I gather that FRS needs migrating to DFSR on the Windows 2008 before doing any transfer ? 2) The following is the DCDIAG output from the 2008 server, there is only one server onsite. Is there anything on the DCDIAG output which may cause FSMO roles transfer issues ? Thanks all, Microsoft Windows [Version 6.1.7601] Copyright © 2009 Microsoft Corporation. All rights reserved. C:\Users\admin>dcdiag Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = Server01 * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\Server01 Starting test: Connectivity ......................... Server01 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\Server01 Starting test: Advertising ......................... Server01 passed test Advertising Starting test: FrsEvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... Server01 failed test FrsEvent Starting test: DFSREvent ......................... Server01 passed test DFSREvent Starting test: SysVolCheck ......................... Server01 passed test SysVolCheck Starting test: KccEvent ......................... Server01 passed test KccEvent Starting test: KnowsOfRoleHolders ......................... Server01 passed test KnowsOfRoleHolders Starting test: MachineAccount ......................... Server01 passed test MachineAccount Starting test: NCSecDesc Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have Replicating Directory Changes In Filtered Set access rights for the naming context: DC=DomainDnsZones,DC=streamline,DC=local Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have Replicating Directory Changes In Filtered Set access rights for the naming context: DC=ForestDnsZones,DC=streamline,DC=local ......................... Server01 failed test NCSecDesc Starting test: NetLogons ......................... Server01 passed test NetLogons Starting test: ObjectsReplicated ......................... Server01 passed test ObjectsReplicated Starting test: Replications ......................... Server01 passed test Replications Starting test: RidManager ......................... Server01 passed test RidManager Starting test: Services IsmServ Service is stopped on [server01] ......................... Server01 failed test Services Starting test: SystemLog ......................... Server01 passed test SystemLog Starting test: VerifyReferences ......................... Server01 passed test VerifyReferences Running partition tests on : DomainDnsZones Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Running partition tests on : ForestDnsZones Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Running partition tests on : Schema Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Running partition tests on : Configuration Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Running partition tests on : streamline Starting test: CheckSDRefDom ......................... streamline passed test CheckSDRefDom Starting test: CrossRefValidation ......................... streamline passed test CrossRefValidation Running enterprise tests on : streamline.local Starting test: LocatorCheck ......................... streamline.local passed test LocatorCheck Starting test: Intersite ......................... streamline.local passed test Intersite C:\Users\admin>
pooley Posted July 15, 2019 Posted July 15, 2019 Take a look at the failed tests in that log. Starting test: FrsEvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... Server01 failed test FrsEvent IsmServ Service is stopped on [server01] ......................... Server01 failed test Services It's probably a DNS thing or You may need to rebuild the sysvol tree or It's DNS Si
mrwoberts Posted July 15, 2019 Posted July 15, 2019 On a separate note, I personally would not be migrating to 2016 at this stage - 2019 at least has the major benefit of an improved patch system, whereas 2016 can have problems applying patches - hit and miss for some.
discoveranother Posted July 15, 2019 Author Posted July 15, 2019 (edited) Take a look at the failed tests in that log. Starting test: FrsEvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... Server01 failed test FrsEvent IsmServ Service is stopped on [server01] ......................... Server01 failed test Services It's probably a DNS thing or You may need to rebuild the sysvol tree or It's DNS Si Thanks for the response. Not sure why this error is there, it must be from a long time ago, as apparently the last time a server was installed at these premises was when 2008 came out and whoever did it must have also transferred over roles from 2003 I presume. Edited July 15, 2019 by discoveranother
discoveranother Posted July 15, 2019 Author Posted July 15, 2019 On a separate note, I personally would not be migrating to 2016 at this stage - 2019 at least has the major benefit of an improved patch system, whereas 2016 can have problems applying patches - hit and miss for some. Thanks, I've read various things in the past that 2019 is not really fully ready and can be problematic and go for 2016, so i'm a bit confused now. Maybe a personal preference for some.
mrwoberts Posted July 15, 2019 Posted July 15, 2019 (edited) Here are a couple of Edugeek threads that may help... http://www.edugeek.net/forums/windows-server-2016/207993-windows-server-2016-stuck-restarting.html#post1781538 http://www.edugeek.net/forums/windows-server-2016/204222-windows-server-2016-slow-update.html http://www.edugeek.net/forums/windows-server-2012/208306-upgrading-server-2016-a.html EDIT: Here's an MS link in case you'd like to do an in-place upgrade... https://www.microsoft.com/upgradecenter/scenario/WS2008R2-on-prem-to-WS2019 Edited July 15, 2019 by mrwoberts
discoveranother Posted July 15, 2019 Author Posted July 15, 2019 Take a look at the failed tests in that log. Starting test: FrsEvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... Server01 failed test FrsEvent IsmServ Service is stopped on [server01] ......................... Server01 failed test Services It's probably a DNS thing or You may need to rebuild the sysvol tree or It's DNS Si Thank you Checking the event logs for File Replications Service shows the following:- The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" Replica root path is : "c:\windows\sysvol\domain" Replica root volume is : "\\.\C:" A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons. [1] Volume "\\.\C:" has been formatted. [2] The NTFS USN journal on volume "\\.\C:" has been deleted. [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. [4] File Replication Service was not running on this computer for a long time. [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:". Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state. [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service. [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again. To change this registry parameter, run regedit. Click on Start, Run and type regedit. Expand HKEY_LOCAL_MACHINE. Click down the key path: "System\CurrentControlSet\Services\NtFrs\Parameters" Double click on the value name "Enable Journal Wrap Automatic Restore" and update the value. If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
discoveranother Posted July 15, 2019 Author Posted July 15, 2019 Here are a couple of Edugeek threads that may help... http://www.edugeek.net/forums/windows-server-2016/207993-windows-server-2016-stuck-restarting.html#post1781538 http://www.edugeek.net/forums/windows-server-2016/204222-windows-server-2016-slow-update.html http://www.edugeek.net/forums/windows-server-2012/208306-upgrading-server-2016-a.html EDIT: Here's an MS link in case you'd like to do an in-place upgrade... https://www.microsoft.com/upgradecenter/scenario/WS2008R2-on-prem-to-WS2019 Thanks, interesting. In place upgrade is out of the question but fsmo transfer to a new server 2019 looks now like the best option, but need to sort out the issues with the 2008 first, unless I build a completely new domain.
mrwoberts Posted July 15, 2019 Posted July 15, 2019 On the server that is reporting this error, what do you get when you run this command from a cmd prompt fsutil usn queryJournal
discoveranother Posted July 16, 2019 Author Posted July 16, 2019 On the server that is reporting this error, what do you get when you run this command from a cmd prompt fsutil usn queryJournal Thank you for the response. The output is:- fsutil usn queryJournal c: Usn Journal ID : 0x01cc3f68c4c65d6c First Usn : 0x000000705d480000 Next Usn : 0x00000070a2ed2548 Lowest Valid Usn : 0x0000000000000000 Max Usn : 0x7fffffffffff0000 Maximum Size : 0x000000003ffc0000 Allocation Delta : 0x000000000ccc0000 Doesn't mean anything to me unfortunately
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now