Just built 2 new Windows 2016 Servers with 9.5.7.90 server and client on one server and just the client on the other system to test installing a remote WebUI instance. WebUI fixlets are not showing relevant on the local server or the remote.
It looks as if all the relevance checks are not evaluating true.
Anyone else seeing this?
It should become relevant after time. How long did you wait as BES Support will have to gather and evaluate.
It has been over 24 hours.
Do you know which relevance is failing on the endpoint?
Fixlet ID 3102
Relevance 3 is showing an error in QnA
Q: version of registration server = "9.5.7"
E: No Inspector context
However the root server and the remote server are showing relevant for the fixlet now. I’ll give it a try and see what happens. That seem to be a really long time for the fixlet to become relevant.
That can’t be queried in QnA you’d have to do that using the client context. Restarting the client on the machine usually corrects that but it should correct over time as well.