-
1. Re: Console Install for 2016.3 fails on windows 10 1709
Could you provide more information as to what's failing? There's no inherent incompatibility with 1709.
-
2. Re: Console Install for 2016.3 fails on windows 10 1709
I'm on 1709 and have installed the console for 2016.3 installed multiple times without issue. What's stopping the install?
-
3. Re: Console Install for 2016.3 fails on windows 10 1709
Ryan, the guy that had the problem couldn't remember the error. He wiped his computer and is installing windows 10 again.
-
4. Re: Console Install for 2016.3 fails on windows 10 1709
timeconsumer, we think it is because 1709 had .net 4.7. we are still trying to find whats causing the problem.
By the way we just tried it on another Windows 10 version 1709 that had .net 4.7 and it is failing at installing Data Analytics which is something we don't use.
-
5. Re: Console Install for 2016.3 fails on windows 10 1709
The DA install issue is a known one that's fixed in 2017.3. Here's a doc explaining it and a workaround script:
https://community.ivanti.com/docs/DOC-47883
Essentially the installer just
-
6. Re: Console Install for 2016.3 fails on windows 10 1709
Ryan, I'm marking your answer as Correct but that's only 90% of the fix. Once you follow that doc it lets the install finish.
However when opening the console you get "The Strong name Verification System contains exclusion entries in the registry, blocking access"
To fix this do this: Strong name verification system contains exclusion entries in the registry. Blocking access
