Anavem
EnglishFrancais
Anavem
Languagefr
security settingsComputer ConfigurationNot configured

Logon message banner text

Defines legal notice displayed at logon. Essential for MSP legal compliance and access policies.

10 May 20264 min —
Policy path
Computer Configuration > Administrative Templates > Windows Components > Windows Logon Options
Supported on
Windows 10, Windows 11, Windows Server 2016 and later

Defines legal notice displayed at logon. Essential for MSP legal compliance and access policies. Security baselines recommend setting it to Authorized use only. All activity is monitored..

Description

Logon message banner text is a Windows Group Policy setting located under Computer Configuration > Administrative Templates > Windows Components > Windows Logon Options. It applies to the Computer Configuration branch and is classified as a Warning-level policy in the Windows Logon & Authentication category.

Defines legal notice displayed at logon. Essential for MSP legal compliance and access policies.

Microsoft sets the default value to Not configured while industry security baselines (CIS, NIST, DISA STIG) recommend Authorized use only. All activity is monitored..

Under the hood, this policy is enforced through the Windows registry at HKLM\Software\Policies\Microsoft\Windows\Winlogon using the value name LegalNoticeText. Modifying the value directly through regedit.exe or PowerShell produces the same effect as configuring the GPO, but going through Group Policy is preferred so that the setting is centrally managed and survives reboots, image rebuilds, and policy refresh cycles.

In-depth explanation

This setting has a meaningful impact on the security posture or operational stability of the system. Leaving it at the Microsoft default is acceptable for standalone or low-risk environments, but most security baselines (CIS, NIST, DISA STIG) explicitly call for hardening it before the device is exposed to untrusted users or networks.

The policy is grouped under Windows Logon & Authentication, which means it is typically applied through a domain-wide GPO linked at the OU level. In a multi-tenant MSP context, scope it through WMI filters or security group filtering rather than linking at the domain root, so that you can roll out progressively (pilot OU → wider rings → all production).

The setting takes effect after the next Group Policy refresh (gpupdate /force for immediate testing, or by default within ~90 minutes for workstations and ~5 minutes on domain controllers). For computer-side policies a reboot may be required; for user-side policies, a sign-off/sign-on cycle is enough.

Use cases

  • Apply organization-wide hardening of windows logon & authentication on all domain-joined Windows endpoints.
  • Roll out a CIS Benchmark-aligned baseline targeting 'Logon message banner text' via a dedicated GPO.
  • Reduce attack surface for accounts that handle privileged credentials or sensitive data.
  • Standardize the configuration across multiple customer tenants for an MSP-managed fleet.

Security implications

Leaving this policy at default does not directly grant an attacker access, but it widens the blast radius once initial access is obtained – passwords are easier to guess, lockout doesn't fire, audit trails are incomplete, or lateral movement is quieter. Most regulators and cyber-insurance underwriters now expect this control to be in place at least at the recommended level.

How to configure

  1. Open Group Policy Management Console (gpmc.msc) on a domain controller or a workstation with RSAT installed.
  2. Create or edit a GPO linked to the OU containing the target computer configurations. We recommend a dedicated baseline GPO (e.g. SEC – Windows Logon & Authentication) instead of editing Default Domain Policy.
  3. Navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Logon Options.
  4. Open Logon message banner text and set it to Authorized use only. All activity is monitored..
  5. Click OK and close the editor.
  6. On the target endpoint, run gpupdate /force (or wait for the next refresh cycle), then verify with rsop.msc or gpresult /h report.html.

Direct registry path: HKLM\Software\Policies\Microsoft\Windows\Winlogon\LegalNoticeText. You can apply the same change with PowerShell:

New-Item -Path 'HKLM\Software\Policies\Microsoft\Windows\Winlogon' -Force | Out-Null
Set-ItemProperty -Path 'HKLM\Software\Policies\Microsoft\Windows\Winlogon' -Name 'LegalNoticeText' -Value <value> -Type DWord

Registry mapping

Registry pathHKLM\Software\Policies\Microsoft\Windows\Winlogon
Value nameLegalNoticeText
Value typeREG_SZ
Enabled valueAuthorized use only. All activity is monitored.

Frequently asked questions

What does the Logon message banner text Group Policy do?
Defines legal notice displayed at logon. Essential for MSP legal compliance and access policies.
Where do I find this setting in the GPO editor?
Open <code>gpmc.msc</code>, then navigate to <code>Computer Configuration > Administrative Templates > Windows Components > Windows Logon Options</code> and look for <strong>Logon message banner text</strong>.
What value do security baselines recommend?
<code>Authorized use only. All activity is monitored.</code> – aligned with CIS, NIST, and DISA STIG guidance for current Windows versions.
Can I configure this without a GPO?
Yes, by writing to <code>HKLM\Software\Policies\Microsoft\Windows\Winlogon\LegalNoticeText</code> directly via <code>regedit</code>, PowerShell, or Intune. A GPO is preferred for centrally managed environments because it survives reimaging and is easier to audit.
How quickly does the change take effect?
After the next Group Policy refresh — run <code>gpupdate /force</code> for immediate testing or wait ~90 minutes for workstations / ~5 minutes for domain controllers. Some computer-side policies require a reboot, and some user-side policies require sign-off/sign-on.