We're talking about things like JD Edwards (ERP), Livelink by Opentext (ECM), our accounts payable system which is a wrapper that combines third party code with a program that integrates that code with the JDE pages.
We only have one single third-party document management app that's reliant on that crawling horror for some bloody reason, and it's the only thing preventing us from rolling out Firefox (and a damn nicely customized, extended, and AD-manageable build of it too). We're slowly but surely phasing all AX content out of our internal website.
Not to knock on you, but why IE at all? Why ActiveX? Why a non standards-compliant browser? You could have done something other than AX during your initial deployment and not been in this boat. To do all that work there's me and my junior admin and a few QA folks and we have to make sure it's as bulletproof as the existing farm has been for the last 3.5 years for our ~800 users. But it will probably take about 6 months between building the new master image, full regression testing with QA, and user acceptance testing with the business and then deploying the new farm and decommissioning the old farm. In the last 6 months or so we have finally been able to upgrade a few of those major apps to point release updates (combined with hardware replacement of the hosting servers) that finally offer support for IE7 and so we are now going through the process of doing a rebuild of our Citrix farm with IE7. Of course, it will also never occur to these sub-simians that they can employ virtualization on the desktop to get around their prior stupidity.Ī lot of it isn't that we built it, it's that we bought it, 3.5 years ago when IE7 was just being released and so wasn't on the current versions supported apps list.
Short-sighted idiots build critical apps around a poor product from a single vendor.
0 kommentar(er)
