Direct answer
Identify each device's edition, release and servicing channel, check the applicable Microsoft lifecycle, then schedule migration and verification before its support arrangements end.
Inventory versions and ownership
Record edition, release, build, servicing option, device owner and last inventory time. Separate offline devices and special-purpose machines. Two devices with the same version number can have different lifecycle dates because of edition or servicing channel.
Check the applicable lifecycle
Use Microsoft's current lifecycle information for the exact product and edition. Confirm whether an extended support program applies to the actual device and organization; do not assume a general support date or paid arrangement covers every machine.
Reference: Microsoft: Windows lifecycle FAQ.
Migrate and verify
Pilot the supported release with representative applications, drivers, encryption recovery and remote support. Assign an owner and deadline for every device that cannot migrate. Recollect version and update status after deployment, and review exceptions with a defined expiry and compensating controls.
Handle an incompatible application
If a laboratory application cannot run on the supported release, verify the vendor's version and replacement options with its owner. Record the affected device, data and network exposure, temporary protections, migration owner and deadline. Test the replacement using representative files before retiring the old machine; an exception should be reviewed as lifecycle dates or exposure change.
Assessment limits
Lifecycle dates and available support arrangements change. A supported release is not proof that all updates or other security controls are installed.
Frequently asked questions
Does a recent patch prove a Windows release is supported?
No. Check the exact edition, servicing channel and current lifecycle information.
Can a failed migration be ignored?
Track the affected device, responsible owner, temporary mitigations and a review date.
Does version inventory cover offline devices?
Not necessarily. Record last collection time and separately reconcile devices that have not reported.
Primary sources and further reading
These guides combine published security guidance with practical assessment planning. Adapt checks to the owner's policy, environment, and authorized scope.
This guide was prepared with AI assistance using the linked sources and illustrative examples. Check current vendor guidance and your environment before making changes.