Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Windows Server

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:	Windows Server is a proprietary operating system developed by Microsoft for use on server computer systems. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
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 v24.3
Decision Date:	03/18/2024 at 23:46:36 UTC
Aliases:	Windows Server 2025, Windows Server 2022, Windows Server 2019; Windows Server 2016; Windows Server 2012; Windows Server 2008; Windows Server 2003; MS Windows Server; Microsoft Edge
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
2000 (all versions)	03/31/2000		07/13/2010
2003 SP2	06/19/2003		07/14/2015
2003 R2 SP2	03/13/2007		07/14/2015
2008 SP2	05/06/2008	01/13/2015	01/14/2020
2008 R2 SP1	02/22/2011	01/13/2015	01/14/2020
2012	10/30/2012	10/09/2018	10/10/2023
2012 R2 (KB2919355)	10/30/2013	10/09/2018	10/10/2023
2016 (v10)	10/15/2016	01/11/2022	01/11/2027
2019	11/13/2018	01/09/2024	01/09/2029
2022	10/01/2022
2025	01/26/2024

Current Decision Matrix (03/14/2024)

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

CY2027

CY2028

CY2029

Future>

Release

2000 (all versions)

Unapproved

2003 SP2

Unapproved

2003 R2 SP2

Unapproved

2008 SP2

Unapproved

2008 R2 SP1

Unapproved

2012

Unapproved

2012 R2 (KB2919355)

Unapproved

2016 (v10)

Unapproved

2019

Divest
[23, 32, 33, 34, 35, 36]

2022

Approved w/Constraints
[23, 32, 33, 34, 35, 36]

2025

Approved w/Constraints
[1, 23, 32, 33, 34, 35, 36]

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 server images, which are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted. The use of Windows BitLocker disc encryption that is integrated into the Windows Operating System is not allowed without a waiver from the Core Systems Engineering and/or Client Services organizations within VA Enterprise Systems Engineering.

[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 server images which are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted by the AERB. No new installs of Deprecated Versions are allowed without a waiver. The use of Windows BitLocker disc encryption that is integrated into the Windows Operating System is not allowed without a waiver. The Windows Defender component of the optional Desktop Experience package is not allowed to be used without a waiver. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. The Hyper-V Role may only be used on approved versions of Windows Server identified on the version tab of this entry, versions 2008 R2 and later, and following Hyper-V Role version and configuration standards set by ESE Core Systems Engineering Services for Hyper-V Roles.

[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 server images which are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted by the AERB. No new installs of Deprecated Versions are allowed. Windows Server 2014 (v10) Preview is in planning and only Enterprise System Engineering (ESE) Core Engineering may use the technology at this time for planning purposes. No production deployment date for Windows 2014 (v10) has been set as of this writing. The use of Windows BitLocker disc encryption that is integrated into the Windows Operating System is not allowed without a waiver. The Windows Defender component of the optional Desktop Experience package is not allowed to be used without a waiver. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. The Hyper-V Role may only be used on approved versions of Windows Server identified on the version tab of this entry, versions 2008 R2 and later, and following Hyper-V Role version and configuration standards set by ESE Core Systems Engineering Services for Hyper-V Roles. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server.

[5]	Configuration and deployment standards for Windows Server images, including standards for Hyper-V Roles, which are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx No new installs of Deprecated Versions are allowed. Unapproved versions or components can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.) Due to the critical nature of JASBUG, Windows Server 2003 is TRM unapproved and should only be used when the security risks are outweighed by the benefits as reviewed and approved by the AERB waiver process. The use of Windows BitLocker disc encryption that is integrated into the Windows Operating System is unapproved and should only be used when standard VA encryption technology cannot be used and is reviewed and approved by the AERB waiver process. The Windows Defender component of the optional Desktop Experience package is unapproved and should only be used when standard VA security technology cannot be used and is reviewed and approved by the AERB waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server.

[6]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[7]	Configuration and deployment standards for Windows Server images including standards for Active Directory and Hyper-V Roles which are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. No new installs of Deprecated Versions are allowed. Unapproved versions or components can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.) Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) should migrate to Windows 2008 R2 or 2012 R2. Due to the critical nature of JASBUG, Windows Server 2003 is TRM unapproved and should only be used when the security risks are outweighed by the benefits as reviewed and approved by the AERB waiver process. It is recommended that the AERB require all waivered instances of Windows 2003 Server to install Internet Explorer (IE) Version 8 which is the latest supported version of IE for this product. The use of Windows BitLocker disc encryption that is integrated into the Windows Operating System is unapproved and should only be used when standard VA encryption technology cannot be used and is reviewed and approved by the AERB waiver process. The Windows Defender component of the optional Desktop Experience package is unapproved and should only be used when standard VA security technology cannot be used and is reviewed and approved by the AERB waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server.

