KB articles:
http://kb.vmware.com/kb/2021901
http://kb.vmware.com/kb/1022287

A blog post:
http://thinappguru.blogspot.se/2012/03/notes-on-packaging-office-project-and.html

If you have Office locally installed but need to virtualize Project or Visio (many steps are the same as for Office 2010):
http://blogs.vmware.com/thinapp/2013/02/thinapp-microsoft-visio-and-project-2010-while-locally-installed-microsoft-office-2010.html

Additional information for German Windows XP:
If you follow the procedures described in above posts your package should work very well on an English OS. Jonathan Wilk (@DooDleWilk), Escalation Engineer at VMware Global Support Services, just sent me his notes working on a case. The package worked just fine on English Operating Systems and German Windows 7 (32 and 64-bit) but failed on a German Windows XP.

After some troubleshooting he realized that on an English Windows XP the OfficeSoftwareProtectionPlatform folder is located in the “Documents and Settings” folder. On a German Windows XP the folder is called “Dokumente und Einstellungen”. So the workaround was simply to create the “Dokumente und Einstellungen” folder underneath the %Drive_C% folder macro and copy the content from your “Documents and Settings” folder. Rebuild and it works.

I wouldn’t be surprised if other applications will have the same issue and therefore would need the same fix in order to be portable.

