So you want to re-use the packages already built on a 32bit OS?? In some cases the packages will work, but once they get a little more complicated and have more requirements (for example the Oracle client just caused me issue, etc etc). They may no longer work.
My Problem: App-V variables for file path
The App-V Sequencer and client use Windows “well-known” paths such as
%ProgramFiles% for a 32bit computer as “C:\Program Files” but on a x64 computer this is “C:\Program Files” and there is also %ProgramFiles(x86)% which is “C:\Program Files (x86)”.
With the client doing the substitution when the software installs then it can go to the wrong location and break internal links and references…
And before you ask, no you cannot change these settings. So you may need to update your source program BEFORE you sequence it.
Additional to this is the registry can cause issues, that has not affected me yet, but read the following article for more information. Oh and good luck…
Note: App-V 4.6 supports x86 and x64 bit applications on x86 and x64 operating systems.
Note2: Supported platform matrix:
Really good details are here:
http://blog.gridmetric.com/2011/09/26/possible-caveats-in-mixing-32-bit-and-64-bit-app-v-packages-and-environments/
Story about App-V 64 bit support:
http://myitforum.com/cs2/blogs/kkaminski/archive/2010/02/22/app-v-4-6-64-bit-application-support.aspx
No comments:
Post a Comment