App Rationalization Considerations

If you have gone through a recent M&A, or haven’t had to clean up your application inventory list since the move to XP, (or both), you know that you’re going to have a huge amount of applications in your list that you’re going to need to shrink down before you migrate. Most of the inventory collection tools out there are going to crawl through your environment and provide you with a list of your applications mixed in with every O/S update, driver and security patch you’ve deployed in the last several years. While it’s obvious that a lot of this stuff can go in the trash, what about the rest of it?

To help you pare that pile down, you need to be able to identify where you have multiple versions of the same application. You know those calls to the help desk where someone can’t open a PDF file, and you eventually determine that the user is running Acrobat 7 while the rest of the organization is on 10.x? Well there’s no good excuse for why that situation should carry forward when you move to Windows 7. I know that you already know this, but it’s in your best interest to clean up as much of that mess now while moving to your new O/S so that it makes your life a little bit easier after the project has ended. Find those stragglers and get rid of them!

While the problem is much worse when merging the IT departments of two discrete organizations, you no doubt have multiple applications that are performing the same function. Identifying these applications is not overly difficult, but it is incredibly time consuming to do it manually.

The rationalization reports within AppRx can do this for you quickly. You can export the reports into PDF, CSV or Excel docs, and then head over to the application owners to chat about what can stay, and what can go.