Networking Blog
The Official Blog Site of the Windows Core Networking Team at Microsoft
Home
Options
1,149
Daniel Havey on 02-14-2019 10:04 AM
2,239
Daniel Havey on 02-14-2019 10:03 AM
2,158
Dan Cuomo on 02-14-2019 10:03 AM
712
Daniel Havey on 02-14-2019 10:02 AM
617
Harini Ramakrishnan on 02-14-2019 10:01 AM
348
Gabriel Montenegro on 02-14-2019 10:00 AM
419
David Schott on 02-14-2019 10:00 AM
255
AnirbanPaul on 02-14-2019 09:59 AM
1,034
Jason Messer on 02-14-2019 09:59 AM
184
AnirbanPaul on 02-14-2019 09:59 AM
505
Daniel Havey on 02-14-2019 09:58 AM
420
Gabriel Montenegro on 02-14-2019 09:58 AM
129
AnirbanPaul on 02-14-2019 09:58 AM
232
Daniel Havey on 02-14-2019 09:57 AM
445
Jason Messer on 02-14-2019 09:57 AM
188
AnirbanPaul on 02-14-2019 09:57 AM
174
AnirbanPaul on 02-14-2019 09:57 AM
Latest Comments
True for Server as well AFAIK.  You need to create the registry keys.
0 Likes
Yes @Dan Cuomo , on my Win10(1809) I can't see PtpClient in the registry (only VMIC and NTP).
0 Likes
Hi @VasiliiNuzhnov - Thanks for reading. You would perform the same steps on a Windows 10 system as on the 2019 VM. There's no functional difference between the PTP provider on Client or Server SKUs. Are you running into an issue in your attempt?
0 Likes
Hi Dan. you wrote "Windows 10 system can also work", how can I do this without Windows Server 2019?
0 Likes
HI Dan, Separation is based on network segments (which reflect geographical location). PTPmasters are each others backups which is why the 2 ptp domains are necessary. Peter
0 Likes