Random Thread - Anything Goes
-
-
-
@nadnerB said in Random Thread - Anything Goes:
Reward2: Not being clawed to shreds for petting the kitty.
-
@JaredBusch said in Random Thread - Anything Goes:
And as for the the updates not being done, that is also the administrator’s problem to not have configured the devices to check automatically.
What? that's the default setting in Windows 10 - you have to go out of your way to disable that.
-
@JaredBusch said in Random Thread - Anything Goes:
And as for the the updates not being done, that is also the administrator’s problem to not have configured the devices to check automatically.
It was caused by NinjaRMM. Apparently it disables all patching, but then reports that patching is done so that it looks like it is handling things when, in fact, it is disabling them. So people were checking for years (via NinjaRMM rather than manually) and thinking that it was patching.
So even when people set it to check, it would get turned off. The error was in believing the RMM and not verifying it when it said that it was doing something.
-
@scottalanmiller said in Random Thread - Anything Goes:
@JaredBusch said in Random Thread - Anything Goes:
And as for the the updates not being done, that is also the administrator’s problem to not have configured the devices to check automatically.
It was caused by NinjaRMM. Apparently it disables all patching, but then reports that patching is done so that it looks like it is handling things when, in fact, it is disabling them. So people were checking for years (via NinjaRMM rather than manually) and thinking that it was patching.
So even when people set it to check, it would get turned off. The error was in believing the RMM and not verifying it when it said that it was doing something.
Holy hell!
-
@scottalanmiller said in Random Thread - Anything Goes:
@JaredBusch said in Random Thread - Anything Goes:
And as for the the updates not being done, that is also the administrator’s problem to not have configured the devices to check automatically.
It was caused by NinjaRMM. Apparently it disables all patching, but then reports that patching is done so that it looks like it is handling things when, in fact, it is disabling them. So people were checking for years (via NinjaRMM rather than manually) and thinking that it was patching.
So even when people set it to check, it would get turned off. The error was in believing the RMM and not verifying it when it said that it was doing something.
This sounds like a lazy administrator had something misconfigured, or just didn't care, in either case the issue lies with a human error / laziness.
-
@scottalanmiller said in Random Thread - Anything Goes:
The error was in believing the RMM and not verifying it when it said that it was doing something.
The error was not correctly configuring the RMM.
-
@JaredBusch said in Random Thread - Anything Goes:
@scottalanmiller said in Random Thread - Anything Goes:
The error was in believing the RMM and not verifying it when it said that it was doing something.
The error was not correctly configuring the RMM.
Nice try, but the vendor couldn't figure it out either. We've heard from other companies that have used it that they have the same problem. It's not supposed to need to be configured, either, the setting to keep it patched and report on it being patched was configured, but it doesn't do what is described.
-
Even if that wasn't the problem, that you have to manually reconfigure an RMM because the assumption that a default disables patching, but claims to be patching is just as absurd and ridiculous.
-
-
-
-
@scottalanmiller said in Random Thread - Anything Goes:
Microsoft is ridiculously cavalier with "Your device is up to date." It literally says that no matter what the status is. I've never seen it say anything but that, and I've almost never seen a machine that was even kind of up to date.
Curious to know what someone did to stop or prevent updates 3 years ago on a Windows version I'm sure is currently no longer supported lol.
-
@Obsolesce said in Random Thread - Anything Goes:
Curious to know what someone did to stop or prevent updates 3 years ago on a Windows version I'm sure is currently no longer supported lol.
they installed NinjaRMM. It turns out, that it stops updates and reports that everything is up to date regardless.
But the issue that Windows claims to be up to date totally regardless of the update status is different, that happens even with a vanilla install. Just a vanilla install will update itself, so it isn't generally too far off being accurate.
-
@scottalanmiller A lot of RMM don't show that it is up to date on that screen. However it does show on the installed Updates so just check that. I know I have seen many RMMs do that however the devices are actually updated.
-
@dbeato said in Random Thread - Anything Goes:
@scottalanmiller A lot of RMM don't show that it is up to date on that screen. However it does show on the installed Updates so just check that. I know I have seen many RMMs do that however the devices are actually updated.
These devices are absolutely not updated. The problem is the opposite... it says up to date, but isn't. Not one. We manually checked around one hundred this weekend. Got about fifteen hundred to go. Those being patched since the RMM was configured to patch and report... zero. But every single one says it is up to date, until you check.
-
@scottalanmiller said in Random Thread - Anything Goes:
Microsoft is ridiculously cavalier with "Your device is up to date." It literally says that no matter what the status is. I've never seen it say anything but that, and I've almost never seen a machine that was even kind of up to date.
While the words "Your device is up to date" it doesn't really say it's up to date - it says, as of 11/29/2017 - it was up to date.. that wouldn't mean anything for any day after that.
Sure it would be nice to say - only "last checked on date"...
-
-
