Hello,
It sounds like you're on the right track with enabling AES encryption for your Active Directory (AD) user accounts, but there are a few key points to ensure everything is set up correctly.
1.Group Policy Application:
Ensure that the Group Policy Object (GPO) you configured is properly linked to the appropriate Organizational Unit (OU) where user accounts are created.
Run gpupdate /force
on the domain controllers and client machines to ensure the latest group policies are applied.
2.AD Schema Version:
Ensure that your Active Directory schema is updated and supports AES encryption types. AES encryption types were introduced with Windows Server 2008, so if you have older domain controllers, this might be an issue.
3.User Account Properties:
When a new user account is created in Active Directory Users and Computers (ADUC), it inherits default settings. The AES options must be manually enabled unless you script or automate this process.
4.Template Accounts:
If you are using a template account for creating new users, ensure that the template has the AES settings configured. This way, any new accounts created from the template will inherit those settings.
5.Password Change Requirement:
It's important to note that existing accounts will need to have their passwords changed for the AES settings to take effect. This is because the Kerberos ticket is generated based on the password hash, and if the password was set before AES was enabled, it will continue to use the old encryption type (like RC4).
Best Regards,
Yanhong Liu
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.