Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 23.5

Windows Client

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Microsoft Windows is an operating system produced by Microsoft for use on personal computers, laptops and other end-user devices. Microsoft Windows is an industry standard desktop operating system. This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.4
Decision Date:	04/06/2023
Aliases:	Windows 7; Windows 8; Windows 10; Windows Vista; Windows XP; Remote Server Administration Tools; Windows AdminPack; Microsoft Edge; Embedded POSReady; Embedded Handheld
Introduced By:	Enterprise Program Management Office (EPMO) TRM Team
Vendor Name:	Microsoft

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
XP Pro SP2	09/17/2004	06/13/2010	06/13/2010
XP Pro SP3	05/06/2008	04/08/2014	04/08/2014
Embed POSReady 2009	03/10/2009	04/08/2014	04/09/2019
Vista	01/25/2007	04/13/2010	04/13/2010
Vista SP1	04/25/2008	05/25/2011	07/12/2011
Vista SP2	05/25/2009	04/10/2012	04/11/2017
Windows 7	10/22/2009	02/22/2013	04/09/2013
Windows 7 SP1	02/22/2011	01/13/2015	01/14/2020
Embedded POSReady 7	09/10/2011	10/12/2021	10/12/2021
Windows 8	10/30/2012	11/13/2015	11/13/2015
Windows 8.1	10/17/2013	01/09/2018	01/10/2023
Embedded Handheld6.5	09/11/2009	01/08/2013	01/14/2020
Win 10 (LTSB 1507)	07/29/2015	10/14/2025	10/14/2025
Win 10 (LTSB 1607)	08/02/2016	10/13/2026	10/13/2026
Win 10 (LTSC 1809)	11/13/2018	01/09/2029	01/09/2029
Windows 10 (FU 1709)	07/29/2015	10/09/2018	10/08/2019
Windows 10 (FU 1803)	03/01/2018	11/12/2019	05/11/2021
Windows 10 (FU 1809)	11/13/2018	11/10/2020	05/11/2021
Windows 10 (FU 1903)	05/21/2019	12/08/2020	12/08/2020
Windows 10 (FU 1909)	11/12/2019	05/11/2021	05/10/2022
Windows 10 (FU 2004)	05/27/2020	12/14/2021	12/14/2021
Windows 10 (FU 20H2)	10/20/2020	05/09/2023	05/09/2023
Windows 10 (FU 21H1)	05/18/2021	12/13/2022	12/13/2022
Windows 10 (FU 21H2)	11/16/2021	06/11/2024	06/11/2024
Windows 10 (FU 22H2)	10/22/2022	05/13/2025
Windows 11 (FU 21H2)	10/04/2021	10/10/2023	10/08/2024
Windows 11 (FU 22H2)	09/20/2022

Current Decision Matrix (04/05/2023)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2022

CY2023

CY2024

Future>

Release

XP Pro SP2

Prohibited

Unapproved

XP Pro SP3

Prohibited

Unapproved

Embed POSReady 2009

Prohibited

Unapproved

Vista

Prohibited

Unapproved

Vista SP1

Prohibited

Unapproved

Vista SP2

Prohibited

Unapproved

Windows 7

Prohibited

Unapproved

Windows 7 SP1

Prohibited

Unapproved

Embedded POSReady 7

Unapproved

Prohibited

Unapproved

Windows 8

Prohibited

Unapproved

Windows 8.1

Prohibited

Unapproved

Embedded Handheld6.5

Prohibited

Unapproved

Win 10 (LTSB 1507)

Unapproved

Prohibited

Unapproved

Win 10 (LTSB 1607)

Unapproved

Prohibited

Unapproved

Win 10 (LTSC 1809)

Unapproved

Windows 10 (FU 1709)

Prohibited

Unapproved

Windows 10 (FU 1803)

Prohibited

Unapproved

Windows 10 (FU 1809)

Unapproved

Prohibited

Unapproved

Windows 10 (FU 1903)

Prohibited

Unapproved

Windows 10 (FU 1909)

Unapproved

Prohibited

Unapproved

Windows 10 (FU 2004)

Unapproved

Prohibited

Unapproved

Windows 10 (FU 20H2)

Unapproved

Windows 10 (FU 21H1)

Approved w/Constraints
[7, 17, 18, 19]

Unapproved

Windows 10 (FU 21H2)

Approved w/Constraints
[1, 7, 17, 18, 19]

Approved w/Constraints
[7, 17, 18, 19]

