Oizo's Posts

"this local directory is the same location as the pepper flash, which seems to no longer work (the flash work arounds do work by disabling pepper flash and app linking to an adobe flash)." Can y... See more...
"this local directory is the same location as the pepper flash, which seems to no longer work (the flash work arounds do work by disabling pepper flash and app linking to an adobe flash)." Can you provide more details about the problem..? - How do you test Pepper Flash..? Can you provide us with a link..? If I try this link, it works for me with Pepper Flash :http://www.chemgapedia.de/vsengine/help/en/flash/ Is this what you try to do..? Or do you want to use Applink'd Flash with Chrome..? Or am I missing something..? "The two both USED to work a few versions ago, and at about the same time stopped." They use to both work with the same ThinApp version... If you look at "how to disable Pepper Flash" online, and attempt to follow this, you will notice that the location of the "pepflashplayer.dll" changed location from the user profile to the ProgramFiles directory... I'd say that Google changed their code a lot...
Google Chrome 34 and 35 are still showing the same behaviour... Perform this test : - Launch packaged Chrome - Right click the "Blank" icon - Right click "Google Chrome" and select "Propert... See more...
Google Chrome 34 and 35 are still showing the same behaviour... Perform this test : - Launch packaged Chrome - Right click the "Blank" icon - Right click "Google Chrome" and select "Properties" - Click "Change Icon" and notice the error message : Windows can't find the file %USERPROFILE%\AppData\Local\Google\Chrome\User Data\Default\Google Profile.ico That file exists in the package, and if you copy the "Google Profile.ico" from the capture folder to this location on the native environment, it works! As you probably notice, I did bold the word "Windows". If you use ProcMon to troubleshoot the behaviour, and look for "Google Profile.ico", you will see that the process "Explorer.exe" returns "PATH_NOT_FOUND". This is normal, because "Explorer.exe" does not and cannot run in the virtual environment. Another workaround than putting the file manually on the native environment, would be to rename the "%Local Appdata%\Google\Chrome\User Data\Default" to "%Local Appdata%\Google\Chrome\User Data\Default.old". Then create a new "Default" folder, with MERGED isolation. After the package is rebuilt, it should work fine. Google Chrome checks if this folder exists for this user, and if not, re-creates it. With the isolation being MERGED, it does create it in the user profile. For the Flash bit that does not work, did you follow that KB..? http://kb.vmware.com/kb/2037251
Hi Mike, We are already aware of this, and a PR was raised. We must wait for them to come with a code fix. The issue is based on the fact that MS includes a licensing mechanism, even if yo... See more...
Hi Mike, We are already aware of this, and a PR was raised. We must wait for them to come with a code fix. The issue is based on the fact that MS includes a licensing mechanism, even if you do not have to enter a key during install, like this product. That licensing mechanism dislike being virtualized, and therefore refrain form starting. Thanks, and regards, Jonathan
Regarding the Hardware Acceleration, this depends on the deployment platform... (View platform without HW Acc, or a physical machine with HW Acc) This is what we indicate in that KB, especially ... See more...
Regarding the Hardware Acceleration, this depends on the deployment platform... (View platform without HW Acc, or a physical machine with HW Acc) This is what we indicate in that KB, especially the mms.cfg config :http://kb.vmware.com/kb/2037251
Just a quick update with this thread... You should be successful to package the 32bit version of SQL 2012 Management Studio on a Win7 32, using ThinApp 4.7.3, and running it on a Win 7 32 on t... See more...
Just a quick update with this thread... You should be successful to package the 32bit version of SQL 2012 Management Studio on a Win7 32, using ThinApp 4.7.3, and running it on a Win 7 32 on the exact same machine. I receive this exact same error when running the 32 bit package on a Win 7 64, though. VSTCVENT : - Did you try to use 4.7.3..? - And the path is too long! During the capture process, instead of using the default location path for the capture, choose a folder very close to the root of the drive. Edited - 27 Sept 2013 It seems to have something left over, or linked to that Capture Machine... I can pass Dirty, Washed and Clean test (on same machine), but not the Production...
Hi Aaron, Nice move from them! Working alltogether to keep everyone's happy! Regards, Jonathan
Hi, As Aaron reported, it is functioning as designed. BUT, we did included a way to change the Client behaviour. Please check this document : https://www.vmware.com/pdf/view-client-linux-do... See more...
Hi, As Aaron reported, it is functioning as designed. BUT, we did included a way to change the Client behaviour. Please check this document : https://www.vmware.com/pdf/view-client-linux-document.pdf On page 22, you'll find the explanation on the parameter "--once"      Specifies that you do not want View Client to retry connecting in the case of an error occurring.      Use --once if you want to obtain a similar workflow to the View 4.6 client. This option will force the View client to exit after the user disconnects or logs off from a desktop.      You should usually specify this option if you use kiosk mode, and use the exit code to handle the error. Otherwise, you might find it difficult to kill the vmware-view process remotely.      If you are setting the configuration key, specify "TRUE" or "FALSE". Default is "FALSE". You can use this like this (tested on an Ubuntu machine) : - Open a terminal and run "vmware-view --once" or - Modify the file in the home folder of the user, called : .vmware/view-preferences - Add the line : view.once = "TRUE" For the iGel client, or any other types/brands/models, I'm not sure if you can access it and apply modification, so I would recommend you to contact the Technical Support Services of those devices. Hope this helps, Regards, Jonathan