[8]	Configuration and deployment standards for Windows Server images including standards for Active Directory and Hyper-V Roles which are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. No new installs of Deprecated Versions are allowed. Unapproved versions or components can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.) Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) should migrate to Windows 2008 R2 or 2012 R2. Due to the critical nature of JASBUG, Windows Server 2003 is TRM unapproved and should only be used when the security risks are outweighed by the benefits as reviewed and approved by the AERB waiver process. It is recommended that the AERB require all waivered instances of Windows 2003 Server to install Internet Explorer (IE) Version 8 which is the latest supported version of IE for this product. The use of Windows BitLocker disc encryption that is integrated into the Windows Operating System is unapproved and should only be used when standard VA encryption technology cannot be used and is reviewed and approved by the AERB waiver process. The Windows Defender component of the optional Desktop Experience package is unapproved and should only be used when standard VA security technology cannot be used and is reviewed and approved by the AERB waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and should not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server.

[9]	Configuration and deployment standards for Windows Server images, including standards for Active Directory and Hyper-V Roles which are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE), must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. No new installs of Deprecated Versions are allowed. Unapproved versions or components can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.) Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) must migrate to Windows 2008 R2 or 2012 R2. Due to the critical nature of JASBUG, Windows Server 2003 is TRM unapproved and must only be used when the security risks are outweighed by the benefits as reviewed and approved by the AERB waiver process. It is recommended that the AERB require all waivered instances of Windows 2003 Server to install Internet Explorer (IE) Version 8 which is the latest supported version of IE for this product. The use of Windows BitLocker disc encryption that is integrated into the Windows Operating System is unapproved and must only be used when standard VA encryption technology cannot be used and is reviewed and approved by the AERB waiver process. The Windows Defender component of the optional Desktop Experience package is unapproved and must only be used when standard VA security technology cannot be used and is reviewed and approved by the AERB waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and must not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server.

[10]	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.

[11]	Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[12]	Configuration and deployment standards for Windows Server images, including standards for Active Directory and Hyper-V Roles which are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE), must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. No new installs of Deprecated Versions are allowed. Unapproved versions or components can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.) Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) must migrate to Windows 2008 R2 or 2012 R2. Due to the critical nature of JASBUG, Windows Server 2003 is TRM unapproved and must only be used when the security risks are outweighed by the benefits as reviewed and approved by the AERB waiver process. It is recommended that the AERB require all waivered instances of Windows 2003 Server to install Internet Explorer (IE) Version 8 which is the latest supported version of IE for this product. The use of Windows BitLocker disc encryption that is integrated into the Windows Operating System is unapproved and must only be used when standard VA encryption technology cannot be used and is reviewed and approved by the AERB waiver process. The Windows Defender component of the optional Desktop Experience package is unapproved and must only be used when standard VA security technology cannot be used and is reviewed and approved by the AERB waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and must not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server.

