Lakshman's Posts

Please read the below links for Office 2010 ThinApp: http://blogs.vmware.com/thinapp/2011/02/quick-start-guide-for-deploying-office-2010-using-thinapp-461.html http://kb.vmware.com/k... See more...
Please read the below links for Office 2010 ThinApp: http://blogs.vmware.com/thinapp/2011/02/quick-start-guide-for-deploying-office-2010-using-thinapp-461.html http://kb.vmware.com/kb/1022287
Yes. You no need any additional script. Activating Office 2010 ThinApp depends on type of license you have. If the type of license is KMS, then office can be activated silently. If MAK, launc... See more...
Yes. You no need any additional script. Activating Office 2010 ThinApp depends on type of license you have. If the type of license is KMS, then office can be activated silently. If MAK, launching any office thinapp application (say WORD) will pop up the activation dialog, where in you have to activate it first time, either online or through telephone. May i know the type of license you have and the issues? Thanks Lakshman
Please look into this: http://communities.vmware.com/message/1733871#1733871 Thanks Lakshman
Matt, Is the application supported on Win 7? What happens if you install the native application on Win 7 and launch it? Thanks Lakshman
Please check this: http://blogs.vmware.com/thinapp/2010/08/captured-on-xp---running-on-win-7.html What is the observation when launching the ThinApp on Windows XP? Thanks Lakshman
I guess the native application might have already installed on that machine, sharing the same MSI GUIDs. Can you test the ThinApp on other machine to check if you get the same error? Or, by a... See more...
I guess the native application might have already installed on that machine, sharing the same MSI GUIDs. Can you test the ThinApp on other machine to check if you get the same error? Or, by any chance, have you installed the ThinApp already? ☺
Are you getting any error during compiling or the build.bat command prompt closes off without compiling? If it is the second case, please make sure the EXE is not in use (see Task Manager). Also... See more...
Are you getting any error during compiling or the build.bat command prompt closes off without compiling? If it is the second case, please make sure the EXE is not in use (see Task Manager). Also, remove the sandbox before running the new EXE.
Please make sure MSIProductCode is different for both the packages.
Peter, What happens when you launch Setup capture after the third logon? I assume you should be getting a new dialog with an option to continue from the prescan (see attachment). If then, ... See more...
Peter, What happens when you launch Setup capture after the third logon? I assume you should be getting a new dialog with an option to continue from the prescan (see attachment). If then, you can continue and finish the rest of it.
Don’t bother about all the white space warnings, make sure to remove the ones that I marked in the attachment for Steps 17 and 18. It may cause the activation to fail.
Reboot the system. When the system boots up, continue with the setup capture and retry the command “C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe executequeueditems”
#4 – Are you able to activate the thinapp successfully on XP SP3? You can check it by launching any application (say Word), go to File -> Help menu and check the activation status (You should ... See more...
#4 – Are you able to activate the thinapp successfully on XP SP3? You can check it by launching any application (say Word), go to File -> Help menu and check the activation status (You should see either Product Activated or Not activated). Sometimes, it gets activated only at the second time.
1. Make sure your capture machine is clean (just the OS and ThinApp 4.6.1 with tools installed) 2. Do not activate office 2010 during capturing 3. Make sure you remove the extra wh... See more...
1. Make sure your capture machine is clean (just the OS and ThinApp 4.6.1 with tools installed) 2. Do not activate office 2010 during capturing 3. Make sure you remove the extra white spaces in HKEY_CURRENT_USER.TXT and HKEY_LOCAL_MACHINE.TXT that may arise when you copy/paste in steps 17 and 18 (See the attachment) 4. When launching the ThinApp first time, you should activate it online/telephone on every machine. Once activated, it never asks again next time on that machine. This is a mandatory step and you cannot skip it. Thanks Lakshman
No additional scripts required. What type of volume licenses are you using? MAK or KMS?
Open Package.ini, look for “Shortcuts=” for the main EXE under Application-Specific Parameters section and remove “%Desktop%” For example, Source=%ProgramFilesDir%\MainApp\MainApp.exe Read... See more...
Open Package.ini, look for “Shortcuts=” for the main EXE under Application-Specific Parameters section and remove “%Desktop%” For example, Source=%ProgramFilesDir%\MainApp\MainApp.exe ReadOnlyData=bin\Package.ro.tvr WorkingDirectory=%ProgramFilesDir%\MainApp Shortcuts=%Programs%\MainApp;%Desktop% Change the last line to Shortcuts=%Programs%\MainApp Now, rebuild the ThinApp by running build.bat again. This should not create shortcut on the desktop. Thanks Lakshman
If you want to change the default to other location, you need to reinstall ThinApp by passing the parameter /v INSTALLDIR=”NEW LOCATION” For example, VMware-ThinApp-Enterprise-4.6.1-361923.... See more...
If you want to change the default to other location, you need to reinstall ThinApp by passing the parameter /v INSTALLDIR=”NEW LOCATION” For example, VMware-ThinApp-Enterprise-4.6.1-361923.exe /v INSTALLDIR=D:\ThinApp Thanks Lakshman