Approved w/Constraints
[7, 17, 18, 20]

Approved w/Constraints
[18, 20, 21, 22]

Approved w/Constraints
[18, 21, 22, 23]

Divest
[18, 21, 22, 23]

Unapproved

Windows 10 (FU 22H2)

Unapproved

Approved w/Constraints
[1, 7, 17, 18, 20]

Approved w/Constraints
[1, 18, 20, 21, 22]

Approved w/Constraints
[18, 21, 22, 23]

Windows 11 (FU 21H2)

Unapproved

Approved w/Constraints
[1, 7, 17, 18, 19]

Approved w/Constraints
[1, 7, 17, 18, 20]

Approved w/Constraints
[1, 18, 20, 21, 22]

Approved w/Constraints
[1, 18, 21, 22, 23]

Windows 11 (FU 22H2)

Unapproved

Approved w/Constraints
[1, 7, 17, 18, 20]

Approved w/Constraints
[1, 18, 20, 21, 22]

Approved w/Constraints
[1, 18, 21, 22, 23]

Decision Constraints


[1]	This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population.

[2]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows desktop images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted by Client Services or the Architecture Engineering Review Board (AERB). The use of Windows BitLocker disc encryption that is integrated into the Windows Operating System is not allowed without a waiver from the Client Services organization within VA Enterprise Systems Engineering or the AERB.

[3]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted by the Architecture Engineering Review Board (AERB). No new installs of deprecated versions are allowed. The installation of Windows Vista is currently prohibited. Windows 8 and 8.1 are currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test of the these versions as approved by ESE Client Services or an AERB waiver while under evaluation. The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions is not allowed without a waiver from the AERB. The use of Remote Server Administration Tools for approved Windows Client versions is approved for use following the configuration and deployment standards maintained by the ESE Client Services organization.

