Mic_Impero

Apologies, misunderstood. Yes it will do, I can't see any reason for it to do so though, so my advice would be to include the names in the injection exclusion list in the Impero server application. You may need a reboot at the client end for that to take place. Mic

@gshaw Please follow the link below for our anti-virus exclusions advice. Thanks Mic https://bit.ly/ImperoEdProAntiVirusExc

Hi @talksr If we can be of any help directly, please do contact us in the support team - [email protected] or 05109 611 341. Kindest regards Mic Sanderson Impero

This isn't something I've seen before, but happy to take a look with you. Please could you PM me your details and one of the team will be in touch in the morning? Thanks Mic

Thank you Arthur, i'll ensure we update the source of that information. Mic

A quick confirmation from me that we're working with this and testing it. Mic @ Impero

Hi Tim, Release notes for the product are sent at the same time as the product release; as soon as it's the latest version it also appears in the server application. I can make a habit of pinning them to the top of the direct support forum too as another place to find them easily. @free780 There's nothing here named Impero as a Service. Most things as a service are SaaS based products hosted in the cloud. You can purchase Impero on a SaaS license which is less money up front, but less economical long term. Mic

You're likely to see version 7 today, and 7.1 on the 18th of August all being well. If you'd like to plan to do this only once and go straight to 7.1 towards the end of August, that would be understandable. In scenarios like this a monthly release doesn't benefit schools who aren't using the software for these weeks, but for the majority of the year it's a benefit (and in today's global market, summer holidays are at different times). If you're building a new image, put 7 on your new image now, and you have the option to then roll them up to 7.1 at your convenience, and if you're not going to benefit from a fix or feature in 7.1 you can leave them on 7, and go straight to a later release later in the year, for example. Thanks Mic

Hi Timbo, We're not missing out on 7, it's in early adopter now and going to full release tomorrow. We're about to move to a monthly release cycle and so 7 will be tomorrow, and 7.1 will be as near as possible to a month afterwards. What that does mean is you may see that we're on version 7, but your fix isn't coming until 7.2, for example, and that will be because 7.1 is code complete and in testing. But what it also means is you're only 2 months max from 7.2 instead of a term away max. This means we'll be able to develop faster, with less risk to each release, and you'll get any fixes and new features faster too. It isn't necessary to upgrade every time (although we'd encourage it) so if you don't benefit from anything in the 'next' release and you'd rather wait until the school holidays for example, and keep to doing it only a few times per year, you can still do so. Mic

Hi all, Sorry I'm late, I've been out visiting a great bunch of customers. Just to clarify what we've seen at our end, there are some instances of Impero causing this, and the dll injections in place from version 6 onwards (which @timbo343 you already have from the original issue) resolve this. We've seen some other conflicts which entering dllhost.dll resolves, and this is in the software by default as of version 7.1. This will be due during August. In the mean time if anyone needs a hand with how to add this injection exclusion, please PM me. For anyone running Kaspersky 11, we've discovered just today that version 10 doesn't inject dwp.exe and version 11 does, which we inject at the same time, and this can cause this issue also. Excluding dwp.exe from Impero injections will resolve that. I haven't heard of 1803 being involved specifically though, we've only seen this in an environment where Impero is already in place and a customer updates from Kaspersky 10 to 11, or installs Kaspersky 11 from scratch. The vast majority of Impero HQ is running 1803 (and Sophos) and the Impero client and we've not seen any issues like this at all. Some have been from updates and some have been fresh builds, across a mix of bespoke computers and Dell optiplex kit, lenovo, dell, and asus laptops. We also carry out extensive testing of various Windows 10 builds including 1803 and haven't seen this issue. I'll ask dev and our own infrastrucutre manager whether there's any no Impero related ideas they can think of to help identify the cause when i'm back in the office on Monday. Hth Mic

Signed.

We've got our Pi's emailing us now so if anyone would like to go down that route, PM me.

Thanks for the quick response, that's interesting. We've seen some MS processes using dllhost and have included that in version 7.1 which is due in August. Please could you try adding dllhost.exe and let us know if that has a positive impact?

Hi @Boredguy , Sorry to hear that. There's a very definite scenario here where every machine running 1803 breaks until we enter those exclusions, then it works. We've not yet encountered Impero causing a problem once those extensions are in. Please could you disable Impero on your technicians workstation (stop and disable the services) and see if this still happens? If that's the case, it may be there is an issue with pushing those settings to that (or potentially other) workstations, which we'd been keen to take a look at. Impero works in a similar way to some security products in the way that it injects processes; if the problem still happens with Impero disabled, my next port of call would be any antivirus I had installed. Thankfully with it being the technicians PC i guess you could quickly identify that by disabling AV, run time scanning, etc, on that machine and see if the problem is resolved at that stage. Please PM me if we're able to help further more directly. Thanks Mic @ Impero

Since build 1803, Impero now crashes Edge browser. Most schools using Impero have Edge browser blocked due to the lack of ability to deploy Edge extensions from MS, so haven't noticed this issue. For those who still with to allow the use of Edge (bear in mind Impero will not monitor it unless you have the Edge extension installed and enabled), you need to exclude a new Impero Injection exclusion in the server application. We've added this by default in version 7, which is released for early adopters today (notification pending). Here are the instructions to resolve the issue pre version 7 of Impero. Open the Impero Server 1. Select the Tools tab and click on Injection Exclusions 2. Under Application enter the following browser_broker.exe 3. Under Description enter the follow Microsoft Edge 4. Click Add Exclusion 5. Repeat point 3, 4 and 5 again adding RuntimeBroker.exe and Microsoft Edge 6. You will need to restart the Impero Client services Please be aware once you have added the above, if you have any block polices already applied for Microsoft Edge as an application block this will no long block. To resolve this issue you will need to change the block from an application block to caption block Open the impero console Select the group, right click and select Advanced Policies. Select the block list under policy name, on the right hand side select ADD In the popup box then enter *Microsoft edge* and select Window Caption then click Add. Mic @ Impero