Remote Desktop host
Answer: Windows Professional, Enterprise, and Education editions can accept incoming Remote Desktop connections. Windows Home can be an RDP client but cannot serve as the Remote Desktop host.
Administrator playbook
Decide, verify, and document
Use the curated answer as a starting point, then prove the outcome against the target tenant or device.
What it means
- Client and host capabilities are different
- Enabling Remote Desktop exposes a network service
- Windows Server Remote Desktop Services is a separate multi-user product and licensing model
What to check next
- Confirm the target edition can act as a host
- Limit access to trusted networks or a properly secured remote-access path
- Use strong authentication and review permitted users
Verify success
- Confirm the feature is present or enabled on the target edition and build.
- Test the intended workflow with a pilot device and least-privileged user.
- Confirm policy reports success from the actual management authority.
Escalate when
- The documented edition and hardware requirements are met but the feature is absent.
- Policy reports success while the user or device state is incorrect.
- Licensing or OEM terms—not technical prerequisites—control the outcome.
Copyable admin briefAnswer, next checks, source, and review date
Capture edition and build
Get-ComputerInfo | Select-Object WindowsProductName,WindowsVersion,OsBuildNumber,OsArchitectureRead-only. Edition and exact build often control availability.
List optional feature state
Get-WindowsOptionalFeature -Online | Where-Object State -ne "Disabled" | Select-Object FeatureName,StateRead-only. Not every Windows capability is represented as an optional feature.
Evidence to preserve
- Windows edition, version, and build
- Hardware and firmware prerequisites
- Management authority and policy source
- Required user or device experience