Be useful piece of “functionality” right?
- If you are using 32-bit Internet Explorer, copy shell32.dll and shlwapi.dll from the capture machine to the %SystemSystem% folder in the Internet Explorer project.
If you are using 64-bit Internet Explorer, copy shell32.dll and shlwapi.dll from the capture machine to the %SystemSystem(x64)%folder in the Internet Explorer project.
- In Package.ini, add LoadShellOnlyForWin10Higher=1.
- Build the project.
Took me ages to find this which I put down to put googling on my part 🙂
Might of heard of shell32.dll before but not shlwapi.dll – more info on that here for what its worth – https://msdn.microsoft.com/en-us/library/windows/desktop/bb759845(v=vs.85).aspx
Just some i’ve found useful when troubleshooting ThinApp packages i’ve put together.
- Launch from the command prompt your application. Is a good determiner of whether you have an entry point issue or not eg i) Run cmd.exe ii) go to folder for application eg c:\program files (x86)\winzip iii) launch winzip.exe – if the app launches ok, indicates something is wrong with the entry point. Check the WorkingDirectory and CommandLine parameters.
- Move suspected files into the support folder: if the application crashes, its sometimes due to the fact that captured DLL’s are not supported to run in certain OSes.
- Package registration: certain apps needs to be registered to be fully functional. Run thinreg.exe to register the package on your test machine.
- Modify the process name behavior: some apps don’t work when they cannot find its processes listed in taskmgr when running. Worth noting here that ThinApp packages hide the original process names. Add ProcessExternalNameBehavior=original to your package.ini and the processes names will be listed
ThinApp 3.x being used to virtualize Internet Explorer 6
Xenapp 6.5 HRP05
Citrix Profile Management 5.2
After virtualization published as a citrix published application, on launch it would appear to launch all the way – run through pieces licensing/policies etc but disappear – in fact the session would appear on the Citrix farm but not on the client. Turns out during application capturing specifying the default “user profile (%AppData\Thinstall) was to blame – specifying Custom location and network share resolved.
As such came to this conclusion as using admin-level privileges would launch application no problem via xenapp (twigged profile management then as administrators were not set to to be UPM-enabled).
As per http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1026565
Worked a charm. Interesting to utilize VMware technology to help reduce my citrix legacy farm footprint. Of course unsupported to run IE6 in Windows 2012 r2/Windows 2008 r2 but fancy its as “much as muchness” given its age. Plugin’s (java,Active X) all performing as should crucially