How to Manage the rollout of IE 9

So with the rollout of IE9 the same problem faces IT staff everywhere.  First, how many different key business websites or web apps will stop working if IE9 gets installed?  How do you manage the rollout especially when you’ve got update happy users who don’t seem to care that it will break functionality that they need to do there job so they just install everything WAU suggests?

Kaseya Connections to the rescue!  We’ve got a knowledge exchange write up of how to control the deployment of IE9.

Click here to read the post inside Kaseya Connections.

4 thoughts on “How to Manage the rollout of IE 9

  1. Hi, and thanks to ben the autor of this article.

    I think kaseya should write articles like this, not only the users/community!

    1. link not working… 🙁

      Server Error in ‘/’ Application.
      ——————————————————————————–

      Index was outside the bounds of the array.
      Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

      Exception Details: System.IndexOutOfRangeException: Index was outside the bounds of the array.

      Source Error:

      The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

      1. Add a “Debug=true” directive at the top of the file that generated the error. Example:

      or:

      2) Add the following section to the configuration file of your application:

      Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

      Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

      Stack Trace:

Leave a Reply

Your email address will not be published. Required fields are marked *