CMCB 1610 & UWP Detection Method

Configuration Manager CB version 1610 has a confirmed bug in detecting Universal Windows Platform (UWP) apps.

The Detection Method is correctly created, but the script execution on client side is ignoring the app version.

Updating an UWP will always result in ‘Already Compliant’

Rebuild:

  • Create Application from appx-/appxbundle-file as ‘Windows app package’
  • Check Detection Method
  • cmcb_uwp_01
  • Deploy to test-client
  • Create newer version of the same application
  • Check Detection Method
  • cmcb_uwp_02
  • Deploy to test-client
  • App is not updated
    • Monitoring shows ‘Already Compliant’
    • sw_euc03
    • Client log shows the detection script (“C:\Windows\CCM\SignedScripts\detectwindows8app.ps1”) is executed w/o parameters

Workaround:

  • Create Application as script
  • Use the existing script (“C:\Windows\CCM\SignedScripts\installwindows8app.ps1”) in Deployment Type per platform
  • Handover parameter

e.g.


-AppPath "yourapplication.appx" and -DependencyPath "Dependencies\x64\Microsoft.NET.Native.Framework.1.3.appx" "Dependencies\x64\Microsoft.NET.Native.Runtime.1.4.appx" "Dependencies\x64\Microsoft.VCLibs.x64.14.00.appx"

  • Use script as Detection Method

e.g.


AppxPackageFullName = "%YourPackageFullName%"
$exists = Get-AppxPackage | Where-Object {$_.PackageFullName -match $AppxPackageFullName}
if ($exists)
{
Write-Host "Installed"
}

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s