[13]	VA security configuration baseline standards and deployment standards for Windows Server images, including standards for Active Directory and Hyper-V Roles, 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 versions/editions of Windows Server are NOT approved for VA use: - Semi-annual Releases (i.e. Windows Server version 1709 or vNext) - Non-Enterprise versions i.e. Small Business Edition, Essentials and Home Server - OEM versions, including Storage Server The VA will use Long Term Service Branch (LTSB) releases only for Windows Server to allow security policy compliance. Windows Server 2019 is in planning and only Solution Delivery Platform Engineering may use or authorize the technology for planning and pilot evaluation purposes until the VA baseline for Server 2019 is published. No production deployment date for Windows 2019 has been set as of this writing. No new installs of Deprecated Versions are allowed. Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) must migrate to a supported version. Due to the critical nature of JASBUG, Windows Server 2003 is TRM unapproved and must only be used when the security risks are outweighed by the benefits as reviewed and approved by the STAT waiver process. It is recommended that the STAT Working group require all waivered instances of Windows 2003 Server to install Internet Explorer (IE) Version 8 which is the latest supported version of IE for this product. The use of Windows BitLocker disk encryption integrated into the Windows Operating System may be used for full volume encryption provided that the following conditions are met: 1) A TPM chip is present on the machine (either physical or virtual) and used to store the disk encryption certificate(s) and; 2) A robust solution is employed to ensure that the BitLocker recovery key is available to the approved individuals by following an approved process. The Windows Defender component of the optional Desktop Experience package is unapproved and must only be used when standard VA security technology cannot be used and is reviewed and approved by the STAT waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and must not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server.

[14]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[15]	VA security configuration baseline standards and deployment standards for Windows Server images, including standards for Active Directory and Hyper-V Roles, 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 versions/editions of Windows Server are NOT approved for VA use: - Semi-annual Releases (i.e. Windows Server version 1709 or vNext) - Non-Enterprise versions i.e. Small Business Edition, Essentials and Home Server - OEM versions, including Storage Server The VA will use Long Term Service Branch (LTSB) releases only for Windows Server to allow security policy compliance. Windows Server 2019 is in planning and only Solution Delivery Platform Engineering may use or authorize the technology for planning and pilot evaluation purposes until the VA baseline for Server 2019 is published. No production deployment date for Windows 2019 has been set as of this writing. No new installs of Deprecated Versions are allowed. Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) must migrate to a supported version. The use of Windows BitLocker disk encryption integrated into the Windows Operating System may be used for full volume encryption provided that the following conditions are met: 1) A TPM chip is present on the machine (either physical or virtual) and used to store the disk encryption certificate(s) and; 2) A robust solution is employed to ensure that the BitLocker recovery key is available to the approved individuals by following an approved process. The Windows Defender component of the optional Desktop Experience package is unapproved and must only be used when standard VA security technology cannot be used and is reviewed and approved by the STAT waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and must not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server.

[16]	VA security configuration baseline standards and deployment standards for Windows Server images, including standards for Active Directory and Hyper-V Roles, 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 versions/editions of Windows Server are NOT approved for VA use: - Semi-annual Releases (i.e. Windows Server version 1709 or vNext) - Non-Enterprise versions i.e. Small Business Edition, Essentials and Home Server - OEM versions, including Storage Server The VA will use Long Term Service Branch (LTSB) releases only for Windows Server to allow security policy compliance. Windows Server 2019 is in planning and only Solution Delivery Platform Engineering may use or authorize the technology for planning and pilot evaluation purposes until the VA baseline for Server 2019 is published. No production deployment date for Windows 2019 has been set as of this writing. No new installs of Deprecated Versions are allowed. Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) must migrate to a supported version. The use of Windows BitLocker disk encryption integrated into the Windows Operating System may be used for full volume encryption provided that the following conditions are met: 1) A TPM chip is present on the machine (either physical or virtual) and used to store the disk encryption certificate(s) and; 2) A robust solution is employed to ensure that the BitLocker recovery key is available to the approved individuals by following an approved process. The Windows Defender component of the optional Desktop Experience package is unapproved and must only be used when standard VA security technology cannot be used and is reviewed and approved by the STAT waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and must not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server.

