Promoted 2012, NtFrs Errors, Restarted FRS and renamed jet folder, now SYSVOL and NETLOGON missing on both DCs

I have an SBS server that is experiencing many issues, crashing weekly. To help alleviate that I have booted up a Server 2012 machine to act as a DC and a DHCP server in a 50/50 setup.

I promoted the server to a Domain Controller and had errors and no SYSVOL or NETLOGON folders along with the following error:

The File Replication Service is having trouble enabling replication from MCA-SBS2008 to SPICEWORKS01 for c:\windows\sysvol\domain using the DNS name MCA-SBS2008.MCA.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 MCA-SBS2008.MCA.local from this computer. 
 [2] FRS is not running on MCA-SBS2008.MCA.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.

and

The File Replication Service is having trouble enabling replication from MCA-SBS2008.MCA.local to SPICEWORKS01 for c:\windows\sysvol\domain using the DNS name MCA-SBS2008.MCA.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 MCA-SBS2008.MCA.local from this computer. 
 [2] FRS is not running on MCA-SBS2008.MCA.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 left it a little while incase but the error just continued. I could confirm DNS resolution to the domain and DC. At this point attempting to load the AD Sites and Services to check the domain information and try to force replication gave this error - from either DC:

Naming information cannot be located because:

The specified domain either does not exist or could not be contacted. Contact your system administrator to verify that your domain is properly configured and is currently online.

At this point I looked online and found to stop the FRS Service, rename the Jet folder on the DC (MCA-SBS2008) then start the service. I've done this and now cannot load any AD information from either server and the NETLOGON and SYSVOL folders are missing from either DC.

Further than this though I can't find any errors in the Application or System logs even back on the SBS that are not just follow on issues. For instance:

The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name Sysytem (DNS) is configured and working correctly.

The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

But again these sort of things just look to be follow on.

IPCONFIG of both DCs:

MCA-SBS2008:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : MCA-SBS2008
   Primary Dns Suffix  . . . . . . . : MCA.local
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : MCA.local

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS
 VBD Client) #2
   Physical Address. . . . . . . . . : E4-1F-13-C1-F0-6E
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::1bd0:c8c5:baf5:4f9d%12(Preferred)
   Link-local IPv6 Address . . . . . : fe80::4c90:f48e:1b11:9f07%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.203.2(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.203.1
   DHCPv6 IAID . . . . . . . . . . . : 216276755
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-9E-E8-10-E4-1F-13-C1-F0-6C

   DNS Servers . . . . . . . . . . . : fe80::1bd0:c8c5:baf5:4f9d%12
                                       192.168.203.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{75EB23DB-98EA-47A3-B8B3-27701B81B
02F}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

SPICEWORKS01

From here I'm stuck - haven't seen this before and unfortunately this is a network I've inherited so there's a lot of quirks I haven't figured yet - getting a second DC up seemed like the smarted move as this organisation requires things to keep ticking 24 hours.