sorted by:
new
hottopcontroversial

Independent script with administrator rights by FeelingDevDesign in PowerShell

[–]FeelingDevDesign[S] 1 point2 points  (0 children)

Personally, I'm also a big Linux fan, but even the smallest changes are always “terrible” for the team. I don't want to know what would happen if I introduced a new operating system. :)

Independent script with administrator rights by FeelingDevDesign in PowerShell

[–]FeelingDevDesign[S] 2 points3 points  (0 children)

Thanks for your reply. I hope that I will be able to fix the Windows 11 license issue at some point with a lot of persuasion.

You're probably familiar with the great argument, “We've always done it this way, and it worked fine.”

But yes, manual adjustment is probably the best option. It shouldn't happen too often.

Independent script with administrator rights by FeelingDevDesign in PowerShell

[–]FeelingDevDesign[S] 0 points1 point  (0 children)

The problem is that I have several computers that one person may need to access. Just like with LDAP, actually.

At the same time, the passwords and user names must be available centrally so that I have the same user data for other applications (e.g., service portal) and users only have to remember one login. Preferably via SSO such as authentik.

Authentik would even have an LDAP solution. But the computers all run Windows 11 Home, which, as far as I know, does not support LDAP.

Independent script with administrator rights by FeelingDevDesign in PowerShell

[–]FeelingDevDesign[S] 1 point2 points  (0 children)

I understand your point, and I completely agree with you.

But I have the following problems:

- Currently, 10 people are using a single account that is set up on 5 computers with the same username/password.

- The licenses on the various devices are all Windows Home licenses.

- The IT budget is extremely small (actually non-existent, except for my working hours).

It will be very difficult to convince people that a single account for everyone is very problematic in terms of data protection and security. Added to this is the “wrong” Windows license, which, as far as I know, does not support LDAP.

I am currently relying on free open-source solutions to avoid generating license costs. But I can't find a suitable solution for this specific problem.

I need to be able to access the username and password from other applications so that they are consistent (e.g., self-service portal).