1. Copy ThinApp MSI of another application to the folder that has ThinApp EXE
2. Rename MSI filename to be same as ThinApp EXE name
3. Install MSI editor tool, preferably Microsoft Orca (Download link:  http://www.technipages.com/wp-content/uploads/2007/11/orca.Msi)
4. Edit the MSI with Orca by right clicking on the MSI
5. Go to File table. Change the FileName to the ThinApp EXE filename. Also change the  values of FileSize and Version to that of the ThinApp EXE

6. Go to Directory table. Change the DefaultDir value to the ThinApp Name. Make sure not to delete D0000001| at the beginning of the value and (VMware ThinApp):. at the end

7. Go to Proprety table. Change the value of ProductName to the ThinApp EXE filename. Make sure the product name ends with (VMware ThinApp)

Run the MSI, the ThinApp EXE should be installed to Program files folder.  Check the Add/Remove programs entry to make sure the MSI has picked the new ThinApp name

One of the changes that was announced is that at the end of the year ThinApp will no longer be sold as a standalone product as in the past.  Unfortunately, the product support life cycle has limited terms of description so the ‘End of Availability’ announcement has caused some some concern as some interpreted this as EOA of the technology.  I apologize for the confusion and want to clarify that the EOA term ONLY applies to the standalone SKU as ThinApp will actually be included in ALL of the Horizon bundles - VMware Horizon View™, VMware Horizon Mirage™, VMware Horizon Workspace™ and VMware Horizon Suite™.  A good place to get a feel for the bundles can be found here - Horizon Suite.  Being included across the Horizon suite means that more customers than ever will be able to use the features and capabilities of ThinApp.  The Horizon licensing model still allows flexibility for ThinApp to be used on the desktop without any other products if that is the use case needed by the customer.

I highly encourage you to consider the affinity between Horizon Mirage and ThinApp as we now have the capability to address every application on the Windows desktop; if you need apps with drivers and remote DCOM then use Mirage application layers, if you need cross platform support or isolation then ThinApp containers are ideal.  Not only do these technologies cover 100% of the application list but Mirage is an ideal deployment mechanism for ThinApp containers as it can deliver ThinApps to the farthest endpoints without any dependence on branch infrastructure, Active Directory, or costly backend architecture.  Customers can deploy layers and containers and then inventory those endpoints for centralized management of both native and virtualized applications.

To be clear to our customers (and competitors), our commitment to ThinApp technology hasn’t changed as we are actively working on our next release for mid-year which will include some very tangible architectural and compatibility improvements.  Here is an FAQ that has been created which should help address any particular details.

Some general tips when it comes to cleaning up a ThinApp project folder:

1. A virtual application is not as fragile as a natively installed application. So you can allow for some unnecessary files/registry keys within the project folder. Personally I do like an as lean and mean package as possible.
2. When hunting for unnecessary components don’t delete the files. I move them into the Support folder found in the root of all project folders. This way I can easily restore files if needed.
3. The size of the package does not have a direct impact on performance. If you have files not loaded or used in your package the ThinApp runtime will not load them, i.e. they will not affect your performance.
4. MSI self repair will most likely not work within the virtual environment. Reason being the Windows Installer service always runs outside the virtual environment. So keeping MSI cache rarely makes any sense.

These folders contain files that can often be safely removed from your project:

 %Cookies%
 %Drive_C%\Documents and Settings
 %Drive_C%\MSOCache
 %Favorites%
 %Fonts% (if the fonts are needed you may want to install them natively)
 %History%
 %Internet Cache%
 %SystemRoot%\Installer
 %SystemRoot%\ServiceProfiles
 %Temp%

It’s worth investigating the %ProgramFilesDir%\<app folder> for any backup or setup folders. These folders contain either backup of changed files during the installation or backup of setup files used for self-repair. Sometimes you need to go down a couple folders to find them.

In special cases you might want to clean up %AppData%, %Local AppData%, and %Profile% as well. Just make sure you don’t delete user settings you want to include in the package. If you don’t know the application in detail, trial and error is often the method you have to relay on when it comes to these locations.

What can and cannot be deleted from the registry is a little harder. The virtual registry is not very easy to browse in the format it’s stored as in the project folder. To make the task easier you can use a third-party tool. ThinAppHelper is a good candidate, http://www.cis.nl/thinapphelper/download.html. With this tool you can browse the project’s registry and easier delete whole branches. I don’t have any examples of what to delete in the registry. Please leave your suggestions as comments to this post.

Follow these steps to successfully package Microsoft Visio and Project 2010 using ThinApp. Using this procedure will allow the package to coexist with natively installed Microsoft 2010 and integrate with Outlook (send email functionality).

IMPORTANT: Visio/Project should not be activated prior to the postscan. This means installing with the network adaptor disabled for KMS installations. The Capture VM must be clean (Vanilla OS plus MS patches, with just the VMware Tools and ThinApp 4.7.3)

1.         Copy .Net Framework 3.5 (only needed if you plan to include .Net in your package), Microsoft Visio 2010 or Project 2010, and any required Microsoft Visio/Project source files to C: drive.

2.         Disconnect the NIC

4.         Copy or extract the Microsoft Visio 2010 installation source to a location where the files can be edited.

5.         Locate config.xml. This is in a folder called suiteWW, where suite is replaced by the suite of Microsoft Visio 2010 you are installing.

6.         Add these lines to the bottom of the file, immediately above the last line which reads </Configuration>:

For KMS licensing activation:

<Setting Id=”KMSSERVICENAME” Value=”kmsserver.domain.com” />

<Setting Id=”AUTO_ACTIVATE” Value=”1″ />

<PIDKEY Value=”AAAAA-BBBBB-CCCCC-DDDDD-EEEEE” />

Note: Replace kmsserver.domain.com with the name of your KMS server.

Note: Replace AAAAA-BBBBB-CCCCC-DDDDD-EEEEE with correct product edition code (Visio Std, or Visio Pro, etc…).

7.         Save the modified config.xml.

8.         Launch ThinApp Capture, take a prescan

9.         Install .Net Framework if required to be included in package

10.       Install Visio/Project by running setup.exe from the modified installation source.

11.       Install any product service packs

12.       Once the product installed, open an elevated Command Prompt, and run those 2 commands:

C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE

net stop osppsvc

Note: The first command re-arms the license (it resets the CMID used of KMS licensing), while the second turns the Office Protection Platform service off.

13.       Run ThinApp postscan

14.       Change the Inventory name to something appropriate for your use.

15.       Move the OfficeSoftwareProtectionPlatform folder from %drive_C%\Documents and Settings\All Users\Microsoft to %Common AppData%\Microsoft

16.       Set the following folders to MERGED by editing the ##ATTRIBUTES.INI in the root of each

%APPDATA%\MICROSOFT\AddIns\

%APPDATA%\MICROSOFT\Office\

%APPDATA%\MICROSOFT\Outlook\

%LOCAL APPDATA%\MICROSOFT\Outlook\

%LOCAL APPDATA%\MICROSOFT\FORMS\

%TEMP%\

%APPDATA%\MICROSOFT\

%LOCAL APPDATA%\

Set the following folder and subfolders to WRITECOPY

 %Program Files Common%

%ProgramFilesDir%

17.       Put the following in HKEY_CURRENT_USER.txt:

 isolation_writecopy HKEY_CURRENT_USER\Environment

Value=ALLUSERSPROFILE

REG_SZ~%Common AppData%

 

isolation_merged HKEY_CURRENT_USER\Identities

 

isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Office

 

isolation_merged HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Security

 

isolation_merged HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem

18.       Put the following at the beginning of HKEY_LOCAL_MACHINE.txt:

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{32820823-eb9f-42bf-badb-4482911536bb}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{32f506a9-36f4-45ca-a3b7-e220e2fadcfc}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{0b6faa6c-afa9-4c9f-92a9-d1b9e13e49e7}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{b3fd0790-e46d-44d8-a88c-fcd99771da5e}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{4918cead-10bb-4345-b406-c0096b646c24}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{80f8087e-f900-4c25-b7fb-66ddf3ad2685}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{2fe7e56b-8195-4c8f-a199-fde2e4e09456}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{f1f1e3ad-0dff-41f3-96d0-11b3aa4f0c96}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{c722abe9-52ee-45de-b7aa-1cb7f27dac05}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{458b6290-216a-410c-bdc8-24008876301b}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{491ccf72-9e19-45bc-8a78-5e8c8be7f464}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{529c81ad-3788-4f3d-8c1c-71ccf202de21}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{2b402eec-0c7f-447c-8d44-e816888b1115}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{ce175ea0-8692-4968-b769-1b0029498a41}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{b69b7cc0-0e89-46d0-a99e-abddd4b61743}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{de5206e8-c4ad-42cc-bd53-8cbb3558e80c}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{f9285c37-8314-4516-89d5-e4932dc92de6}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{dce06134-5696-4fa8-b13e-51aad6def5d9}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{fc4fc45c-be7e-4704-99ac-951db77b91dc}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{947a7174-52b0-44f2-bfb6-7f3e07843277}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{69c6e0d2-c565-4d52-9930-d46c4116f708}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{aedd0615-3da5-4d6a-abde-63cedf4e80a4}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{23a22094-b01e-43cf-a372-6d4ee6d9eabf}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{22c493c3-99e2-45e9-a739-ee497e141be3}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{d049f335-4ac7-4400-b449-c532f4876693}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{8d2d2f50-cdf0-45cb-8949-9a39ade5cb7a}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{3ff290b5-342b-40dd-a66b-00e76c0e5b80}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{3086391e-945a-44f8-880a-24d7eee14dae}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{2f9a3248-de98-4b16-b56c-0cdc2d4d3d42}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{23b98090-64e4-400f-9107-921a78bc2cdd}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{8d95965c-956f-4eed-a18f-cf18e6d31e88}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{4530f183-15be-4eba-8bef-e68b6686b921}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{7f76b468-81a6-49ec-9c38-069143206618}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{37d23cc0-470c-4312-a01c-77e1c6e0ad61}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{b17b4b81-bb80-4c17-871c-57d5ab14991d}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{b2e79a4f-f632-43af-86dc-191cd03082ae}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{ea2c0345-2c36-45d4-9692-6972ce4e96c6}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{35dee61f-342b-41a2-acdb-2e207760af1b}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{8c74e7e1-d44a-4cce-9ec0-144a0e037d43}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{816b6d90-87e6-430f-a5fd-734be662bb55}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{a5fb8c3a-6da1-4438-a6cf-44c589aa2665}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{6a4a43f1-4846-4c4b-9a70-c4eac0184d97}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{c3fe9663-9bde-40dd-ae25-f2f8aa2d6b1a}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{26cd69c4-d593-4936-a8bb-e592816a0fad}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{ad89527a-aed4-4382-be23-19be89f9d01e}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{c00469cb-209b-4823-94bb-4139e48f5923}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{a5ce878d-59a9-48ae-8e0a-ed717267302d}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{1a821936-fee1-43a8-8222-87f4e049afb9}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{a5e4db17-4067-4d19-9812-2e3b879b8a35}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{712cbb5d-58be-48dc-b930-c8362f63fdee}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{f986cdbd-8807-418a-adbd-b8ddbf92c590}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{8abec68c-a5d1-40f5-966c-501dddf5c3fe}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{cc0569bb-bde5-4d6b-ac65-b1fa7a227258}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{fbdc5f1a-0b96-4b9e-8f17-df17a3dc59ef}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{17e35d4e-df3a-4a2b-83be-a1b17e710e8a}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{a1971a89-4e84-41d9-b3e0-18a109146bff}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{f4bc39d7-c2c0-40f1-8e59-fe9bd797d755}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{0b753f3d-cf41-42b6-8289-b7a8d334e8f9}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{9d9abca5-0a0b-485a-a962-d1b983ec8274}

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\{d19d1258-ada6-40e1-b4d6-5d160e2ebfc9}

 

isolation_full HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Search\Preferences

Value=PreventIndexingOutlook

REG_DWORD=#01#00#00#00

 

isolation_merged HKEY_LOCAL_MACHINE\Software\Clients

 

isolation_merged HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\00004109A10090400000000000F01FEC

 

isolation_merged HKEY_LOCAL_MACHINE\Software\Classes\Installer\Components\0470D1FF722D1D114A0B000680FA28E0

 

isolation_writecopy HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\User Settings\Outlook_Intl

Value=Count

REG_DWORD=#01#00#00#00

Value=Order

REG_DWORD=#01#00#00#00

19.       In PACKAGE.INI uncomment the line VirtualizeExternalOutOfProcessCOM=0

and add:

 ChildProcessEnvironmentExceptions=WINWORD.EXE;EXCEL.EXE;POWERPNT.EXE;OUTLOOK.EXE;MOC.EXE

ChildProcessEnvironmentDefault=Virtual

ExternalDLLs=mso.dll

20.       For Project 2010 you may have to change Isolation Mode from Full to WriteCopy on these folders within your Project Folder:

%ProgramFilesDir%\Microsoft Office\Office14

%ProgramFilesDir%\Microsoft Office\Office14\1033

21.       Build your project folder by running build.bat.

(Make sure to get rid of any extra line breaks when copying text from this post into your registry files.)

When it comes to creating an Horizon update package there is two package.ini parameters of interest.
AppID=
VersionID=

The AppID is used to identify the package internally in Horizon. VersionID is used to specify package version. In order for Horizon to identify and automatically publish an updated version of a package the new package must contain the original package’s AppID and a VersionID higher than the original package.

So how do I get the current AppID from my deployed package? Unfortunately today you cannot extract that information from the Horizon Admin interface. There’s a UUID listed in the web interface but this is another identification ID and is not the one we need. This KB article discusses a couple different methods on how to extract the correct ID: http://kb.vmware.com/kb/2030248. This blog post will focus on one specific method using relink.exe (more relink.exe and Horizon info can be found here: http://kb.vmware.com/kb/2021928).

If you run relink.exe –h on a package that is already Horizon enabled, relink.exe will reuse the existing AppID in the package, i.e. keeping the original AppID. When you run relink.exe –h it will show you the package’s AppID. We will use this to our advantage.

Using relink.exe –h VersionID + will not only reuse existing AppID it will increment the VersionID automatically, creating an update package. This is all good but most of the times you are looking for creating an update using a completely new project folder.

Let’s have a look how we can go about using relink.exe to extract the AppID and then implement it in our new project folder.

For this example will I use 7-zip.

In my original project folder’s package.ini I’ve activated Horizon manageability.

I upload the original package to my Horizon ThinApp repository, making sure to place it in a folder on my repository share. Folder is called 7-zip.

Once my ThinApp repository been synchronized my original version is available in the Horizon Admin interface. Please note it’s identified as version 1.0. Now I can entitle users to the ThinApp package.

Next is to create an updated version of my 7-zip package.

First I run relink.exe -h on my original package. As you can see in the screenshot above relink.exe shows the existing AppID when doing so. Copy this AppID.

I paste in the original package’s AppID into my new version’s package.ini file. I also specify VersionID=2 (must be higher than published version).

I upload my new version into my ThinApp repository making sure I create a new folder for it. I use the folder name 7-zip New in this example. The original package should be left untouched at this point.

Once synched with my ThinApp repository, Horizon Application Manager automatically recognizes the new version of my 7-zip package and version 2.0 is now the active one. If you are using streaming deployment, version 2.0 will be used next time the user launches the package. If you are using local deployment, version 2.0 will automatically be copied down to your clients.

ThinApp 4.7.3 is now available @  http://bit.ly/Is2ZvV
Release Notes @  http://bit.ly/T662Mv
ThinApp 4.7.3 SDK @  http://bit.ly/oZJD7h
ThinApp Factory @ http://bit.ly/MOqVp1

As always, we invite you to evaluate ThinApp and see for yourself how virtualizing Windows applications can simplify delivery and management.

Do you or your users get an error “Do you want to allow this website to open a program on your computer?” prompt the first time they go to launch a ThinApp package in Horizon?

In most cases, the prompt is not a big deal for Horizon users on a Windows system where ThinApp packages are being deployed. But if you have a dynamic desktop environment where users are dynamically assigned a virtual system or randomly use physical desktops, this could be an issue.

Resolution:

First, it’s important to note, this is not a Horizon or ThinApp specific issue. Rather it’s a security configuration within Windows.

Here is how to resolve this issue. Simply create a GPO with a custom registry value or manually edit the registry of your virtual desktop master gold image to have the following registry setting within.

Registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ProtocolExecute\horizon

Create a DWORD called “WarnOnOpen” and set the value to “00000000”.

The MSDN Blog article “URL Protocols, Application Protocols, and Asynchronous Pluggable Protocols. Oh My!” explains this behavior and the fix under the Application Protocol section within Windows, which is basically what Horizon is using when it launches a ThinApp package.

To put it simply, there are multiple locations for icon definitions within a ThinApp package (MSIARPProductIcon, InventoryIcon, and Entry Point Icon). Regarding Horizon, it only cares about seeing the Inventory Icon and the Entry Point icon.

It is important to know, Horizon has multiple areas where it shows the icon. The app upload screen, app deployment screen, and the user screen to name the most common. In most cases, we don’t really care about any of the others except the last one.

In order for the icon to appear properly for the user, I’ve always had to ensure both the Entry Point icon and the Inventory Icon are set correctly in the ThinApp package.

• Inventory Icon: Under [Build Options] in the PACKAGE.INI, look for an InventoryIcon= value. If one doesn’t exist, create it. Use a path internal to the project to define either an EXE or DLL with a numerical value or an ICO without a numerical value.

  Examples:
  This denotes use of the first ICON in the EXE.
  InventoryIcon=%ProgrameFilesDir%\AppFolder\program.exe,0

  This denotes use of the ICO file.
  InventoryIcon=%ProgrameFilesDir%\AppFolder\file.ico

• Entry Point Icon: Under each enabled Entry Point, you may need to define an Icon= value if the icon doesn’t properly appear from the defined executable in the Source= value. If manually defining the Icon= value, one must use a path internal to the project to define either an EXE or DLL with a numerical value or an ICO without a numerical value.

  Examples:
  This denotes use of the first ICON in the EXE.
  Icon=%ProgrameFilesDir%\AppFolder\program.exe,0

  This denotes use of the ICO file.
  Icon=%ProgrameFilesDir%\AppFolder\file.ico

The VMware KB “Handling the application suite icon when enabling a VMware ThinApp package for Horizon” goes into this in great detail.


]]> http://blogs.vmware.com/thinapp/2012/11/thinapp-icons-not-appearing-in-horizon.html/feed 0 http://blogs.vmware.com/thinapp/2012/11/thinapp-icons-not-appearing-in-horizon.html