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)
Oct 01, 2020 11:20 AM
I wouldn't think that would technically be an issue. Even if you have more than one direct membership rule for the same client (not sure SCCM even allows that), it wouldn't add the client to the collection more than once. In any case, you could enable the option in App Portal to block identical requests within a certain time period.
https://docs.flexera.com/appportal2019r1/default.htm#helplibrary/APR_Settings_Website_CatBeh.htm
Catalog item reorder waiting period (in days) Block catalog item reorder during waiting period |
In the Catalog item reorder waiting period (in days) field, enter the number of days a requester must wait before submitting a second request for the same catalog item. By default, this value is 7 days. If a requester attempts to submit a second request for the same catalog item within the specified time frame, one of the following will occur, depending upon whether or not the Block catalog item reorder during waiting period option is also selected:
|
Oct 01, 2020 11:53 AM
If I'm not mistaken, it's based on software title and targeted device. So, if you request it for one device today and a different device tomorrow (or your case of a manager requesting for multiple different machines), that's not an issue. Having said that, I always recommend (and have only configured) using computer-targeted deployments. If you were to configure a catalog item as a user-based target, I'm not sure if the check would be based on user or if it's always based on device.
Oct 06, 2020 09:00 AM
Oct 01, 2020 11:25 AM
I wouldn't think that would technically be an issue. Even if you have more than one direct membership rule for the same client (not sure SCCM even allows that), it wouldn't add the client to the collection more than once. In any case, you could enable the option in App Portal to block identical requests within a certain time period.
https://docs.flexera.com/appportal2019r1/default.htm#helplibrary/APR_Settings_Website_CatBeh.htm
Catalog item reorder waiting period (in days) Block catalog item reorder during waiting period |
In the Catalog item reorder waiting period (in days) field, enter the number of days a requester must wait before submitting a second request for the same catalog item. By default, this value is 7 days. If a requester attempts to submit a second request for the same catalog item within the specified time frame, one of the following will occur, depending upon whether or not the Block catalog item reorder during waiting period option is also selected:
|
Oct 01, 2020 11:53 AM
Oct 01, 2020 12:56 PM
If I'm not mistaken, it's based on software title and targeted device. So, if you request it for one device today and a different device tomorrow (or your case of a manager requesting for multiple different machines), that's not an issue. Having said that, I always recommend (and have only configured) using computer-targeted deployments. If you were to configure a catalog item as a user-based target, I'm not sure if the check would be based on user or if it's always based on device.
Oct 06, 2020 09:00 AM
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.
Oct 06, 2020 11:13 AM