[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]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[19]	Users must ensure that Microsoft Internet Information Services (IIS) and Microsoft Internet Explorer are implemented with VA-approved baselines. VA security configuration baseline standards and deployment standards for Windows Server images, including standards for Active Directory and Hyper-V Roles, 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 versions/editions of Windows Server are NOT approved for VA use: - Semi-annual Releases (i.e. Windows Server version 1709 or vNext) - Non-Enterprise versions i.e. Small Business Edition, Essentials and Home Server - OEM versions, including Storage Server The VA will use Long Term Service Branch (LTSB) releases only for Windows Server to allow security policy compliance No new initial project installs of Deprecated Versions are allowed (existing projects may expand their existing server footprint). Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) must migrate to a supported version. The use of Windows BitLocker disk encryption integrated into the Windows Operating System may be used for full volume encryption provided that the following conditions are met: 1) A TPM chip is present on the machine (either physical or virtual) and used to store the disk encryption certificate(s) and; 2) A robust solution is employed to ensure that the BitLocker recovery key is available to the approved individuals by following an approved process. The Windows Defender component of the optional Desktop Experience package is unapproved and must only be used when standard VA security technology cannot be used and is reviewed and approved by the STAT waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and must not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server. Using the below link, please reference the VA Cyber Security Operations Center (CSOC) Bulletin addressing “VA CSOC SAR S-20-054 Microsoft Addresses `Wormable` RCE Vulnerability in Windows DNS Server” which was published on July 15, 2020. https://vaww.vashare.oit.va.gov/sites/ois/KnowledgeService/TAAP/Pages/Situational-Awareness-Reports.aspx

[20]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[22]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[23]	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.

[24]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place.

[25]	Users must ensure that Microsoft Internet Information Services (IIS) and Microsoft Internet Explorer are implemented with VA-approved baselines. Users must ensure that Microsoft Windows Domain is implemented with VA-approved baselines (refer to the ‘Reference’ tab). VA security configuration baseline standards and deployment standards for Windows Server images, including standards for Active Directory and Hyper-V Roles, 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 versions/editions of Windows Server are NOT approved for VA use: - Semi-annual Releases (i.e. Windows Server version 1709 or vNext) - Non-Enterprise versions i.e. Small Business Edition, Essentials and Home Server - OEM versions, including Storage Server The VA will use Long Term Service Branch (LTSB) releases only for Windows Server to allow security policy compliance No new initial project installs of Deprecated Versions are allowed (existing projects may expand their existing server footprint). Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) must migrate to a supported version. The use of Windows BitLocker disk encryption integrated into the Windows Operating System may be used for full volume encryption provided that the following conditions are met: 1) A TPM chip is present on the machine (either physical or virtual) and used to store the disk encryption certificate(s) and; 2) A robust solution is employed to ensure that the BitLocker recovery key is available to the approved individuals by following an approved process. The Windows Defender component of the optional Desktop Experience package is unapproved and must only be used when standard VA security technology cannot be used and is reviewed and approved by the STAT waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and must not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server. Using the below link, please reference the VA Cyber Security Operations Center (CSOC) Bulletin addressing “VA CSOC SAR S-20-054 Microsoft Addresses `Wormable` RCE Vulnerability in Windows DNS Server” which was published on July 15, 2020. https://vaww.vashare.oit.va.gov/sites/ois/KnowledgeService/TAAP/Pages/Situational-Awareness-Reports.aspx At the time of this writing, Version 2022 is available for Planning & Evaluation purposes and only Solution Delivery Platform Engineering may use or authorize this technology for Pilot Evaluation purposes until the VA Baseline for Server 2022 is published.

