Oizo's Accepted Solutions

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, 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