Not at all, he has no screenshots! LOL

But seriously, I would have reached out for help before three months had 
passed. My personal limit is one hour for something this critical. Just ask MBS 
and Brian Desmond, I am not afraid to reach out for help. BUT, I make sure I 
have done my research first before I bother anyone. But I would not have done 3 
months' worth of effort and 322 very detailed pages of notes before I reached 
out.

Heck, I've even reached out to you while you were in a pub once (forgetting the 
6 hour time difference).

Thanks


Webster

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of James Rankin
Sent: Thursday, November 17, 2016 6:22 AM
To: ntsysadm@lists.myitforum.com
Subject: [NTSysADM] RE: How to force an authoritative and non-authoritative 
synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)

322 pages of notes? Is he related to you? ;-0

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Webster
Sent: 17 November 2016 12:13
To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com>
Subject: [NTSysADM] RE: How to force an authoritative and non-authoritative 
synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)

Now that I am back in the "office".

Got brought into this call yesterday at 1500 and the customer had a hard stop 
at 1630.

Here is what I know:

Customer has two DCs, one in each datacenter on opposite sides of the state.
This issue of SYSVOL not replicating has been going on for over two months.
The main DC has the DFSR service but the second one does not.
Running dfsrmig /GetMigrationState on both DCs returns "eliminated".
It appears that even though the DFSR service does not appear in services.msc 
that dfsrmig still works.
The guy who originally handled IT stuff quit just over two months ago and the 
new guy steps in to a hornet's nest (SYSVOL was already broken).
This is a one guy IT shop for a company with 17 users.
He has 322 pages of meticulous notes of everything he has done over the past 
two months (that alone scares the crap out of me).
Why the guy waited over two months to ask for help is beyond me.
The company has known for months that electric work was scheduled at the "main" 
datacenter (main being the DC with all the FSMO roles).
Electric power will be down from 1800 this Friday and not guaranteed to be back 
before at least 0300 Monday.
>From what I was told they have been instructed that no sources of power are 
>allowed in this datacenter during this time.
Obviously if the second DC has no SYSVOL, "things" just aren't to work right 
for the users on that side.

I have asked for the results of "net share" from both DCs.
If the first DC has SYSVOL and NetLogon and the second one does not, then 
dcpromo down the second DC, reboot and dcpromo back.
If the first DC does not have SYSVOL share but has SYSVOL contents, then follow 
the Microsoft KB and take it from there.

Any advice, suggestions and thoughts are welcome.

Once they are back working, talk them in to putting in some 2012 R2 DCs since 
they have the licenses already.

Thanks


Webster

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith
Sent: Wednesday, November 16, 2016 6:44 PM
To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com>
Subject: [NTSysADM] RE: How to force an authoritative and non-authoritative 
synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)

You have a File Replication Service service, yes?

You want THAT KB instead.

Which is:

https://support.microsoft.com/en-us/kb/290762


From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Webster
Sent: Wednesday, November 16, 2016 7:02 PM
To: NT Issues 
(ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com>)
Subject: [NTSysADM] How to force an authoritative and non-authoritative 
synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)

Anyone ever had to use this KB to fix SYSVOL?

https://support.microsoft.com/en-us/kb/2218556

Unfortunately, the two DCs are Server 2008 so they can't call Microsoft for 
support.

I was looking at the section How to perform an authoritative synchronization of 
DFSR-replicated SYSVOL (like "D4" for FRS) and Steps 4 and 10 confuse me. Those 
steps say to start the DFSR service but there are no previous instructions that 
say to stop the service. On one of the broken DCs, there is no DFSR service 
that shows in services.msc.

Any advice on using that KB would be appreciated.

Thanks


Webster


Reply via email to