Vista Bleed, Non-Admin & Cost of COTS Print E-mail
  • Vista Bleed
    How many times has your company REALLY held the line on not going to the next version of Windows before you were ready? You remember when sales had to have XP Tablets before your W2K deployment was complete? How about when R&D needed NT 4 while everyone else was on 98. Eventually you'll get that call "We're having problems getting our 5 year old, mission critical application running on Vista/Win7." while you're thinking "They aren't supposed to be installing Vista/Win7 yet!" Be prepared for what you know will really happen in your company.
  • Moving to Non-Admin Users
    Some organizations are using the upgrade to Vista (or Windows 7) as a time to reevaluate whether they can finally take admin rights away from users. Under Windows XP this was mainly a question of file and registry permissions. For applications where this is the simple case, Vista does intelligent, on the fly virtualization (redirection). Depending on the application, however, there are other areas of application interoperability where Vista has tightened up on what can and cannot be done even with admin rights. Knowing how to analyze the underlying API calls allows non permissions problems to be isolated and mitigated. Application Compatibility Toolkit includes mitigation shims for many of these APIs. It also includes redirection (file / registry virtualization) for areas not covered by Vista's built-in virtualization.
  • Unnecessary COTS Upgrade Costs
    Most times vendors roll Vista support into an upgraded version - they are understandably reluctant not to invest in an old code base. If the release is a major one, there may be upgrade costs and expensive user re-training costs as well. Understanding the free tools available in this space may allow you to make your current versions run properly. Across all of your applications this can result in a snowball effect for Desktop project budgets.
  • Qualifying & Troubleshooting Fixed Applications
    If you are dealing with a large application portfolio, even the best efforts by service providers and framework tools will yield some results that don't work as advertised. With the rights skills and tools you can qualify applications that have been fixed and you can provide helpful troubleshooting knowledge if you need to run an application through again.
  • Internally Written Applications
    Applications that have been written by your company may still require special testing and troubleshooting - especially if your service provider or framework tool depends on a general knowledge base of applications that are commercially available.