none
App-V 5.0 SP1 Managing Connection Group Priority from the publishing server

    Question

  • Hello,

    We have several connection groups published to users, some of them contain the same package. We need to use connection group priority in order to be able to publish 2 or more connection groups to users that contain the same base package.

    When we set the connection group priority from the App-V 5.0 Service Pack 1  management server the priority is not passed on to clients:

    Management Server: (the application names are edited)

    PS C:\Windows\system32> Get-AppvServerConnectionGroup
    
    Id            : 20
    Name          : Application1
    Description   : 
    GroupGuid     : 28ecf8d0-ecc3-4341-93d7-ed8d7cce34f5
    VersionGuid   : 5264fff3-489a-4adf-9eca-99b2247233ad
    VersionNumber : 2
    Priority      : 0
    Packages      : {Application0, Application1}
    Entitlements  : {MYDOMAIN\App-V Users}
    IsPublished   : True
    
    Id            : 21
    Name          : Application2
    Description   : 
    GroupGuid     : fadf93cd-526e-47bb-a873-97759ac873be
    VersionGuid   : 6ba73b86-1027-4062-8fba-8b9be17f6450
    VersionNumber : 2
    Priority      : 1
    Packages      : {Application0, Application2}
    Entitlements  : {MYDOMAIN\App-V Users}
    IsPublished   : True
    
    
    PS C:\Windows\system32> 

    SQL Server:

    

    On the client: http://<management server>:54321

    - <Groups>
    - <Group GroupId="28ecf8d0-ecc3-4341-93d7-ed8d7cce34f5" VersionId="5264fff3-489a-4adf-9eca-99b2247233ad" Priority="0" Name="Application1">
      <Package PackageId="90a84f78-80b2-4879-99b3-82159b6a5b32" /> 
      <Package PackageId="bd68d855-af8a-4bf4-a2ba-4bd4696db160" /> 
      </Group>
    - <Group GroupId="fadf93cd-526e-47bb-a873-97759ac873be" VersionId="6ba73b86-1027-4062-8fba-8b9be17f6450" Priority="0" Name="Application2">
      <Package PackageId="90a84f78-80b2-4879-99b3-82159b6a5b32" /> 
      <Package PackageId="d2129d2f-8104-43a5-a400-843ea63166c9" /> 
      </Group>
      </Groups>
      </Publishing>

    On the Client in powershell:

    PS C:\Windows\system32> Get-AppvClientConnectionGroup GroupId : fadf93cd-526e-47bb-a873-97759ac873be VersionId : 6ba73b86-1027-4062-8fba-8b9be17f6450 Name : Application2 IsEnabledToUser : True UserPending : False IsEnabledGlobally : False GlobalPending : False InUse : False InUseByCurrentUser : False PercentLoaded : 100 Priority : 0 GroupId : 28ecf8d0-ecc3-4341-93d7-ed8d7cce34f5 VersionId : 5264fff3-489a-4adf-9eca-99b2247233ad Name : Application1 IsEnabledToUser : True UserPending : False IsEnabledGlobally : False GlobalPending : False InUse : False InUseByCurrentUser : False PercentLoaded : 100 Priority : 0 PS C:\Windows\system32>

    Any idea's on why this is happening?

    Thanks!

    p.s. to better understand what i am trying to do, take a look at this post from Thamim Karim.

    http://blogs.technet.com/b/virtualvibes/archive/2013/02/13/connection-group-conflicts-in-app-v-5-0.aspx




    • Edited by KoenEijken Friday, April 12, 2013 2:32 PM
    Friday, April 12, 2013 6:29 AM

Answers

  • Thanks in part to Tim Mangan's AppV_Manage tool found here (http://www.tmurgent.com/Tools/AppV_Manage/ I was able to come up with work around while Microsoft attempts to fix this.  The work around involves a few more steps and at large scale I would not use it but it suffices for now.

    Step 1. Download AppV_Manage and install on App-V 5.0 client

    Step 2. Create the connection group(s) you need using the tool. Set the appropriate priority for the group.

    Step 3. Copy the connection group XML files from the client to a central repository; optionally renaming them something that makes sense. I rename the XML files the same name that I chose for the connection group name.

    Step 4. Go to each end point where clients will be logging in and add the connection group; DO NOT enable it at this point. Powershell: Add-AppvClientConnectionGroup -Path C:\pathtoXMLFile.xml

    Step 5. Use a logon script or similar technology to enable the connection group for the user at logon based on their AD group membership.  I am using Appsense to do this.  Basically if user is in group A then enable connection group A.   Powershell: Enable-AppvClientConnectiongroup -Name NameofCconnectiongroup

    I still am maintaining the Default Connection group with a priority of 0 on the management server with no issue. All subsequent groups need to be managed in this way or something similar.

    I would be interested to find out about any other work arounds people find.

    PS. This is just one of several problems with App-V 5.0.  Microsoft please fix your product!!!

    Tuesday, June 25, 2013 1:17 PM