[26]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[27]	Users must ensure that Microsoft Internet Information Services (IIS) and Microsoft Internet Explorer are implemented with VA-approved baselines. Users must ensure that Microsoft Windows Domain is implemented with VA-approved baselines (refer to the ‘Reference’ tab). VA security configuration baseline standards and deployment standards for Windows Server images, including standards for Active Directory and Hyper-V Roles, 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 versions/editions of Windows Server are NOT approved for VA use: - Semi-annual Releases (i.e. Windows Server version 1709 or vNext) - Non-Enterprise versions i.e. Small Business Edition, Essentials and Home Server - OEM versions, including Storage Server The VA will use Long Term Service Branch (LTSB) releases only for Windows Server to allow security policy compliance No new initial project installs of Deprecated Versions are allowed (existing projects may expand their existing server footprint). Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) must migrate to a supported version. The use of Windows BitLocker disk encryption integrated into the Windows Operating System may be used for full volume encryption provided that the following conditions are met: 1) A TPM chip is present on the machine (either physical or virtual) and used to store the disk encryption certificate(s) and; 2) A robust solution is employed to ensure that the BitLocker recovery key is available to the approved individuals by following an approved process. The Windows Defender component of the optional Desktop Experience package is unapproved and must only be used when standard VA security technology cannot be used and is reviewed and approved by the STAT waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and must not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server. Using the below link, please reference the VA Cyber Security Operations Center (CSOC) Bulletin addressing “VA CSOC SAR S-20-054 Microsoft Addresses `Wormable` RCE Vulnerability in Windows DNS Server” which was published on July 15, 2020. https://vaww.vashare.oit.va.gov/sites/ois/KnowledgeService/TAAP/Pages/Situational-Awareness-Reports.aspx At the time of this writing, Version 2022 is available for Planning & Evaluation purposes and only Solution Delivery Platform Engineering may use or authorize this technology for Pilot Evaluation purposes until the VA Baseline for Server 2022 is published. Versions 2008 and 2008 R2 have been reverted to unapproved status until Jan 13, 2023 to allow for waivered use by business critical applications. Use of these versions of Windows during this period must have current POAM(s) for remediation by Jan 13, 2023 when all support for these versions ends and these versions return to TRM prohibited status.

[28]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[29]	Users must ensure that Microsoft Internet Information Services (IIS) is implemented with VA-approved baselines. Users must ensure that Microsoft Windows Domain is implemented with VA-approved baselines (refer to the ‘Reference’ tab). VA security configuration baseline standards and deployment standards for Windows Server images, including standards for Active Directory and Hyper-V Roles, 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 versions/editions of Windows Server are NOT approved for VA use: - Semi-annual Releases (i.e. Windows Server version 1709 or vNext) - Non-Enterprise versions i.e. Small Business Edition, Essentials and Home Server - OEM versions, including Storage Server The VA will use Long Term Service Branch (LTSB) releases only for Windows Server to allow security policy compliance No new initial project installs of Deprecated Versions are allowed (existing projects may expand their existing server footprint). Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) must migrate to a supported version. The use of Windows BitLocker disk encryption integrated into the Windows Operating System may be used for full volume encryption provided that the following conditions are met: 1) A TPM chip is present on the machine (either physical or virtual) and used to store the disk encryption certificate(s) and; 2) A robust solution is employed to ensure that the BitLocker recovery key is available to the approved individuals by following an approved process. The Windows Defender component of the optional Desktop Experience package is unapproved and must only be used when standard VA security technology cannot be used and is reviewed and approved by the STAT waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and must not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server. Using the below link, please reference the VA Cyber Security Operations Center (CSOC) Bulletin addressing “VA CSOC SAR S-20-054 Microsoft Addresses `Wormable` RCE Vulnerability in Windows DNS Server” which was published on July 15, 2020. https://vaww.vashare.oit.va.gov/sites/ois/KnowledgeService/TAAP/Pages/Situational-Awareness-Reports.aspx At the time of this writing, Version 2022 is available for Planning & Evaluation purposes and only Solution Delivery Platform Engineering may use or authorize this technology for Pilot Evaluation purposes until the VA Baseline for Server 2022 is published. Versions 2008 and 2008 R2 have been reverted to unapproved status until Jan 13, 2023 to allow for waivered use by business critical applications. Use of these versions of Windows during this period must have current POAM(s) for remediation by Jan 13, 2023 when all support for these versions ends and these versions return to TRM prohibited status.

