Windows 10: Time Sync Not Working Accross Domain

Hey everyone,Late last week I decided to start using a time server to prevent time skew and drift across our domain. I pointed our primary domain controller to a few of the NIST time servers. Everything seemed good at first but it now seems that the other 3 domain controllers aren't syncing at all with the PDC, rather using the local CMOS clock. The workstations aren't syncing time with a DC either. My first guess is that some group policy was messing things up but I can't locate any policy that seems related. The PDC and the rest of VMs, no time is synced with any host.Here's the configuratio

:)

 

UnattendedJoin error: failed to find the domain data (0x6e)

Thanks for the suggestion! I don't want to add a domain account, as this is a generic unattended install that will be used for all company machines. Do you think it's possible that the computer would join the domain if, instead of using UnattendedJoin in specialize, I used your steps but left out the specific account?

The other thing I was thinking was to use a generic account to allow the domain join during the specialize step. I added a machine password in the UnattendedJoin component, and instead of getting the error listed above, I got an authentication error, which makes me think I could probably do a secure join instead of the unsecure join.

Thoughts?

 

Time sync not working

Hello,

For some reason time sync is not functioning correctly on my new laptop. I feel like for some reason it has something to do with permissions. So far I've tried to troubleshoot it myself but nothing seems to function. Due to inability to sync the time some
online games that require timestamp certificates in order to function.

This problem has been ongoing since I took the laptop out of the box, but I briefly managed to somehow fix it. Now the fix doesn't work anymore tho. I will explain this later in more detail.

I've gone through this list How to fix Windows Time service not running on Windows 10/11 which includes

1. Perform SFC and DISM scans
   • These came out clean, no issues
2. Set the Windows Time Service to automatic
   • This was set on automatic and it says "running" but still the time wont sync"
3. Make sure that the Local System account starts the Windows Time service
   • I have set this as the local system account and the process starts normally without error messages. I managed to get the sync to work for one day by changing the "Log on" option from local system account to another account. Now it doesn't work anymore for
     some reason.
4. Register the W32Time file again
   • Did this, No effect
5. Check the Windows Time Service in the Task Scheduler
   1. Checked this, everything seems to be normal except for the fact that ForceSynchronizeTIme has Unspecified Error (0x80004005) as the last run result. However SynchronizeTIme
6. Use a different time server
   • When trying to switch servers it gives the error that sync failed because request timed out. Same result for every server.
7. Force Windows to sync the time
   • Does not work, cmd gives the following message: The computer did not resync because no time data was available.
8. Use sc triggerinfo command
   • Did not work
9. Check your motherboard battery
   • Battery is fine, don't think this is the issue since the laptop is brand new

If anyone would have any insights or suggestions I would be happy to hear them!

 

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