1.1.41 release not showing as latest version #6861
-
|
Has the 1.1.41 release been pulled for any reason? I just attempted to update my existing 1.1.40 installs (I have two separate MeshCentral servers) and both are showing that 1.1.40 as being the latest version. If I manually run 'npm dist-tag ls meshcentral' it also shows 1.1.40 as being the latest release. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 6 replies
-
|
yes this is because the release no longer works with windows 7 or server 2008 r2 or lower OS! you can force the install to 1.1.41 using im in the middle of trying to fix the agent now anf find out what commit goofed up old OS's |
Beta Was this translation helpful? Give feedback.
-
|
Still having Window 7 and 2008 is a security risk on its own. |
Beta Was this translation helpful? Give feedback.
-
|
Very true. But that's an entirely different discussion. The same can be said for Windows 8/Server 2012 and, very soon, Windows 10/Server 2016. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, corporate software needs support in some way. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I didn't see that. No problem at all. I was concerned something had gone wrong with my existing MeshCentral servers that might have been preventing them from grabbing the new version. |
Beta Was this translation helpful? Give feedback.
-
|
its because with NPM you cant |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your quick work on getting this resolved. I just updated one of my MeshCentral servers to 1.1.42 without issue. I am using MeshCentral to automatically codesign my agents with my own code signing cert and all went well. That said, I don't have any Windows 7/Server 2008 devices connected to this server. My other MeshCentral server does still have one or two Windows 7 machines. When I update that one I'll let you know if I see any issues with the Windows 7 devices after updating the agents. |
Beta Was this translation helpful? Give feedback.
-
|
great thank you!sadly i lost access to my win 7 machine i look after but at the same time i was right next to it today, |
Beta Was this translation helpful? Give feedback.
-
|
I decided to go ahead and update my other server- which is the primary MeshCentral server with hundreds of devices. There is just one Windows 7 box still on it- so I wasn't too concerned if just one device could have an issue. This server was still running 1.1.39. The update to 1.1.42 went perfectly and all agents are updating to the new version. The lone Windows 7 box updated to the new agent and is showing as being online and is fully accessible. Also see that the program info in Programs and Features is updating with the new date/version for the agents. |
Beta Was this translation helpful? Give feedback.
-
|
yep i fixed the version/date/size for the registry before Ylian did the release for 1.1.42 so it should be good for future updates too! |
Beta Was this translation helpful? Give feedback.
yes this is because the release no longer works with windows 7 or server 2008 r2 or lower OS!
https://github.com/Ylianst/MeshCentral/releases/tag/1.1.41 (see comment)
Ylian was not happy when i told him so hes pinned the stable to 1.1.40 WHICH I FULLY UNDERSTAND BECAUSE
YOU WILL LOSE ACCESS TO YOUR 7/2008R2 MACHINES if you have auto-update enabled for agents (which iS the default)
you can force the install to 1.1.41 using
npm install meshcentral@1.1.41im in the middle of trying to fix the agent now anf find out what commit goofed up old OS's