Sysvol folder doesn’t exist in Windows 2012/16 after deploying DC in AD 2008.

Hi guys,

After deployed Windows 2012/16 and promoting it to AD SYSVOL folder is not sync with Windows 2008. Problem this exists because Windows 2008 in default is using FSRM when Windows 2012/16 DFSR to sync SYSVOL.

Fix: migrating FRS to DFSR SYSVOL.
1. If you deployed Windows 2012 and have this problem please uninstall AD role from new server.

2. Go to your old AD server and raised domain level to at least Windows Sever 2008.

Set-ADDomainMode -Identity domain.name.com -DomainMode Windows2008Domain

FSRM to DFSR Migration
3. Migrate to Prepared State
Type: Dfsrmig /setglobalstate 1

Type: Dfsrmig /getmigrationstate

When all DCs are ready, the output will look like this:

4.Migrate to Redirected State
Type: Dfsrmig /setglobalstate 2

Type: Dfsrmig /getmigrationstate

When all DCs are ready, the output will look like this:

5.Migrate to Eliminated State
Type: Dfsrmig /setglobalstate 3

Type: Dfsrmig /getmigrationstate

When all DCs are ready, the output will look like this:

Your migration is complete.

5. Please install AD role on the new sever.

6. Check SYSVOL folder on the new server.

That’s all!

How to migration DHCP from Windows Server 2008 to 2012

Today simple tip how to migrate DHCP from Windows Server 2008 to 2012.

  • Log on to the old/existing DHCP server.
  • Click Start, click Run, type cmd in the Open box, right-click, and then “Run as Administrator”.
  • Type netsh dhcp server export C:\Users\Desktop\dhcp.txt all , and then press ENTER.
  • Install the DHCP role on the new (2012) DHCP server using Server Manager.
  • Copy the exported DHCP text file to the desktop of the new DHCP server.
  • Verify that the DHCP service is installed and started on the new DHCP server.
  • Click Start, click Run, type cmd in the Open box, right-click, and then “Run as Administrator”.
  • Type netsh dhcp server import C:\Users\Desktop\dhcp.txt all , and then press ENTER
  • Open DHCP console on the new server.
  • In the console tree, right-click DHCP.
  • Select “Authorize”.

That’s all folks.