Hi there,

Does anyone have a clue why I am not able to install the Forefront UAG client components while using Internet Explorer 11 and Windows 10? It looks like there are additional security settings that have been changed on the os level. In Windows 8.1 everything works fine!

The bar that should have popped up requesting the installation of the activex component just does not show up. In the JavaScript console I see quite a few access denied messages. Also, inspecting one of the exceptions, it mentions something like "component cannot be created by automation layer".

Being able to use the Forefront UAG application portal is extremely critical to my daily workflow. I hope there is a simple remedy available. In the meanwhile I will need to keep Windows 8.1 around.

I've got it working!

I fiddled a bit in the F12 developer tools emulation settings with the following:

 Document mode 11 (or 7???)
 Custom string: Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko

And suddenly it went installing the client componenten???

Albeit that the first screen still stays. But one can click through the message and then the applications suddenly show up correctly.

I have got the feeling that the server components don't process the Windows NT 10 part of the user agent string correctly???

I've got it working!

I fiddled a bit in the F12 developer tools emulation settings with the following:

 Document mode 11 (or 7???)
 Custom string: Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko

And suddenly it went installing the client componenten???

Albeit that the first screen still stays. But one can click through the message and then the applications suddenly show up correctly.

I have got the feeling that the server components don't process the Windows NT 10 part of the user agent string correctly???

• Proposed as answer by DJITS 21 hours 57 minutes ago

I've got it working!

I fiddled a bit in the F12 developer tools emulation settings with the following:

 Document mode 11 (or 7???)
 Custom string: Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko

And suddenly it went installing the client componenten???

Albeit that the first screen still stays. But one can click through the message and then the applications suddenly show up correctly.

I have got the feeling that the server components don't process the Windows NT 10 part of the user agent string correctly???

• Proposed as answer by DJITS Tuesday, August 25, 2015 9:28 AM

I've got it working!

I fiddled a bit in the F12 developer tools emulation settings with the following:

 Document mode 11 (or 7???)
 Custom string: Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko

And suddenly it went installing the client componenten???

Albeit that the first screen still stays. But one can click through the message and then the applications suddenly show up correctly.

I have got the feeling that the server components don't process the Windows NT 10 part of the user agent string correctly???

• Proposed as answer by DJITS Tuesday, August 25, 2015 9:28 AM

Hi Carl,

Thank you for the info. It worked for me.

Regards,

DJITS

Great! Have you heard anything back from your server colleagues? Is there something they can do to fix it server-side?

just as a work arround, on server-side you can edit the web.config file under PortalHomePage and InternalSite and insert in Windows8 section following:

OR UserAgent Contains "windows nt 10.0"

It works for me.

I remember, It's quit the same issue as Windows 8.1 and IE11 was released...

• Proposed as answer by DJITS 19 hours 57 minutes ago

Hi SteffenRak,

Thanx for this. It works.

Our users will be happy.

Regards,

DJITS.

just as a work arround, on server-side you can edit the web.config file under PortalHomePage and InternalSite and insert in Windows8 section following:

OR UserAgent Contains "windows nt 10.0"

It works for me.

I remember, It's quit the same issue as Windows 8.1 and IE11 was released...

• Proposed as answer by DJITS Friday, August 28, 2015 11:31 AM