• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 478
  • Last Modified:

2012 Publish legacy Apps

One of my clients has an legacy Application that only will run on XP. Compatibility mode doesn't work. They want to update their windows but need the legacy app. They don't want VDI. Is it possible to publish this app with Server 2012, so that it could run in a browser? If not does anyone have a solution?
0
WIZU2
Asked:
WIZU2
  • 2
1 Solution
 
Ayman BakrSenior ConsultantCommented:
If the legacy app won't run on OS versions higher than XP even with compatibility mode, then most probably it won't run as a published application on 2012.

We have faced a similar situation, and the reasons why the client would still need the legacy app is one or more of the following:
1. Resistive towards learning new things
2. Afraid that all the previous work won't be migrated to the new version or new app
3. No trust for any other app with newer technologies
4. Loyalty and attachment to the legacy app since he/she worked for years with it

The only solution I could think of, is to approach the vendor of the legacy app and see if they have a newer version, built into the newest OS, and check whether they will help in transferring/converting all the old work to be compatible and workable with the new app. You also need to approach your client to eliminate any concerns they have regarding the move to a new technology and address any needs they require (training for example) - you also need to explain to your clients the cost of keeping on the legacy app (lack of support, inability to move forward, eventually end of support for XP etc...).
0
 
WIZU2Author Commented:
Thing is to update the legacy software would cost clien 200K per year. That is why they don't want to upgrade. Has anyone tried to publish an old legacy app?
0
 
Ayman BakrSenior ConsultantCommented:
Thing is not about publishing the legacy app. It is about the architecture around which it was built on. So if you could make the legacy app run with compatibility mode on a Windows 7 for example then you would also be able to successfully publish it on Windows 2012, provided licensing is taken care of. Windows 2012 is the newer technology and architecture which built over Windows 2008 and 7. If you failed to run it in compatibility mode on Windows newer than XP then most probably you won't succeed in doing so while publishing it on Windows 2012. I say, "most probably" and this doesn't mean "definitely", so you could try and you won't lose anything.

However, your client makes it difficult: no upgrade, no VDI, yet wants to go for a newer Windows OS!! Some dollars have to go either here or there. You can't live foreover on a legacy app, especially on a business environment!!!
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now