what did you learn today? (part 2)
- Thread starter continuum
- Start date
Well, I spent all day with Broadcom support yesterday trying to get it fixed. The results? Hung up on twice so I had to requeue as no ticket was created in that time even though they said they were going to, 3rd call I got a Zoom because they said I had rights to my entitlements so they saw nothing wrong. Zoom showed the issue so they got it partially fixed. I can now see and download 1/3rd of my entitled software but not the stuff I need right now so new case created to investigate that now. In the process of doing that my account is no longer valid in the support portal (happened after I logged out after the zoom session) so I cannot actually see the case that was created nor can I create a new case, I have to call in again. I've been summarizing the woes with all this to my boss every week as more reason to ditch vmware for something else.
At this point you should engage your VAR/Reseller and lean on them to get this fixed via the partner channels.
I don't think partner channels are any more useful than frontline support at the moment.
Ugh Microsoft. TIL about Get-Unique and also the list you feed it has to be sorted for it to work, not that it's hard but still.
If you feed it "A,A,B,B,C,C" You'll get "A,B,C" out, but if you Feed it A,B,C,A,B,C you'll get A,B,C,A,B,C out.
If you feed it "A,A,B,B,C,C" You'll get "A,B,C" out, but if you Feed it A,B,C,A,B,C you'll get A,B,C,A,B,C out.
TIL that Microsoft doesn't have a first-party module for managing Windows updates (checking for them, installing them, etc) through PowerShell. You have to rely on an open-source project for that.
May be no more useful, but it pushes the effort off to someone else!
I had issues with the MSWindowsUpdate PS Module and never could get it to do what I wanted.
Well Windows Update has generally always been a dumpster fire in one way or another, but I've been using a VBScript to do basic patch installation for almost a decade now with good success. But Microsoft is killing VBScript because they want everyone to move to PowerShell. Hence it's rather amusing that they don't have a native module for that. The good news is the linked project is rather robust (and gives me more options than the VBScript ever did).
TIL I learned of the RailRunOnce registry key, a special registry key to run apps at startup of a Windows RDP Services Server session. This key is separate from all the other Run keys to auto-launch apps in Windows.
The most common use, as was mine, was to let OneDrive run in the background so a RemoteApp can use the user's OneDrive folders.
The most common use, as was mine, was to let OneDrive run in the background so a RemoteApp can use the user's OneDrive folders.
TeamViewer's corporate network was breached in alleged APT hack
The remote access software company TeamViewer is warning that its corporate environment was breached in a cyberattack yesterday, with a cybersecurity firm claiming it was by an APT hacking group.
Looks like Teamviewer has been hacked again.
Our Canadian business uses some accounting software that uses an embedded version of TV's remote support for vendor support, but it uses all the same public endpoints as normal TV. We keep it blocked in zScaler and only enable it when requested. sigh
Did the attacker convince an employee to install TeamViewer on their workstation & got their backdoor that way? I saw some posts refer to that, but not sure it was joking (just desserts) or not. The reporting I saw didn't say that unless I overlooked it.
A plug for another tool that leverages powershell (same module as pswindowsupdate I think) for updates And rolls in other updating like chocolatey.
Releases · topgrade-rs/topgrade
Upgrade all the things. Contribute to topgrade-rs/topgrade development by creating an account on GitHub.
github.com
Sadly microsoft changed some tooling in the later versions of Windows 11 that breaks both topgrade and pswindowsupdate.
Windows 11 UsoClient failed · Issue #345 · topgrade-rs/topgrade
What did you expect to happen? Windows Update step to successfully exit. What actually happened? UsoClient fails with exit code 0x80070057. Snippet from Microsoft support regarding "exit code 0x800...
github.com
(champing at the bit to get Windows 11 LTSC, it has gone gold but not released beyond partners. Yes, I work for a partner(just too far removed from the microsoft feed) so it isn't technically illicit..)
When Microsoft started forcing updates in Windows 10 (which you find in my posting history over the years that I mostly agree with that direction) I expected Windows Update to get some decent PowerShell support. At the very least, I wanted something that could kick off updates from the command line reliably, something I've wanted built-in for years since PSWindowsUpdate requires changes to the default execution policy.
Instead, we get the retirement of wuauclt and the Windows Update log requiring a new PowerShell command to be read. So I guess we got some form of PowerShell, just not anything useful.
Instead, we get the retirement of wuauclt and the Windows Update log requiring a new PowerShell command to be read. So I guess we got some form of PowerShell, just not anything useful.
PS to read the windows logs has been there since 2012. But yes, it is very frustrating.
I'm doing all my testing of PSWindowsUpdate in Windows 11 23H2 and it seems to be working fine?
I don't like this either, but I'm working around it by just changing it temporarily:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process 
I think I saw something mentioning that Microsoft has too, and is just rolling out the change later this year.