[30]	Users must ensure that Microsoft Internet Information Services (IIS) is implemented with VA-approved baselines. Users must ensure that Microsoft Windows Domain is implemented with VA-approved baselines (refer to the ‘Reference’ tab). VA security configuration baseline standards and deployment standards for Windows Server images, including standards for Active Directory and Hyper-V Roles, 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 versions/editions of Windows Server are NOT approved for VA use: - Semi-annual Releases (i.e. Windows Server version 1709 or vNext) - Non-Enterprise versions i.e. Small Business Edition, Essentials and Home Server - OEM versions, including Storage Server The VA will use Long Term Service Branch (LTSB) releases only for Windows Server to allow security policy compliance No new initial project installs of Deprecated Versions are allowed (existing projects may expand their existing server footprint). Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) must migrate to a supported version. The use of Windows BitLocker disk encryption integrated into the Windows Operating System may be used for full volume encryption provided that the following conditions are met: 1) A TPM chip is present on the machine (either physical or virtual) and used to store the disk encryption certificate(s) and; 2) A robust solution is employed to ensure that the BitLocker recovery key is available to the approved individuals by following an approved process. The Windows Defender component of the optional Desktop Experience package is unapproved and must only be used when standard VA security technology cannot be used and is reviewed and approved by the STAT waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and must not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server. Using the below link, please reference the VA Cyber Security Operations Center (CSOC) Bulletin addressing “VA CSOC SAR S-20-054 Microsoft Addresses `Wormable` RCE Vulnerability in Windows DNS Server” which was published on July 15, 2020. https://vaww.vashare.oit.va.gov/sites/ois/KnowledgeService/TAAP/Pages/Situational-Awareness-Reports.aspx At the time of this writing, Version 2022 is available for Planning & Evaluation purposes and only Solution Delivery Platform Engineering may use or authorize this technology for Pilot Evaluation purposes until the VA Baseline for Server 2022 is published.

[31]	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.

[32]	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.

[33]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. 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 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513. The local ISSO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place.

[34]	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 both VA Handbook 6500 and VA Directive 6500.

[35]	Users must ensure that Microsoft Internet Information Services (IIS) is implemented with VA-approved baselines. Users must ensure that Microsoft Windows Domain is implemented with VA-approved baselines (refer to the ‘Reference’ tab). VA security configuration baseline standards and deployment standards for Windows Server images, including standards for Active Directory and Hyper-V Roles, 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 versions/editions of Windows Server are NOT approved for VA use: - Semi-annual Releases (i.e. Windows Server version 1709 or vNext) - Non-Enterprise versions i.e. Small Business Edition, Essentials and Home Server - OEM versions, including Storage Server The VA will use Long Term Service Branch (LTSB) releases only for Windows Server to allow security policy compliance No new initial project installs of Deprecated Versions are allowed (existing projects may expand their existing server footprint). Windows Server 2008 SP2 is deprecated after 6/1/2015 and is only approved for use on servers that support SCCM 2007. Non-SCCM servers running Windows 2008 (non-R2) must migrate to a supported version. The use of Windows BitLocker disk encryption integrated into the Windows Operating System may be used for full volume encryption provided that the following conditions are met: 1) A TPM chip is present on the machine (either physical or virtual) and used to store the disk encryption certificate(s) and; 2) A robust solution is employed to ensure that the BitLocker recovery key is available to the approved individuals by following an approved process. The Windows Defender component of the optional Desktop Experience package is unapproved and must only be used when standard VA security technology cannot be used and is reviewed and approved by the STAT waiver process. After the install of the optional Desktop Experience package, the Windows Defender Service must be disabled and deleted using the `SC Delete` command to prevent it from being enabled. Windows Internal Database (WID) is authorized only for use by Windows Server and must not be used by any end-user applications. See the `Component` section of this TRM entry for more details. The Microsoft Virtual Server component which was replaced by the Hyper-V Role is prohibited from use and users must use the Hyper-V Role on approved versions of Windows Server. Using the below link, please reference the VA Cyber Security Operations Center (CSOC) Bulletin addressing “VA CSOC SAR S-20-054 Microsoft Addresses `Wormable` RCE Vulnerability in Windows DNS Server” which was published on July 15, 2020. https://vaww.vashare.oit.va.gov/sites/ois/KnowledgeService/TAAP/Pages/Situational-Awareness-Reports.aspx At the time of this writing, Version 2025 is available for Planning & Evaluation purposes and only Solution Delivery Platform Engineering may use or authorize this technology for Pilot Evaluation purposes until the VA Baseline for Server 2025 is published.

[36]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

Note:

At the time of writing, version 2025 is the most current version, released 10/01/2022.

