Periodically, I see a series of events on a notebook which is part of a windows domain that has a physical PDC running Windows Server 2008 R2 and a virtual secondary DC running Windows Server 2012 R2.

These events seem to line up in time with remote desktop sessions disconnecting.

Please see the questions that follow the information.

The PDC (xdc4.devxx.local, physical machine) is configured to get its time from:

[TimeProviders]

NtpClient (Local)
DllName: C:\Windows\system32\w32time.dll (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Local)
ResolvePeerBackoffMaxTimes: 7 (Local)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 1 (Local)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 7200 (Local)
Type: NTP (Local)
NtpServer: 0.us.pool.ntp.org 1.us.pool.ntp.org 2.us.pool.ntp.org (Local)

The secondary DC (xdc5.devxx.local, virtual) is configured to get its time from:

[TimeProviders]

NtpClient (Local)
DllName: C:\Windows\system32\w32time.dll (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Local)
ResolvePeerBackoffMaxTimes: 7 (Local)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 1 (Local)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 3600 (Local)
Type: NTP (Local)
NtpServer: xdc4.devxx.local 0.us.pool.ntp.org 1.us.pool.ntp.org 2.us.pool.ntp.org (Local)

NOTE: I did set the secondary DC to get its time from "DOMHIER",
but after I did so, w32tm /query /source showed only the local CMOS time source.

The virtual DC xdc5 runs in Hyper-V on xsvrc, which is running Windows Server 2008 R2.
The configuration for xdc5 has "Time synchronization" disabled (unchecked) in Hyper-V.

The event sequence is:
---------------
Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          9/3/2015 10:37:18 AM
Event ID:      129
Task Category: None
Level:         Warning
Keywords:     
User:          LOCAL SERVICE
Computer:      wsx010.devxx.local
Description:
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1)
---------------
Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          9/3/2015 10:37:19 AM
Event ID:      37
Task Category: None
Level:         Information
Keywords:     
User:          LOCAL SERVICE
Computer:      wsx010.devxx.local
Description:
The time provider NtpClient is currently receiving valid time data from xdc5.devxx.local (ntp.d|0.0.0.0:123->192.168.25.115:123).
---------------
Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          9/3/2015 10:38:00 AM
Event ID:      129
Task Category: None
Level:         Warning
Keywords:     
User:          LOCAL SERVICE
Computer:      wsx010.devxx.local
Description:
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1)
---------------
Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          9/3/2015 10:38:02 AM
Event ID:      129
Task Category: None
Level:         Warning
Keywords:     
User:          LOCAL SERVICE
Computer:      wsx010.devxx.local
Description:
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1)
---------------
Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          9/3/2015 10:38:07 AM
Event ID:      37
Task Category: None
Level:         Information
Keywords:     
User:          LOCAL SERVICE
Computer:      wsx010.devxx.local
Description:
The time provider NtpClient is currently receiving valid time data from xdc4.devxx.local (ntp.d|0.0.0.0:123->192.168.25.109:123).
---------------
Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          9/3/2015 10:38:07 AM
Event ID:      35
Task Category: None
Level:         Information
Keywords:     
User:          LOCAL SERVICE
Computer:      wsx010.devxx.local
Description:
The time service is now synchronizing the system time with the time source xdc4.devxx.local (ntp.d|0.0.0.0:123->192.168.25.109:123).
---------------

QUESTIONS:
1) Is there something I'm missing about configuring the time service on the virtual DC?
2) Is there something I should do so the virtual DC doesn't advertise itself as a time source?
3) Any other suggestions for what I should try to track down for information to help resolve this?

Thanks,
Bob

On the virtual run taken from here: http://blogs.msmvps.com/acefekay/category/configure-windows-time-service-hierarchy/  The PDC should be fine as it is an outside time source.

Windows Server 2003 and all newer server operating systems: 

1. Open an Administrator Command Prompt
2. w32tm /config /syncfromflags:domhier /update /reliable:no
3. w32tm /resync /rediscover
4. net stop w32time && net start w32time
5. Check it with W32tm /query /configuration   
   1. You may have to repeatedly run it a few times until you see it change from the CMOS clock to the time server you set it to. If it doesnt change after a few minutes, you may have to reset the time service in the Contingency section below

http://blogs.msdn.com/b/w32time/archive/2007/09/04/keeping-the-domain-on-time.aspx

• Marked as answer by BGood26 15 hours 51 minutes ago

This looks like it's resolved my issues.

Thanks!