Report: Microsoft Planning To Add New ‘Enterprise Mode’ In Internet Explorer 11

Microsoft is not just fixing and tweaking Windows 8.1 to better serve enterprise users, there is another important component for enterprise which is Internet Explorer. Lots of enterprises depend on IE everyday for their legacy and custom built internal apps. Since Windows 7 shipped with Internet Explorer 8, it became the de-facto standard for designing apps. Microsoft has released Internet Explorer 9, 10 and 11 versions for Windows 7 after that. Often, these latest versions breaks compatibility with sites designed for Internet Explorer 8. ZDNET’s Mary Jo Foley today reported that Microsoft is working on a new Enterprise Mode feature in IE11 that will allow enterprises to run their websites and custom apps in IE8 mode.

There may be a Microsoft-made solution to this dilemma, however. Sources say it’s a new IE feature known as EMIE.

Enterprise Mode for IE (EMIE), as it’s referred to internally, is supposedly going to be a new feature of IE11. According to my sources, EMIE will allow businesses to specify which sites should be loaded in IE8 compatibility mode and which don’t need it. Users who need IE8 to view certain intranet sites and internal apps would still be able to move to┬áIE11 on Windows 7 (or Windows 8.x) thanks to the new compatibility mode functionality. But they still would be able to make use of all the rest of IE11’s features the rest of their browser needs.

As long as Microsoft is giving the choice, I’m totally fine with it. What do you think?

Source: ZDNET

  • BeefNeeg

    How bout getting rid of the need for Compatibility mode on half the web sites I visit. i cant use UI. Firefox is better for porn. I like whackin!

  • freeman

    Yet another dumb compatibility mode that developers need to look at. Haven’t Microsoft listened to the development community who say support free & open standards that just work. This same old failed model sucks & is the primary reason developers hate IE but love chrome. All other browsers Chrome, Safari, Firefox & even Opera don’t need stupid compatibility modes as they historically supported standards.

    • Cormang

      This isn’t intended for the average website. This is intended for those who require access to outdated web applications which were designed for Internet Explorer 8. Its a very common problem for users of the enterprise rely on outdated web applications that were built only for IE. As of IE9, many standards were adopted by the browser causing web applications to break. The compatability button is available but not many users know about it. So we push a list of websites to users computers to automatically load the website in compatability mode. It drastically cuts down Helpdesk calls.

      • freeman

        Really, you do know that every version of IE since 6 has had a compatibility mode. Some with multiple.

        This just for enterprise users is garbage. I have written web apps for consumers that need this poorly designed work around. IE even have meta tags for site devs to switch modes. Most users don’t even know that sites they are visiting are running in an out of date browser mode.

        The problem Microsoft have is this is the second largest reason developers hate IE and why its reputation is in the gutter. I have written web apps for Chrome 4 & Firefox 3.5. They still work today in the latest versions of these browsers. No need to update code no stupid compatibility mode .

        • Cormang

          I don’t understand what you’re arguing. I’m a web developer and I have no reason to worry about a “compatibility mode” button in IE. I don’t understand why it’s a bad thing to have a compatibility mode. It doesn’t affect modern web applications that adhere to standards. It in no way affects modern web apps.

          Compatibility mode is required in the enterprise. Many legacy web applications were built for older versions of IE. There’s nothing we can do about it. It has nothing to do with modern web developers. But for Enterprise users, it’s an absolute must have. For example, older versions of SAP on the web require IE8 compatibility mode. In order for the users to visit the website, they must have their browser in compatibility mode. Telling the users to press the “broken page” icon is confusing. To get around this we use Group Policy Preferences to push a list of domains to each client computer on the domain. This list forces IE to automatically load the webpages for a particular domain in compatibility mode.
          Compatibility mode has nothing to do with modern web design. And it’s off by default for all websites unless you specifically ask IE to load a website or domain in compatibility mode (with the exception of Intranet sites). Removing this feature would halt the majority of Enterprises from upgrading to the latest version of IE. It makes no sense to remove this option as it provides no benefit to standards. Removing it would only hurt those who require access to older applications.

          I fail to see how Microsoft including the option to push domains to the compatibility list would cause any problems for any modern web developer. It’s never been a problem for me as my web apps never require it anyway…

          • freeman

            This is the prime example of what in reality what are Microsoft exclusive developers who claim to be web developers don’t see outside their blinkered viewpoint.

            Compatibility view in IE is a poor workaround for a self inflicted.problem basically non standard.code.

            Most enterprises certainly most enterprise software is supporting standards compliant code so the work across the desktop and mobile platforms. To say enterprises won’t upgrade due old software is nonsense. If anything its allowing some backward thinking companies avoid upgrading old non standard code.

            Typically Microsoft though thinking inside.their own box. What happens to companies not using Microsoft’s solutions to admistrate. How do they apply this.

            What’s even more alarming however is the basic grasp of what even why we use web apps. The example you use is SAP. However SAP allows any user to login from a.machine not subject to any policy or windows account. You tell me how I roll this out to that user.

            What compatibility mode should tell any enterprise is don’t no standards code and don’t build your platform on non standard browsers.

            I built a.system for Chrome 4. It still runs today on Chrome 32. No dumb idea.orlf.rolling out browser compatibility polices across a site. Its laughable.

          • Cormang

            I still have no idea what exactly you’re trying to argue. Are you trying to say any legacy applications which were poorly written but have massive dependencies should be forgotten? You’re not making sense. What exactly are your trying to say? Why is offering compatibility mode database to Enterprise users a BAD thing? What makes it bad?
            We have a list of 20+ domains in which require compatibility mode. None of these domains are applications developed or maintained by our company. These include distribution, shipping, government, and municipal applications which are required for those to procure material, bid jobs, download data, or abide by local law. The Enterprises can’t control how their suppliers, customers, or governments maintain their web applications. If it’s outdated, but required, then they still have to use it.
            Providing administrators a quicker way to publish a compatibility list for IE isn’t bad. It in no way affects web development going forward. This isn’t making anything worse.
            You can try the web standards argument all you want but I’m not really sure what you’re arguing. I have no idea what you’re talking about Chrome for? I developed web apps in the 90’s and they all still work too! It’s laughable, you’re right! So what?
            We all know IE is slow to adapt web standards. Is that all you’re trying to say?

          • Mantis Toboggan

            I don’t think you understand “most enterprises”. We only just recently rolled out IE9 and had to exclude 3000 users from the upgrade because they use a website that only works on IE8. We don’t maintain this website, it is some crappy company that we pay to provide their crappy website. They are working on IE9 compatibility but it isn’t ready yet. This is the kind of real-world crap that enterprise admins have to deal with. It’s not about you as a web developer at all. Web developers should ignore compatibility mode and focus on web standards. Compatibility mode is to allow me to bring those 3000 users into this decade.

  • Cormang

    You can already do this using Group Policy Preferences by pushing registry keys. It works extremely well. I already use the same method to add domains to the trusted sites zone. I guess they just plan on adding a Group Policy Object to make it easier..

  • Luke Murphy

    When does this come out, anyone know? There seems to be very little information regarding this, but sounds very interesting and I want to test this out in my company. =)