When we look in the App Portal UI for targeted devices for a retirement campaign or an upgrade campaign, we are not seeing the devices we are expecting to see. I want to confirm that this is not what the known issue is about.
@CharlesW So the application does not even need to exist in App Portal...it just checks FNMS to see if the FlexeraID for the old version is installed on a machine?
@dbeckner, When setting up a retirement campaign, you need to have a catalog item with a matching Flexera ID configured and an associated uninstall package tied to it. The uninstall option for the catalog item must be enabled. It is technically possible to do a retirement campaign without a corresponding catalog item, but then you'd have to set up the SmartUninstall package (which is limited on what it can uninstall).
When setting up an upgrade campaign, you need to have a catalog item with a valid install package. The Flexera ID of that catalog item does not matter, because you select that upgrade catalog item when you configure the campaign properties. The Flexera ID you select to create the upgrade policy will be checked in FNMS, so you don't need a catalog item in App Portal that matches that Flexera ID. Please note that an upgrade campaign only runs the "new" install on the target machine. It does not first run an uninstall of the previously detected application. You must make sure that the installer for the "new" application is able to uninstall the old application first, or you need to set up a supersedence relationship in the SCCM application model such that targeting the new application will automatically target an uninstall of the old application first (all done within SCCM, transparent to App Portal).
Hopefully, this makes it a little clearer.
@CharlesW, keep me honest if I'm blowing smoke.