How set in Windows Server 2008 r2 interval to sync time with the PDC emulator

I'll agree with sysadmin1138 on the first 2 sentences in his answer:

That's not how NTP works, presuming a full NTP client. NTP works by disciplining the local clock so it can't fall out of sync, rather than hard-setting it back to true.

The rest, while true, is quite unnecessary.

All domain controllers are NTP servers by default. The DC which holds the "PDC Emulator" FSMO role should be configured to sync with an Internet NTP server, preferably a stratum 2 server. All other DCs will automagically sync themselves with that DC.

All domain members will automagically sync with their closest DC.

With the exception of the configuration of the PDC Emulator DC, all of this happens with no manual configuration required. There's really no need to mess with it under normal circumstances.

If you have non-Windows machines in your environment, you can simply configure them to use your AD domain name as an NTP server (assuming they are using the same DNS servers as your domain member machines), since the DNS A record for the AD domain name always resolves to all DC IP addresses.

Okay solved it, was just a matter of syntax, this is the default command from the microsoft site.

w32tm /config /computer:<<PDC-FQDN>> /manualpeerlist:time.windows.com /syncfromflags:manual /update

In order for it to execute you have to get rid of the "<< >>" and enter the name of you PDC with the domain name like "servername.domainname"

So suppose you server name (PDC name) is: mynewdomaincontroller1 and your domain name is: twinkles.com

Then this is how you will write the command: w32tm /config /computer:mynewdomaincontroller1.twinkles.com /manualpeerlist:time.windows.com /syncfromflags:manual /update