u/staze

I've got a thread over in Prusa forums (https://forum.prusa3d.com/forum/english-forum-general-discussion-announcements-and-releases/consistent-wrong-code-error-with-mfa-google-auth-via-1password/), and I've contacted their support to no avail. I've mentioned several times it's likely a time issue on their servers, but they don't seem interested or able to investigate.

Anyone see consistent TOTP issues with 1password and any other sites? Wondering if there's ever any other solutions we could mention to Prusa to try to fix this. =/

Anyone else seeing Trim Coat packaging change from 10 wipes to 8? Picked up some at Wallyworld today, and after getting home saw they were only 8 wipes. Website still claims 10 in box. So does cerakotes website, and Amazon...

We have an issue where some machines the drive will fill up, and if you go looking, you see hundreds/thousands of the same installer in there, all same time, same size, etc.

Talking to Patch My PC, they indicated they've seen this, but it's not necessarily their fault, it's just the Windows installer subsystem going a little sideways sometimes.

I'd like to be able to detect machines in this state, and remediate them, but I'm not entirely sure you could just powershell look at everything in C:\Windows\Installer, then look at maybe the signatures, and if they're identical, report out via a compliance baseline if over... 10? 20?

Anyone dealt with this in some way? Uninstalling the offending software clears out all the msi/msp's, but the issue is finding machines in this state.

So far, most of the offenders are Nessus (where we find hundreds of their 68MB installers), and Adobe Acrobat Reader (where there can be dozens-hundreds of the 700MB installer).

Thanks!

I have a script that runs every hour that updates some AD groups based on things like Department, Location, and a few other attributes set on computer objects.

It is, annoyingly slow (takes over 8 minutes to run).

The issue I think is for each group, I'm having to do something silly (this is just an example):

Get-ADComputer -Filter * -SearchBase $OU -properties MemberOf | where-object {[string]$_.MemberOf -notlike "*$GROUP*"} | ForEach-Object {try {Add-ADPrincipalGroupMembership -Identity $_ -MemberOf $GROUP -Credential $cred} catch { write-warning "Computer $_ moved or disappeared while processing..." }}

Get-ADGroupMember -Identity $ALLCOMPUTERS | Where-Object {$_.distinguishedName -notlike "*$OU*"} | ForEach-Object {try {Remove-ADPrincipalGroupMembership -Identity $_ -MemberOf $GROUP -Confirm:$false -Credential $cred} catch { write-warning "Computer $_ moved or disappeared while processing..." }}

Basically, add all the members then remove everyone that shouldn't be there (they got moved to some other OU).

I can probably shorten a lot of this by just doing once

Get-ADComputer -Filter * -Properties name,department,location,memberOf -SearchBase "OU=Computers,DC=example,DC=edu"

Then just work within that.

Though actually... Get-ADGroupMember may be the culprit for the slowness. So maybe just using something like this instead of the removal piece

Get-ADGroup -Identity $ALLCOMPUTERS | Where-Object {$_ -notlike "*$OU*"} | ForEach-Object {try {Remove-ADGroupMember -Identity $_ -MemberOf $GROUP -Confirm:$false -Credential $cred} catch { write-warning "Computer $_ moved or disappeared while processing..." }}

Also looks like I'm using Add and Remove-ADPrincipalGroupMembership instead of just Add-ADGroupMember and Remove-ADGroupMember... not sure if there's a performance difference there. Ideally I'd skip that if the computer was already a member of the group, but I'm unsure how to check that efficiently. I'm also not entirely sure it matters that much?

I guess the main question here is, does someone already have something similar to this?

Otherwise I'm thinking pull list of computers and their memberships. Then for each group, check if computer already a member (get-adgroup seems pretty speedy), and check membership. Then for groups that are location based, remove the member if the location is wrong, or department groups remove if department is wrong. I looked into some of the performance stuff a while back and compare-object, but not sure it made that big of a difference (other than some nice log output).