All replies

  • Hello,

    Have the Publishing server refreshed the configuration from the Management Server?


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

    Friday, April 12, 2013 8:09 AM
  • Hi Nicke,

    Thank you for your reply, the management server and the publishing server role are on the same machine, what should I refresh exactly?

    I tried an iisreset, to be sure but that did not do anything.

    Koen.

    p.s. if you refer to the app-v client side "Sync-AppvPublishingServer" command, that runs successfully, and the published information remains unchanged.

    • Edited by KoenEijken Friday, April 12, 2013 9:25 AM
    Friday, April 12, 2013 9:04 AM
  • Hello,

    The App-V Publishing Server refreshes its configuration on an interval, see this article;

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


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

    Friday, April 12, 2013 9:19 AM
  • Hi Nicke,

    Thank you for your answer.

    Since this is my testing environment I had already set this option to 5.

    PUBLISHING_MGT_SERVER_REFRESH_INTERVAL = 5 

    Instead of the default 600.

    Also, an iisreset should fix the problem if it had anything to do with restarting the iis application pool.

    Koen.


    • Edited by KoenEijken Friday, April 12, 2013 9:46 AM
    Friday, April 12, 2013 9:46 AM
  • Hello,

    I would open a ticket with Microsoft


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

    Friday, April 12, 2013 8:50 PM
  • Hi Nicke,

    I will certaily consider opening a ticket.

    I am wondering if anyone can confirm that they have this working. I have 2 App-V 5/5 SP1 environments, and this issue is present in both. Besides the connection group priority, everything else works fine.

    Thanks,

    Koen.


    • Edited by KoenEijken Thursday, April 18, 2013 12:35 PM
    Thursday, April 18, 2013 12:34 PM
  • Hello,
    i can reproduce this issue in my 5.0SP1 env.
    The priority is set correctly in the database, but on the client the priority stays set to "0".
    Have you heard something from MS?
     
    Best
    Ariel

    Monday, May 13, 2013 10:54 AM
  • Hello,

    We have the exact same issue here.

    Is anybody found how to solve this problem?

    Thank you,

    Sylvain

    Wednesday, May 22, 2013 3:09 PM
  • Thanks in part to Tim Mangan's AppV_Manage tool found here (http://www.tmurgent.com/Tools/AppV_Manage/ I was able to come up with work around while Microsoft attempts to fix this.  The work around involves a few more steps and at large scale I would not use it but it suffices for now.

    Step 1. Download AppV_Manage and install on App-V 5.0 client

    Step 2. Create the connection group(s) you need using the tool. Set the appropriate priority for the group.

    Step 3. Copy the connection group XML files from the client to a central repository; optionally renaming them something that makes sense. I rename the XML files the same name that I chose for the connection group name.

    Step 4. Go to each end point where clients will be logging in and add the connection group; DO NOT enable it at this point. Powershell: Add-AppvClientConnectionGroup -Path C:\pathtoXMLFile.xml

    Step 5. Use a logon script or similar technology to enable the connection group for the user at logon based on their AD group membership.  I am using Appsense to do this.  Basically if user is in group A then enable connection group A.   Powershell: Enable-AppvClientConnectiongroup -Name NameofCconnectiongroup

    I still am maintaining the Default Connection group with a priority of 0 on the management server with no issue. All subsequent groups need to be managed in this way or something similar.

    I would be interested to find out about any other work arounds people find.

    PS. This is just one of several problems with App-V 5.0.  Microsoft please fix your product!!!

    Tuesday, June 25, 2013 1:17 PM
  • Hello,

    See this article;

    http://support.microsoft.com/kb/2873465/en-us


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

    Friday, August 09, 2013 11:20 PM
  • That hotfix does fix the issue with Priority.

    There is another issue where the endpoints do not clean up connection groups that are no longer published or have been deleted from the management console. This can result in a conflict with the connection groups and results in app launch failure. I heard they will be coming out with a fix for this issue but I have not seen it yet.

    Friday, October 04, 2013 11:22 AM
  • I'd like to confirm that the above hotfix solved this issue for me!

    -apply this hotfix on your AppV server

    -set priority with powershell on your server

    -remove the old con.grp's on your clients (powershell and cache)

    Thanks


    Monday, December 02, 2013 1:52 PM