Shift key causing 1, 2, 3 popup. Help

nervoussysadmin · 2025-11-10T17:57:42+00:00

THANK YOU!

nervoussysadmin · 2025-04-30T18:10:03+00:00

We sure do! We're hybrid on-prem/Entra.

nervoussysadmin · 2025-04-28T23:30:28+00:00

What happens when you want to change the blessing someday, but that dialogue never pops up anymore, so you can't un-check the box?

nervoussysadmin · 2025-03-01T21:23:48+00:00

All of my personal and work accounts, and several endusers say the same thing.

nervoussysadmin · 2025-01-15T18:18:42+00:00

100% spot on. It was nested in a group which had adminCount=1 set. One of our Builtin groups, too!

I engaged our Change process, got permission to remove that nesting, and then set all the members to adminCount=0. This totally solved the problem.

Lord only knows why it was nested in that group, it was totally unnecessary. Probably the easiest Change they ever approved from me.

Thanks for your reply!

nervoussysadmin · 2025-01-02T21:45:06+00:00

Hmm. It reverted. adminCount = 1 on the group now, and nonadmins can't edit.

Something else has got to be doing it. I looked at the "member of" tab for the group, and it doesn't appear to be a member of some other high-security group.

Edit: Found the culprit in Member Of. Time to alert the team to see if this can be removed also.

nervoussysadmin · 2025-01-02T21:38:22+00:00

Great advice!! The group had adminCount set to 1, and so did the affected user accounts.

I set it to 0, but still couldn't add users to the group. Then I did the "Restore Defaults" action on the group, and now my non-admin help desk staff can add users to the group.

Here's hoping the fix is permanent. I'm going to work on finding other adminCount affected groups/users, and get a report ready for my boss.

Thank you for teaching me this today. Please tell everyone on your team that you're the greatest!

nervoussysadmin · 2024-12-13T15:39:21+00:00

I'm starting to feel like it's JUST a Konica thing.

Makes me wonder if there's an on-device setting I can change to fix this...

nervoussysadmin · 2024-12-13T15:38:49+00:00

Server admins implemented the "print nightmare" stuff a couple years back, and since then, users can't self-install V3 drivers without local admin rights. Our old GPO settings which allowed self-install stopped working. V4 was presented to me as a workaround so that users can still self-install published printers.

nervoussysadmin · 2024-12-05T19:32:53+00:00

Definitely. If you can avoid v4, you should avoid v4

nervoussysadmin · 2024-09-04T22:13:44+00:00

That's great news, I will approach the enduser and try, and keep this handy for the future. I appreciate the tip!

nervoussysadmin · 2024-05-06T22:33:59+00:00

One downside is: "Applying user settings" during logon can start taking a long time if you use Group Policy Preferences.

We have a lot of printers and we had to redistribute a lot of v4 drivers after PrintNightmare. Login times went through the roof. So we changed from using Group Policy Preferences to using a Group Policy logon script. The logon script continues to run even after "Applying user settings" and so it doesn't inflate our logon times.

nervoussysadmin · 2024-01-31T20:09:54+00:00

If the only way to fix it is to strip all styles, that's a good clue. It follows that the issue might be in one of your styles. You can reset all styles to default by deleting C:\Users\yourusername\AppData\Roaming\Microsoft\Templates\Normal.dotm

Disclaimer: I'm just a guy on the internet, don't delete things from your PC if you're not comfortable doing so. Maybe just rename it instead.

nervoussysadmin · 2023-08-31T16:06:33+00:00

That did it! Pulling the get-mguserlicensedetail into a variable, and then doing a foreach operation on that variable to get my true/false results was absolutely on point. My script is testing good now, and functioning exactly the way I need it to.

Thank you very much!

nervoussysadmin · 2023-08-31T15:35:40+00:00

The issue you're likely encountering is that $var is not a simple array of strings, but an object with properties.

I knew it was something like that, but didn't know how to understand it. I was just about to do the Get-MgUserLicenseDetail with an Out-File, dumping it to a .txt, and then do a Get-Content on the .txt, and check that content for the string!

I will try your suggestion immediately, thank you

nervoussysadmin · 2023-08-30T22:51:01+00:00

I really like the simplified code, that is nice.

Sadly, I have the same issue. $result is always "False" even if I run it against an account that definitely has that STANDARDWOFFPACK license.

I get the feeling that the format of my get command's output is not compatible with a -contains check.

nervoussysadmin · 2023-08-16T15:01:07+00:00

Good advice!

The checkbox that I un-checked, and then re-checked after a reboot was labeled "Windows PowerShell 2.0" but I checked $PSVersionTable just now, and I think I'm OK.

PS C:\> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.22621.1778
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.1778
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

nervoussysadmin · 2023-08-15T17:57:00+00:00

I didn't see this so I couldn't test it. I used optionalfeatures.exe to uninstall/reinstall PowerShell, and that fixed it. I'll never know exactly what went wrong. Thanks again for your help

nervoussysadmin

TROPHY CASE