**UPDATE – This has been tested against device targeted installs and this also fails with the same error **

A TechNet forum thread was recently raised by Jesse Harris on the issue of applications not publishing within ConfigMgr 2012 R2 Sp1 when targeted at user collections. Jesse did some testing and discovered that hotfix 4 was the issue.

Off I went into my lab and confirmed this problem. The error reads:

Publish-AppvClientPackage : A parameter cannot be found that matches parameter
name ‘UserSID’.
At line:1 char:351
+ … 113b564c-648b-4e88-9a1b-bb1e5e960d56_UserConfig.xml’ -UserSID ‘S-1-5- …
+                                                          ~~~~~~~~
+ CategoryInfo          : InvalidArgument: (:) [Publish-AppvClientPackage]
, ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.AppV.AppvClient
PowerShell.PublishAppvPackage

AppEnforce 26/05/2015 00:33:12 2912 (0x0B60)
AppV command [“C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe” -ExecutionPolicy Bypass import-module ‘C:\Program Files\Microsoft Application Virtualization\Client\AppvClient\AppvClient.psd1’;  Publish-AppvClientPackage -PackageID 113b564c-648b-4e88-9a1b-bb1e5e960d56 -VersionID ea35e5ee-0a64-4006-a71b-906d6b348324  -DynamicUserConfigurationPath ‘C:\WINDOWS\CCM\SystemTemp\AppVTempData\113b564c-648b-4e88-9a1b-bb1e5e960d56_UserConfig.xml’ -UserSID ‘S-1-5-21-1892080804-1021483945-3126336620-1128’ -ev err; if(($err -ne $null) -and ($error[0].Exception.AppvWarningCode -eq 8589935887)) {$host.SetShouldExit(4736)}] failed with return code 1. AppEnforce 26/05/2015 00:33:12 2912 (0x0B60)
AppVCommandUtil::RunAppVCommand() failed. (0x87d0128f) AppEnforce 26/05/2015 00:33:12 2912 (0x0B60)
AppVManageClient5X::PublishAppVPackage() failed for package [113b564c-648b-4e88-9a1b-bb1e5e960d56]. (0x87d0128f) AppEnforce 26/05/2015 00:33:12 2912 (0x0B60)
CAppV5XHandler::PublishSpecifiedAppVComponents() failed. (0x87d0128f) AppEnforce 26/05/2015 00:33:12 2912 (0x0B60)
CAppV5XHandler::PublishAppVComponentsForDT() failed. (0x87d0128f) AppEnforce 26/05/2015 00:33:12 2912 (0x0B60)
CAppV5XHandler::InstallApp() failed. (0x87d0128f) AppEnforce 26/05/2015 00:33:12 2912 (0x0B60)

I did further testing and discovered that HF5 works fine and the problem does not manifest with this release.

I hope to do some more testing today to discover if computer targeted collections are also effected and to see if earlier hotfix versions were impacted.

In the meantime I have raised this at Connect so Microsoft has some visibility of the problem.

**UPDATE – This has been tested against device targeted installs and this also fails with the same error **

Here’s a breakdown of the testing:

App-V 5.0 SP2 – Tested ok

App-V 5.0 SP2 HF1 – Not tested

App-V 5.0 SP2 HF2 – Tested ok

App-V 5.0 SP2 HF4 – Fails to publish

App-V 5.0 SP2 HF5 – Tested ok

App-V 5.0 SP3 – Tested ok

App-V 5.0 SP3 HF1 – Tested ok

Advertisements