Windows Time syncing options


hi, i've been piecing informaiton various sources (after time setup when south last week) time source setup org.

here's i've decided go in our single forest, multi domain setup;

1. physical dc holding pdc fsmo in each domain syncing external time source single point of failure internet conection

2. windows 2008r2 virtual host cluster hosts additional dc's. hosts set manualy sync physical pdc's

3. virtualised dc's (not running pdc unless pdc fails) set sync both physical pdc's adding registry key s0

reg add hklm\system\currentcontrolset\services\w32time\timeproviders\vmictimeprovider /v enabled /t reg_dword /d 0

this command stops windows time service (w32time) using hyper-v time synchronization integration when guest domain controller’s operating system started. setting disabled, hyper-v time synchronization provider used if guest domain controller rebooted or restored a saved state.

4. other domained servers , clients tto use default windows options (nt5ds)

5. non domained windwos clients use physical pdc's

6. don't care non windows boxes :p

thanks

himesh

sounds right. might want consider setting physical dc redundancy (to can transfer/seize pdc emulator role if needed)...

hth
marcin



Windows Server  >  Directory Services



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client