A baseline configuration of this technology was developed by the BCM team. At the time of writing, the baseline version is 2022.

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
Active Directory	Active Directory (AD) is an implementation of Lightweight Directory Access Protocol (LDAP) directory services by Microsoft that is built on and released with Windows server for use primarily in Windows environments. The main purpose of Active Directory is to provide central authentication and authorization services for Windows based computers. Active Directory also allows administrators to assign policies, deploy software, and apply critical updates to an entire organization. Active Directory stores information and settings relating to an organization in a central, organized, accessible database. Active Directory networks can vary from a small installation with a few hundred objects, to a large installation with millions of objects. Configuration and deployment standards for Windows Server and AD Domain Software configuration levels and Forest Functional configuration levels of implementation for AD are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed for any implementation of Active Directory. Please see the reference section of this entry for more information on the Windows Server configuration baseline and the Active Directory configuration baseline.
Active Directory Lightweight Directory Service (AD LDS)	Active Directory Lightweight Directory Service (AD LDS), formerly known as Active Directory Application Mode (ADAM), is a light-weight implementation of Active Directory. AD LDS is capable of running as a service on computers running Microsoft Windows Server. AD LDS shares the code base with Active Directory and provides the same functionality as Active Directory, including an identical API, but does not require the creation of domains or domain controllers. Configuration and deployment standards for Windows Server and AD Software are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed for any implementation of Active Directory. Please see the reference section of this entry for more information on the Windows Server configuration baseline and the Active Directory configuration baseline.
Active Directory Rights Management Service (AD RMS)	Microsoft Active Directory Rights Management Services (AD RMS) is an information protection technology that works with AD RMS enabled applications to help safeguard digital information from unauthorized use. Content owners can define who can open, modify, print, forward, or take other actions with the information. AD RMS consists of both a server and a client component that are included in the windows server and client operating systems.
BitLocker	BitLocker disk encryption built into the Windows Server operating system is approved for use following the specific constraints listed in the constraints section of this entry.
Desktop Experience	The Desktop Experience feature enables you to install a variety of Windows 7 features on your server running Windows Server 2008. NOTE: The Windows Defender component of Desktop Experience is not approved for use. After the install of Desktop Experience, the Windows Defender Service must be disabled and deleted using the "SC Delete" command to prevent it from being enabled.
Hyper-V Role (Integrated Hyper-V Server)	Hyper-V in Windows Server enables you to create a virtualized server computing environment. Each virtual machine is a virtualized computer system that operates in an isolated execution environment allowing users to run multiple operating systems simultaneously on one physical computer. NOTE: The Hyper-V Role may only be used on approved versions of Windows Server identified on the version tab of this entry and following Hyper-V Role version and configuration standards set by ESE Core Systems Engineering Services for Hyper-V Roles.
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. On Windows Server, this service can be applied to Microsoft`s Office365 environment through the following services: Microsoft Defender for Identity (MDI) monitors the traffic on the domain controllers. Microsoft Defender for Endpoint (MDE) delivers preventative protection, post-breach detection, automated investigation, and response.
Microsoft Edge	Microsoft Edge is a web browser developed by Microsoft. The version of Microsoft Edge is controlled by the Windows 10 Baseline.
Remote Desktop Server (RDS)	A Remote Desktop Session (RDS) host which allows for building virtualized solutions including delivering individual virtualized applications, secure mobile and remote desktop access, and providing end users the ability to run their applications and desktops from the cloud.
Remote Desktop Server (RDS) Client Access License (CAL)	A client access license (CAL) is needed for each user and device that connects to a Remote Desktop Session (RDS) host. The CAL used by users or devices must correspond to the version of Windows Server that the user or device is connecting to.
Windows Internal Database (WID)	Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server 2008 (SQL 2005), Windows Server 2008 R2 (SQL 2005) and Windows Server 2012 (SQL 2012). Windows Internal Database is not available as a standalone product for use by end-user applications; Microsoft provides SQL Server Express and Microsoft SQL Server for this purpose. Additionally, it is designed to only be accessible to Windows Services running on the same machine. Therefore, Windows Internal Database (WID) is authorized only for use by Windows Server and should not be used by any end-user applications.
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.


Platforms and Storage Operating Systems	OS - Server

- The information contained on this page is accurate as of the Decision Date (03/18/2024 at 23:46:36 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/14/2024)

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 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/14/2024)

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