Hello! I´m running View server on my enviroment, and with ThinApp I packaged my first application - Internet Explorer 8 using .msi output. VDI image I have, is XP SP3 with original IE6. I moved all output files to View server share, and scanned for ThinApp in View Administrator console. VDI machine recieves this IE8 fine, but none of shortcuts are created and original IE6 is started via shortcut. Still, IE8 can be launched manually via Program Files\Internet Explorer 8 ThinApp folder and it works ok.
Question is, how to use thinreg.exe utility with View publish method? I read through ThinApp guide, but all I have is this:
Creating a login script that queries applications entitled to the user and runs the thinreg.exe utility with the option that registers the applications on the local machine.
Where/how I should create login script and am I on the right track here? I´m femiliar with Group Policies.
Copy all the files from the 'bin' folder (EXE and MSI) to the fileshare that will serve as the ThinApp Repository. Make sure MSIStreaming=1 is set in the package.ini.
You may have a look at this video of ThinApp Assignments in View 5: http://www.youtube.com/watch?v=d19toUaelCw&feature=youtube_gdata_player
For deployments to user desktop (not using View), you may use either MSI (with MSIStreaming=0) which needs no registration (ThinReg) or the EXE and register using ThinReg.
For deployments from network share (not using View), you may use only the EXE. ThinReg logon script is helpful for registering the ThinApp automatically when the user logs in. http://blogs.vmware.com/thinapp/2008/10/thinapp-thinreg.html
Hi,
If you are using MSI, you no need to use ThinReg for registration to create the shortcut.
To create shortcut of IE8 on desktop, please do the changes mentioned below in the package.ini.
[Internet Explorer.exe]
Source=%ProgramFilesDir%\Internet Explorer\iexplore.exe
;Change ReadOnlyData to bin\Package.ro.tvr to build with old versions(4.6.0 or earlier) of tools
ReadOnlyData=Package.ro.tvr
WorkingDirectory=%Profile%
FileTypes=.gif.htm.html.mht.mhtml
Protocols=ftp;HTTP;https
ObjectTypes=InternetExplorer.Application;InternetExplorer.Application.1
Shortcuts=%Programs%;%Desktop%
Thanks, I´ll try that.
- When saving output data of packaged IE8 to View server, should I include all folders of the packaged project, or just IE8.msi file?
- In what case I should save and use .msi file, and when to use only .exe?
- If using .exe, how should I launch/trigger thinreg.exe?
Copy all the files from the 'bin' folder (EXE and MSI) to the fileshare that will serve as the ThinApp Repository. Make sure MSIStreaming=1 is set in the package.ini.
You may have a look at this video of ThinApp Assignments in View 5: http://www.youtube.com/watch?v=d19toUaelCw&feature=youtube_gdata_player
For deployments to user desktop (not using View), you may use either MSI (with MSIStreaming=0) which needs no registration (ThinReg) or the EXE and register using ThinReg.
For deployments from network share (not using View), you may use only the EXE. ThinReg logon script is helpful for registering the ThinApp automatically when the user logs in. http://blogs.vmware.com/thinapp/2008/10/thinapp-thinreg.html
I´ve succsessfully have created MS 2003 package with shortcuts in Program Files, but no succsess with IE8. Let me clear this - I first modify Package.ini and then build the package? Package.ini is not stored in View Server's share?
Ou yeah, I got it! I also noticed, that if you before building create a shortcut to your desktop on a packaging machine, package.ini will be updated with desktop parameter.
Thanks for the first support! I´ll have to look more into the instructions!
Welcome.
Yes, you can do that way too by re-capturing the application again.
On the other question, package.ini is not stored in View fileshare. Only the EXE and MSI will be scanned by View when adding the ThinApp repository.
Can you please explain me, in what case I should repack application in .msi, and when into exe?
And how I should distribute the thinreg.exe to register shortcuts, if I have .exe application, not .msi. Cheers and thank you!
ThinApp MSI installs the ThinApp and registers the package (creating shortcuts, file associations, entry in Add/Remove programs). ThinReg does the same when using ThinApp EXE.
1. When deploying ThinApp to a large enterprise of 1000+ machines, MSI is helpful as it can install and register the package silently
2. ThinApp EXE can be launched from any network file share so that the user no need to install it. Using ThinReg, it registers the ThinApp EXE
You may use ThinReg during logon script to register the ThinApp packages automatically
http://blogs.vmware.com/thinapp/2008/10/thinapp-thinreg.html
