IE11 now available for Windows 7

[dhoward_westexetc]

All we know for certain is that there won't be a fix for 2003.

 

There's actually been no announcement that there will be a fix for 2010, it's just an assumption that they will fix it at some point. 2007 and 2010 are still supported products, so it's reasonable to expect there will be a fix in the next cumulative update.

 

I hope this turns out to be the case. Many thanks.

[speckytecky]

What's the general feeling on Edugeek now about IE11 - we blocked IE10, is the recommendation to also block IE11 or is it going to be ok with proxies etc?

[edutech4schools]

Blocked on server as that killed proxy but 10 and 11 are fine for my schools on client computers. We also use Chrome as an alternative.

[dhoward_westexetc]

What's the general feeling on Edugeek now about IE11 - we blocked IE10, is the recommendation to also block IE11 or is it going to be ok with proxies etc?

 

I have an open call with the SWGfL regarding staff proxy not working correctly, IE 10 works fine.

 

We're deploying IE 10 at the moment as that works but not IE 11.

 

I always test new IE versions anyway before I deploy them to find the issues.

[Michael]

I would highly recommend you test, test and test again. I've also checked every other day and Microsoft still haven't published IE11 to WSUS. This is a better way rather than using the blocking tool as you can easily reverse the policy once you wish to deploy IE11.

[DrCheese]

*shrug* I don't test/test/test chrome updates

 

With IE updates tho, I tend to deploy to a bunch of machines in stages, i.e the staff workroom and one or two computer labs. Leave it a week or two then deploy it everywhere. It honestly doesn't bother me nowadays - Worst case I just undeploy it on the machines that have software that has issues with it (usually SIMS)

[dhoward_westexetc]

All we know for certain is that there won't be a fix for 2003.

 

There's actually been no announcement that there will be a fix for 2010, it's just an assumption that they will fix it at some point. 2007 and 2010 are still supported products, so it's reasonable to expect there will be a fix in the next cumulative update.

 

Update Rollup 3 for Exchange 2010 SP3 now fixes the OWA Premium issue on IE 11. Can't load OWA Premium by using Internet Explorer 11 in an Exchange Server environment

 

Just Exchange 2007 SP3 to go now!

[DrCheese]

It's on Windows update catalog now if you want to import it manually.

[Michael]

Heads up - IE11 is now on WSUS on page 2

[dhoward_westexetc]

I may do that once they fix the OWA issue for Exchange 2007 SP3 and when I hear back from the SWGfL regarding staff proxy.

[Michael]

When you import the Update Rollups, they're Not Approved by default, but I would recommend you search and decline the update in WSUS for the time being.

[dhoward_westexetc]

When you import the Update Rollups, they're Not Approved by default, but I would recommend you search and decline the update in WSUS for the time being.

 

The latest update rollup for Exchange 2007 SP3 is 11, which we have already installed and does not contain the fix for the user agent string. I am hoping that MS release update rollup 12 soon, and that it contains that fix.

[Mark182]

I may do that once they fix the OWA issue for Exchange 2007 SP3 and when I hear back from the SWGfL regarding staff proxy.

 

Have a look at this

 

Link to the MS KB article.

 

 

 

Can't load OWA Premium by using Internet Explorer 11 in an Exchange Server environment

[dhoward_westexetc]

Have a look at this

 

Link to the MS KB article.

 

 

 

Can't load OWA Premium by using Internet Explorer 11 in an Exchange Server environment

 

Thanks @Mark182, but I have already seen this. I am hoping that they will actually change OWA in Exchange 2007 SP3 instead of relying on compatibility mode. I could do compatibility mode though if push came to shove.

Edited November 27, 2013 by dhoward_westexetc
Changed last sentence

[Mark182]

Ah no worries

[dhoward_westexetc]

Thanks for the thought all the same. I will keep an eye on that KB article and the Exchange Team Blog, so if I see something I will post on here. Edited November 27, 2013 by dhoward_westexetc
changed 2nd sentence, improved

[Michael]

The latest update rollup for Exchange 2007 SP3 is 11, which we have already installed and does not contain the fix for the user agent string. I am hoping that MS release update rollup 12 soon, and that it contains that fix.

 

I think your options are either block IE11 via WSUS or deploy IE11 with the hassle of setting Compatibility View settings. As far as I know, you cannot deploy an exclusion list of URLs via GPO or GPP, as you can say the popup blocker for example.

[Gatt]

I think your options are either block IE11 via WSUS or deploy IE11 with the hassle of setting Compatibility View settings. As far as I know, you cannot deploy an exclusion list of URLs via GPO or GPP, as you can say the popup blocker for example.

 

This is another reason why I like SCCM - you control what can and cannot be sent out to client machines. Especially when you combine it with a GPO to disable users going to Windows Update as well, thereby forcing them to get their updates from SCCM

[Arthur]

As far as I know, you cannot deploy an exclusion list of URLs via GPO or GPP, as you can say the popup blocker for example.

There's a GPO called Use Policy List of Quirks Mode sites which can force IE11 to use IE7's user agent string.

 

Before

Mozilla/5.0 (Windows NT 6.1; Win64; x64; Trident/7.0; rv:11.0) like Gecko

 

After

Mozilla/4.0 (compatible; [color="#FF0000"]MSIE[/color] 7.0; Windows NT 6.1; Win64; x64; Trident/7.0; .NET CLR 2.0.50727; SLCC2; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; Tablet PC 2.0; InfoPath.3)

[Michael]

Thanks Arthur, I've never looked at that policy properly. It's still not clear whether it'd work with Exchange 2013, as it runs in IE7 Compatibility Mode essentially.

 

It would be nice if Microsoft allowed us to specify the version of IE when specifying Compatibility Mode. IE7 may be too old, but IE9 or IE10 would most probably work.

[Arthur]

It's still not clear whether it'd work with Exchange 2013, as it runs in IE7 Compatibility Mode essentially.

OWA Premium is supported for IE7 with Exchange 2007 & 2010, just not with Exchange 2013.

 

http://i.imgur.com/TH2JOl3.png

Edited November 28, 2013 by Arthur

[Michael]

OWA Premium is supported for IE7 with Exchange 2007 & 2010, just not with Exchange 2013.

 

http://i.imgur.com/TH2JOl3.png

 

This is what I mean - All Office 365 installs are now based on Exchange 2013. Only admins with in-house Exchange servers have more flexibility, however I still think IE11 is better blocked until early 2014 at least. It doesn't really offer anything above IE10, other than hardened security. I've not had the chance to look at it in detail.

[kennysarmy]

Just to double check : our WSUS does not syncronize "Update Rollups" - so does this mean we will be safe from WSUS presenting IE 11 to our windows 7 clients?

 

Thanks

[glennda]

All i have done the last few days is remove ie11 from peoples machines who it causes conflict with various websites!

[Michael]

Just to double check : our WSUS does not syncronize "Update Rollups" - so does this mean we will be safe from WSUS presenting IE 11 to our windows 7 clients?

 

Thanks

 

That's correct, but I would still recommend you import it and decline it yourself. You'll then have absolutely no worries of it suddenly being deployed.