Windows Server 2022 is an operating system for running shared infrastructure rather than an ordinary personal desktop. Administrators add roles for identity, file storage, web workloads, virtualization, or remote access, then manage the services that other computers depend on. Windows Server 2022 can host Active Directory, SMB shares, Hyper-V guests, and server processes on one machine or across a managed group. It does not turn each role on automatically, and choosing the installation form determines how the machine will be administered later.
Core or desktop
Setup separates Server Core from Server with Desktop Experience. Server Core omits the familiar Windows shell and most local graphical management. The administrator works through SConfig, PowerShell, command-line commands, or a remote console. That smaller installation reduces the local component set, but a technician who expects to manage every setting through windows and menus may find the first sign-in unexpectedly sparse.
The choice is permanent for that installation. Windows Server 2022 cannot switch between Server Core and Desktop Experience by adding or removing a component later. Moving to the other form requires a clean installation, so role compatibility and the administration plan need checking before the system disk is prepared. Some roles and supporting programs also require Desktop Experience rather than Server Core.
Move file servers
Storage Migration Service separates a file-server move into inventory, transfer, and optional cutover. Inventory records shares, files, and security settings on the source. Transfer copies the selected data to the destination. Cutover can then give the destination the old server name and network identity, which lets existing paths continue to point at the familiar name.
Cutover changes more than a folder location. The source keeps its files, but Windows Server 2022 makes the old identity unavailable there after the handoff. Administrative credentials, domain conditions, destination capacity, and firewall access must be ready before migration. SMB-In, Netlogon, WMI, and DCOM traffic can all affect discovery or transfer. A domain controller cannot take the ordinary cutover path, so an identity server needs a different migration plan.
Compress SMB traffic
SMB compression reduces the bytes sent during a file copy. It can help when the network is slower than the disks or when a congested link carries large compressible files. Windows Server 2022 spends processor time compressing and expanding the data, so the change exchanges CPU work for network capacity. Already compressed archives and media may gain little.
The administrator can request compression for a copy or configure it on a share. It does not combine with SMB Direct over RDMA. A storage path designed around RDMA throughput therefore cannot simply add SMB compression without losing that transfer mode. Testing with the real file mix is more informative than enabling compression for every share.
Virtualize with limits
Hyper-V can expose processor virtualization extensions to a guest, which lets that virtual machine run Hyper-V itself. Nested hosts are useful for training labs, isolated development, container work, and repeatable test environments. Windows Server 2022 still adds another scheduling and storage layer between the nested workload and the hardware.
Memory assigned to a nested host cannot vary while Hyper-V runs inside it. The outer virtual machine must be turned off before its memory amount changes. Nested virtualization also adds latency and does not fit failover-cluster or performance-sensitive production work. A lab that starts successfully does not prove that the same layout is an appropriate production cluster.
Hardware-backed security
Secured-core protections begin below the operating system. Compatible systems combine TPM 2.0, Secure Boot, boot DMA protection, and virtualization-based security to protect startup and isolate sensitive code. Windows Server 2022 can use those controls, but installation alone cannot create missing firmware or processor support. A procurement list and firmware settings must match the intended security baseline before deployment.
