Windows 10: I have a domain DC is running Windows Server 2016 Standard and have the Account Lockout...

I have a domain DC is running Windows Server 2016 Standard and have the Account Lockout Policy enabled. that locks the computer after 10 minutes of inactivity. I have a problem with only one of my users, he has a new Windows 11 computer and when he attempts to log into his PC with the correct password after the computer has been locked by the policy he receive the following error: The referenced account is currently locked out and may not be logged on to., in the morning when he turn on the computer everyday he's able to login without any issues.

:)

 

My Domain controller is running on Server 2016. I have a new machine in my network which is running on Serer 2019. Can I add Server 2019 machine to the existing DC which is running on Server 2016?

My Domain controller is running on Server 2016. I have a new machine in my network which is running on Serer 2019. Can I add Server 2019 machine to the existing DC which is running on Server 2016?

 

windows server 2016 standard as addtional domain controller

Hi,

I have a primary domain controller running on windows server 2008 R2 & also have a additional domain controller running on same windows server 2008 R2.

Recently I have bought a new server hardware and installed windows server 2016 standard OS. Now the requirement is to promote this new server 2016 as domain controller. I will make this server additional domain controller and still the PDC will be running
on windows server 2008 R2 only. I need to know when the PDC & ADC server version will be different then will it causes any issue in functionality of domain controller.

Group policy will be migrated to the ADC or not. We will check the functionality of ADC by shutting down the PDC server.

Kindly let me know what all difficulties I can face during this setup. Are there any compatibility issue which can occur.

Regards

Ankur

[Moved from: Windows / Windows 10 / Windows update, recovery, & backup]

 

Trust Relationship between Server and DC Fails

I am having problems establishing a trust relationship between a server and a DC.

Here are the things I have tried(that I can rememeber):

• Unjoining and rejoining the Domain
• Running: netdom reset 'computername' /domain:abc /userO:xxx /passwordO:*
• Running Test-ComputerSecureChannel -Repair -Verbose
• Resetting the password of the computer from the DC
• After all of these, Test-ComputerSecureChannel still returns false

Many of the error messages I get revolve around 'Access is Denied'. However, all of these commands are run from elevated PowerShell, as a domain administrator, with the netdom command run on both the local machine and the DC. The local machine is running
Server 2012 and the DC is Server 2016. Any thoughts would be appreciated.