trying to add a new 2019 DC

[chazzy2501]

I'm trying to add a 2019 DC to my existing 2012r2 DCs, they've done the DRFS migration "eliminated" (and are all in the same state, dfs is happy with no errors) and now have sysvol_DRFS as the sysvol share on the 2012r2s

 

When I go to add a new 2019 DC and promote it, it creates a sysvol NOT sysvol_DRFS and DFS will not sync correctly the new server. (dfs has a timeout error with new server, possible error) I've tried with a second (new) DC and I'm getting the same result... (it want to make a sysvol not sysvol_DRFS) what gives?

 

The new server does create a sysvol folder with files in it, so it is syncing... so it is doing something.

 

is sysvol_DRFS only for migrated servers? and it is the share name that is important not the location on a given server? Then why does dfs get upset?

[Koldov]

sysvol_DRFS only for migrated servers

 

Can't help with the errors, but iirc yes to this.