Wouldn't you do chargebacks based on the installation/usage reporting you see in FNMS? Assuming you've loaded the enterprise group information into FNMS, you should be able to see those reports based on Cost Center. ... View more

I agree it would be great if we could extract the icon images from the EXE, but even if App Portal had the ability to extract images from ICO/EXE files, it doesn't have access to the package source in SCCM (plus App Portal supports several other deployment systems in addition to SCCM).  I generally find it isn't too hard to do a Google/Bing image search for "<InsertApplicationNameHere> icon PNG" and then download the image to the <AppPortalInstallationFolder>\web\backgrounds\packages folder on the server.  Since the App Portal UI automatically resizes images for display to 80x80 pixels, as long as you find an image with square dimensions that isn't too large (file size), you should be in good shape.  If you're using App Broker for ServiceNow, then you need to either locate images that are already the appropriate size, or you can use one of many image processing tools to batch process them all to a common size (since ServiceNow's UI doesn't automatically resize the images for you). What I'd really like to see is the ability for App Portal/App Broker to pull things like title, description, category, icon, etc. from either the deployment system metadata or from something like Technopedia/Application Recognition Library.  I believe we'll start to see some of that in the SaaS version of App Broker when that's released; however, the images would probably carry some degree of difficulty due to things like publisher copyrights/redistribution rights. ... View more

I was also going to suggest an IISReset/ESDService restart.  Do you see any errors related to the FNMS integration?  That is usually the most common cause of not seeing that tab.  If there are problems with the FNMS integration, that tab will not appear, regardless of the user's administrative permissions. ... View more

As stated previously, they are two different SKU's of the same product.  Depending on what entitlements are tied to your account, you may see both links in the Product and License Center, but the installation binaries will be the same whether you pull them from the App Portal folder or the App Broker folder.  After you run the installation, you will be prompted to upload your license file.  The license file you select will determine which SKU is activated. Note: I am only referencing the on-prem products here.  Once the SaaS version of App Broker becomes available, it will have some downloadable components, and those will be different than what is downloadable for the on-prem version.   ... View more

Another thing I've stumbled across recently (though I don't think it's the cause in this particular case) is that App Portal can add a device to a direct membership rule on a collection even if that device does not fall within the parent limiting collection.  The end result is that App Portal will indicate the device has been successfully added to the collection and may even indicate a successful policy refresh.  However, since the device is not part of the parent limiting collection, it will never actually be added to the collection membership of the target collection and will therefore not receive the policy either.  Since you said you can remove the device and re-add it to the collection and have it succeed, I don't think this is the issue you're experiencing, but just wanted to bring attention to this scenario.  I suppose it's also possible that you could have two devices with the same name (perhaps different domains) and that App Portal is putting the wrong one into the collection rule.  Then when you remove that and re-add the "correct" device, it succeeds. ... View more

Sorry, I'm not following the scenario.  I'm not sure why having an active/valid ServiceNow connection would be required simply to upgrade App Broker from one version to the next.  Even from a testing perspective after upgrading, you could create a test request without ServiceNow just within the App Broker UI to verify that the connections to FNMS (if relevant) and SCCM (or other deployment system) are working.  If you actually want to test the ServiceNow workflow, then of course you'd need a "good" working environment. When you say you have a bunch of duplicate assets, what do you mean by that? ... View more

Teri is 100% spot on.  A few other (hopefully) helpful notes: If using a catalog item for harvesting (which is the most reliable/recommended way), it must have an uninstall deployment, and you must check the box under Deployment > Global > Installation Options that says Enable Uninstallation (Remove from collection)?.  If you have an uninstall deployment but you don't check that box, App Portal will still attempt to use SmartUninstall (if enabled) or will simply not attempt to uninstall (if SmartUninstall is not enabled) instead of using the uninstall deployment on the catalog item. If there are multiple catalog items with the same Flexera ID (ARL), App Portal will check to see if there is a previous App Portal deployment to that device and will attempt to use the uninstall deployment for the same catalog item that was used for the install deployment.  If there is no previous install deployment for that device, or if the catalog item that was used to install does not have an uninstall deployment tied to it, then one of the catalog items with that Flexera ID that has an enabled uninstall deployment will be selected at "random" (it's probably not actually random, but I'm not sure what the "algorithm" is -- perhaps the one with the highest catalog/package ID, i.e. the most recently created one?). If using SmartUninstall, please note that the uninstall is performed by using msiexec /x <product_code> and is run in the context of the account that SCCM is configured to run under for that deployment (e.g. installer account, currently logged in user, SYSTEM, etc.).  As such, if the installation was performed under the same user context, or if the installation was installed for "all users", then the uninstall should work fine.  If the installation was performed under a different user context and was installed "only for the current user", the installation may fail or may leave some traces behind (e.g. Start Menu/Desktop shortcuts) because they would have been installed into a different registry hive/user profile.   ... View more

App Broker is not a "free" version of App Portal.  App Broker for ServiceNow and App Broker for BMC are separate SKUs of the same product that are intended for immersive integration with the corresponding ITSM system's own portal UI.  End users and approvers interact only with ServiceNow or BMC Digital Workplace (formerly MyIT), while catalog administrators still interact with Flexera's (App Broker) admin web UI.  The installation binaries are the same.  The only difference will be the license file you upload after installation.  The license file will dictate if you have an App Portal license, App Broker for ServiceNow license, or App Broker for BMC license. ... View more

@sempra123 , all product documentation can be found on HelpNet.  You can also get there by selecting Documentation from the Other Resources menu in the navigation bar of this website.  Once on the HelpNet site, select App Portal / App Broker as the Product and then select your desired version (e.g. 2019 R1) from the Version drop-down.  You'll see a few different guides and release notes (including the Installation Guide) available as both browsable HTML and downloadable PDF formats. ... View more

First, make sure that you don't have "backup" copies of the original or new DLL's in the App Portal directories.  Any backups should be stored in a separate location outside of the installation path.  Second, replacing DLL's usually involves replacing those DLL's in a few different locations (usually 4 different locations).  While the files may be named the same in each folder and sometimes may even be the same/similar size, they are not always identical.  Make sure you put back the right files in the right places.  Third, check the Windows event logs to see if there are any detailed errors provided when attempting to start the ESDService.  If all else fails, try rebooting the server (or perhaps you've already done that, in which case, I'm all out of ideas). ... View more

Strictly from an App Portal/FNMS integration perspective, here are places to look (assuming you're using the Flexera Service Gateway): The webapi.config has 3 instances of the FNMS URL that need to be updated.  Make sure you got all 3 of them. Launch FlexeraServiceGatewayHost and View Services to verify the URL's that are currently registered.  If not correct, check the webapi.config from #1 above and then rerun the registration tool.  Repeat this check to verify the newly registered service URLs. Within the App Portal admin UI, on the Flexera Integration tab, you should see (in small blue text directly below the FSG server name) the URL to the FNMS endpoint.  Make sure that is correct.  If incorrect, see #2 above. ... View more

Teri, I think you had been working with flexible approvals at one point.  Did you ever get that working?  Would that address (avoid) this issue? ... View more