![]() Apparently this fix is quite dangerous and not for the faint of heart. I’m not 100% sure why I’m warning you, but I’ll take Rob’s word on the matter. Rob P recently spent some time and effort with Microsoft support and came up with a solution that can be applied. Logic would suggest that once a DC knows it is the only DC in the Forest that it would shake off the USN Rollback blues and start humming away normally again. There has been some discussion in the comments in that post about what to do when you have a single domain controller that thinks it is in a USN Rollback condition (eg has disabled outbound replication and paused the NetLogon service). ![]() ![]() Some time ago I wrote about my experience recovering a customer’s Active Directory from a USN Rollback condition that had been caused by some virtualisation work.
0 Comments
Leave a Reply. |