One of the questions I’ve been discussing a lot lately, both internally and with customers, is how to go about disabling the default Compatibility View for the Local Intranet zone. Customers really want to disable this option! But you certainly can’t do that at the expense of compatibility.
These are the two considerations we’ve come across so far, but it’s not even been two months yet, so it’s still early days. I think it’s potentially really interesting to remove the old-by-default configuration and I think we’ll win, and I’m super curious to understand what you discover if you find this to see if there is something I can advocate for you or some solutions we can come up with. Don’t hesitate to reach out to me either via comments here or the “Email Blog Author” link if you’re trying this and have experiences to share!
The other interesting side-effect of this approach is that it further consolidates your list of “dependencies on old stuff” – which you can then manage down gradually! Basically, it becomes your to-do list. Some sites are going to be removed from the list because they just plain go away. Some will be removed when new versions are done. But no doubt there are some that will continue to live on and yet don’t have a modernization plan. Now you have that information in front of you, and you can consider the business value of modernization versus the cost, both individually and in aggregate. You can do some hard thinking about your portfolio as a whole, and it truly becomes a to-do list as you charge towards what I hope is one of your goals: restoring technology agility by removing the shackles of legacy software.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.