Hello Ajay, So I ran a few tests with different version of IS and different settings and still got mixed results. While you are correct that "This is why this is a bit tricky", however even when I was targeting x64 OS I got the same results. I understand the challenge in determining the targeted OS, as during capture IS simply extracts the MSI but is not being able to determine the targeted OS. I also understand that MS Sequencer captures the state of an actual MSI installation where the package is installed on a particular (x86 or x64) OS with and already determined Program Files location ... ie. when the application state capture occurs (final state), the application is already installed into the proper Program Files location (x86 or X64). However I would expect to see the same behavior in IS. When I use OS targeting under "App-V \ Package Information" to WIN7 (64-bit), I would expect IS to be able to determine from the four pieces of information that I provided, for a 32-bit app targetting a x64 platform: - Template Summary: Intel - 64-bit Component: No - INSTALLDIR: ProgramFilesFolder (would equate to Program Files (x86) based on above two settings and it does with the MSI install on X64 but not App-V capture) - Win7 x64 targeting in App-V \ Package Information (I'd expect this to dictate ProgramFilesX86 vs. ProgramFilesX64) Unfortunately, specifying targeted X64 OS does not change things. As per VFS mapping, indeed, as of App-V 5 SP3 I have noticed that root installs are mapped to VFS. The odd thing is that, when using VFS mapping in IS, the Program Files captures correctly as ProgramFilesX86 .... even WITHOUT targeting x64 OS (ie. targeting is set to all OS) So, as I mentioned, I ran a few test and here were the results. - SEQ 5 SP1 - NO OS targeting (ALL OS) - Result: - Captures to Root - FilesystemMetadata entry: Root="C:\Program Files (x86)\SomeApp" - SEQ 5 SP3 - NO OS targeting (ALL OS) - Result: - Captures to Root\ProgramFilesX86\SomeApp - FilesystemMetadata entry: Root="[GUID]" - IS 2013 Pro - VFS mapping NOT available - NO OS targeting (ALL OS) -OR- OS target set to Windows 7 64-bit - Result: - Captures to Root - FilesystemMetadata entry: Root="C:\Program Files\SomeApp" - IS 2015 Premier - VFS mapping NOT selected - NO OS targeting (ALL OS) -OR- OS target set to Windows 7 64-bit - Result: - Captures to Root - FilesystemMetadata entry: Root="C:\Program Files\SomeApp" - IS 2015 Premier - VFS mapping selected - NO OS targeting (ALL OS) - Result: - Captures to Root\ProgramFilesX86\SomeApp - FilesystemMetadata entry: Root="[GUID]" As expected both Sequencer 5 SP1 and SP3 captures correctly to ProgramFilesX86, however only IS 2015 with VFS mapping captured correctly to ProgramFilesX86. I am not sure if this is by design, but it is good to know that OS targeting has no effect in IS on INSTALLDIR when no VFS mapping is used. I have not tried targeted OS with VFS mapping, but I assume it captures correctly to ProgramFilesX86. Also good to know that at least now we can produce correct captures with VFS mapping. Thanks for your input. ... View more

Absolutely! We are implementing a continuous integration framework that has IS with App-V as one of its component. Developers can compile code and package (MSI and App-V) simultaneously with a single click of a button. Takes some effort to implement, though. Next ... is single click deployment of packages. The only major caveat is the AS 2014 and lower is missing a major function in the App-V virtualization feature, that we use on 80% of our packages. It is the Isolation Settings feature that allows COM interaction for App-V packages. MS Sequencer has introduced this long ago. The good news is that IS Premier 2015 already has this in place ... so I am eagerly awaiting for the arrival of AS 2015 to have the function available. 🙂 ... View more