Like many things, you tend stand by what you know and what is easy. Depending on your org/industry, IE is either easy or its hard. In my experiences, newer versions of IE typically have the most problems with backward compatibility in comparison to other browsers - and because of those compatibility issues, its easiest to rollback to a earlier version until all issues are known to be resolved. Otherwise you can be open to a prolonged tweak and upgrade battle.
Compatibility issues insure a loss in end-user productivity, resulting in a loss in IT-support productivity, which always cascades the perception of incompetence. If you want to have less work for yourself, and less issues for your users: rollback to an earlier version until stability has been achieved for at least 90 days. Follow vendor recommendations. Depending on your industry this type of thing is obvious and common, or rare and obscure. I've seen both and would say that hospitals and mechanically-related industry get snagged by IE versions the worst. Regardless, I find it advantageous for any org to error on the side of caution. -- Espi On Mon, Oct 14, 2013 at 6:03 PM, James Hill <[email protected]>wrote: > I’ve stood by IE for quite a while as I watched many sing the praises of > Chrome, Firefox etc.**** > > ** ** > > But IE11, well, so many sites don’t work with it. They seem to have > completely removed the compatibility button so now the average user has > even less chance of getting it working than they did before. Compatibility > mode is still there but it requires more clicking to enable it.**** > > ** ** > > It doesn’t work on many sites, it isn’t user friendly and it will just > drive the remaining few supporters away. I’m sure it’s because now IE > follows some standard and the websites don’t but end users don’t care about > that. They’ll just use whatever works.**** > > ** ** > > James.**** > > ** ** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Micheal Espinola Jr > *Sent:* Tuesday, 15 October 2013 4:01 AM > > *To:* [email protected] > *Subject:* Re: [Exchange] OWA and IE 11**** > > ** ** > > For everyone's sanity and security, I recommend simply downgrading IE. I > cant recommend it more strongly enough for compatibility as well as > security reasons.**** > > > **** > > -- > Espi**** > > **** > > ** ** > > On Mon, Oct 14, 2013 at 10:49 AM, Damien Solodow < > [email protected]> wrote:**** > > Yep, but IE 11 comes with Windows 8.1 and I’m anticipating at least a > few users updating their home PCs shortly after the 18th and wanted to > see if I can avoid the headache.**** > > **** > > DAMIEN SOLODOW**** > > Systems Engineer**** > > 317.447.6033 (office)**** > > 317.447.6014 (fax)**** > > HARRISON COLLEGE**** > > **** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Micheal Espinola Jr > *Sent:* Monday, October 14, 2013 1:46 PM > *To:* [email protected] > *Subject:* Re: [Exchange] OWA and IE 11**** > > **** > > This doesn't directly help you - but I wouldn't recommend upgrading to a > new browser version until at least 30 days after a proper stable release. > IE11 is still RTM/Gold, and should be avoided unless absolutely necessary. > **** > > > **** > > -- > Espi**** > > **** > > **** > > On Mon, Oct 14, 2013 at 10:35 AM, Damien Solodow < > [email protected]> wrote:**** > > I know there is an issue with OWA Premium and IE 11 (KB2866064) and it > looks like there is a fix for Exchange 2013.**** > > **** > > Anyone know if there is a planned fix for Exchange 2010 or is it “upgrade > slacker”? J**** > > **** > > DAMIEN SOLODOW**** > > Systems Engineer**** > > 317.447.6033 (office)**** > > 317.447.6014 (fax)**** > > HARRISON COLLEGE**** > > 500 North Meridian St**** > > Suite 500**** > > Indianapolis, IN 46204-1213**** > > www.harrison.edu**** > > **** > > **** > > ** ** >
