locked
App-V 5.1 Client UI not showing RRS feed

  • Question

  • Hello,

    We have installed the App-V 5.1 client and are currently having issues with the UI not coming up so at the moment, everything has to be done through powershell.

    Would there be some GPO setting that we are missing to cause this?

    Thanks,

    Robert

    Tuesday, December 1, 2015 5:29 PM

Answers

  • From AppV 5.0 SP2, Microsoft separated the Client Console from Client. You now have to install the UI application which is available below,

    https://www.microsoft.com/en-au/download/details.aspx?id=41186

    This is for AppV 5.0. I don't find one for 5.1. Will check & get back to you if I find one for 5.1


    Posted AS IS with No Warranties. Mark as Answer if this answers your question, It will help other community members.

    Wednesday, December 2, 2015 6:09 AM

All replies

  • From AppV 5.0 SP2, Microsoft separated the Client Console from Client. You now have to install the UI application which is available below,

    https://www.microsoft.com/en-au/download/details.aspx?id=41186

    This is for AppV 5.0. I don't find one for 5.1. Will check & get back to you if I find one for 5.1


    Posted AS IS with No Warranties. Mark as Answer if this answers your question, It will help other community members.

    Wednesday, December 2, 2015 6:09 AM
  • There is none (yet) for 5.1, but you can use the 5.0 version without issues on the 5.1 client. you can even virtualise the GUI if you want to.
    Wednesday, December 2, 2015 11:04 AM
  • Thank you for checking. It's ridiculous to think of that as the only answer (Using the 5.0 AppV UI). I honestly agree with making the UI a separate package.

    What I'm referring to that makes this ridiculous is tech net article: https://technet.microsoft.com/en-us/library/mt346490.aspx

    To access the client management console

    On the computer running the App-V 5.1 client, click Start and select Microsoft Application Virtualization Client.

    Wednesday, January 27, 2016 7:21 PM
  • I totally agree on that. This is just incorrect.
    Thursday, February 4, 2016 1:12 AM