Svasu's Posts

Use Applink functionality, where you can capture add-ins separately and link it to office application using package.ini parameters. The power of AppLink | VMware ThinApp Blog - VMware Blogs R... See more...
Use Applink functionality, where you can capture add-ins separately and link it to office application using package.ini parameters. The power of AppLink | VMware ThinApp Blog - VMware Blogs Refer AppLink part in Thinappp documentation. https://www.vmware.com/pdf/thinapp50_manual.pdf
Refer the following link. VMware KB: Issues with VMware ThinApp 4.x and Microsoft Office 2010
There was an issue with Activex in ThinApp 4.7. Please try with latest ThinApp version 5.0. and let me know if you still face the same issue.
While capturing the package, edit the proxy setting in the registry/inetcpl.cpl to the proxy url and then capture. Here the registry keys used to update proxy. [HKEY_CURRENT_USER\Software\Mic... See more...
While capturing the package, edit the proxy setting in the registry/inetcpl.cpl to the proxy url and then capture. Here the registry keys used to update proxy. [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings] "ProxyEnable"="1" "ProxyServer"=<proxy url> Here the reference link. How to configure client proxy server settings by using a registry file
Please verify native proxy settings is reflected in Thinapped Internet Explorer.
There is no way to recreate the project folder using thinapped exe's/Binaries, you can update the runtime(in binaries) using relink.exe. VMware KB: VMware ThinApp relink command to update the Th... See more...
There is no way to recreate the project folder using thinapped exe's/Binaries, you can update the runtime(in binaries) using relink.exe. VMware KB: VMware ThinApp relink command to update the ThinApp runtime of a virtual application
Hi, I found a workaround for your problem. osk.exe needs this DWORD("HKCU->Software->Microsoft->Windows NT->CurrentVersion->AccessibilityTemp->osk=3") to be set as 3. I wrote a script. Pl... See more...
Hi, I found a workaround for your problem. osk.exe needs this DWORD("HKCU->Software->Microsoft->Windows NT->CurrentVersion->AccessibilityTemp->osk=3") to be set as 3. I wrote a script. Place this script in project folder(along with build.bat), rebuild the application by executing build.bat. delete any existing sandbox. Now launch the thinapped osk.exe, "Ease of access" problem you mentioned is disappeared.
Let me know the Thinapp and Horizon-View versions. Which version of the Microsoft Office 2010 application you are trying to deploy(32 or 64 bit)? Horizon-View 5.2 does not support Thinapp5.0 x... See more...
Let me know the Thinapp and Horizon-View versions. Which version of the Microsoft Office 2010 application you are trying to deploy(32 or 64 bit)? Horizon-View 5.2 does not support Thinapp5.0 x64 bit applications. Please refer the link. VMware ThinApp 5.0 Release Notes
Hi Kyle, Using Thinapp5.0, postscan operation captures SysWOW64 folder. This can be tested by copying a file/dll in SysWOW64 directory during prescan and postscan operation. Possible scenar... See more...
Hi Kyle, Using Thinapp5.0, postscan operation captures SysWOW64 folder. This can be tested by copying a file/dll in SysWOW64 directory during prescan and postscan operation. Possible scenarios, where thinapp would have missed the dll file may be.      1. The dll file may pre-exist on the system before application installation.      2. The dll would have not been copied during "save project" operation(Copy error would have displayed during the operation). Please capture the application on a clean machine. before capturing make sure the dll is not present in "SysWOW64" directory. Thanks, Sathish
Hi, OSK.exe launches multiple native processes, when launched(eg: winlogon.exe, winutil.exe, explorer.exe) and then again launches osk.exe. so the behavior you get through packaged osk.exe is ... See more...
Hi, OSK.exe launches multiple native processes, when launched(eg: winlogon.exe, winutil.exe, explorer.exe) and then again launches osk.exe. so the behavior you get through packaged osk.exe is expected.
I believe Office 2010 SP1 is a x64 bit application. Horizon-View 5.2 does not have support for Thinapp5.0 x64 bit applications(Supports Thinapp5.0 32bit applications). Horizon-View 5.3 support... See more...
I believe Office 2010 SP1 is a x64 bit application. Horizon-View 5.2 does not have support for Thinapp5.0 x64 bit applications(Supports Thinapp5.0 32bit applications). Horizon-View 5.3 supports Thinapp5.0 32 and x64 bit applications. Please refer the link. VMware ThinApp 5.0 Release Notes
I have built the package. got the same behavior, will have to debug and keep you updated on this.
Could you upload the captured package?