Windows XP SP3 x86

　　　.net framework 3.5 SP1がインストールされていること。
　　　別途事前にインストールしておきます。

仮想化手順：

#1.キャプチャ用のクリーンなWindows 7にvSphere Client 5.5のインストーラを
デスクトップ等に、事前にコピーしておきます。
  VMware-viclient-all-5.5.0-1281650.exe

#2.VMware ThinApp Setup Captureを起動します。[Next>]をクリック

#3.Prescanを行います。

#4.Prescanが完了すると、Install Application画面が表示されるので、最小化しておきます。

#5.VMware-viclient-all-5.5.0-1281650.exeを実行します。日本語を選択してOKを押します。

#6.vSphere Client 5.5 のインストールを行います。

#7.このまま状態で本来であれば、キャプチャ作業は、完了ですが、
vSphere Clientは、多くの言語に対応しているので、充実したHELPコンテンツがあります。
そのファイル郡が大量にあるので、キャプチャが中々完了しません。小一時間かかります。
そのため、日本語と英語を残して、それ以外の言語については、削除してしまいます。

HELPファイルだけで、なんとファイル数　15,449個、フォルダ数294個
サイズは、112MBです。
これらの作成にかかったと思われる方々の労力を考えると、申し訳ないのですが。。。

エクスプローラを起動し、HELPフォルダから「C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Help」

英語と日本語を残し、それ以外の言語については、削除します。

追加で、英語と日本語以外の言語リソースファイル群を削除してしまいます。
この辺りは、好みでお願いします。

#8.最小化しておいた、Setup Captureを元のサイズに戻し、Postscanを押します。

#9.エントリーポイントの設定では、VMware vSphere Client.exeにチェックを付けてNextを押します。

#10.後は、ウィザードに従って、次々と進めていきます。

[Compression]
;圧縮を有効
CompressionType=Fast

[Isolation]
DirectoryIsolationMode=Merged

[FileList]
;不要なファイルをパッケージに含めないようにします。
ExcludePattern=*.msi,:*.msp,*.log,*.inf,*.cat

[BuildOptions]
;Disk優先圧縮を有効にする。
OptimizeFor=Disk

;IME対策
ExternalCOMObjects={FCE4078B-72B5-4122-95E4-45B5E2E88031};{F57CA90F-D309-4056-9616-6670A27BE8A1}
ChildProcessEnvironmentExceptions=svchost.exe;DLLHost.exe;msiexec.exe;explorer.exe;ImeBroker.exe

;デバッグ用のvCMD.exeとvRegedit.exeをエントリーポイント化します。
[vCmd.exe]
Source=%SystemSystem%\cmd.exe
Shortcut=VMware vSphere Client 5.5.exe
Disabled=0

[vRegedit.exe]
Source=%SystemRoot%\regedit.exe
Shortcut=VMware vSphere Client 5.5.exe
Disabled=0

動作確認：
　Windows7 SP1 x86環境で動作させた結果
　ちゃんと動きました。もちろんインストールされていません。

　Windows XP SP3のクリーンな環境で動作させた結果

　※必ず、.net Framework 3.5 SP1をインストールしてから実行し下さい。

※.net3.5SP1をインストールしていない環境で動作させると以下のエラーが表示されます。

　「Unable to load DLL C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe->mscoree.dll
指定したモジュールが見つかりません。」

 mscoree.dllは、.netのランタイムです。
要約すると、.net3.5 SP1がインストールされていないので、モジュールが見つからない。
と言うエラーです。

番外編：
ちょっとしたこだわり。
仮想化したvSphere Clientを起動すると、ディスプレイの右下にLaunchingバーが表示されますが
そこの名称がVpxClientと表示されます。（実際のEXE名が表示されます。）

どうせなら、vSphere Client 5.5と表示したいですよね。
変更方法ですが、Package.iniの設定で名称の変更は、可能です。

StatusbarDisplayName=VMware vSphere Client 5.5

例）

[VMware vSphere Client 5.5.exe]

Source=%ProgramFilesDir%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe

WorkingDirectory=%ProgramFilesDir%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\

Icon=%SystemRoot%\Installer\{4CFB0494-2E96-4631-8364-538E2AA91324}\arpIcon.exe

Shortcuts=%Desktop%;%Programs%\VMware

ReadOnlyData=Package.ro.tvr

StatusbarDisplayName=VMware vSphere Client 5.5

英語版のUIを用意してみる。

仮想化でプリセールスしてるSEの一日 さんのネタなのですが、

「VMware vSphere Client を一時的に英語表示に切り替える」

http://d.hatena.ne.jp/ogawad/20120426/1335436039

ショートカットでパラメータを付加することも可能なのですが、

-locale en_US

What's New

