NTRFS: error event 13508

I ran into this problem so I ran the Authoritative FRS restore procedure using the D4 flag on the old server.
Click Start, and then click Run.
In the Open box, type cmd and then press ENTER.
In the Command box, type net stop ntfrs.
Click Start, and then click Run.
In the Open box, type regedit and then press ENTER.
Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
In the right pane, double click BurFlags.
In the Edit DWORD Value dialog box, type D4 and then click OK.
Quit Registry Editor, and then switch to the Command box.
In the Command box, type net start ntfrs.
Quit the Command box.

Then I ran the non-authoritative restore process using the D2 flag on the SBS2008 server.
Click Start, and then click Run.
In the Open box, type cmd and then press ENTER.
In the Command box, type net stop ntfrs.
Click Start, and then click Run.
In the Open box, type regedit and then press ENTER.
Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
In the right pane, double-click BurFlags.
In the Edit DWORD Value dialog box, type D2 and then click OK.
Quit Registry Editor, and then switch to the Command box.
In the Command box, type net start ntfrs.
Quit the Command box.

The reason is your new DC is not advertising itself as an DC due to missing Netlogon shares.
http://support.microsoft.com/kb/947022

You can try above link or perform non authoritative restore of sysvol/Netlogon(Ignore the OS version).
http://msdn.microsoft.com/en-us/library/cc507518%28v=vs.85%29.aspx
http://social.technet.microsoft.com/Forums/en/winserverDS/thread/58e47cf0-d3ec-4adc-aac4-35dfdfc8151e
http://support.microsoft.com/kb/840674

Make sure new DC also GC & it is configured to point windows 2003 as preferred & itself as a alternate DNS server in their NIC & once the replication has been completed revert the settings, so new DC point itself for DNS & alternate to other DC’s with DNS running on it. More on below article.
http://awinish.wordpress.com/2011/03/08/dns-recommendations-from-microsoft/

Make sure DC holding PDCEmulator FSMO role is allowed to sync time from external source & other DC’s following PDC for time sync & you require to ope port 123UDP for time service on your firewall.

how to configure authoritative time server
http://support.microsoft.com/kb/816042

You can force the replication using repadmin /syncall /APed

Other commands you want to run to find out any problems:
ntfrsutl ds |findstr /i “root stage”

DCDiag.exe /v /test:Advertising /test:SysVolCheck

Things worth considering:
LINK1
LINK2
LINK3 – list of useful procedures
LINK4 – Verify Schema Verions
LINK5 – DNS issues
LINK6 – NETLOGON share not present
LINK7
LINK8 – Migration step by step
LINK9 – Migration by MS