MeshCentral Updates
-
@scottalanmiller said in MeshCentral Updates:
@stacksofplates said in MeshCentral Updates:
@scottalanmiller said in MeshCentral Updates:
@stacksofplates said in MeshCentral Updates:
@scottalanmiller said in MeshCentral Updates:
This is at least a vastly more trustworthy vendor (Intel)
Intel is a terrible vendor. Security especially and just overall not good. You've complained about how bad they are multiple times here. And it's being developed by a single person not Intel. They may back it in some way which has yet to be proven, but they are not the vendor. And while a single person may be helpful sometimes for quick responses in fixes, more often than not that isn't the case. How many people here who are demanding changes are contributing back to the project either through payments or through code commits? Hopefully this guy doesn't get burnt out like we've seen from other other tools that have popped up here before.
Intel used to advertise it as an Intel product. "Yet to be proven" makes it sound like this has been somehow disputed in the past.
I never saw them advertise it. Where was that? The only thing I ever found was a blog post about it on an Intel site.
Earlier version, they used to have it somewhere associated with the AMT products.
Isn't the new version still associated with AMT?
-
@Dashrender said in MeshCentral Updates:
@scottalanmiller said in MeshCentral Updates:
@stacksofplates said in MeshCentral Updates:
@scottalanmiller said in MeshCentral Updates:
@stacksofplates said in MeshCentral Updates:
@scottalanmiller said in MeshCentral Updates:
This is at least a vastly more trustworthy vendor (Intel)
Intel is a terrible vendor. Security especially and just overall not good. You've complained about how bad they are multiple times here. And it's being developed by a single person not Intel. They may back it in some way which has yet to be proven, but they are not the vendor. And while a single person may be helpful sometimes for quick responses in fixes, more often than not that isn't the case. How many people here who are demanding changes are contributing back to the project either through payments or through code commits? Hopefully this guy doesn't get burnt out like we've seen from other other tools that have popped up here before.
Intel used to advertise it as an Intel product. "Yet to be proven" makes it sound like this has been somehow disputed in the past.
I never saw them advertise it. Where was that? The only thing I ever found was a blog post about it on an Intel site.
Earlier version, they used to have it somewhere associated with the AMT products.
Isn't the new version still associated with AMT?
Yes, but the AMT sites used to point to it. Maybe they still do, but I don't mean it pointing to AMT.
-
@scottalanmiller said in MeshCentral Updates:
@stacksofplates said in MeshCentral Updates:
@scottalanmiller said in MeshCentral Updates:
@stacksofplates said in MeshCentral Updates:
@scottalanmiller said in MeshCentral Updates:
This is at least a vastly more trustworthy vendor (Intel)
Intel is a terrible vendor. Security especially and just overall not good. You've complained about how bad they are multiple times here. And it's being developed by a single person not Intel. They may back it in some way which has yet to be proven, but they are not the vendor. And while a single person may be helpful sometimes for quick responses in fixes, more often than not that isn't the case. How many people here who are demanding changes are contributing back to the project either through payments or through code commits? Hopefully this guy doesn't get burnt out like we've seen from other other tools that have popped up here before.
Intel used to advertise it as an Intel product. "Yet to be proven" makes it sound like this has been somehow disputed in the past.
I never saw them advertise it. Where was that? The only thing I ever found was a blog post about it on an Intel site.
Earlier version, they used to have it somewhere associated with the AMT products.
That's the only thing I have ever seen referencing it not from the MeshCentral side. And that's just a blog on the Intel developer site.
-
And not only that but Ylian himself says Intel is not involved.
-
@ScottyBoy said in MeshCentral Updates:
And not only that but Ylian himself says Intel is not involved.
Interesting. It definitely used to be posted on Intel's site.
-
FYI, Do not update to the current version (0.7.47) of Meshcentral today. Its having issues. About 90% of my systems cannot connect back.
EDIT: Actually it is the Windows machines having issues. Linux machines are fine.
-
@pmoncho said in MeshCentral Updates:
FYI, Do not update to the current version (0.7.47) of Meshcentral today. Its having issues. About 90% of my systems cannot connect back.
I'm not noticing any issues and I've been on that version for awhile now.
-
Interesting. I am trying to figure it out at the moment. It has something to do with the meshagent.update.exe getting stuck.
From C:\Program Files\Mesh Agent\MeshAgent.log file.
[2021-01-12 07:10:45 AM] SelfUpdate -> Checking Updater Version on: C:\Program Files\Mesh Agent\MeshAgent.update.exe , C:\Program Files\Mesh Agent\MeshAgent.exe[2021-01-12 07:10:45 AM] SelfUpdate -> UpdaterVersion_ERROR: child_process.execFile(): Could not exec [C:Program FilesMesh AgentMeshAgent.update.exe]Followed by a bunch of these:
[2021-01-12 08:11:10 AM] Microstack STUCK: @ [NtDelayExecution] [SleepEx] [FuncAddr: 0x1251E5D2F67F0000] [FuncAddr: 0x8E5FE5D2F67F0000] [FuncAddr: 0x56CCEED2F67F0000] [FuncAddr: 0xC9CEEED2F67F0000] [FuncAddr: 0x64B3EDD2F67F0000] [FuncAddr: 0xFFBDEDD2F67F0000] [FuncAddr: 0xFE23EED2F67F0000] [FuncAddr: 0xF5B5E5D2F67F0000] [FuncAddr: 0x14C4EFD2F67F0000] [LsaLookupUserAccountType] [BaseThreadInitThunk] [RtlUserThreadStart] -
0.7.46 introduced some behaviour that is a problem. 0.7.47 didn't have a fix for it. He's looking into it now.
-
@pmoncho said in MeshCentral Updates:
FYI, Do not update to the current version (0.7.47) of Meshcentral today. Its having issues. About 90% of my systems cannot connect back.
EDIT: Actually it is the Windows machines having issues. Linux machines are fine.
We have the same issues. Our Linux machines are fine, but Windows is not.
-
@pmoncho said in MeshCentral Updates:
Interesting. I am trying to figure it out at the moment. It has something to do with the meshagent.update.exe getting stuck.
From C:\Program Files\Mesh Agent\MeshAgent.log file.
[2021-01-12 07:10:45 AM] SelfUpdate -> Checking Updater Version on: C:\Program Files\Mesh Agent\MeshAgent.update.exe , C:\Program Files\Mesh Agent\MeshAgent.exe[2021-01-12 07:10:45 AM] SelfUpdate -> UpdaterVersion_ERROR: child_process.execFile(): Could not exec [C:Program FilesMesh AgentMeshAgent.update.exe]Followed by a bunch of these:
[2021-01-12 08:11:10 AM] Microstack STUCK: @ [NtDelayExecution] [SleepEx] [FuncAddr: 0x1251E5D2F67F0000] [FuncAddr: 0x8E5FE5D2F67F0000] [FuncAddr: 0x56CCEED2F67F0000] [FuncAddr: 0xC9CEEED2F67F0000] [FuncAddr: 0x64B3EDD2F67F0000] [FuncAddr: 0xFFBDEDD2F67F0000] [FuncAddr: 0xFE23EED2F67F0000] [FuncAddr: 0xF5B5E5D2F67F0000] [FuncAddr: 0x14C4EFD2F67F0000] [LsaLookupUserAccountType] [BaseThreadInitThunk] [RtlUserThreadStart]Okay, I see what you mean.
[2021-01-08 12:02:08 AM] SelfUpdate -> Checking Updater Version on: C:\Program Files\Mesh Agent\MeshAgent.update.exe , C:\Program Files\Mesh Agent\MeshAgent.exe [2021-01-08 12:02:08 AM] SelfUpdate -> UpdaterVersion_ERROR: child_process.execFile(): Could not exec [C:Program FilesMesh AgentMeshAgent.update.exe] [2021-01-09 12:03:10 AM] SelfUpdate -> Checking Updater Version on: C:\Program Files\Mesh Agent\MeshAgent.update.exe , C:\Program Files\Mesh Agent\MeshAgent.exe [2021-01-09 12:03:10 AM] SelfUpdate -> UpdaterVersion_ERROR: child_process.execFile(): Could not exec [C:Program FilesMesh AgentMeshAgent.update.exe] -
The only solution I've seen which I posted on Github was to kill the Mesh Agent processes, with one being the MeshAgent.Update.exe process, then restart the Mesh Agent Service. That works.
-
I'm on 0.7.47, I don't see a problem w Windows machines?
