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.

On 4/19/24 23:05, VanguardLH wrote:
> 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
> ^ ^^ ^ ^ ^ ^

Stinking typos. Mumble, Mumble ...

> 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

I love it! Thank you!

>
> 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.

No fooling! Hopefully, WMIC will probably be around for a while.

I read somewhere that I can not remember that Power Shell
has not been all that popular for administrative tasks.

> 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.

Thank you for the insightful response!

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.

--
....w¡ñ§±¤ñ

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

On 4/20/24 12:43, ...w¡ñ§±¤ñ wrote:
> 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.
>
>

Everything you need is just right there. Saves tons of time.

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.

On 4/20/24 14:15, VanguardLH wrote:
> 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.

There are something like four command I user from PowerShell.
I have them written down in my keepers.

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.

>
> 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.

I use lusrmgr all the time in Pro editions. Everything
is just right there to set up users and groups. It is
nice now have the same option in Home edition too.
It saves me a bunch of time. But if the tool does
not synergize with you, then obviously, do not use it.

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.

It is an individual thing. Whatever works for you.

T <T@invalid.invalid> wrote:

> 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.

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.

> 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.

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).

On 4/20/24 14:55, 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.

On 4/20/24 14:55, VanguardLH wrote:
> 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).

Awesome!

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.

On 4/20/24 20:11, VanguardLH wrote:
> 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.

Seen that on some cmd shells too. When I tried
with PowerShell to do what you stated, it did not
work the second time. I probably gave up too easily.

Since I issue a lot of stuff to the system when
I am programming, I just stay in cmd so I can
troubleshoot it. My calls to the system are all
cmd calls (when I am not doing API calls), so it
works for me.

On 20/04/2024 22:34, T wrote:

> 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.

Try running stuff from within the Powershell ISE

You can change colours in Tools/Options if required.

On Sat, 20 Apr 2024 12:43:28 -0700, ....w¡ñ§±¤ñ
<winstonmvp@gmail.com> wrote:

>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.

Thanks, Winston.

On Sat, 20 Apr 2024 14:00:01 -0700, T <T@invalid.invalid> wrote:

>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

Thanks, T. Since I use Pro, it's probably not for me.

VanguardLH wrote:

> I don't

[know?]

> what your lusrmgr alternative uses: calls to CLI or API.

The VB source is available, can see plenty of windows API calls, can't
see any spawning of wmic.exe

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. (Pro has always seemed
like a silly moneymaking scam to me, and I'm not interested
in BitLocker.)

But you do realize the even gpedit is just a wrapper for IT
people who don't know how to use the Registry? What sorts
of user settings do you need to set that you can't just do in
the Registry? I don't understand why Home "drives you nuts".

Newyana2 wrote on 4/21/24 9:22 AM:
> 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 do have gpedit for Home Edition. (Pro has always seemed
> like a silly moneymaking scam to me, and I'm not interested
> in BitLocker.)
>
>   But you do realize the even gpedit is just a wrapper for IT
> people who don't know how to use the Registry?
>
That's a far cry from being accurate.
In and IT managed Admin environment GP Editor plus MSFT available ADMX
files provides the ability to change policies for multiple items in on
single instance across image without the need to create scripts or reg
files with the necessary changes for all Windows(Home, Pro, Enterprise,
Education).

ADMX files include options not included in the base GP Editor snap-in
In an IT Admin environment deployment of multiple GPO changes and latest
ADMX files can be done to a base image for deployment to new or existing
devices. Also, the ability to deploy ADMX files to domain controller
across a domain controller then replicated to all domain controllers in
the domain.

Another benefit, when updating hardware and Windows, the GPO/ADMX changes
can be isolation tested on a group of devices before deploying to an
image or domain across existing devices in the entire fleet(hundreds,
thousands).

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.

--
....w¡ñ§±¤ñ

VanguardLH wrote on 4/20/24 8:11 PM:
> 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.
>

Another route, just open Powershell in its GUI/Full Menu bar mode -
Windows Powershell ISE, then use the menu bar item 'Tools/Options' to
make the necessary changes.

Powershell ISE provides the same command type console but adds more
flexibility and both an interactive and execution approach than just a
commad console....including the entire array of powershell commands(that
can be searched, scrolled, selected and inserted into the command console
without having to type(the command).

--
....w¡ñ§±¤ñ

On Sun, 21 Apr 2024 11:22:08 -0500, Newyana2 <mayayana@invalid.nospam> wrote:

> 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 was interested enough to try it, but the same result for me.

On 4/21/24 09:22, Newyana2 wrote:
> I do have gpedit for Home Edition.

Where did you get it?

Also Pro has one license for RDP server. A lot
of my cyusotmers use it. It automatically descales
your screen to your monitor, which is a wonderful
feature. Plus, it is fast.

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.

On 4/21/24 17:03, Newyana2 wrote:
> 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.
>

I like the built in explanations and the fact
that the settings take effect immediately
without having to reboot.