/build/static/layout/Breadcrumb_cap_w.png

APP-V MSI

Hi,

I'm just after a little knowledge and understanding so hope you can help.

When a package is packaged up as an APP-V package you also get the MSI in the output.
What I'm after is how the MSI works?
Does it run in a virtual environment like an SFT file would, essentially running in a virtual bubble, or does it just run the same as a physical MSI, cretaing files \ folders and writing to the registry etc.
If you have links to docs that would be great.

Thanks
in advance

0 Comments   [ + ] Show comments

Answers (11)

Posted by: rajdera1 13 years ago
Orange Belt
0
The msi created is basically for a stanalone enviorement which does not have a streaming server but the app-v client should be installed on the machine check out this link
http://www.tmurgent.com/WhitePapers/Microsoft_AppV_Stand-Alone.pdf

you need to supply some command line override commands to run the msi
Posted by: skylizard 13 years ago
Senior Yellow Belt
0
Thanks for the link rajdera1, much appreciated.

Could you confirm: My understandng is (in a stand alone \ Download and execute environment) that if you deploy a Virtual MSi say through SCCM, it will still download and cache the SFT file as well, is that a correct assumption?


thanks
again
Posted by: SeeQuench 13 years ago
Senior Yellow Belt
0
This thread might help you:
http://www.myitforum.com/forums/m206237-print.aspx
S
Posted by: skylizard 13 years ago
Senior Yellow Belt
0
Thanks for the replies guys, it helped find what I was looking for.... cheers
Posted by: charles123krik 13 years ago
Senior Yellow Belt
0
The Application Virtualization (App-V) Sequencer creates applications that can be run in a virtual environment. Geting is likely that "not valid" message just because you're trying to import from network share on the App-V client processes (ie, services that run on the system) triggered by the command sfttray sftmime / can not access. MSI container actually extract the package files (with the exception of TSP, of course) to your local computer, because this way you will unfortunately have the source files locally before importing.
Posted by: knevr 13 years ago
Senior Yellow Belt
0
APP-V MSI enables the distribution of virtual application. It provides virtualization without streaming. Still the deployment and configuration is now easy, it is bit complicated. The only benefit is virtualization, rest of the steps are same as usual. Not much specific information is available. It is difficult to configure the setting correctly. More user friendly documentation is required to use the software easily. It can be recommended for future use.
Posted by: arnolddepth 12 years ago
Yellow Belt
0
Traditional desktop transformation project APP-V eliminate the burden of many projects related to users and applications barriers. IT managers can migrate to new desktops faster and with less risk, critical applications, while providing a consistent end-user experience across all platforms.
Posted by: rock_star 12 years ago
4th Degree Black Belt
0
Try to open msi with Orca or whatever tool you use.


Go to Custom Action table. You will get good idea about what it does :)
Posted by: staycygills 12 years ago
Yellow Belt
0
The computer must have read access to the L: drive and the share its mapped to.
Posted by: angelinadepth 12 years ago
Yellow Belt
0
The software can also analyze the organization own environmental applications, which will produce higher quality results and recommendations of the repair, which means a higher accuracy than manual testing.
Posted by: sivaiah_b 12 years ago
Orange Senior Belt
0
Hi all
I am sequencing autodesk design Review 2008 and version is 4.1.0. when we publish shortcut is working fine.when we come to FTA's ".DWF",".DWFX" those are launching fine but after some time (after 15 to 20 minutes)those giving the error message.

ERROR MESSAGE:


---------------------------
Application Virtualization Error
---------------------------
The Application Virtualization Client could not launch Autodesk DWF Application 8.1.0.87.



The application took too long to be ready to interact with the user, possibly because the system was too busy. Try again in a few minutes. If the problem persists, report the following error code to your System Administrator.



Error code: 4615186-0B01FD04-0000041E
---------------------------
OK
---------------------------

and we observe the following info in SFTlog.txt

[01/25/2012 12:42:08:810 ???? INF] {tid=15C4:usr=fbdadmin01}
An error occurred while opening the virtual registry (section: 9), rc: 07B01F0C-0000004A


[01/25/2012 12:42:08:873 ???? INF] {tid=15C4}
An error occurred while opening the virtual registry (section: 9), rc: 07B01F0C-0000004A


[01/25/2012 12:42:08:904 SWAP INF] {hap=2A:app=Autodesk Design Review 8.1.0.87:tid=15C4:usr=fbdadmin01}
Elapsed time for upload: 0.219 seconds


[01/25/2012 12:42:10:232 SWAP INF] {hap=2A:app=Autodesk Design Review 8.1.0.87:tid=15C4:usr=fbdadmin01}
Elapsed time for launch: 1.719 seconds


[01/25/2012 12:43:55:089 SWAP INF] {hap=2A:app=Autodesk Design Review 8.1.0.87:tid=15C4:usr=fbdadmin01}
App shut down


[01/25/2012 12:43:57:454 ???? INF] {tid=1308:usr=fbdadmin01}
An error occurred while opening the virtual registry (section: 9), rc: 07B01F0C-0000004A


[01/25/2012 12:43:57:485 ???? INF] {tid=1308}
An error occurred while opening the virtual registry (section: 9), rc: 07B01F0C-0000004A


[01/25/2012 12:43:57:495 SWAP INF] {hap=2B:app=Autodesk DWF Application 8.1.0.87:tid=1308:usr=fbdadmin01}
Elapsed time for upload: 0.94 seconds


[01/25/2012 12:53:57:671 SWAP ERR] {hap=2B:app=Autodesk DWF Application 8.1.0.87:tid=1308:usr=fbdadmin01}
Timed out waiting for app to be ready for user input


[01/25/2012 12:53:57:686 SWAP ERR] {hap=2B:app=Autodesk DWF Application 8.1.0.87:tid=1308:usr=fbdadmin01}
The client could not launch C:\Program Files (x86)\Common Files\Autodesk Shared\Dwf Common\ExpressViewer.exe (rc 0B01FD04-0000041E, last error 0).


[01/25/2012 12:53:58:624 TRAY ERR] {tid=1020:usr=fbdadmin01}
The Application Virtualization Client could not launch Autodesk DWF Application 8.1.0.87.

The application took too long to be ready to interact with the user, possibly because the system was too busy. Try again in a few minutes. If the problem persists, report the following error code to your System Administrator.

Error code: 4615186-0B01FD04-0000041E


Please suggest me on this issue

regards,

Sivaiah.B
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