Windows 10: Forcing Time Sync Windows 10 PRO Domain connected December 2020

We have Windows 10 PRO and Domain connected PCs, and the tab on the clock settings for Internet Time no longer allows a time server to be set.

And the clock are all off by a minimum of 3 minutes as much as 6, some off by couple hours.

Setting the time by clicking in bottom right does no good.


When clocks drift by too much, email can stop. Tricky, but we figured that out, when users complain of email issues we ask them

if their clock is set correctly.

:)

 

Things to do once connected new G-Sync monitor

I'm getting my G-Sync monitor today.

I think I have to take the following steps:

• Connect 1440p G-sync monitor with DP cable
• Connect second 1080p 60Hz monitor by HDMI
• Startup PC
• Reinstall display driver
• Restart PC (I always do that after display driver install)
• Activate G-Sync in NV control panel (I believe also V-Sync is auto on after that?)
• Set my 1440p monitor from 1080p to 1440p
• Calibrate my 1440p monitor

Also ingame, I should turn off V-Sync?
Are there any problems running a second 60Hz 1080p monitor?

Is there anything else I should do/know?

 

Windows Time is constantly out of sync


As the title suggests, my time is always out of sync, it makes it increasingly difficult to follow conversations on Skype, for instance. I try to manually update the time and it tells me fairly often that there's an error when trying to update. It doesn't matter if my PC is powered off or if I'm using it, the time is bound to get out of sync, so I doubt it has anything to do w/ the CMOS battery. Should I be using a different time server other than time.windows.com? I'm also using Webroot SecureAnywhere Anti-virus. Not sure if that's causing a conflict or not.

I'm on Windows 10 RTM
I'm not connected to a domain, just a regular Windows Home network.

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW