locked
AppV application publishings problems with AD Access RRS feed

  • Question

  • I have setup an new environment for POC. I have installed the APPV 5.0 SP1 server installation successfull for my MANAGEMENT, PUBLISHING, AND DATABASE SERVER. I have also sequenced and packaged applications successfully. The problem I am having is that for testing I have domain admins in the AD Access group on the Management server for the applications. If I create another security group and give the access to the package, nothing gettings published.

    When I open the Publisher website, this is all I get:

    <Publishing Protocol="1.0">

    <Packages/>

    </Publishing>

    If I remove the new security group and leave domain admins, applications shows up and ready to be published.

    If somebody know how to fix this, Please share. Thanks!

    reference:

    

    http://social.technet.microsoft.com/Forums/en-US/98b79491-fa7d-42e1-9110-bea60b6f37af/appv-5-package-ad-access-issues?forum=mdopappv

    Monday, October 6, 2014 3:07 PM

Answers

All replies

  • By default you need to wait 10 min for sync at the backend. For a PoC or test envirnoment I would advice increasing the sync-cycle. Have a look here on how you can do that.
    What client do you use? SP2hotfix5?.

    Monday, October 6, 2014 4:01 PM
  • I have increased the sync-cycle and it registers with the management console.

    Now the only thing I see if I assign an application to an domain admin, the publishing server shows the publishing informaton from the website. (ex:http://appv-pub1:8080)

    If I assign an application to an security I just created, the publishing server showes

    This shows what Im doing:

    

    Monday, October 6, 2014 4:40 PM
  • Hello,

    1. When you access the website of the publishing server - is that account a member of the group the application is assigned to?

    2. Have you verified that no errors were generated when the publishing server attempts to retrieve the updated publishing information from the management server?

    3. 


    Nicke Källén | The Knack| Twitter: @Znackattack

    Monday, October 6, 2014 8:17 PM
  • 1. No. Just a domain admin created for the APPV environment.

    2. I do get errors from the publishing server:

    Monday, October 6, 2014 8:28 PM
  • If you browse to http://appv-pub1:8080 with an account which does not have any groups listed in the appv backend, this is default behavior. The url shows all packages the user has access to. So please add an user to your 7-zip group, log on to a client with that user, and browse to that website.
    As for these event errors; I've only seen them if you sequenced an app for instance on a 64-bit sequencer and try to publish it to a 32-bit client. Also; did you limit the OS during sequence?

    Monday, October 6, 2014 9:10 PM
  • Your error message indicates that the Management Server can't recognize the client's Operating System as to be supported. 

    If your clients are running Win 8.1 you have to install at least Hotfix 2 for SP1 on the App-V server(s)

     http://support.microsoft.com/kb/2897087/

    Your clients should have SP2 installed.


    Falko

    Twitter @kirk_tn   |   Blog kirxblog   |   Web kirx.org   |   Fireside appvbook.com

    Tuesday, October 7, 2014 7:57 AM
    Moderator
  • Ok. Thanks for the response, but I have tried that. I have also repackaged the application and published it, still same problem.

    Problem is more focused to the Management Server and Publishing Server. I am able to give domain admins access, then it lists on the xml of the publishing server. If I removed the domain admins and added domain users, then the xml lists no application(Whats shown above). If I keep everything with domain admins, application is able to be delivered to the client and working on the client.

    Tuesday, October 7, 2014 3:14 PM
  • Its not the client. If the xml not showing application on the publishing server then clients will not get application anyway.
    Tuesday, October 7, 2014 3:17 PM
  • Hello,

    If you create a new AD-Group. Make the account you are accessing the website member of the AD-Group. Ensure that the change of membership is updated on the client (you can verify this gpresult /R).

    Then assign the application the AD-Group.

    Does this change anything?


    Nicke Källén | The Knack| Twitter: @Znackattack

    Thursday, October 9, 2014 7:14 PM
  • The error message is exactly what is going on. There are no OS strings in the query string which is odd. Are you accessing through a proxy or some other intermediary device?

    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

    Saturday, October 18, 2014 5:50 AM