Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

No SYSVOL Shares

$
0
0

Hi All,

I have searched and tried several things, but I have a problem with two new 2016 DC that have no SYSVOL Shares.

Originally, I had a single SBS 2011 Std Server, acting as the sole DC.  The server is old and is no longer required, so the plan is to replace with two new servers, running 2016 Std.

The Domain Functional Level is 2008R2

I have introduced the two new 2016 Servers.  Although they will both run as DCs, they will both also provide a couple of other services.

2016Srv1 - Hyper-V Host running small VM for local application.

2016Srv2 - Running two files shares.  Has Nic Teaming Enabled.

Both Servers appeared to join the domain OK and are also DNS Servers.  Each Server has its own static IP Address as the Primary DNS Entry.

There are a number of errors in the Application and Services Logs

Under

ADWS Log. On a boot I get the Event 1202, then it goes to ADWS is now started and accepting requests

DFS Replication - Error 1202 Failed to contact DC, Replication Stopped, then 1206 Replication service successfully Contacted the Local DC.

Under DNS I have a number of 4010 events, that mention records in the reverse look up zone.  Looking at them they all belong to older devices that no longer exist.  If I delete one from the SBS server, it is replicated to the two 2016 Servers.

File Replication Service Log Warning 13508

The File Replication Service is having trouble enabling replication from SBS to 2016SRV2 for c:\windows\sysvol\domain using the DNS name SBS.domainname.local. FRS will keep retrying. 
 Following are some of the reasons you would see this warning. 
 
 [1] FRS can not correctly resolve the DNS name SBS.domainname.local from this computer. 
 [2] FRS is not running on SBS.domainname.local. 
 [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. 
 
 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

I have spent a couple of days trying to resolve this, any ideas?



Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>