STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated 4 hours ago
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to Omnissa Horizon Client Security Technical Implementation Guide

V-287324

CAT II (Medium)

The Horizon Client must not store a log on username.

Rule ID

SV-287324r1289658_rule

STIG

Omnissa Horizon Client Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000366

Discussion

The Horizon Client allows for storing a username and password to facilitate authentication with a connection server. This configuration is not acceptable in the DoW and must not be enabled.

Check Content

Verify the "vdm_client*.admx" templates have been added to the Active Directory Domain.

Open the "Group Policy Management" MMC snap-in, then open the applicable GPO that is applying the Horizon Client settings to the desktop machines.

Navigate to Computer Configuration >> Administrative Templates >> Omnissa Horizon Client Configuration >> Scripting definitions.

If "Logon UserName" is set to "Enabled", this is a finding.

Fix Text

Verify the "vdm_client*.admx" templates have been added to the Active Directory Domain.

Open the "Group Policy Management" MMC snap-in, then open the applicable GPO that is applying the Horizon Client settings to the desktop machines.

Navigate to Computer Configuration >> Administrative Templates >> Omnissa Horizon Client Configuration >> Scripting definitions.

Double-click the "Logon UserName" setting.

Verify "Logon UserName" is set to either "Not Configured" or "Disabled".

Click "OK".