locked
Issue syncing App-V publishing server with standard users RRS feed

  • Question

  • Hi everyone,

    We've got several terminal servers that rely heavily on App-V packages. The packages themselves sit on a file server but generally every package is held on the file server. Every package is fully cached on every terminal server.

    Currently, apps are published by AD group. A logon script first unpublishes every assigned package the user has, then checks membership for each group.  For each group, the script runs the Publish-AppVClientPackage for the corresponding app.

    We're trying to migrate the publishing to use an App-V server instead.

    So far, the publishing works like a charm for admin users. But when standard users log in, they get the progress bar but there's no further action.

    • Standard users can read and execute the .appv files on the file server (packages aren't hosted on the App-V server)
    • App-V packages can publish – as the existing system demonstrates
    • Event viewer is showing 19104 on event viewer (Part or all packages publish failed.)

    Any suggestions would be greatly appreciated!

    Additional info:

    • Servers are 2012R2, so the suggestion of installing KB 2533623 wouldn't count, no?
    • output of get-appvpublishingserver:
    Id                                    : 1
    SetByGroupPolicy             : False
    Name                              : <redactedserver01>
    URL                                 : http://<redactedserver01>.<domain>.local:8081
    GlobalRefreshEnabled       : True
    GlobalRefreshOnLogon     : True
    GlobalRefreshInterval       : 1
    GlobalRefreshIntervalUnit : Hour
    UserRefreshEnabled         : True
    UserRefreshOnLogon        : True
    UserRefreshInterval          : 1
    UserRefreshIntervalUnit   : Hour


    • Edited by SKLFX Tuesday, August 16, 2016 5:21 AM clarification
    Tuesday, August 16, 2016 5:11 AM

All replies

  • 1. Are there any connection groups created on the server?

    2. Can you open http://<redactedserver01>.<domain>.local:8081 in browser and see if the packages published to the user are listed there?

    Tuesday, September 20, 2016 1:00 AM
  • If you're using the appv infra, why are you still using a custom login script?

    Roy Essers

    Thursday, September 22, 2016 8:49 PM
  • 1. Are there any connection groups created on the server?

    2. Can you open http://<redactedserver01>.<domain>.local:8081 in browser and see if the packages published to the user are listed there?

    Thanks for the reply! The packages that are being deployed don't need to interact with one another so there are no connection groups defined.

    I'm getting all the right packages listed when connecting via port 8081.

    If you're using the appv infra, why are you still using a custom login script?

    The custom login script works, but its functionality is limited. When we've got the infrastructure working properly for standard users, the plan is to kick out the login script. Testing has involved users that don't get the login script.


    • Edited by SKLFX Tuesday, September 27, 2016 5:20 AM
    Tuesday, September 27, 2016 5:19 AM