LinkBack URL
About LinkBacks
Reply With QuoteHave you looked in the registry if it's trimmed there too or if it's only showing it as that.
100+ Helpful Posts!
50+ Helpful Posts
Our company has a fairly long Acceptable Computer Use Policy, which we have enabled and written in a GPO, which we have linked to a OU, which contains all computer objects. After a change was done within that policy, only half of the string is showing in the ACUP notice window after they do ctrl+alt+del.
We have a mixed mode 2000/2003 domain.
Appreciate any ideas on why this is happening?
100+ Helpful Posts!
50+ Helpful Posts
Have you looked in the registry if it's trimmed there too or if it's only showing it as that.
100+ Helpful Posts!
50+ Helpful Posts
In the reg key HKLM --> Software --> Microsoft --> Windows --> Current Version --> policies --> system --> legalnoticetext - REG_SZ, the string showing is also truncated and not showing the full text we have set in the GPO policy.
100+ Helpful Posts!
50+ Helpful Posts
Depending upon the version of Windows and also depending upon whether MS had changed this in a subsequent Service Pack or Hot Fix, there was a definitely a truncating length for the setting. We ran into it several years ago when some folks handed us a new version of the text to deploy without consulting us for testing to see if it would work. It was way too long. Here's the gist of what we discovered.
================================================== ============
Windows XP Professional added support for configuring logon banners that can exceed 512 characters in length and that can also contain carriage-return line-feed sequences. However, Windows 2000 clients cannot “interpret and display†the message text created by Windows XP Professional computers. You must use a Windows 2000 computer to create a logon message policy that applies to Windows 2000 computers (as well as Windows XP devices). If you inadvertently create a logon message policy using a Windows XP Professional computer, and you discover that it does not display properly on Windows 2000 computers, do the following:
• Undefine the setting.
• Redefine the setting using a Windows 2000 computer.
Simply changing a Windows XP Professional-defined logon message policy using a Windows 2000 computer does not work. The setting must be undefined first.
That said, we rarely use this setting as it messes up all of our multi-reboot device unattended imaging processes for client and server devices (thousands per year). Instead, we continue to use the older keys located in the WinLogon registry entry. This allows our server administrators to build auto-logon weekly maintenance scheduled tasks that temporarily remove the banner (and thus allow multiple reboots as necessary) and then to reestablish the banner when activities are complete. Doing so in GPOs would break those auto-reboot and auto-logon maintenance processes. The same goes for the desktops (but more for initial imaging than anything else).
[code:1]Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Wind ows NT\CurrentVersion\Winlogon]
"LegalNoticeCaption"="Whatever title you want"
"LegalNoticeText"="Whatever message you want."[/code]
100+ Helpful Posts!
50+ Helpful Posts
Thank you for your explanation - now it sounds more clear to me why it happened. However I did manager to re-type a new logon banner by using carriage-return after a certain amount of characters and space. I had to use carriage-return to prevent the text for being truncated after 512 characters.
I like the idea of using a reg key located in WinLogon - I will seak to tht solution, if I run into problems again.
Thank you.
Posting Permissions