Hardened Windows Server 2022 Datacenter - Simplified Chinese Tools

This product provides the Windows Server 2022 Datacenter Desktop Experience build, Simplified Chinese localization, and development/utility tool inventory identified in the published release manifest, delivered as an Amazon Machine Image (AMI) by Hanwei. The image applies Hanwei's versioned security-hardening baseline, records build-date Windows and tool state, and is constructed without embedded customer credentials or account-specific configuration.

Marketplace software charges cover Hanwei's operating-system preparation, Simplified Chinese localization preparation, documented tool integration, application of the verified security-hardening baseline, build-date update and package recording, credential-free AMI construction, repeatable image build process, and bounded final-image testing. Hanwei support is supplementary and is not the sole basis for Marketplace software charges. Applicable Microsoft Windows Server licensing, third-party tool charges, EC2, and Marketplace charges are determined by the final AWS and Seller Portal terms.

• Microsoft lists Windows Server 2022 Datacenter under the Fixed Lifecycle Policy.
• Microsoft lifecycle information lists mainstream support through October 14, 2026 and extended support through October 15, 2031, with dates displayed in Pacific Time.
• Customers are responsible for monitoring the applicable Microsoft lifecycle, applying eligible updates, testing them, and planning migration before end of support.
• The Windows Server 2022 lifecycle does not establish that every third-party tool, Windows feature, driver, application, or customer workload is supported.

• Datacenter Desktop Experience and localization preparation: Hanwei prepares the Windows Server 2022 Datacenter Desktop Experience configuration and Simplified Chinese language settings identified in the final release manifest. The final release record identifies the display language, system locale, regional format, keyboard/input configuration, and time zone actually verified on the AMI.
• Documented development and utility inventory: Hanwei records every represented component by product/package/binary name, exact version, publisher or source, installer/checksum/signature state where available, installation path, license/notice status, update configuration, and validation result. Only components in that final manifest are included in the public release scope.
• Versioned security-hardening baseline: Hanwei applies a versioned Windows security profile. Only controls, values, exceptions, and effective states verified on the final AMI are included in the published release scope.
• Build-date update baseline: The release manifest records the Windows build number, edition, installation type, cumulative-update KBs, servicing state, update source, represented tool versions, and image-build date. This records a point in time and does not represent the AMI as continuously current after publication or launch.
• Credential-free construction: The published AMI contains no reusable customer password, EC2 key pair private key, AWS access key, secret access key, session token, domain credential, certificate private key, application secret, source code, copied customer project, or account-specific endpoint configuration.
• Repeatable construction and bounded EC2 testing: Final-image verification covers EC2 launch, Windows activation state, edition and installation type, Simplified Chinese UI and locale state, tool inventory/version/path checks, device state, restart behavior, recorded administrative-access configuration, update state, security-profile controls, and credential absence on the recorded EC2 baseline.

• Windows Server 2022 Datacenter edition and Desktop Experience installation type identified in the final release manifest
• Simplified Chinese localization configuration identified in the final release manifest
• Windows updates identified by build and KB in the final release manifest
• Development and utility components identified by exact version and license/notice state in the final release manifest
• Hanwei versioned security-hardening configuration

The final release manifest must determine whether Git, Visual Studio Code, Python, Node.js, 7-Zip, Notepad++, PowerShell, Firefox, WinSCP, Wireshark, or any other component is actually included. No RDS role, hardware-backed Windows security feature, cloud operational feature, Remote Desktop configuration, domain configuration, endpoint-protection tool, web server, application server, database, container runtime, monitoring agent, encryption, backup, performance configuration, or tool setting is represented as included unless it appears in the final package manifest and published release scope.