Native - HKLM\Software\7-Zip
ThinApp - HKLM\Software\7-Zip
Native - HKCR\CLSID\{23170F69-40C1-278A-1000-000100020000
ThinApp - HKCR\CLSID\{23170F69-40C1-278A-1000-000100020000

Redirected keys - (32-bit registry keys are redirected)
Native - HKLM\Software\7-Zip
ThinApp - HKLM\Software\Wow6432Node\7-Zip
32-bit keys are redirected to Software\Wow6432Node

Shared keys - (Shared by both 32-bit and 64-bit view)
Native - HKLM\SOFTWARE\Clients
ThinApp - HKLM\SOFTWARE\Clients

• The .alt file is required for Application Synchronization of ThinApp 5.0 packages. In case of forced AppSync, if the .alt file is missing, the user will receive a message box and the downloaded file will be named as .1 update
• If the Appsync feature uses IIS server the user needs to add .alt file to the mime types.
• All the shortcuts, entry points and PDC's of both (old and new) applications should have the same name for a successful AppSync. Example Microsoft office word 2003.exe andMicrosoft office word 2007.exe should be named as Microsoft office word.exe.

• Conditional support for virtualizing App Sense.
• Existing version of Horizon will work with ThinApp 5.0, 32 bit applications, but support for 64 bit applications might be available in future releases.
• Conditional support for virtualizing 64 bit applications.
• Previous versions of View will work with ThinApp 5.0, 32 bit applications, but support for 64 bit applications might be available in View 5.3.
• Conditional support for virtualizing Microsoft Office 2013 and Internet Explorer 10.

• http://www.vmware.com/products/thinapp/
• http://www.vmware.com/go/thinappsdk/

仮想化手順：

#1.キャプチャ用のクリーンなWindows 7にView Client 2.2のインストーラを
デスクトップ等に、事前にコピーしておきます。
  VMware-Horizon-View-Client-x86-2.2.0-1404668

#2.VMware ThinApp Setup Captureを起動します。[Next>]をクリック

#3.Prescanを行います。

#4.Prescanが完了すると、Install Application画面が表示されるので、最小化しておきます。

#5.VMware-Horizon-View-Client-x86-2.2.0-1404668.exeを実行します。

#6.vSphere Client 5.5 のインストールを行います。

USBリダイレクトの機能は、仮想アプリでは利用できないので、

インストールオプションから除外しておきます。

#7.のインストールが完了すると、システムの再起動を求められます。
キャプチャ中なので、再起動すると全てが失われてしまいそうで、躊躇すると思いますが
気にせずに、「はい」を押して再起動してしまいます。

ログインします。(同じユーザーアカウント)

自動的にSetup Captureが起動します。

「Continue installation process」を選択して、「Next」をクリックします。

元の画面に戻ってきました。

一安心ですね。

#8.Setup CaptureのPostscanを押します。

#9.エントリーポイントの設定では、VMware Horizon View Client.exeにチェックを付けてNextを押します。

#10.後は、ウィザードに従って、次々と進めていきます。

[Compression]
;圧縮を有効
CompressionType=Fast

[Isolation]
DirectoryIsolationMode=Merged

[FileList]
;不要なファイルをパッケージに含めないようにします。
ExcludePattern=*.msi,:*.msp,*.log,*.inf,*.cat

[BuildOptions]
;Disk優先圧縮を有効にする。
OptimizeFor=Disk

;IME対策
ExternalCOMObjects={FCE4078B-72B5-4122-95E4-45B5E2E88031};{F57CA90F-D309-4056-9616-6670A27BE8A1}
ChildProcessEnvironmentExceptions=svchost.exe;DLLHost.exe;msiexec.exe;explorer.exe;ImeBroker.exe

;デバッグ用のvCMD.exeとvRegedit.exeをエントリーポイント化します。
[vCmd.exe]
Source=%SystemSystem%\cmd.exe
Shortcut=VMware Horizon View Client 2.2.exe
Disabled=0

[vRegedit.exe]
Source=%SystemRoot%\regedit.exe
Shortcut=VMware Horizon View Client 2.2.exe
Disabled=0

動作確認：
　Windows7 SP1 x86環境で動作させた結果
ちゃんと動きました。もちろんインストールされていません。

※Windows ファイアウォールの警告が表示されますが、アクセスを許可すればOKです。

　Windows8 x86環境で動作させた結果

WindowsXP SP3 x86環境で動作させた結果

　エラーが表示されました。

　

「MSVCR90.dll が見つからなかったため、このアプリケーションを開始できませんでした。アプリケーションをインストールし直すとこの問題は解決される場合があります。 」


MSVCR90.dllは、Microsoft Visual C++ 2008 SP1 再頒布可能パッケージ (x86)に含まれるランタイムです。
（VC2008ランタイム）

VisualC++2008で開発されたソフトを動作させるために必要です。
ViewClient2.2は、VC2008で開発されているんですね。

キャプチャ環境を今回は、Windows7で行ったので、こんな結果になります。
Windows7は、VC2008ランタイムがある程度存在しているので、キャプチャしても
仮想アプリには、含まれません。
Windows8も同様にOS自体にVC2008ランタイムの大部分がインストールされています。

Windows XPの場合は、このVC2008ランタイムは存在しないので、別途インストールするか
WindowsXP環境でキャプチャすれば、VC2008ランタイムも仮想アプリケーションパッケージに
含まれるようになります。

必要なバージョンは、MSVCR90.dll 9.0.30729.4148限定です。
古いバージョンだと動作しません。

「Microsoft Visual C++ 2008 Service Pack 1 再頒布可能パッケージ ATL のセキュリティ更新プログラム」をインストールした後に、Windows Updateすると動作します。
http://www.microsoft.com/ja-jp/download/confirmation.aspx?id=11895


VC2008 SP1ランタイムそのままでは、動作しません。
理由は、MSVCR90.dllのバージョンが9.0.30729.1のためです。
このライブラリには、脆弱性に関する問題があったようで、更新モジュールは、
Windows Update経由で適用する必要があります。
（もしかしたら、ダウンロードできるかも知れないですが、見つけられませんでした。。。）

2013-11-21追加：確認したところ、上記リンクでDLできるVC2008のランタイムで動作しました。ごめんなさい。

※「Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148」が必要。

詳細は、wsnm.exeのApplicationManifestの中で以下のように利用するMSCVR90.dllを指定しているためですが、厳格な方法なのでお作法に則った正しい記述です。

<assemblyIdentity type="win32" name="Microsoft.VC90.CRT" version="9.0.30729.4148" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

と、色々書きましたが、Windows XPで利用する場合は、WindowsXP環境でViewClientを
キャプチャしたほうが手っ取り早いと思います。

簡単にWindowsXPで動作すると思ったのですが、意外とめんどくさかったです。。。
「利用するOSと同じOSでキャプチャする。」という鉄則を守らなかった私が悪いんですけどね。

参考情報：
「貸そうか？」さんのBlogに、View Client 2.2の詳細な情報があるので
一読すると幸せになれると思います。
VMware Horizon View Client for Windows バージョンアップ
http://vm-fun.blogspot.jp/2013/11/vmware-horizon-view-client-for-windows.html

ThinApp ライセンスキーと表示名の更新方法について

はじめに：

Setup Capture のライセンスキーの更新方法：

仮想アプリを起動すると、画面右下に起動バーが表示されます。

表示される名称を変更する場合は、License display nameを変更し

再度、Buildします。

更新が完了したら、Capture済みの仮想アプリケーションProjectをbuildします。

「ThinApp で仮想化したアプリのバージョンアップについて」

What's New

The ThinApp 5.0.1 has the following new enhancements,

• The welcome page of ThinApp Setup Capture now has a link to a KB article, which provides guidelines on how to virtualize applications using ThinApp.
• The two ChildProcessEnvironment parameters which are now present by default inPackage.ini file are:
• ChildProcessEnvironmentDefault
• ChildProcessEnvironmentExceptions
• Package.ini parameters are now case insensitive.

The ThinApp 5.0.1 release provides a number of key bug fixes detailed in the Resolved Issues section.

For additional information about ThinApp 5.0.1, visit the following Web sites:

• http://www.vmware.com/products/thinapp/
• http://www.vmware.com/go/thinappsdk/

Supported Operating Systems

VMware ThinApp supports the following operating systems for running virtualized 64-bit applications

• Windows 7 64-bit
• Windows Server 2008 R2
• Windows 8 64-bit
• Windows Server 2012
• Windows 8.1 64-bit
• Windows Server 2012 R2

VMware ThinApp does not support the following operating systems for running virtualized 64-bit applications

• Windows XP 64-bit
• Windows Server 2003 64-bit
• Windows Vista 64-bit
• Windows Server 2008 64-bit

NOTE:The operating system platforms listed under 64-bit application exclusion list are supported for 32 bit applications.

Earlier Releases of VMware ThinApp

Features from prior releases of VMware ThinApp are described in the release notes for each release. To view release notes for prior releases, click one of the following links:

• VMware ThinApp 5.0
• VMware ThinApp 4.7.3

Resolved Issues

The ThinApp 5.0.1 release resolves the following issues:

• Autodesk AutoCAD 2014 displays error 80004005 on launch
  When you start virtual version of Autodesk AutoCAD 2014, the application exits with an error message similar to the following
  CLR Error 80004005.
  Resolution: Increase in the limit on DLL loading, improves the support for applications that load large number of DLLs.


• Microsoft Office 2010 fails to install virtualized Japanese Microsoft Office 2010 MSI on Japanese Windows Server 2003 R2 32-bit, German Windows Server 2003 R2 32-bit and Windows Server 2008 operating systems 
  When you attempt to install virtualized Japanese Microsoft Office 2010, the installation fails on Japanese Windows Server 2003 R2 32-bit and German Windows Server 2003 R2 32-bit operating systems.
  Resolution: Internationalization support has been improved further.


• ThinDirect feature might not work if you capture Internet Explorer 10 with Include an entry point for the system installed IE option
  If you capture Internet Explorer 10 through the Setup Capture using the Include an entry point for the system installed IE option, the ThinDirect feature might not work,
  Resolution: Fixed an issue where the memory section of the Internet Explorer 10 frame process to a sandbox was not being properly isolated.


• Incorrect service names are displayed on virtual command prompt 
  When you run the net start on a virtual command prompt, the services are displayed with path name instead of service name, which is DLL name and resource ID. This is incorrect.
  Example: @%systemroot%\system32\browser.dll,-100
  Resolution: Executing services.msc now lists running services by their name.


• Microsoft Office 2010 applications fail if you open or save a file on Windows 8 64-bit operating system 
  When you open or save a file on a Windows 8 x64, the virtual version of Microsoft Office 2010 might stop responding.
  Resolution: An incorrect call to free an already allocated memory was fixed.


• Microsoft Office 2010 64-bit package is installed on Windows7 32-bit View Agent desktop
  The virtual version of 64-bit Microsoft Office 2010 package can be installed on Windows 7 32-bit View Agent desktop which is incorrect.
  Resolution: We now check the bitness of the package and deployed operating system. 


• AutoCAD 2009 LT freezes with unable to load scree.dll message
  Virtualized AutoCAD LT 2009 fails to start with an unable to load scree.dll error message.
  Resolution: A flaw in loading 32-bit resource DLL from a 64-bit process was fixed.


• Fatal Application Exit error is displayed when you start Microsoft PowerPoint 2013 on Windows 8.1
  When you start virtual version of Microsoft PowerPoint 2013, on the Windows 8.1 operating system, the application displays a warning message similar to the following
  Fatal Application Exit.
  This issue occurs because, Microsoft Office2013 uses Windows activation servicesppsvc.exe on Windows8.1 instead of osppsvc.exe.
  Resolution: To resolve, add ChildProcessEnvironmentExceptions=sppsvc.exe in Package.ini.


• SolidWorks eDrawings 2013 x64 Edition might not start on Windows 7 x64
  Virtualized SolidWorks eDrawings 2013 x64 Edition fails to start on Windows 7 64-bit operating system. The SolidWorks 64-bit application is dependent on the Visual C++ 2005 SP1 (64 Bit) runtime, which is one of the prerequisites for using this application.
  Resolution: For more information see KB article 2070004


• Microsoft Office is fails to insert OLE objects that are not office components
  The virtual version of Microsoft Office (2003, 2007, 2010 and 2013) fails to insert OLE components like Bitmap image or WordPad document. This issue is observed on Windows 8 and Windows 8.1 operating systems.
  Resolution: Improved COM support on Windows 8 and Windows 8.1 solves this issue.


• Internet Explorer 7 and Internet Explorer 10 might not start on Windows 7 and Windows 8.1 operating systems.
  The virtual version of Internet Explorer 7 and Internet Explorer 10 fail to start on Windows 7 and Windows 8.1 operating systems. On Windows 8.1, 32-bit system Internet Explorer 10 freezes on launch and on Windows 8.1, 64 bit system Internet Explorer 10 exits silently after launch.
  Resolution: ThinApp now loads the KernelBase and Kernel32.dll from the runtime machine.


• Firefox displays a termination exception after playing a Flash clip
  If you start the virtual Firefox browser and play a flash clip, the browser stops with a Windows error message.
  Resolution: This is a Firefox issue, which has been fixed in the Firefox codebase. Please use the latest version of Firefox.


• Virtual registry might not read the value that contains both non-ASCII characters and # or % symbol
  Virtual registry might not read a value that contains both the ASCII characters and # or % symbols. When non English Unicode characters are part of macro string, the string comparison of macros was incorrect.
  Resolution: Fixed a bug in ThinApp Macro strings expansion.


• ThinDirect plug-in might cause a native Internet Explorer 8 to stop responding
  When you use the ThinDirect plug-in the native Internet Explorer 8 might stop responding.
  Resolution: For more information see KB article 2073845.


• Unable to download any files with virtual Internet Explorer 10
  Using a Virtual Internet Explorer 10, when native Internet Explorer 10 is not installed, if you click on download link, the Save as dialog box might not appear and the file download might not happen.
  Resolution: Improved support for packages which use COM surrogacy. Virtual COM surrogacy is now supported through TASurrogate.exe/TASurrogate64.exe, which are new additions to this release.

Known Issues

The following known issues are known to occur in the ThinApp 5.0.1 release:

• Microsoft Project 2010 and Microsoft Visio 2010 cause an MSI installer and licensing error on deployment systems with Microsoft Office 2010 natively installed.
  For more information see KB article 2077860.


• The virtual version of Internet Explorer 6.0 fails to open some specific URLs.
  Workaround: Add the following parameter in Package.ini build options
  [BuildOptions]
  NotificationDLLs=T2embed.dll


• The virtual version of Microsoft Outlook 2010 32-bit captured on Windows 7 64-bit fails to start on Windows 7, Windows 8 and Windows Server 2012, 64-bit operating systems.
  For more information see KB article 2063264.


• When you use virtual Internet Explorer 10 in low or medium integrity to download files and later close it, you may find orphaned Internet Explorer(iexplore.exe) processes still running after the application has been closed.  These processes will be re-used if application is re-opened, this issue will be fixed in a future release.


• If the protected view is enabled in Microsoft Excel 2013, then the virtual version of Microsoft Excel 2013 fails to open a file from the network path.
  Workaround: Disable protected view from File > Options > Trust Center > Trust Center Settings > Protected View > Enable Protected View for files located in potentially unsafe locations.


• Microsoft Visio 2010 help files are not displayed on all 64-bit operating systems.


• When you start virtual version of Microsoft Office 2013 (32-bit or 64-bit) on Windows 8, or Windows 8.1 operating system, the application exits with an error message. For more information, see KB article 2062691


• In a virtualized Microsoft Office 2013 package, if you attempt to launch the help file with the F1 key , the application displays an Installer 1719 error message. This issue is observed on Windows 7, 64-bit operating system.


• Virtualized Internet Explorer 10 (32-bit) does not work on Windows 8.1 operating systems (32-bit and 64-bit).


• If the user provides an AppLink path to all the files using Regular expressions, for exampleRequiredApplinks=c:\Flash\bin\*;
  the AppLink feature will fail if there are files present in the bin directory other than PDC.
  Workaround: AppLink will display an incompatibility error when any file other than an application PDC is linked with the application.
  For a successful AppLink, please mention the absolute path of the application PDC as:RequiredApplinks=c:\Flash\bin\FlashPDC.dat


• When capturing 64-bit Internet Explorer 9 on Windows 7, the ThinDirect feature does not work.
  Workaround
  1. On a clean machine run Setup Capture and do a prescan.
  2. Install 64-bit Internet Explorer 9 and do a postscan.
  3. At the Setup Capture - Entry Points screen, ensure that Internet Explorer (64-bit).exeis checked.
  4. At the Setup Capture - Native Browser Redirection screen, do not add any URLs.
  5. Save the project.
  6. At the Setup Capture - Ready to Build screen, check Skip the build process and clickNext > Finish.
  7. Create the text file ThinDirect.txt in the project directory.
  8. Ensure that the first line reads [Internet Explorer (64-bit).exe].
  9. On each line below, add a URL you want redirected by ThinDirect.
  10. Save ThinDirect.txt and double-click build.bat to build the package.


• In ThinApp 5.0.1, the Package.ini parameter AllowUnsupportedExternalChildProcesses is not working.


• In ThinApp 5.0.1, the Package.ini parameter HidePrinters is not working.


• If you attempt to start two instances of virtual Microsoft Word 2013 or Microsoft PowerPoint 2013, the application becomes unresponsive.


• Horizon Workspace 1.5 does not have the support necessary for reading metadata from 64 bit ThinApp binaries and is thus incompatible with ThinApp 5.0 packages. The Horizon Workspace vNext would support ThinApp 5.0 packages.


• ThinApp fails to rebuild the project on a Windows 7, x86 English operating system, if you change the Outdir parameter in package.ini and replace it with any of the following language characters
  • Simplified Chinese
  • Traditional Chinese
  • Japanese
  • Korean


• Issues with ThinApp 5.x and Microsoft Office 2010, see KB article 2062694.


• Issues with ThinApp 5.x and Microsoft Office 2013, see KB article 2062691.

For more information about known issues with ThinApp packages, see the VMware Knowledge Base.

仮想化手順：

#1.キャプチャ用のクリーンなWindows 7にView Client のインストーラを
デスクトップ等に、事前にコピーしておきます。
  VMware-Horizon-View-Client-x86-3.0.0-1887158.exe

#2.VMware ThinApp Setup Captureを起動します。[Next>]をクリック

#3.Prescanを行います。

#4.Prescanが完了すると、Install Application画面が表示されるので、最小化しておきます。

#5.VMware-Horizon-View-Client-x86-3.0.0-1887158.exeを実行します。

#6.View Client のインストールを行います。

USBリダイレクトの機能は、仮想アプリでは利用できないので、

インストールオプションから除外しておきます。

#7.のインストールが完了すると、システムの再起動を求められます。
キャプチャ中なので、再起動すると全てが失われてしまいそうで、躊躇すると思いますが
気にせずに、「はい」を押して再起動してしまいます。

ログインします。(同じユーザーアカウント)

自動的にSetup Captureが起動します。

「Continue installation process」を選択して、「Next」をクリックします。

元の画面に戻ってきました。

一安心ですね。

#8.Setup CaptureのPostscanを押します。

#9.エントリーポイントの設定では、VMware Horizon View Client.exeにチェックを付けてNextを押します。

#10.後は、ウィザードに従って、次々と進めていきます。

[Compression]
;圧縮を有効
CompressionType=Fast

[Isolation]
DirectoryIsolationMode=Merged

[FileList]
;不要なファイルをパッケージに含めないようにします。
ExcludePattern=*.msi,:*.msp,*.log,*.inf,*.cat

[BuildOptions]
;Disk優先圧縮を有効にする。
OptimizeFor=Disk

;IME対策
ExternalCOMObjects={FCE4078B-72B5-4122-95E4-45B5E2E88031};{F57CA90F-D309-4056-9616-6670A27BE8A1}
ChildProcessEnvironmentExceptions=svchost.exe;DLLHost.exe;msiexec.exe;explorer.exe;ImeBroker.exe

;デバッグ用のvCMD.exeとvRegedit.exeをエントリーポイント化します。
[vCmd.exe]
Source=%SystemSystem%\cmd.exe
Shortcut=VMware Horizon View Client 3.0.exe
Disabled=0

[vRegedit.exe]
Source=%SystemRoot%\regedit.exe
Shortcut=VMware Horizon View Client 3.0.exe
Disabled=0

動作確認：
　Windows8.1 x64環境で動作させた結果
ちゃんと動きました。もちろんインストールされていません。

※Windows ファイアウォールの警告が表示されますが、アクセスを許可すればOKです。

　

参考：
　View Client 2.2の仮想化手順は、こちら。
　http://tunemicky.blogspot.jp/2013/11/horizon-view-client-22.html

「ThinApp で仮想化したアプリのバージョンアップについて」

What's New

VMware ThinApp 5.1 is the latest version of ThinApp. This release has the following enhancements.

ThinApp Package Management

In earlier versions of ThinApp, to change some specific Package.ini parameters, you had to first make those changes in the configuration file, save the file, and rebuild the package. Using the new ThinApp package management feature, you can dynamically reconfigure the attributes of deployed ThinApp packages at runtime. ThinApp Package management helps IT administrators manage ThinApp packages and define group policy for each package. Each package to be managed must have an associated group policy defined using its inventory name.

When you install ThinApp 5.1, a new folder named Policy is created in the installation directory. This folder contains tools and templates for managing ThinApp packages and contains the following files:

• AppPolicy.exe
• README.TXT
• ThinAppBase.adml
• ThinAppBase.admx
• ThinAppGeneric.adml
• ThinAppGeneric.admx

ThinApp selects the policy precedence when you rebuild a package and deploy it. If a package is managed by a group policy, ThinApp gives precedence to the policy over its Package.ini configuration.

Group Policy Administrative Templates

ThinApp 5.1, introduces the group policy administrative template (ADMX/ADML) files. With these template files you can reconfigure group policy settings for applications that were packaged by ThinApp. The GPO files work on domain controllers that run in the following environments:

• Windows Server 2008
• Windows Server 2008 R2
• Windows Server 2012

Administrative Template files contain markup language that is used to describe a registry-based Group Policy. The administrative files are divided into language-neutral (.admx files)and language-specific resources (.adml files), available to all Group Policy administrators. These factors allow Group Policy tools to adjust the user interface according to the administrator's configured language.

Reconfiguring Attributes of Deployed ThinApp Packages

In addition to ThinDirect, with ThinApp 5.1 you can now reconfigure or manage the following attributes of a deployed package:

• AppSync
• AppLink
• Entry-Point Shortcuts

Note: To know how to reconfigure these package attributes, see the ThinApp 5.1 User's Guide.

ThinDirect

In ThinApp 5.1, the following enhancements have been made to the ThinDirect plug-in:

• Support for the update of ThinDirect settings at specified time intervals
In ThinApp 5.1, the ThinDirect functionality has been enhanced to periodically poll for the ThinDirect setting changes. Since, the ThinDirect settings are now detected dynamically, the user need not restart the browser to view the updated changes.
• Support for dynamic changes to Thindirect via ADM
In ThinApp 5.1, you can use ThinDirect.ADM file to manage the thindirect enabled firefox.
• Support for Overriding the Thindirect settings through GPO
In ThinApp installation directory, locate the Thindirect.admx and ThinDirect.adml files. Use these files to manage the settings for ThinDirect feature by defining a group policy object. If the Thindirect feature is defined through the GPO, these settings would override the text file (thindirect.txt) based redirection.
• Support for Redirection between two virtual browsers
ThinApp 5.1 supports redirection between two virtual browsers.
• Support for Thindirect in Mozilla Firefox
In ThinApp 5.1, ThinDirect has been enhanced to work with Mozilla Firefox version 22 and later. In earlier versions of ThinApp, ThinDirect was limited to Internet Explorer.

New Package.ini Parameter Introduced

ThinApp 5.1 introduces the SandboxWindowClassName parameter. When you set theSandboxWindowClassName=1 you can sandbox or isolate the application defined window class names created and used within the ThinApp package. 

Extracting an existing ThinApp project to a system

ThinApp 5.1 allows you to extract an existing ThinApp project to a capture and build operating system by using snapshot.exe and snapshot64.exe commands. 

Pre-requisites
Before you extract an existing ThinApp project to a capture and build operating system, ensure that the following conditions are met:

• Verify that the architecture and type of the captured operating system is the same as that of deployed operating system.
• Perform the extraction of an existing ThinApp project on a clean capture and build machine.
• Ensure that the user profile in the existing virtual project is the same as that of the capture and build machine.

ThinApp 5.1 has the following command line options to extract existing projects to capture and build operating systems.

• snapshot.exe: Is used to extract an existing ThinApp project to a capture and build 32-bit operating system
• snapshot64.exe: Is used to extract an existing ThinApp project to a capture and build 64-bit operating system

Note: To know more about the process for extracting existing ThinApp packages, see the ThinApp 5.1 User's Guide.

MAPI Support

ThinApp 5.1 supports the Messaging Application Programming Interface (MAPI) on the following Microsoft Windows platforms:

• Windows 7
• Windows 8 32-bit
• Windows 8 64-bit
• Windows 8.1 32-bit
• Windows 8.1 64-bit

ThinApp 5.1 provides the DefaultEmailProgram option in Package.ini to register a virtual email client as the host's default email program. You have to enable this option to register the default email program. The Messaging Application Programming Interface (MAPI) is not supported on Windows XP x86 operating system. For more information, see KB artilce2087898.

Support for Internet Explorer 10 and Internet Explorer 11

ThinApp 5.1 supports Internet Explorer 10 and Internet Explorer 11 only on the Windows 7 operating system.

Support for Windows 8.1

ThinApp 5.1 works on the Windows 8.1 August update (Update 2).

For additional information about ThinApp 5.1, visit the following Web site:

• http://www.vmware.com/products/thinapp/

Resolved Issues

The ThinApp 5.1 release resolves the following issues:

• When you access web sites with Flash content virtualized Adobe Flash 11.3 freezes the Firefox browser 
  When you package Firefox along with Adobe Flash 11.3 and access a web site with Flash content, the browser freezes and fails to load the flash content.
  Resolution: This issue is resolved in ThinApp 5.1.
• ThinDirect plug-in should read configuration files more often
  In ThinApp 5.1, the ThinDirect plug-in does not poll the registry and files for setting changes, the changes to the file and registry are not detected dynamically, you must restart the browser to update the changes.
  Resolution: ThinDirect plug-in has been enhanced to handle this issue.
• ThinApp fails to use virtual Microsoft Outlook as the host's default email program
  On a system with a virtual Microsoft Outlook 2013 (or other email clients), if you right-click a file and select the Send to Mail Recipient option from the pop-up menu, the virtual Outlook 2013 fails to start and does not send the mail.
  Resolution: ThinApp 5.1 provides the DefaultEmailProgram option in Package.ini to register a virtual email client as the host's default email program. You have to enable this option to register the default email program.
• ThinApp displays the encoding of the trace reports in ANSI, replacing any occurrence of non-ASCII characters with question marks
  On a Simplified Chinese Windows 7, 64-bit operating system, while virtualizing the Firefox 18 application, if you include non-ASCII characters for the Inventory Name and build the package and generate the text trace report, you might notice that the report encoding has changed to ANSI and some of the non-ASCII characters are replaced with question marks.
  Resolution: ThinApp 5.1 has enhanced the existing localization support with the introduction of Unicode characters, which resolves this issue.
• An error message is displayed when you copy some characters from a PDF using a virtual version of Adobe Reader 11
  When you open a pdf file using a virtual version of Adobe Reader 11 and attempt to copy some characters, ThinApp displays a pop-up error message:
  There was an error while copying to the Clipboard. An internal error occurred
  This issue is observed on Windows 7, 32-bit and 64-bit Service Pack 1 operating systems.
  Resolution: Enhanced support for Clipboard APIs in ThinApp 5.1 resolves this issue.
• Log Monitor displays a warning message if you close and relaunch it without closing the associated ThinApp application
  When you close the Log Monitor associated with a ThinApp application and attempt to relaunch the Log Monitor without closing the ThinApp application, ThinApp displays the following warning message:
  Log Monitor is already running, only one copy may be active at a time.
  If you check the Task Manager you might not notice any instance of Log Monitor running.
  Resolution: Modifying the synchronization mechanism of Log Monitor module resolves this issue.
• ThinApp cannot print when a 32-bit virtual application is deployed to a 64-bit operating system
  On a 64-bit Windows operating system, you cannot print from a ThinApp virtual package captured using a 32-bit Windows operating system.
  Resolution: Setting the isolation mode of %SystemSystem(x64)%\spool in the ThinApp package 64-bit operating system to MERGED state resolves this issue.
• Adding a ThinApp application to a repository results in an API object error
  When you attempt to add a ThinApp application (Flash Player 12) to a repository, VMware View does not allow this action and displays the following error message:
  : HRESULT hr = 0x8c420002. Internal error: unable to create API object
  Resolution: Enhanced support for ThinApp MSI in ThinApp 5.1 resolves this issue.
  
• Internet Explorer 10 fails to load JAVA
  On a Windows 7 32-bit operating system, if you package Internet Explorer 10 with Java or use the Applink feature, Internet Explorer fails to load JAVA.
  Resolution: To resolve this issue ThinApp no longer loads kernel32.dll orkernelbase.dll from the package.
• On 64-bit operating systems, the ThinDirect plug-in does not work between virtual browsers
  If you enable a 32-bit virtual browser with ThinDirect, deploy it on a 64-bit environment and allow the browsers to participate in redirection with other 32-bit and 64-bit systems (with or without ThinDirect plug-in enabled), the ThinApp application fails to launch the browsers redirected using the ThinDirect plug-in.
  Resolution: To resolve this issue, generate an .alt file, set theAltArchitectureShortcut=1 in Package.ini file and rebuild the package.
• On Simplified Chinese and Japanese operating systems, virtual applications fail to start if you use non-ASCII characters in folder paths or application names when Log Monitor is running
  In Simplified Chinese and Japanese Windows 7 64-bit environments, if you virtualize an application that includes non-ASCII characters in the application name, and then copy the virtual application to a non-ASCII directory and launch the Log Monitor before you launch the application, the application launch fails.
  Resolution: ThinApp 5.1 has enhanced the existing localization support with the introduction of Unicode characters, which resolves this issue.
• ThinApp fails to launch native and virtual instances of Adobe Reader 11 concurrently 
  On a Windows 7 32-bit operating system, when you have virtual and native instance of Adobe Reader 11, ThinApp can launch only one instance.
  Resolution: Setting the parameters SandboxWindowClassName=1 andIsolatedSynchronizationObjects=ACROSEMAPHORE_R11 in package.ini resolves this issue.
• Adobe Reader 11 displays incorrect content in the print preview window and in the printed document
  When you virtualize Adobe Reader 11 and attempt to print a pdf document, you might notice some inconsistency in content in the Print Preview window and the printed document.
  Resolution: Improved communication support between parent and child processes resolves this issue.
• Microsoft Visio 2007 and 2010 display an error message if you insert an equation
  On a virtual version of Microsoft Visio 2007 and 2010, if you attempt to insert an equation using the Insert > Picture > Equation option, the ThinApp application displays the following error message:
  Visio internal error: #3400 Action 1646: Insert Equation
  Resolution: ThinApp 5.1 has fixed issues related to virtual OLE object, which resolves this issue.
• ThinApp 5.0 does not create a Thinstall registry key
  Using ThinApp 5.0, if you virtualize any application and navigate to the virtual registry, you may not see the Thinstall registry key. This issue is observed for all the applications virtualized using ThinApp 5.0.
  Resolution: This issue is fixed in ThinApp 5.1.
• J-Trader Client fails to start on Windows 7 32-bit operating system
  If you virtualize the J-Trader client on a Windows 7 32-bit operating system that has Java 1.6u31 natively installed and edit the value of -Xmx in JTrader.14J.ini file, the virtual application fails to start.
  Resolution: Enhanced support for memory management in ThinApp 5.1 resolves this issue.
• WinCVS fails to save registry settings
  When you log in to virtual WinCVS as Administrator and make changes to the preferences by using the Admin > Preferences option, the application fails to save the changes to the registry and displays the following error message:
  Error while saving preferences!
  Resolution: This issue is resolved in ThinApp 5.1.
• taskschd.msc fails to start from a virtual command prompt
  On a Windows 7 32-bit operating system, when you capture an empty package, launch a virtual command prompt, and then start taskschd.msc, the taskschd program displays a fatal error message with non-specific error information.
  Resolution: This issue is resolved in ThinApp 5.1.
• schtasks executable exits silently when run from a virtual command prompt
  On a Windows 7 32-bit operating system, when you capture an empty package, launch a virtual command prompt, and then start schtasks.exe, the schtasks program exits silently without displaying summary information for all scheduled tasks.
  Resolution:This issue is resolved in ThinApp 5.1.
• The IgnoreDDEMessages ThinApp parameter does not work on Windows 8.1 64-bit operating system
  On a Windows 8.1 64-bit operating system that has Microsoft Office 2013 natively installed, if you copy *.xls, *.ppt, *.doc and *.html files to file system, set the ThinApp package ini parameter IgnoreDDEMessages=1 and if you double click on any of the copied files, the ThinApp application does not allow the native Microsoft Office 2013 applications to open these files. Incorrectly, virtual Microsoft Office 2013 applications opens the files instead.
  Resolution: This issue is resolved in ThinApp 5.1.
• The virtual version of the Citrix v11.150 client launches the native Citrix Receiver instead of the virtual Citrix client
  When you start the virtual version of Citrix v11.150 client, the virtual client launches a native Citrix Receiver instead of the virtual Citrix client and displays the following error message:
  Citrix Receiver Configuration Manager: Could not find the file named (C:\Planon.ica). Please check your installation, or contact your administrator
  Resolution:This issue is resolved in ThinApp 5.1. For more information, see KB article2087931.
• Citrix Receiver fails with ThinApp 5.0.1
  If you start a Citrix Receiver that was virtualized using ThinApp 5.0.1, the Citrix receiver fails to start and displays a fatal error message.
  Resolution:This issue is resolved in ThinApp 5.1.
• Internet Explorer 6 displays ClassFactory cannot supply requested class error on Windows 8.1 operating system
  On a virtualized version of Internet Explorer 6, if you attempt to save a file to a folder shortcut using the File > Save as option, ThinApp displays the following error message:
  ClassFactory cannot supply requested class
  This issue is observed on the Windows 8.1 operating system.
  Resolution:To resolve this issue in ThinApp 5.1, support for handling calls to the native shell have been enhanced.
• During application synchronization, the Thinreg option fails to register an application if there is a whitespace in the path
  If you use the AppSync option to synchronize an application and there is a whitespace in the path of the application executable, Thinreg option fails to register the new application.
  Resolution:ThinApp now registers new binaries after Application Synchronization, even if the path contains a whitespace.
• The ExportReg option of ThinApp�s virtual registry tool, vregtool, fails if the REG_SZ, REG_BINARY and REG_DWORD values are not set
  When you virtualize Adobe Reader 11, and the registry parameters REG_SZ, REG_BINARYand REG_DWORD are not set,vregtool's ExportReg option fails.
  Resolution:The ExportReg option of vregtool now handles empty REG_DWORD values.
• Log Monitor logs extraneous information along with the version of Internet Explorer on Windows 8 and 8.1.
  If you use Log Monitor on Windows 8 or 8.1 to generate a trace report, you might notice that the version of Internet Explorer shown in the logs has an extraneous prefix along with its actual version number. This issue occurs on Windows 8.1 and Windows 8 operating systems.
  Resolution:Log Monitor no longer displays extraneous information along with the Internet Explorer version.
• Google Chrome browser displays blank web pages on Windows Server 2003
  When you start a native Chrome browser to view a Web site, close it,  and then view a Web site with a virtual version of Chrome, the virtual browser might display a blank page. This issue is observed on Windows Server 2003 operating systems.
  Resolution:This issue is resolved in ThinApp 5.1.

Known Issues

The following issues are known to occur in the ThinApp 5.1 release:

• Internet Explorer 11 fails to start on Windows 8 and Windows 8.1 operating systems.
• Messaging Application Programming Interface (MAPI) is not supported on Windows XP x86 operating systems.
• The virtual version of Internet Explorer 6.0 fails to open some specific URLs.
  Workaround: Add the following parameter in Package.ini build options
  [BuildOptions]
  NotificationDLLs=T2embed.dll
• If protected view is enabled in Microsoft Excel 2013 it will fail to open files from a network path.
  Workaround: Disable protected view from File > Options > Trust Center > Trust Center Settings > Protected View > Enable Protected View for files located in potentially unsafe locations.
• Microsoft Visio 2010 help files are not displayed on 64-bit operating systems.
• 32-bit Internet Explorer 10 does not work on Windows 8.1 operating systems (32-bit and 64-bit).
• If you attempt to start two instances of virtual Microsoft Word 2013 or Microsoft Power Point 2013 they will become unresponsive.
• ThinApp fails to build package on Windows 7 x86 English operating systems if you change the Outdir parameter in Package.ini and replace it with any of the following language characters:
  • Simplified Chinese
  • Traditional Chinese
  • Japanese
  • Korean
• ThinApp cannot change registry key names on Windows 8 x86 operating systems.