u/CharcoalGreyWolf

Okay, so I've tried this with Winget and my own scripting (my own downloads from Microsoft's permalinks) and can confirm this is true.

Approximately 6-8 months, (this is not exact so pleas no-one go pedantic) Microsoft went from the following:

"Microsoft Visual C++ 2015-2022 Redistributable"

to

"Microsoft Visual C++ v14 Redistributable"

Which was fine, because we're long past 2022, it made sense, easier to keep track of, right? So, I updated some of my updater scripts and went on my merry way.

This month, Microsoft releases new Visual C++ Redistributables. What are they now?

"Microsoft Visual C++ 2015-2022 Redistributable"

With a *new* numeric version (14.51.36231.0 up from the v14 14.50.35719), but reverting to the *previous* name.

I'm just wondering why Microsoft can't get their sheot together with things like this. Are they just letting AI do this for them? Have they decided to re-staff departments like this with primates and pay in bananas? At least I found out pretty quick, but why is it so hard to get something this simple consistently right, and why does Microsoft continue on the path of ridiculous mistakes like this?

This is a question where the answers I've found have been a little quirky, so I'm trying to get confirmation.

Is there a way to set up desktops in an Intune environment where a fingerprint only has to be enrolled once, and it's saved in the user profile and they can move across machines in an organization? I'm checking because we have multiple clients where someone might not be on the same system (and occasionally, not even at the same location) on different days. We already have other hardening methods through Intune, but I'm wondering if it's possible to ensure that the biometric information is saved to their user profile and can roam, so to speak.

This is just a preliminary wondering on my part; I didn't think it was an option (neither does my CTO), but some of my searches have seemed to indicate otherwise. It could mean the data was saved to the local user profile on a system and was just worded ambiguously, but I'd like to be sure.

So, it appears another Forticlient VPN 7.4.3 build was released March 20th in Forticloud.

March 20 build: 7.4.3.4726

Previous build: 7.4.3.8758

As it seems difficult to find release notes indicating changes between sub-builds, does this make sense to anyone, or does anyone here have the information? I need to understand more before this build gets pushed out to hundreds of systems on our end, and I've never seen Fortinet go with a lower number for a newer build.

I also found that when installing the .4726 build over the .8758 (without removing the previous first) that the .4726 build shows in Programs and Features, but the "About" screen shows the old "7.4.3 hotfix 1.8758". Whereas if I uninstall the old build first, reboot, and install the new build, the "About" screen shows up as 7.4.3.4726 (no hotfix listed any more).

If others have more information I would be very interested to know.

If you were a board game, what would you be?

Andy Dirks: I would be Operation. I’d at least like to feel something in my lifetime.