locked
App-v vs xp mode RRS feed

  • Question

  • We currently run windows 7 x64 workstations and a certain application will only print to a printer that does not have x64 support. How can we run this app to where we can print to this particular printer with 32 bit drivers loaded? Would app-v do this or would we be able to load 32 bit drivers for this app to run in xp mode environment? Keep in mind I don't see this happening for more than 20 users/workstations.
    Tuesday, May 21, 2013 9:54 PM

Answers

  • App-V will not resolve this for you. So that's your answer in terms of this App-V Forum.

    Alternatively:

    The best path to go is to go to the vendor of the application and get a 64-bit version. Then use the 64-bit drivers that come with that.

    XP Mode is not scalable and manageable for an Enterprise environment. The Enterprise version is called MED-V which is a part of the MDOP suite, however this would be a band-aid solution and it's getting to the end of it's usefulness. Since it's for 20 users you could use XP mode but you need to ask yourself the question, how do you manage that XP VM? How to you ensure that's secure? Will it be on your domain?

    You need the application to be able to print from XP Mode which is a VM...so you'll need to ensure the VM has access to the printer.

    The drivers should load onto a 32-bit XP VM. Maybe you have a different Virtual Desktop solution which may be better than using XP Mode?


    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    Tuesday, May 21, 2013 10:44 PM

All replies

  • App-V will not resolve this for you. So that's your answer in terms of this App-V Forum.

    Alternatively:

    The best path to go is to go to the vendor of the application and get a 64-bit version. Then use the 64-bit drivers that come with that.

    XP Mode is not scalable and manageable for an Enterprise environment. The Enterprise version is called MED-V which is a part of the MDOP suite, however this would be a band-aid solution and it's getting to the end of it's usefulness. Since it's for 20 users you could use XP mode but you need to ask yourself the question, how do you manage that XP VM? How to you ensure that's secure? Will it be on your domain?

    You need the application to be able to print from XP Mode which is a VM...so you'll need to ensure the VM has access to the printer.

    The drivers should load onto a 32-bit XP VM. Maybe you have a different Virtual Desktop solution which may be better than using XP Mode?


    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    Tuesday, May 21, 2013 10:44 PM
  • This is all due to an in house app that prints to a forms printer that does not have a x64 driver as it is very old. It would be pointless to upgrade this printer with a 5k price tag, when eventually the software vendor is coding in for this application to print on laser. Obviously the virtual app would need to access a SQL database on the network, so yes connectivity is an issue.
    Tuesday, May 21, 2013 11:20 PM
  • Hello,

    More options (prolonging the problem...);

    1. Run a Windows Server 2008 (NOT R2) 32-bit server that hosts the software and provide it via RemoteApp / Xenapp / something else.

    2. Run a Windows Server 2003..... same as above....

    As you can see - getting this to work will most likely keeping something unsupported or close to, and soon to be, unsupported running for a long time.


    Nicke Källén | The Knack| Twitter: @Znackattack

    Wednesday, May 22, 2013 8:24 AM