Possible Connection Group bug in AppV_Manage

Ahh ok, will start using 5.1.5 from now then. Cheers heaps!

Thanks, will look out for it.

From your compatibility chart, I see that v5.0.1.0 was the last version of AppV_Manage to work with App-V Client v5.0 SP3 or below. Will you be releasing an update to this for those of us whose estates are lagging behind and still haven't upgraded to 5.1 yet?

Ta,

Hi Tim,

I don't think I've explained my problem well enough. Pictures are reported to be worth a thousand words though so let me try 4000 words-worth instead

Here's the config screen of my setup.

You can see I'm running AppV_Manage v5.1.1.0 with App-V Client v5.0 SP2 HF4. You can also see I have disabled the new connection group format which as I understand it is correct for my client version because it pre-dates the CG format change in SP3.

Here's what happens when I try to create a CG.

Here I have two packages published and their Package and Version IDs are present and correct in the top pane. The problem is that for whatever reason, the Version IDs are not being retained when the packages are added to the CG. Note the VersionId column in the lower pane is blank.

Clicking "Create Group" at this point creates the XML OK but because the Version IDs are blank, we get this:


Here's what the resultant XML looks like in the flesh (word-wrapped purely to fit it all in the screengrab):

Note the blank section highlighted in red. I can confirm that populating these entries manually and re-running the relevant Powershell commands against the fixed XML file creates a CG perfectly so it is just the absence of the Version IDs that is the problem.

I've tried this with AppV_Manage v4.0, v5.0.1.0, v5.1.1.0 and v5.1.3.0 and it persists so I'm a bit confused. Am I still doing something wrong here or is this a genuine bug?

Thanks for the help, much appreciated!