Impero versions

[Jawloms]

Hi all,

 

I've got Impero 5.0.03 throughout. I'm going to upgrade to the latest version. Has anyone had differing versions running and had any issues? Obviously I'm going to upgrade everything ASAP, but I want to know if it has to all be done at once or whether I can stagger it. Impero are being vague on it.

 

Thank you

 

Stuart

[6Foot2]

We are at version 6.2.49. I have enabled automatic update at the server: Once the server has been updated my clients get updated too. If I were deploying Impero via SCCM I could deploy to these stations, but not these, but some Impero versions do not play well with others (v5 and v6, for example)

 

There were some problems with versions before the current one, but the one we have now does not seem too bad. I did report a problem earlier this week, but that was resolved by taking Impero Console off the server (Installed there on the recomendationj of the helpdesk a while ago )

 

Overall: It's OK.

[Boredguy]

We still have a v5 Mac that talks happily to our v6 Impero server, so you can update the server install then send the new MSI to clients via your preferred method.

 

It was actually recommended to disable the automatic update within Impero Server to prevent any connectivity issues in your classrooms due to unexpected installs.

 

We normally schedule the Server update for near the end of the day then use WPKG (or soon SCCM) to sent the client MSI out the following morning when the stations wake up.

Oh just make sure you have .Net Framework 4.6 or 4.7 installed on your clients before you put the Impero v6 client on otherwise it won't be able to talk to the server.

Edited December 1, 2017 by Boredguy

[Jawloms]

Oh just make sure you have .Net Framework 4.6 or 4.7 installed on your clients before you put the Impero v6 client on otherwise it won't be able to talk to the server.

 

This is why I may be staggering the upgrade, I don't have 4.6 everywhere at the moment. The ones which don't have 4.6 yet will remain on v5 and I want to make sure they'll talk to the v6 server.

 

Stuart

[Mic_Impero]

Good afternoon all,

 

There are some versions you can stagger quite safely, but it depends entirely on what's been changed in the software.

Most of the time our literature states that you must run matching versions, and our testing cycle only includes matching versions, so we can predict the behaviour of staggering but can't guarantee it.

 

I know for certain that the changes between 5003 and 6.x are so vast that you will experience connectivity issues, logging issues, and the policies will not apply correctly (if all all) - this will include groups, settings, schedules, keyword monitoring, etc.

 

My strong recommendation would be to upgrade all of your machines to the requirement of .NET 4.6 as a minimum prior to implementing versino 6.x on your network.

The only other solution I can think of would be to run two servers for a short while, and connect the Win 10 machines to the new version, and win 7 to the old one, but depending on how you use Impero and your safeguarding policies etc this could get really complex. For example, if one person looks at logs, they'd have two sets of logs to look at. And if there were a teacher machine in ever room, you'd connect the teacher machine to the same server as that room, so the machines could all be controlled from that teacher pc.

If, though, the teacher has a laptop which roams, this wouldn't work, and if the learners have 1-1 devices this would be a non starter too.

 

The lesser workload would definitely be to upgrade .NET as required and then proceed with the update.

 

Mic@Impero

[Jawloms]

Thanks for this. All my computers are Windows 7. I'll get the framework on before I begin anything.

 

Stuart