[4]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted by the Architecture Engineering Review Board (AERB). The Windows Virtual PC component of Windows 7 is approved for use, but all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use. The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions is not allowed without an AERB waiver. No new installs of Deprecated Versions are allowed. Windows XP becomes TRM unapproved on 4/8/2015 when VA`s extended support contract expires. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in planning and only Enterprise System Engineering (ESE) Client Services may use the technology at this time for planning purposes. Windows 8.1 is currently not approved for production except as part of an official ESE production pilot or production test of this version as approved by ESE Client Services or an AERB waiver while under evaluation. No production deployment dates for Windows 8.1 or 10 have been set as of this writing.

[5]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted by the Architecture Engineering Review Board (AERB). The Windows Virtual PC component of Windows 7 is approved for use, but all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use. The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions can only be used when configured with the required enterprise settings and centralized management per the Windows configuration baseline. See the reference section for more information on Windows baselines. Contact ESE Client Services (Mail: VA IT Engineering CS Desktop Technologies Team) for more information on the use of BitLocker. No new installs of Deprecated Versions are allowed. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in planning and only Enterprise System Engineering (ESE) Client Services may use the technology at this time for planning purposes. Windows 8.1 is currently not approved for production except as part of an official ESE production pilot or production test of this version as approved by ESE Client Services or an AERB waiver while under evaluation. No production deployment dates for Windows 8.1 or 10 have been set as of this writing.

[6]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted by the Architecture Engineering Review Board (AERB). The Windows Virtual PC component of Windows 7 is approved for use, but all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use. The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions can only be used when configured with the required enterprise settings and centralized management per the Windows configuration baseline. See the reference section for more information on Windows baselines. Contact ESE Client Services (Mail: VA IT Engineering CS Desktop Technologies Team) for more information on the use of BitLocker. No new installs of Deprecated Versions are allowed. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in Evaluation and only Enterprise System Engineering (ESE) Client Services may use the technology at this time for evaluation purposes. Windows 8.1 is currently not approved for production except as part of an official ESE production pilot or production test of this version as approved by ESE Client Services or an AERB waiver while under evaluation. No production deployment dates for Windows 8.1 or 10 have been set as of this writing.

[7]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[8]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) images which are defined and maintained by the Endpoint Engineering organization within VA Solution Delivery must be followed and adhered to unless an appropriate waiver is granted by the STAT Board. The Windows Virtual PC component of Windows 7 is approved for use, but all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use. The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions can only be used when configured with the required enterprise settings and centralized management per the Windows configuration baseline. See the reference section for more information on Windows baselines. No new installs of Deprecated Versions are allowed. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in Evaluation and only Solution Delivery may use the technology at this time for evaluation purposes. Windows 8.1 is being removed from the VA environment because Windows 10 will be the next Windows Client standard. No production deployment date for Windows 10 has been set as of this writing.

[9]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) baselines which are defined and maintained by the Endpoint Engineering organization within VA Solution Delivery must be followed and adhered to unless an appropriate waiver is granted by the STAT Board. The Windows Virtual PC component of Windows 7 is not approved for use, and all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use. The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions can only be used when configured with the required enterprise settings and centralized management per the Windows configuration baseline. See the reference section for more information on Windows baselines. No new installs of Deprecated Versions are allowed. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in IOC Testing and there is limited deployment and testing at other non-IOC sites. The production deployment date for Windows 10 is tentatively scheduled to start in October 2018 and last 18 months. The exact schedule is not published.

[10]	This product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) baselines which are defined and maintained by the Endpoint Engineering organization within VA Solution Delivery must be followed and adhered to unless an appropriate waiver is granted by the STAT Board. The Windows Virtual PC component of Windows 7 is not approved for use, and all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use. The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions can only be used when configured with the required enterprise settings and centralized management per the Windows configuration baseline. See the reference section for more information on Windows baselines. No new installs of Deprecated Versions are allowed. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in IOC Testing and there is limited deployment and testing at other non-IOC sites. The production deployment date for Windows 10 is tentatively scheduled to start in October 2018 and last 18 months. The exact schedule is not published.

[11]	The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows images produced by Endpoint Engineering.

[12]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[13]	The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering.

[14]	Hyper-V on Windows 10 is currently unapproved due to VA standardization and the lack of a required VA baseline. DISA states the following: `Microsoft has produced a security guide for Hyper-V. However, due to funding constraints, this is listed on the unfunded STIG development list. When a STIG does not exist, organizations may use a vendor developed guide to use to configure their systems. Organizations using the Hyper-V software need to also review the appropriate Windows Server STIG when setting up their Hyper-V system.` The only security guides listed are for Server 2012 and 2016. No guideline was found for Windows 10 and the vendor was unable to provide one. Due to potential information security risks, Software as a Service/ Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering. VA security configuration baseline standards and deployment standards for Windows Client images, including standards for Active Directory must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information and links to the official standards.

[15]	Users must ensure that Microsoft .NET Framework and Microsoft Internet Explorer are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Hyper-V on Windows 10 is currently unapproved due to VA standardization and the lack of a required VA baseline. DISA states the following: `Microsoft has produced a security guide for Hyper-V. However, due to funding constraints, this is listed on the unfunded STIG development list. When a STIG does not exist, organizations may use a vendor developed guide to use to configure their systems. Organizations using the Hyper-V software need to also review the appropriate Windows Server STIG when setting up their Hyper-V system.` The only security guides listed are for Server 2012 and 2016. No guideline was found for Windows 10 and the vendor was unable to provide one. Due to potential information security risks, Software as a Service/ Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering. VA security configuration baseline standards and deployment standards for Windows Client images, including standards for Active Directory must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information and links to the official standards. The following constraints apply to the Embedded Handheld edition of this technology: Due to the lack of documentation and vendor support, there is no way to determine if Windows Embedded Handheld is FIPS 140-2 certified. Windows Embedded Handheld cannot be used for processing any data containing Personal Health Information (PHI), Personally Identifiable Information (PII), or VA sensitive information. According to the vendor, an Original Equipment Manufacturer (OEM) such as Zebra would be responsible for support after the EOL date. The OEM cannot confirm or demonstrate an acceptable level of support after Windows Embedded Handheld EOL date. Neither the vendor nor the OEM can demonstrate a support model in which the devices would be patched or updated.

[16]	Windows 7 ended traditional support in January 2020. VA has ceased support for imaging new Win 7 PCs and other routine support functions. Because there are a few hundred Win 7 machines that must remain due to legacy application migration delays, VA purchased extended support through 2020 and all Windows machines must be removed from VA as soon as possible. TRM has extended divest status though 2020 while these migrations are finished and it will not be extended further. Users must ensure that Microsoft .NET Framework and Microsoft Internet Explorer are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Hyper-V on Windows 10 is currently unapproved due to VA standardization and the lack of a required VA baseline. DISA states the following: `Microsoft has produced a security guide for Hyper-V. However, due to funding constraints, this is listed on the unfunded STIG development list. When a STIG does not exist, organizations may use a vendor developed guide to use to configure their systems. Organizations using the Hyper-V software need to also review the appropriate Windows Server STIG when setting up their Hyper-V system.` The only security guides listed are for Server 2012 and 2016. No guideline was found for Windows 10 and the vendor was unable to provide one. Due to potential information security risks, Software as a Service/ Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering. VA security configuration baseline standards and deployment standards for Windows Client images, including standards for Active Directory must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information and links to the official standards. The following constraints apply to the Embedded Handheld edition of this technology: Due to the lack of documentation and vendor support, there is no way to determine if Windows Embedded Handheld is FIPS 140-2 certified. Windows Embedded Handheld cannot be used for processing any data containing Personal Health Information (PHI), Personally Identifiable Information (PII), or VA sensitive information. According to the vendor, an Original Equipment Manufacturer (OEM) such as Zebra would be responsible for support after the EOL date. The OEM cannot confirm or demonstrate an acceptable level of support after Windows Embedded Handheld EOL date. Neither the vendor nor the OEM can demonstrate a support model in which the devices would be patched or updated.

[17]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[18]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[19]	Hyper-V on Windows 10 is currently unapproved due to VA standardization and the lack of a required VA baseline. DISA states the following: `Microsoft has produced a security guide for Hyper-V. However, due to funding constraints, this is listed on the unfunded STIG development list. When a STIG does not exist, organizations may use a vendor developed guide to use to configure their systems. Organizations using the Hyper-V software need to also review the appropriate Windows Server STIG when setting up their Hyper-V system.` The only security guides listed are for Server 2012 and 2016. No guideline was found for Windows 10 and the vendor was unable to provide one. Due to potential information security risks, Software as a Service/ Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering. VA security configuration baseline standards and deployment standards for Windows Client images, including standards for Active Directory must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information and links to the official standards. The following constraints apply to the Embedded Handheld edition of this technology: Due to the lack of documentation and vendor support, there is no way to determine if Windows Embedded Handheld is FIPS 140-2 certified. Windows Embedded Handheld cannot be used for processing any data containing Personal Health Information (PHI), Personally Identifiable Information (PII), or VA sensitive information. According to the vendor, an Original Equipment Manufacturer (OEM) such as Zebra would be responsible for support after the EOL date. The OEM cannot confirm or demonstrate an acceptable level of support after Windows Embedded Handheld EOL date. Neither the vendor nor the OEM can demonstrate a support model in which the devices would be patched or updated.

[20]	Hyper-V on Windows 10 is currently unapproved due to VA standardization and the lack of a required VA baseline. DISA states the following: `Microsoft has produced a security guide for Hyper-V. However, due to funding constraints, this is listed on the unfunded STIG development list. When a STIG does not exist, organizations may use a vendor developed guide to use to configure their systems. Organizations using the Hyper-V software need to also review the appropriate Windows Server STIG when setting up their Hyper-V system.` The only security guides listed are for Server 2012 and 2016. No guideline was found for Windows 10 and the vendor was unable to provide one. Due to potential information security risks, Software as a Service/ Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering. VA security configuration baseline standards and deployment standards for Windows Client images, including standards for Active Directory must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information and links to the official standards. The following constraints apply to the Embedded Handheld edition of this technology: Due to the lack of documentation and vendor support, there is no way to determine if Windows Embedded Handheld is FIPS 140-2 certified. Windows Embedded Handheld cannot be used for processing any data containing Personal Health Information (PHI), Personally Identifiable Information (PII), or VA sensitive information. According to the vendor, an Original Equipment Manufacturer (OEM) such as Zebra would be responsible for support after the EOL date. The OEM cannot confirm or demonstrate an acceptable level of support after Windows Embedded Handheld EOL date. Neither the vendor nor the OEM can demonstrate a support model in which the devices would be patched or updated. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status.

[21]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[22]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[23]	Per the Initial Product Review for Hyper-V, users must abide by the following constraints: This technology is currently unapproved due to VA standardization and the lack of a required VA baseline. DISA states the following: “Microsoft has produced a security guide for Hyper-V. However, due to funding constraints, this is listed on the unfunded STIG development list. When a STIG does not exist, organizations may use a vendor developed guide to use to configure their systems. Organizations using the Hyper-V software need to also review the appropriate Windows Server STIG when setting up their Hyper-V system.” The only security guides listed are for Server 2012 and 2016. No guideline was found for Windows 10 and the vendor was unable to provide one. Due to potential information security risks, Software as a Service/ Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC. Per the Initial Product Review for Windows Embedded Handheld, users must abide by the following constraints: Due to the lack of documentation and vendor support, there is no way to determine if Windows Embedded Handheld is FIPS 140-2 certified. Windows Embedded Handheld cannot be used for processing any data containing Personal Health Information (PHI), Personally Identifiable Information (PII), or VA sensitive information. According to the vendor, an Original Equipment Manufacturer (OEM) such as Zebra would be responsible for support after the EOL date. The OEM cannot confirm or demonstrate an acceptable level of support after Windows Embedded Handheld EOL date. Neither the vendor nor the OEM can demonstrate a support model in which the devices would be patched or updated. The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering. VA security configuration baseline standards and deployment standards for Windows Client images, including standards for Active Directory must be followed and adhered to unless an appropriate Plan Of Action and Milestone (POA&M) is granted. See the reference section for more information and links to the official standards. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status.

Note:

At the time of writing, Windows 11 (FU 22H2) is the latest released version but has not been approved for general use at this time. A standard configuration of this technology was developed by the DDE team. The standard version is Windows 10 (FU22H2).

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Windows 11 Release History		This is the site that lists the Windows 11 release history.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Client Hyper-V	Client Hyper-V the same machine virtualization technology that is part of Windows Server. Hyper-V allows users to run more than one 32-bit or 64-bit x86 operating system at the same time on the same Personal Computer (PC), by running them inside a virtual machine. Hyper-V replaces Windows Virtual PC in Windows 7 but does not include Windows XP Mode. Client Hyper-V is supported in Windows 8.1 and later and is approved for use only on approved versions of the Windows Client OS on the Version tab of this entry. Configuration and deployment standards for Windows Client (desktop) images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted.Hyper-V for Windows 10 is NOT approved for use. Please see the IPR on the Reference tab and to see the applied constraints.
Microsoft Defender	Microsoft Defender (formally known as Windows Defender) is a service built into the Windows Operating System. Microsoft Defender is an antivirus and malware detection and prevention service that runs in the background of the system.
Microsoft Edge Update	This technology enables updates for Microsoft Edge. The version of Microsoft Edge Update is controlled by the Windows 10 Baseline.
Microsoft Interactive Training application - Unapproved	Microsoft Interactive Training application is pre-installed in Accessories on Windows XP Operating System. This application is unapproved for use because it operates on unapproved OS (Windows XP).
Remote Server Administration Tools / Windows AdminPack	Remote Server Administration Tools, also known as Windows AdminPack, are installed on the Windows Client and enable Information Technology (IT) administrators to remotely manage roles and features that are installed on computers that are running Windows Server. These utilities are specific to the Windows Client OS version that they are installed on and therefore can only be used with approved versions of Windows Client in this entry. Configuration and deployment standards for Windows Client images and utilities, which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted.
Windows BitLocker	Windows BitLocker disc encryption is integrated into the Windows Operating System. The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions can only be used when configured with the required enterprise settings and centralized management per the Windows configuration baseline. See the reference section for more information on Windows baselines.
Windows Resource Kit	Originally released as a Digital Versatile Disc (DVD) included with the Microsoft Windows Server 2003 Resource Kit set of books, this software contains utilities for configuring and troubleshooting Windows-based servers and clients. The Resource Kit is also available for download on the Microsoft website.
Windows Search	Windows Search is a standard component of Windows versions Vista and newer and is enabled by default. Windows Search replaces Windows Desktop Search (WDS), which was available as an add-in for Windows XP and Windows Server 2003.
Windows Update Health Tools	The Windows Update Health Tools are a set of tools introduced through Windows Update to resolve issues that affect the update process in Windows 10.
Windows Virtual PC	Windows Virtual PC (successor to Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) is a virtualization component for Microsoft Windows that allows another copy of a Windows Operating system to be hosted within the Windows Client. Windows Virtual PC is supported on Windows 7 and is approved for use on Windows 7. Please note that all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use. Configuration and deployment standards for Windows Client (desktop) images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted.


Platforms and Storage Operating Systems	OS - Desktop/Laptop

- The information contained on this page is accurate as of the Decision Date (04/06/2023).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 23.5

General Information

Vendor Release Information

Current Decision Matrix (04/05/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 23.5

General Information

Vendor Release Information

Current Decision Matrix (04/05/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES