none
VMware View thick Client

    Question

  • Has anyone successful sequenced this app before?

    I was trying to sequence this yesterday and was successful, but then when I ran the sequence after publishing, I received the following error:

    "VMWare View Client failed to start. Required plugins not available."

    Using v4.6 64bit sequencer running in Windows 2008 Server R2. Reason for this is because the application will be streamed to Citrix client... lol, a a virtual server hosting a virtual app that launches virtual windows; probably to a virtual machine somewhere else.

    Anyway, if anyone has some suggestions or better yet a receipe, it would be VERY much appreciated.  It seems like such a simple job.  Oh, also, I de-selected the USB driver as well during the install.

    ~Lane

     

    Saturday, December 11, 2010 5:33 PM

Answers

  • I've  sequenced it succesfully.

     

    It seems that the client is missing some registry keys in the package after virtualisation. The keys seems te be in the package (you see them in your sequencer!)  but when you stream the package, they will not be available on the workstation. Mayby a bug or so.

    the key is: [HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM

     

    after including the keys in the osd file, the error was gone..

    • Proposed as answer by znack Monday, November 14, 2011 10:48 AM
    • Marked as answer by Aaron.ParkerModerator Monday, November 14, 2011 11:18 AM
    Monday, November 14, 2011 10:41 AM

All replies

  • Hello,

    Have you asked the vendor why such an error message might occur?
    /Znack
    Sunday, December 12, 2010 1:23 AM
  • Not yet since yesterday, but thought maybe someone had done this app already so thought I would ask here as well.
    Sunday, December 12, 2010 1:36 AM
  • Hello,

    Well, some general thoughts;

    1. Is the Windows client 64-bit? Usually its a good idea to sequence on the target operating system if problem arises 

    2. Check VMware forums for more knowledge as to why this error message occurs

    One link suggestion would be; http://communities.vmware.com/message/1540285

    3. Understand the application more of what it loads and tries to perform when starting the application inorder to identify why such a failure would occur


    /Znack
    Monday, December 13, 2010 4:06 PM
  • Hi,

    Did you resolve your issue? I've had the same problem and wondered if you resolved the issue.

    Kind Regards,

    John

    Friday, February 4, 2011 2:56 PM
  • No. Advised them to install locally - sorry.
    Friday, February 4, 2011 6:45 PM
  • Did anyone ever manage to sequence Vmware view client with app v?

    Friday, April 29, 2011 2:38 PM
  • Not I
    Friday, April 29, 2011 2:49 PM
  • I've  sequenced it succesfully.

     

    It seems that the client is missing some registry keys in the package after virtualisation. The keys seems te be in the package (you see them in your sequencer!)  but when you stream the package, they will not be available on the workstation. Mayby a bug or so.

    the key is: [HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM

     

    after including the keys in the osd file, the error was gone..

    • Proposed as answer by znack Monday, November 14, 2011 10:48 AM
    • Marked as answer by Aaron.ParkerModerator Monday, November 14, 2011 11:18 AM
    Monday, November 14, 2011 10:41 AM
  • Hello,

    Great sharing! If possible, please write a complete recipe here;

    http://social.technet.microsoft.com/Forums/en-US/prescriptiveguidance/threads


    /Znack
    Monday, November 14, 2011 10:47 AM
  • Excellent ... I'll give it a try.
    Monday, November 14, 2011 10:59 AM
  • I was able to get the View Client sequenced today after tinkering with the registy settings in the OSD file. I sequenced on a Windows XP SP2 machine running the 4.6 SP1 sequencer.
     
    I had to open the package in the sequencer and on the OSD tab I added the registry elements in there.
     
    Here is a copy and paste from the OSD after it was created so you can see all of the registry keys/values I had to add. Basically I had to add all of the HKLM\SOFTWARE\VMware, Inc.\VMware VDM\Plugins\ keys/values.
     
     
    <REGISTRY>
    <REGKEY HIVE="HKLM" KEY="SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wsnm\winauth" NOREDIR="FALSE">
    <REGVALUE NAME="Filename" REGTYPE="REG_SZ">ws_winauth.dll</REGVALUE>
    </REGKEY>
    <REGKEY HIVE="HKLM" KEY="SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wswc\command" NOREDIR="FALSE">
    <REGVALUE NAME="Filename" REGTYPE="REG_SZ">wswc_command.dll</REGVALUE>
    </REGKEY>
    <REGKEY HIVE="HKLM" KEY="SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wswc\http" NOREDIR="FALSE">
    <REGVALUE NAME="Filename" REGTYPE="REG_SZ">wswc_http.dll</REGVALUE>
    </REGKEY>
    <REGKEY HIVE="HKLM" KEY="SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wswc\pcoip" NOREDIR="FALSE">
    <REGVALUE NAME="Filename" REGTYPE="REG_SZ">wswc_pcoip.dll</REGVALUE>
    </REGKEY>
    <REGKEY HIVE="HKLM" KEY="SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wswc\rdp" NOREDIR="FALSE">
    <REGVALUE NAME="Filename" REGTYPE="REG_SZ">wswc_rdp.dll</REGVALUE>
    </REGKEY>
    <REGKEY HIVE="HKLM" KEY="SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wswc\rsa" NOREDIR="FALSE">
    <REGVALUE NAME="Filename" REGTYPE="REG_SZ">wswc_rsa.dll</REGVALUE>
    </REGKEY>
    <REGKEY HIVE="HKLM" KEY="SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wswc\tunnel" NOREDIR="FALSE">
    <REGVALUE NAME="Filename" REGTYPE="REG_SZ">wswc_tunnel.dll</REGVALUE>
    </REGKEY>
    <REGKEY HIVE="HKLM" KEY="SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wswc\ui" NOREDIR="FALSE">
    <REGVALUE NAME="Filename" REGTYPE="REG_SZ">wswc_ui.dll</REGVALUE>
    </REGKEY>
    <REGKEY HIVE="HKLM" KEY="SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wswc\uimanager" NOREDIR="FALSE">
    <REGVALUE NAME="Filename" REGTYPE="REG_SZ">wssm_uimanager.dll</REGVALUE>
    </REGKEY>
    <REGKEY HIVE="HKLM" KEY="SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wswc\winauth" NOREDIR="FALSE">
    <REGVALUE NAME="Filename" REGTYPE="REG_SZ">ws_winauth.dll</REGVALUE>
    </REGKEY>
    </REGISTRY>
     
     
    Once I did that the package runs fine.
    • Proposed as answer by Rakoz Friday, July 27, 2012 12:16 PM
    Wednesday, January 18, 2012 8:23 PM
  • Nice find LeslieB9! I tested it on my end today since I needed to do it myself here. Here are my steps.

    The following setup are as follow:

    - App V sequencing machine: Windows 7 Enterprise x86 running App-V Sequencer 4.6 SP1
    - VMView 4.5 x86

    1. Create a New Virtual Application Package
    2. Create Package (default)
    3. Ensure virtual package is ready to be packaged and click Next
    4. Select Standard Application (default)
    5. Select Perform Custom Installation and Next
    6. Create a Virtual Application Package Name (ie VMView)
    7. Select Run and start the installation of VMWare-viewclient
    8. Select Next on Welcome Screen of the Installation
    9. Next on EULA
    10. Next on License Agreement
    11. On Custom setup, disable USB Redirection and you may also disable “Log in as current user” option. Change the installation path to the Q:\(name of your package)
    12. Default Server should be empty (if you configure the default server, you may need to import the registry key for that also)
    13. Uncheck Create shortcut on Desktop and Start Menu Programs folder
    14. Verify your installation summary
    15. Once the installation is complete, it will prompt to reboot. Do not reboot at this point and click Cancel.
    16. Finish the sequencing
    17. The next screen will show no application listed on the first use task. This is OK so click Next
    18. Click Next on Installation report
    19. Select Customize and Next
    20. There will be no application shortcut so you must select Add here and point to “Q:\(name of your install dir)\bin\wswc.exe”
    21. On the next screen you may run for optimization then close the app.
    22. Once the sequence is done you may save your work.

    I had a previous installation of View on another Windows 7 and exported the following registry key HKLM\Software\VMware, Inc.\VMWare VDM\Plugins

    Using OSD Editor from Login Consultants, I was able to import the registry key and sucessfully launched the application.

     

    Hopes this helps.

    • Proposed as answer by LeslieB9 Tuesday, June 11, 2013 4:38 PM
    Friday, February 3, 2012 6:59 PM
  • Thanks a lot guys, with the tips here I managed to Appv VMware view. But it's the strangest thing. After you make the package and save the OSD file the Regkeys are gone on the deployment server. And it won't start locally either anymore. (Same error : vmware view client failed to start. required plugins not available) so export them before you make the package,or from another installation)

    If you use a 64-bit version like me the correct key is : HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.

    Import it with OSD editor and it works perfect.

    Wednesday, October 21, 2015 1:42 PM