Local Users and Groups (lsurmgr.msc) for Windows Home edition:
https://github.com/akruhler/AccountManagement/releases
I adore it.
Home edition still drive me nuts. But a little less so
with this utility.
T <T@invalid.invalid> wrote:
Local Users and Groups (lsurmgr.msc) for Windows Home edition:
https://github.com/akruhler/AccountManagement/releases
I adore it.
Home edition still drive me nuts. But a little less so
with this utility.
Correction: lusrmgr.msc, not lsurmgr.msc. "usr", not "sru".
Local USeR ManaGeR
^ ^^ ^ ^ ^ ^
All policies are registry entries. Microsoft publishes an Excel
spreadsheet listing all the policies, and where are the regkeys for
them. That's why you see many articles on policies giving you a regkey
and data item's name and its value.
https://www.microsoft.com/en-us/download/details.aspx?id=104678
By the way, the Github project says it uses WMI (instead of DirectoryServices). WMI got deprecated in 2016.
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/wmi-command-line-wmic-utility-deprecation-next-steps/ba-p/4039242
Starting January 29, 2024, you'll find Windows Management
Instrumentation Command line (WMIC) feature "disabled by default" on the insider build of Windows 11.
PowerShell CIM (Common Information Model) cmdlets replaced WMIC (WMI command-line interface). To see a list of the cmdlets, run "Get-Command -Module CimCmdlets" inside PowerShell. No idea why Microsoft thinks
working with cmdlets inside PowerShell is easier than using WMIC
commands.
https://learn.microsoft.com/en-us/powershell/scripting/learn/ps101/07-working-with-wmi?view=powershell-7.4
Not sure to the replacement lusrmgr.msc Control Panel applet (using the Microsoft Management Console snap-in) you found will work in the future. Looks like the Github project was started 4 years with the last update
was back in Feb 2021. You might want to contact the author to ask the survival of his lusrmgr replacement. So far, the deprecation is only on
the CLI (Command-Line Interface) client to WMI (aka WMIC). No idea what Microsoft plans for WMI itself.
Local Users and Groups (lsurmgr.msc) for Windows Home edition:
https://github.com/akruhler/AccountManagement/releases
I adore it.
On Fri, 19 Apr 2024 20:27:07 -0700, T <T@invalid.invalid> wrote:
Local Users and Groups (lsurmgr.msc) for Windows Home edition:
https://github.com/akruhler/AccountManagement/releases
I adore it.
Can you tell us why? What do you like so much about it?
Ken Blake wrote on 4/20/24 7:51 AM:
On Fri, 19 Apr 2024 20:27:07 -0700, T <T@invalid.invalid> wrote:
Local Users and Groups (lsurmgr.msc) for Windows Home edition:
https://github.com/akruhler/AccountManagement/releases
I adore it.
Can you tell us why? What do you like so much about it?
Hi, Ken.
Not 'T' but a few reasons.
Windows Home does not include the GPO for Local User and Group Management(LUSGM) policy settings/changes.
 - the github program, if understanding correctly, provides a tool that Home does not have for managing Local and Group policies, in addition it
can also be used on Windows Pro as an alternative to Pro's included and built-in GPO LUSGM.
Additionally Microsoft periodically release ADX templates that
update(add new, remove old, modify) existing policies.
 - in the business(Enterprise arena) its quite common for Admins to use
