DELInstallations said:I can't fault Elk with this completely. Yes W10 has been beta for a while, but in the same breath, how many pieces of hardware have you run across that won't work on W10....I've got a pile of them. W10 literally just dropped and the major's out there are staying away for at least the first quarter while MS and others work on the bugs and what has been found so far. Unfortunately, until the final was made public, it's all conjecture to put a compatibility together.
There is the option to use the developer section in W10 to run a VM of an earlier version. I want to say there was a few good links out there with how-to's.
How the changes affect the XEP and M1 is a different question, as the hardware could use a little update itself. Been out for over 10 years.
This is not a hardware driver problem though, it's just dropping support for an insecure SSL/TLS version and insecure certificates. The major browsers all did it at least a year ago. Elk just didn't have the presence of mind to see the writing on the wall. And I'll see if I can find it, but I'm sure at some point Microsoft made an announcement that they were dropping support. The various SSL/TLS vulnerabilities have received plenty of media attention so there's no excuse for them not to know.
I couldn't agree more that the M1XEP needs a hardware update, as clearly Elk is struggling to squeeze in features (they dropped the Virtual Keypad in order to be able to find enough room to add M1Cloud support). There is a third party module out there http://www.setechautomation.com/category-s/1817.htm that is supposedly 2-3 times faster than the M1XEP and claims it uses a 1024 bit RSA key. I'm not sure if it will still suffer from the same issues, but from what I recall you lose IP monitoring and M1Cloud support.
Maybe if we get a a new M1XEP we'll finally get IPv6 support (hah!)