About sara_b

sara_b · ‎Oct 06, 2020

The installations are definitely computer targeted, not user, I just wanted to ensure it wasn't going to block a Requester from requesting the same software for different target machines.

sara_b · ‎Oct 01, 2020

Does that look at just the user, or does that also look at the target? (say - a manager requesting the same software for multiple users in the department)

sara_b · ‎Oct 01, 2020

To add a little information - we're using App Portal 2019 R1

sara_b · ‎Oct 01, 2020

Is there a way to prevent App Portal from just adding a target to an SCCM collection if it's already in the collection? (eg the user is impatient and the deployment hasn't finished but the user submits another request)

sara_b · ‎Jun 03, 2020

Using the General Catalog item, by extension, would be useful for someone deploying in a virtual environment then? Adding a user to an existing AD group that would allow them access to (insert title here) software?

sara_b · ‎Mar 11, 2020

We're using App Portal 2016 11.0.4 with SCCM/Casper integration. When a user requests a Windows software, they get the out of the box "Software -Data" notification. Where does the information come from on the variables in the notifications? Specifically, I'm looking to find out where the ##InstallDate## is pulled from. The documentation simply says "Scheduled install date in client time.", but where is it getting that information?

sara_b · ‎Jan 16, 2020

If Reclamation is set up in App Broker using Flex Net Management Suite for usage data - will the App Broker reclamation deallocate a license that's not being used when the installation reaches the reclamation threshold? Or will it just uninstall the software leaving the allocated?

sara_b · ‎Oct 08, 2019

Yeah - I ended up opening a case to address the issues we're having. Thanks.

sara_b · ‎Sep 24, 2019

@CharlesW wrote: Not sure what you were looking for with regards to "meta tags". meta tags = keywords. Sorry about that.

sara_b · ‎Sep 20, 2019

Is there a way to pull a report of All Enabled titles, their long and short descriptions, meta tags and pricing information? Obviously there's not a canned report that does this. Do you know what tables/sources would be needed for this?

sara_b · ‎Sep 16, 2019

I have some questions that don't seem to be covered in the documentation for App Broker/App Portal. We're running App Portal 2016. I have my FNMS instance connected to App Portal. I have set up reclamation on a target. Ensured that I have plenty of licenses to reclaim. Based on FNMS, there are 793 installations with only 463 being used. My understanding is that the usage is based on what we set up - 90 days unused means that it's NOT being "used". I'd like to get confirmation on that. If that's the case, then that means I have appx 330 licenses that should be available for reclamation through App Portal. I ensured that I have the same ARL in the FNMS license as what I chose in App Portal - and I get a listing of 989 devices for that ARL. There IS an uninstall package for the reclamation. When I look at the Alerts, it looks like it's only run on 61 machines - and that it kicks off on Saturday/Sunday. 1) When does a reclamation campaign kick off? 2) Is there a way to change the day that it runs? 3) Why isn't it running on more devices? 4) What is the point of the Alerts if there's nothing I can do with them to force them to rerun?

sara_b · ‎Aug 23, 2019

Do you happen to know what would be added to ConfigMgr for that?

sara_b · ‎Aug 22, 2019

We currently have our deployments set to not remove from the install collection for some reporting that we're working on. We don't currently have reclamation set up, but we are starting. When using reclamation from the My Apps tab, will the reclamation remove the machine from the install collection, or will it just add it to the uninstall collection?

sara_b · ‎Jun 26, 2019

Charles, You mention that by default, the "auto fail" timer is set to 24 hours, the documentation actually shows it as 168 hours? The technicians tell me that the logs they get don't tell them WHY the installation failed unless we're leaving it in the collection. Also, this allows for reimages of machines to automatically install software already assigned to the target. jdempsey, Reviewing the data is the reason we extended the auto fail timer in the first place from 48 to 96 hours. I think part of the problem we're (my company ) is having is potentially a communication problem. I had a user bring me an example. They requested a software on 6/12. The software was installed that afternoon and was functional (didn't error out or anything). On 6/17, they received a failure notice. When I initially looked at App Portal, it had a failure for both machine policy and installation. I retried machine policy and it succeeded, but the installation is still listed as failed. Question about the last timer - if no value is set - will it continue to monitor indefinitely?

sara_b · ‎Jun 26, 2019

Using App Portal 2016 with SCCM delivering the applications, we are struggling with trying to minimize the failure rate. One of the things that we noticed is that, by default, App Portal removes the target from the collection when it's marked failed. Unfortunately for us, that also meant that we had no audit trail to find out what was causing the failures. To mitigate, we've gone through and unchecked that so that the target will stay in the collection to provide additional data. This is proving a challenge in other ways. Namely, now, since the target is staying in the collection, App Portal can time out/fail the installation, but the software will be installed successfully after that time out. We lengthened the "Automatically fail software requests with no status after " timer from 48 hours to 96 hours. The issue with doing this though is that our failure messages generate trouble tickets for our help desk. Now, if there's a legitimate reason the install is failing, the user has to wait 4 days for that ticket to auto generate, because it's continually trying. Are there any tricks I'm missing here? What are your time outs set as? And looking at the documentation for App Portal 2016, what is the "Monitor threshold for failed deployments to prevent false flags " timer for? The documentation doesn't have a value set, nor does it define what exactly it does.

Online Status	Offline
Date Last Visited	‎Mar 13, 2023 07:08 PM

Re: App Portal and SCCM collections

Re: App Portal and SCCM collections

Re: App Portal and SCCM collections

App Portal and SCCM collections

Re: Benefits of General vs Software Catalog Items

Variables in Notifications

Reclamation and license assignment

Re: My Apps Reclamation questions

Re: Reporting - All Enabled titles including extras

Reporting - All Enabled titles including extras

My Apps Reclamation questions

Re: License Reclamation from My Apps tab

License Reclamation from My Apps tab

Re: App Portal 2016 with SCCM delivery: failures and timers

App Portal 2016 with SCCM delivery: failures and timers

Re: App Portal and SCCM collections

Re: App Portal and SCCM collections

Re: App Portal and SCCM collections

App Portal and SCCM collections

Re: Benefits of General vs Software Catalog Items

Variables in Notifications

Reclamation and license assignment

Re: My Apps Reclamation questions

Re: Reporting - All Enabled titles including extras

Reporting - All Enabled titles including extras