and keep their ADX supported policies updated.
Thus even in no-Enterprise environment, individuals or businesses that support non-Server admin managed devices(Windows Home) can use the
github tool for managing policies on those devices, and a bit easier
than single or multiple created entries in the registry.
T <T@invalid.invalid> wrote:
I read somewhere that I can not remember that Power Shell
has not been all that popular for administrative tasks.
I've not bothered to learn it. I get online snippets of code. My
public library has some PowerShell books, so I'll eventually get those.
The WMIC tool (command line interface to WMI) got deprecated.
PowerShell still uses WMI. Programs can still use the WMI API, too. I
don't what your lusrmgr alternative uses: calls to CLI or API.
The first thing that drives me nuts about Power Shell is
that I have to highlight the output with my mouse to be
able top actually read they dim obscure red outputs
on black backgrounds. Does not make a good impression.
There are a lot of things I just do not like, especially
in Windows 11, that I just do not use. In 11, I typically
will just <win><R> and write in what I want rather than
suffering the Chromebook interface. I have a cheat sheet
of msc and cpl commands I just copy and paste.
I read somewhere that I can not remember that Power Shell
has not been all that popular for administrative tasks.
Just like with the cmd shell, click on the left-mode icon in the
titlebar of the shell window. That's the Control menu. Select
Properties. You can change fonts, colors, buffer size, window size,
etc. Both shells have a ton of customization settings.
In Windows 10, I created a shortcut in the Start Menu tiles to a folder
that has all the old Control Panel shortcuts. For example, one of the folder's shortcuts is to sysdm.cpl (System Properties). I created a
folder (Control Panel shortcuts) in which I created shortcuts to the CP tools, and then pinned the folder to my Start Menu's tile pane. Did the
same for SysInternals and Nirsoft tools: create a folder, put shortcuts
in it, and Pin To Start.
Alternatively, and still available in Win10's taskbar, you can add
toolbars (folders), and within each you can add shortcuts. When the QuickLaunch toolbar disappears, I created a new folder called
QuickLaunch that was added as a toolbar in the taskbar, and which had
the often-used shortcuts. I have toolbars for: QuickLaunch, Web,
E-mail, Entertain, Security, Veracrypt, and the included Address Bar (so
I can enter URLs or special strings, like shell:appsfolder) without
having to open File Explorer to use its address bar. I have 6 toolbars
in my Taskbar, all on the bottom row of a 2-row height Taskbar (which
also makes the Clock and Systray larger).
VanguardLH wrote:
Just like with the cmd shell, click on the left-mode icon in the
titlebar of the shell window. That's the Control menu. Select
Properties. You can change fonts, colors, buffer size, window size,
etc. Both shells have a ton of customization settings.
Did that, didn't work, got pissed, exited. Now
I just go into cmd shell and enter "PowerShell.exe ..."
so I can see it.
T <T@invalid.invalid> wrote:
VanguardLH wrote:
Just like with the cmd shell, click on the left-mode icon in the
titlebar of the shell window. That's the Control menu. Select
Properties. You can change fonts, colors, buffer size, window size,
etc. Both shells have a ton of customization settings.
Did that, didn't work, got pissed, exited. Now
I just go into cmd shell and enter "PowerShell.exe ..."
so I can see it.
I loaded PS from the Start Menu instead of from an existing command
shell. I changed the background color from blue to red. Nothing
changed in the current console window; however, once I exited that
shell, and reloaded it, the background color changed. The changes
appear to pend until the next instance of the PS shell.
The first thing that drives me nuts about Power Shell is
that I have to highlight the output with my mouse to be
able top actually read they dim obscure red outputs
on black backgrounds.
On 4/20/24 07:51, Ken Blake wrote:
On Fri, 19 Apr 2024 20:27:07 -0700, T <T@invalid.invalid> wrote:
Local Users and Groups (lsurmgr.msc) for Windows Home edition:
https://github.com/akruhler/AccountManagement/releases
I adore it.
Can you tell us why? What do you like so much about it?
It is far easier to create and configure users and groups
than the awkward tools that Home users are forced to use.
My customer base is small business and home users.
Now-a-days, I never come across a Windows Server.
Windows Server are of no use to small business and
home users. Even the software that runs on my customer
base that act as a server will run on a workstations
just fine and a TON more reliably.
So the tool is great for setting up users and groups
when the customer buys a bunch of Home editions
because they are two cents cheaper than Pro
Ken Blake wrote on 4/20/24 7:51 AM:
On Fri, 19 Apr 2024 20:27:07 -0700, T <T@invalid.invalid> wrote:
Local Users and Groups (lsurmgr.msc) for Windows Home edition:
https://github.com/akruhler/AccountManagement/releases
I adore it.
Can you tell us why? What do you like so much about it?
Hi, Ken.
Not 'T' but a few reasons.
Windows Home does not include the GPO for Local User and Group >Management(LUSGM) policy settings/changes.
- the github program, if understanding correctly, provides a tool that
Home does not have for managing Local and Group policies, in addition it
can also be used on Windows Pro as an alternative to Pro's included and >built-in GPO LUSGM.
Additionally Microsoft periodically release ADX templates that update(add >new, remove old, modify) existing policies.
- in the business(Enterprise arena) its quite common for Admins to use
and keep their ADX supported policies updated.
Thus even in no-Enterprise environment, individuals or businesses that >support non-Server admin managed devices(Windows Home) can use the github >tool for managing policies on those devices, and a bit easier than single
or multiple created entries in the registry.
I don't
what your lusrmgr alternative uses: calls to CLI or API.
Local Users and Groups (lsurmgr.msc) for Windows Home edition:
https://github.com/akruhler/AccountManagement/releases
I adore it.
Home edition still drive me nuts. But a little less so
with this utility.
On 4/19/2024 11:27 PM, T wrote:
Local Users and Groups (lsurmgr.msc) for Windows Home edition:
https://github.com/akruhler/AccountManagement/releases
I adore it.
Home edition still drive me nuts. But a little less so
with this utility.
I'm not sure what this is supposed to help, but it doesn't load
for me. I get a window that says "loading". ProcExp says
it's eating progressively more memory. But it just hangs there.
I do have gpedit for Home Edition.
I.e. in an IT Admin environment, use of regedit for changes across an
image for use on multiple clients or domain or domain controller is path
of poor execution, lower productivity, and potential error.
On 4/21/2024 2:03 PM, ...w¡ñ§±¤ñ wrote:
I.e. in an IT Admin environment, use of regedit for changes across an
image for use on multiple clients or domain or domain controller is
path of poor execution, lower productivity, and potential error.
  I stand corrected. I'm not familiar with managing a fleet of
computers in corporate environment. I'm just talking about
working with one computer at a time, like most of here are doing.
I've never found any useful purpose for gpedit. It's easier just
to understand the Registry and know the settings.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 457 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 132:19:53 |
| Calls: | 9,337 |
| Calls today: | 8 |
| Files: | 13,534 |
| Messages: | 6,082,343 |
| Posted today: | 1 |