HA! You know what our standard desktop looks like :) There are a ton of clinical web apps that have much more stringent browser requirements/limitations and I really don't want to get involved in that mess. We are a custom shop so our forms are typically much lighter than ITSM. The newer JavaScripting engines past IE8 will be welcomed but IE8 is doing ok for use right now.
Fortunately I found changing *arsystem.compatibility_view* from true to false in config.properties and restarting MT did the trick. I wish there was some documentation on this setting so I could see if there is some downside to doing this but so far things look good. Jason On Thu, Oct 30, 2014 at 5:03 PM, LJ LongWing <[email protected]> wrote: > ** > > I haven't investigated this thoroughly, but, I think it would be worth the > effort to work with your desktop team. It is my understanding that > compatibility mode is significantly slower than non, and that is the > primary reason that the message was instituted. > On Oct 30, 2014 5:44 PM, "Jason Miller" <[email protected]> wrote: > >> ** >> Hi Shawn, >> >> Did you get anywhere with this? We just upgrade our dev and QA to SP2 >> and are now seeing this (annoying) message. Our browser it highly managed >> and I really don't want to have to include our desktop team in order to >> update to SP2. I am not going to put SP2 in production without getting rid >> of this message though. >> >> Thanks, >> Jason >> >> On Wed, Oct 8, 2014 at 7:11 AM, Pierson, Shawn < >> [email protected]> wrote: >> >>> ** >>> >>> It looks like we found a defect in the combination of ARS and Mid-Tier >>> 8.1.2. It is happening with both IE9 and IE11. >>> >>> >>> >>> What happened is that after upgrading the mid-tier, we started seeing >>> this warning at the top of the screen: >>> >>> IE is running in Compatibility View. Please remove Mid-tier URL from >>> either IE Compatibility View Settings or Registry location. (ARWARN 9429) >>> >>> >>> >>> This is completely useless, because it’s not like the Remedy team or our >>> users have any say over whether we run things in compatibility mode or not, >>> so we added 9429 to our Suppress-warnings: list in ar.cfg. >>> >>> >>> >>> This worked great until we also upgraded the application server. Now >>> either Suppress-warnings doesn’t work or this specific error is impossible >>> to disable. We’re working with BMC support and they’ve been responding >>> quickly, but it appears they don’t understand the reason we don’t want that >>> error on the top of every single screen. Unfortunately, if we can’t find a >>> way to disable this, we’re going to be unable to upgrade. Hopefully BMC >>> recognizes the error of their ways and releases a hotfix soon. >>> >>> >>> >>> Do any of you have any ideas of how to suppress that message in the >>> meantime? >>> >>> >>> >>> Thanks, >>> >>> >>> >>> *Shawn Pierson * >>> >>> Remedy Developer | Energy Transfer >>> >>> >>> Private and confidential as detailed here >>> <http://www.energytransfer.com/mail_disclaimer.aspx>. If you cannot >>> access hyperlink, please e-mail sender. >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
