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

I'm running a raspberry Pi with a temperature and humidity sensor in it. We haven't set it up to email yet but we can visit a graph live to within a couple of seconds, in a browser, cost is about £40 per pi. I'll let you know once we've got it to notify us by email of a crossing of the threshold. Once we've got there i'll be happy to clone the SD for anyone that sends me a blank.

We've implemented DirectAccess too, and have looked at AlwaysOn. We don't have a need to move to AlwaysOn at the moment, but can't see a reason we wouldn't implement that now should we be starting again. Koryo is correct about Impero. It will connect to the server if you have a DNS A record in place for the Impero Server, but thumbnails and most other functionality won't operate as they're peer to peer and / or over IPv4. One thing to note is that as the Impero Client is connected to the Impero Server, it does not log activity locally for upload later (it would if the client couldn't find the server). As the connection to upload this is over IPv4, nor does it upload the data. The way to stop this is to block the Impero connection port (support will be able to assist with details / PM me) on the DA server firewall, which means when connected via DA, Impero doesn't connect at all. As it knows it isn't connected, the data will cache locally for upload when the device returns to the network. The other easy work around for some applications which simply need to resolve a host, where the host only has IPv4 is create an A record in DNS to forward the name to IPv4, removing the need to run the thing you're resolving on IPv6. Mic

@Andycat We'll be happy to work with you to get to the bottom of this. Please could you PM me your details, we'll be in touch ASAP. Thanks Mic

OK, thanks for the feedback. I'll speak with the team around adding this as a default.

We've previously been reluctant to suggest blanket adding dllhost as this is essentially a surrogate for running other processes. So anything running within this process we wouldn't inject. The more we understand about this, the less nervous we become and so it may be time to include this as a default. I'll speak to the team about the current defaults and look to add the below. In the meantime, here's the list we've this morning shared with @DCUK6 . If this proves to have a positive impact (it would be great if you could both feedback) i'll pass this back to the team to assist with the rest of our customer base. Thank you Mic Application: Description: fontdrvhost.exe Windows Font Driver Management dwm.exe Desktop Window Manager consent.exe User Account Control werfault.exe Windows Error Reporting dllhost.exe COM Surrogate

Ok, thank you for the update all of you. Will speak with the team to collate any reports of this that we have and see if we can spot some patterns.

@DCUK6 - there are quite a few thread around 'geek listing various different causes. A particular build of windows changed the behaviour of some DLLs which Impero didn't like, and Impero became one of those causes. We since fixed that (quite a while ago) and as far as we know now, this issue isn't caused by running Impero. If you are an Impero customer, please check the version number you're running (specifically on a machine you've seen the problem on). I can't remember off the top of my head which version the fix was in but it was around 6.0 or 6.1, and we're on 6443 now. If I can assist in moving you to the latest version please give me a shout. Mic @ Impero

Not convinced i'll be able to find anything beyond what you've already checked but i'll happily take a look next time i'm nearby; i'll give you a shout.

Shame i'm not around in Yorkshire this weekend Tim else I'd have had a look at it for you. @Jon and I have previously used Martin at Audioworks in Bentham, I reckon they'd sort it. It's about 2 hours from you though so you'd want to courier it, might not be economical. Website link here if it's helpful: Audioworks - Audio and Audio Visual - PA Systems - Induction Loop Systems - Installation - Lancaster Checking the internal fuses is a good shout and a quick easy thing to do just make sure you don't take a jolt from any caps while you're in there. If you're getting audio but not a lot of it, it sounds like it's not a fuse. Also check the monitor switch from the inside - bypass it to main as a test perhaps. The older version of this is on ebay for about £150 as a last resort, or the new version of it is £240 ex VAT. Thinking outside of the box, have you tried the monitor channel? If that works, you could mix on the monitor levels and output to another power amp (for less money than a powered mixer) and amplify the monitor output. Also, you didn't mention what you're putting through it; if you're using mics, do they need the phantom power turning on? Mic

Hi all, I can't add a lot to this but wanted to drop a note in that we're working with a couple of large RDS environments at the moment to reduce our footprint in the kind of deployment, with some great success, and continue to work with others to try and gain as much optimisation across various types of RDS environments covering as many variations as possible. Mic @ Impero