|
Your download link is at the very bottom of the page... always. |
Processed through Paypal No account required. Donate Bitcoin to this wallet: 1KkUMXvQ2ko3xcJkzitB7WYgoW6m79WFfm Donate Ethereum to this wallet: 0x40E56922F43637224935CDC35e2c96E0392A8505 Donate Litecoin to this wallet: LLYAFEyqjH69gkyCEpRjXNyedRCWrVChfL |
Files | ||||
File Name | Rating | Downloads | ||
Logon Message Editor v1.1 Logon Message Editor v1.1 This is a simple "one trick pony" utility to allow one to easily change the logon message on a Windows system. The Windows logon message is the optional message displayed to users, for which they need to click "OK", to get to the actual login screen. (Often on corporate computers, it displays a legal notice about authorized use.) If the message is blank, then the logon message screen never appears. On large corporate systems, the IT guys would normally remotely control this message. On individual systems, say where you want to remind the kids at home or employees in a small business, you can also do this by manually editing the System Registry. However, that's not only a pain, but even if you are a System Registry editing pro, simple editing of the registry keys results in a message with no line formatting, and to get the message to be line formatted with carriage returns requires editing the registry entry at the binary level. Since I manage some Windows machines used for computer simulations by graduate students, as well as have a home workstation dedicated for work related use, I wrote a small editor to allow me to change this message, with line formatting, quickly and simple without having to deal with the Group Policy editor nor with manually binary editing the System Registry. That program is Logon Message Editor (LOMessage). This program has been mostly used on 64-bit Windows 7 Pro, Enterprise & Ultimate machines, but should work on any version of Windows XP & higher (XP, Vista, 7, 8 & 10). Windows requires that the user trying to edit this message be an Administrator, and the program does look at the users privilege level and if they did not start this program with ... |
2,855 | Mar 04, 2021 Michael J. Burns |
Showing rows 1 to 1 of 1 | Showing Page 1 of 1 | 1 |
OlderGeeks.com Copyright (c) 2024