the new client prompts saying that the cert is signed by an unknown authority, but doesn't allow you to continue. Is there a way to configure it to accept this or prompt?
A partner is running Mac OS X 10.7.2 (11C74) and getting the blackscreen of death. He can connect to an internal View Connection Server 5.0 build 481677(non-PCoIP Security Gateway), but not one c...
See more...
A partner is running Mac OS X 10.7.2 (11C74) and getting the blackscreen of death. He can connect to an internal View Connection Server 5.0 build 481677(non-PCoIP Security Gateway), but not one configured with PCoIP SG. I have connected successfully to the same desktop with a 5.0 Windows client. He does have the View Open Client installed. Could that be causing a conflict, or is likely the Secure Gateway? Crash log attached. Phil
A native app cannot see the file system or registry of a thinapp. You can create an entry point within the thinapp, to the native app. Other option is to change the isolation mode for the particu...
See more...
A native app cannot see the file system or registry of a thinapp. You can create an entry point within the thinapp, to the native app. Other option is to change the isolation mode for the particular file system folder to merged and place the files your native app needs to see in there, and remove them from the package. Phil
Why not create a group for Visio Viewer and full Visio and setup PermittedGroups for both, then ensure you add users to one or the other. You could have a script that runs everynight that checks ...
See more...
Why not create a group for Visio Viewer and full Visio and setup PermittedGroups for both, then ensure you add users to one or the other. You could have a script that runs everynight that checks the groups and ensures no user is in both. I know not elegant, but will work for now. I'd also recommend you submit a feature request - https://www.vmware.com/support/policies/feature.html Phil
Toca , you can still do this today. In the Setup Capture wizard, you get the option to select the primary data container. By default, if the size of the package is greater than 100mb (I think th...
See more...
Toca , you can still do this today. In the Setup Capture wizard, you get the option to select the primary data container. By default, if the size of the package is greater than 100mb (I think this is the number, maybe someone else can confirm this if its important), then Setup Capture automatically selects to use a DAT file You can select an entry point instead however when you do it gives you the following error I believe the reason for this is that NTFS has issues showing icons on files greater than 100mb on older OS's and about 2GB on WinXP. Phil
have you tried building on another machine or rebooting the machine you are on? You could also run a command prompt, navigate to the project folder and run build.bat from there. Phil
Hi Chris, you could install Office2010 with KMS into the base image you use to build your vComposer desktops. Obviously it won't be thinapp'd, but if you align your office updates with your ba...
See more...
Hi Chris, you could install Office2010 with KMS into the base image you use to build your vComposer desktops. Obviously it won't be thinapp'd, but if you align your office updates with your base OS updates, vComposer can help. Phil
Charan, you don't need to put procmon.exe into the package, but you will need to run it from an entry point. The easiest way to do this is to enable the CMD.EXE entry point and then navigate to t...
See more...
Charan, you don't need to put procmon.exe into the package, but you will need to run it from an entry point. The easiest way to do this is to enable the CMD.EXE entry point and then navigate to the directory that has procmon.exe and run it. Be aware that you will need to run it once natively first to initialise it. You will then see what the package is doing. I also setup a standard filter when running as native basically removing all standard processes. HTH Phil
Hi Lee, try the following ThinApp Blog entries: http://blogs.vmware.com/thinapp/2009/03/notes-and-considerations-on-deploying-thinapp-packaged-applications-via-active-directory-group-polici...
See more...
Hi Lee, try the following ThinApp Blog entries: http://blogs.vmware.com/thinapp/2009/03/notes-and-considerations-on-deploying-thinapp-packaged-applications-via-active-directory-group-policies.html http://blogs.vmware.com/thinapp/2009/10/integrat.html http://blogs.vmware.com/thinapp/2009/10/integrating-thinapp-packages-with-vmware-view-part-2.html http://blogs.vmware.com/thinapp/2010/01/view-and-thinapp-integration-guide-part-3.html Phil
Are you using VMware workstation shared folders to host the packages? If so, thats the problem. I shutdown my VM after the capture/test and it releases the file locks. Painful, but still quick...
See more...
Are you using VMware workstation shared folders to host the packages? If so, thats the problem. I shutdown my VM after the capture/test and it releases the file locks. Painful, but still quicker than packaging on a physical box. Phil
The machine not on the Domain probably won't work because the computer account needs RO permissions to the share holding the thinapps. When entitling thinapps to computers it should happen withou...
See more...
The machine not on the Domain probably won't work because the computer account needs RO permissions to the share holding the thinapps. When entitling thinapps to computers it should happen without logging off or rebooting but it may take up to 5 minutes. When entitling thinapps to the pool, it requires a reboot. Also if you have folder redirection policies you may not be able to create the shortcuts.
you can comment out the Shortcuts= line for each entry point. Eg. Before [Microsoft Access 2010.exe] Source=%ProgramFilesDir%\Microsoft Office\Office14\MSACCESS.EXE Shortcut=Microsoft Offic...
See more...
you can comment out the Shortcuts= line for each entry point. Eg. Before [Microsoft Access 2010.exe] Source=%ProgramFilesDir%\Microsoft Office\Office14\MSACCESS.EXE Shortcut=Microsoft Office Pro Plus 2010.dat Icon=%SystemRoot%\Installer\{90140000-0011-0000-0000-0000000FF1CE}\accicons.exe FileTypes=.accda.accdb.accdc.accde.accdr.accdt.accdu.accdw.ade.adn.adp.mad.maf.mag.mam.maq.mar.mas.mat.mau.mav.maw.mda.mdb.mdbhtml.mde.mdn.mdt.mdw.wizhtml ObjectTypes=Access.ACCDAExtension;Access.ACCDCFile;Access.ACCDCFile.14;Access.ACCDEFile;Access.ACCDEFile.14;Access.ACCDRFile.14;Access.ACCDTFile;Access.ACCDTFile.14;Access.ACCFTFile;Access.ACCFTFile.14;Access.ADEFile;Access.ADEFile.14;Access.Application;Access.Application.14;Access.Extension;Access.Extension.14;Access.MDBFile;Access.MDEFile;Access.MDEFile.14;Access.Project;Access.Project.14;Access.WebApplicationReference.14 Shortcuts=%Programs%\Microsoft Office After [Microsoft Access 2010.exe] Source=%ProgramFilesDir%\Microsoft Office\Office14\MSACCESS.EXE Shortcut=Microsoft Office Pro Plus 2010.dat Icon=%SystemRoot%\Installer\{90140000-0011-0000-0000-0000000FF1CE}\accicons.exe FileTypes=.accda.accdb.accdc.accde.accdr.accdt.accdu.accdw.ade.adn.adp.mad.maf.mag.mam.maq.mar.mas.mat.mau.mav.maw.mda.mdb.mdbhtml.mde.mdn.mdt.mdw.wizhtml ObjectTypes=Access.ACCDAExtension;Access.ACCDCFile;Access.ACCDCFile.14;Access.ACCDEFile;Access.ACCDEFile.14;Access.ACCDRFile.14;Access.ACCDTFile;Access.ACCDTFile.14;Access.ACCFTFile;Access.ACCFTFile.14;Access.ADEFile;Access.ADEFile.14;Access.Application;Access.Application.14;Access.Extension;Access.Extension.14;Access.MDBFile;Access.MDEFile;Access.MDEFile.14;Access.Project;Access.Project.14;Access.WebApplicationReference.14 ;Shortcuts=%Programs%\Microsoft Office this will keep the file and object associations but not create shortcuts in the Start Menu\All Programs\Microsoft Office folder Phil
Merged and WriteCopy are the most common as they allow interaction with natively installed apps and from the file system perspective - eg My Documents and Desktop. Folders and registry hives with...
See more...
Merged and WriteCopy are the most common as they allow interaction with natively installed apps and from the file system perspective - eg My Documents and Desktop. Folders and registry hives within the package would still be using Full isolation mode, and thinapp sets this automatically for you. the setting you are referring to is for all other folders not specifically set within the package. You can change this after the package is created by editing the PACKAGE.INI and changing [Isolation] DirectoryIsolationMode=Merged to [Isolation] DirectoryIsolationMode=Full Most of the time though, this is not necessary. Phil
It might be related to the new ProcessExternalNameBehavior=WhitelistFriendly setting (default) - discussed here: http://blogs.vmware.com/thinapp/2011/02/vmware-thinapp-461-whats-new.html You ...
See more...
It might be related to the new ProcessExternalNameBehavior=WhitelistFriendly setting (default) - discussed here: http://blogs.vmware.com/thinapp/2011/02/vmware-thinapp-461-whats-new.html You could edit the package.ini and add the following to the [BuildOptions] section: ProcessExternalNameBehavior=Original some apps want to see the proper process name, but some don't. Otherwise you will need to run log_monitor or process monitor to debug whats happening. Phil
Tom et all, I too don't like having credentials in batch files or scripts so I borrowed a base script and modified it to suit. Feel free to use if you like. Usage: create a custo...
See more...
Tom et all, I too don't like having credentials in batch files or scripts so I borrowed a base script and modified it to suit. Feel free to use if you like. Usage: create a customisation spec as mentioned above add a run once with something similar to: cscript.exe C:\Windows\JoinDomainOU1.1.vbs -u UserName -p PasSWorD -d NetBiosDOMAIN -o OU=VDI,O=Workstation copy the script to C:\Windows\JoinDomainOU1.1.vbs Benefit of this approach is the credentials stay in vCenter, not in the template so its safer and its easy to modify! You can also have the same base template for many pools all going to different OUs. Phil
