Intel EMA alert on Meta Key

[phistrom]

When using the Remote Desktop feature of Intel EMA, if you press the meta key (a.k.a. Windows key or Command), an alert box appears saying "Key with code MetaLeft and key Meta not supported." This alert is pretty frustrating since, if I am in full screen, it yanks me out of full screen to prevent this message that I have to press OK on to dismiss before I can get back to what I was doing. Can this be converted to a banner, a tone, or maybe give a checkbox to disable this alert somewhere? I don't need the meta key to be supported. I just forget sometimes that I cannot press Windows Key + X or Windows Key +R, and now I gotta go dismiss this message.

To fix it myself, I went ahead and modified the file at C:\inetpub\wwwroot\ema.js

Just do a search for alert( in there. In my case, I found two entries like this:

alert(`Key with code ${code} and key ${key} not supported.`);

 and just add a // in front of each line that looked like that.

There appear to be alerts for other things, but I didn't touch those. Hope that helps someone. Maybe Intel can patch out that alert or modify it to be a banner or something instead of an intrusive alert(). Thanks.

[vij1]

Hello phistrom

Thank you for sharing detailed feedback regarding the Meta/Windows key alert during Intel EMA Remote Desktop sessions.

We understand how disruptive the current alert behavior can be—especially when it forces the session out of full-screen mode. Your suggestion to replace this with a non-intrusive banner, tone, or an option to disable the alert is very valid and aligns well with a better user experience.

We also appreciate you taking the time to identify the line in ema.js and sharing your workaround. While modifying product files isn’t supported and may be overwritten by updates, your input is extremely helpful for understanding the impact.

I’ve documented this as a feature enhancement request for our engineering team so they can review replacing the blocking alert() with a more user‑friendly notification method in a future release.

Thanks again for bringing this to our attention and for offering a clear workaround.

Best regards,

Vijay N.

Intel Customer Support Technician

https://intel.com/vPro