Mặc định, Windows Server 2012 đã hỗ trợ TLS 1.2 nhưng chưa được kích hoạt mặc định. Để cấu hình TLS 1.2 cho Windows Server 2012, bạn cần thực hiện các bước theo hướng dẫn sau đây:
1. Mở Start > Run và gõ vào regedit để mở Registry Editor.
2. Backup lại Registry để phòng trục trặc trong quá trình cấu hình thì có thể phục hồi. Chọn Computer, sau đó chọn menu File > Export. Nhập địa chỉ lưu trữ fiel backup cấu hình Registry.
3. Mở registry sau: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocols
4. Nhấp chuột phải chọn New > Key. Đặt tên là "TLS 1.2".
5. Nhất chuột phải vào khóa "TLS 1.2" và thêm mới 2 key con thuộc "TLS 1.2" và đặt tên lần lượt là "Client" và "Server".
6. Nhấp chuột phải vào khóa "Client" và chọn New > DWORD [32-bit] Value, đặt tên là "DisabledByDefault". Nhấp đúp vào khóa này, chọn Base là "Hexadecimal" và nhập giá trị là 0.
7. Tương tự, tạo thêm một khóa DWORD [32-bit] Value và đặt tên là "Enabled", sau đó thiết lập giá trị 1 và Base là Hexadecimal.
8. Thực hiện lại các bước 6, 7 cho khóa "Server", tức là tạo 2 DWORD [32-bit] Value "DisabledByDefault" và "Enabled".
9. Reboot lại server. Server đã sẵn sàng hỗ trợ giao thức TLS 1.2
10. Kiểm tra lại server đã hỗ trợ TLS 1.2 hay chưa bằng cách truy cập vào Qualys SSL Tool: //www.ssllabs.com/ssltest/
11. Sau khi kiểm tra thấy server đã hỗ trợ TLS 1.2, bạn cần vô hiệu hóa SSL 3.0, TLS 1.0 và TLS 1.1 trên server bằng cách lặp lại các bước 4, 5, 6, 7 nhưng với các giá trị sau đây:
This update implements phase three of Distributed Component Object Model [DCOM] hardening. See KB5004442. After you install this update, you cannot turn off the changes using the registry key.
- This update addresses an issue that affects the registry size. It grows very large. This occurs because the registry entries are not removed when users sign out of an Azure Virtual Desktop [AVD] environment that uses FSlogix.
- This update affects the United Mexican States. This update supports the government’s daylight saving time change order for 2023.
- This update addresses an issue that might affect lsass.exe. It might stop responding when it sends a Lightweight Directory Access Protocol [LDAP] query to a domain controller that has a very large LDAP filter.
- This update addresses an issue that affects the Local Security Authority Subsystem Service [LSASS]. LSASS might stop responding. This occurs after you run Sysprep on a domain-joined machine.
- This update addresses an issue that affects a computer account and Active Directory. When you reuse an existing computer account to join an Active Directory domain, joining fails. This occurs on devices that have installed Windows updates dated October 11, 2022 or later. The error message is, “Error 0xaac [2732]: NERR_AccountReuseBlockedByPolicy: ‘An account with the same name exists in Active Directory. Re-using the account was blocked by security policy.’” For more information, see KB5020276.
- This update addresses an issue that affects the Routing and Remote Access Service [RRAS]. RRAS cannot accept any new incoming virtual private network [VPN] connections.
- This update addresses an issue that affects Cluster Name Object of Failover Clustering on Azure virtual machines [VM]. The issue stops you from repairing it.
If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.
For more information about security vulnerabilities, please refer to the new Security Update Guide website and the March 2023 Security Updates.
Windows 10 servicing stack update - 17763.4121
This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates [SSU] ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.
Symptom
Workaround
After installing KB5001342 or later, the Cluster Service might fail to start because a Cluster Network Driver is not found.
This issue occurs because of an update to the PnP class drivers used by this service. After about 20 minutes, you should be able to restart your device and not encounter this issue. For more information about the specific errors, cause, and workaround for this issue, please see KB5003571.
After installing updates released January 10, 2023, and later, kiosk device profiles that have auto log on enabled might not sign in automatically. After Autopilot completes provisioning, affected devices will stay on the sign-in screen prompting for credentials.
This issue is addressed in KB5028168.
How to get this update
Before installing this update
Microsoft now combines the latest servicing stack update [SSU] for your operating system with the latest cumulative update [LCU]. SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU. For general information about SSUs, see Servicing stack updates and Servicing Stack Updates [SSU]: Frequently Asked Questions.
Prerequisite:
You must install the August 10, 2021 SSU [KB5005112] before installing the LCU.
Install this update
Release Channel
Available
Next Step
Windows Update and Microsoft Update
Yes
None. This update will be downloaded and installed automatically from Windows Update.
Windows Update for Business
Yes
None. This update will be downloaded and installed automatically from Windows Update in accordance with configured policies.
Microsoft Update Catalog
Yes
To get the standalone package for this update, go to the Microsoft Update Catalog website.
Windows Server Update Services [WSUS]
Yes
This update will automatically sync with WSUS if you configure Products and Classifications as follows:
Product: Windows 10
Classification: Security Updates
If you want to remove the LCU
To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages.
Running Windows Update Standalone Installer [wusa.exe] with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.
File information
For a list of the files that are provided in this update, download the file information for cumulative update 5023702.
For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 17763.4121.
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.