MHiser

[MHiser @TheHiser]

@PJ_Marcum @guyrleech @10ZiGTechnology You won’t be disappointed with igel

[MHiser @TheHiser]

@guyrleech @PJ_Marcum @10ZiGTechnology Have you not seen their software solution? Their OS solution and management is great. Previously heavily a thin client solution but have migrated to the OS management solution but still provide hardware. Their USB OS on any hardware to connect was a huge cost saver.

[MHiser @TheHiser]

@acjuelich Network guys had to find the cert and then push it out to all the Palos. The Palos weren't updating the cert, or MS wasn't publishing everything. This happened several times, same process with the Palos over the last 12 months.

[MHiser @TheHiser]

@acjuelich Certificate chain is missing. That needs to be updated. Couldn’t edit.

[MHiser @TheHiser]

@acjuelich You mentioned Palo. I run into this issue a lot. I don’t know the specifics but somewhere a certain chain isn’t being updated. My network team has to find the cert and push it out and store apps can update again. Happened 4 times in the last 12 months or so.

[MHiser @TheHiser]

@jeremymoskowitz A lot of speculation based on the data released but a very obvious answer is not stated. Correlation is not causation but way too glaring to ignore. Not something I care to state in the open.

[MHiser @TheHiser]

@Michael_Yon @Michael_Yon Do you see this as gearing up for a generational transition or something more immediate? China is fighting a many generations war people are missing - or is this destruction much sooner?

[MHiser @TheHiser]

@manelrodero @xenappblog @Mister_MDM Version comparison (native) is not the same as string comparison
Try: [Version]$value -eq [Version]$expected
Convert the strings to version. $Value.gettype() - Is this a string value? White space? .trim() - Validate the script, values, and type comparisons

[MHiser @TheHiser]

@jarwidmark @pablitobin @Matt_Bradley73 PTO week - won't be touching anything until next week. Lab was killed off as well.
Domain\svc_account was literally the only item changed from the original setup instructions though.

[MHiser @TheHiser]

@StevenKister1 @kaiserschloss I’ve done through individually disabling portions of secure launch/fast boot/VBS without luck this morning. Case opened with MS and info left on feedback hub. Waiting for info. Going to rollback and remove the drivers from the original update and wait.

[MHiser @TheHiser]

@yoemsri @Pirat_Nation It shouldn't be. The original patch was to fix a zero day with other stuff which is causing the issue. Read the release notes, take alternative steps to fix the zero day issue, and hold on patching.

[MHiser @TheHiser]

@StevenKister1 That would be my test. Verify it is off and registry is showing. Otherwise uninstall the update and remove the two modem drivers cited which were the zero day issue. Open case with MS or wait for next month.

[MHiser @TheHiser]

@StevenKister1 First screenshot, disable secure launch. Also can remove the registry key/set to disable if not set by GPO. Testing on it tomorrow to validate functionality.

[MHiser @TheHiser]

@StevenKister1 I'm going with disabling Secure Launch for now to get shutdown functionality back over minimal risk to a secure launch/physical access attack.

[MHiser @TheHiser]

@jarwidmark Adminservice supports kerberos, use UPN when setting username/password variables and it will work again.

[MHiser @TheHiser]

@PJ_Marcum @IntuneSuppTeam @Mister_MDM Late to the game. Write-output for logging, use "Return" send the info back for evaluation. As noted before, the Exit 0/1 was evaluated, switch to using Return and it should work.

[MHiser @TheHiser]

@skatterbrainzz Bold statement. I often curse someone from years ago for doing something wrong back then that I have to fix now before I can move forward. To your point, if you did it right, you're correct, do wrong, hatefully remembered.

[MHiser @TheHiser]

@MMelkersen Thanks, good catch. Documentation says one thing, trust but verify.