K1000 User Download limited by Smart Label
I have group computer with software installed lets name it "Photoshop v5"
I created Smart label that apply to only computers with software made by "adobe" and Software name "Photoshop".
Using that label I can filter those computers out.
Next I created Installation package for Photoshop v6, and I want to enable that installation package for only those users who have Photoshop already on theirs computers so they can login to k1000 Service Desk portal and run update to v6. Because organization license key is assigned to that installation package I want to target only that group of computers.
The same Smart label that filter copmuters I applied to Software package under Access Control (tried with and without Also Restrict By Device Label) and it didn't work
I created Smart label that apply to only computers with software made by "adobe" and Software name "Photoshop".
Using that label I can filter those computers out.
Next I created Installation package for Photoshop v6, and I want to enable that installation package for only those users who have Photoshop already on theirs computers so they can login to k1000 Service Desk portal and run update to v6. Because organization license key is assigned to that installation package I want to target only that group of computers.
The same Smart label that filter copmuters I applied to Software package under Access Control (tried with and without Also Restrict By Device Label) and it didn't work
2 Comments
[ + ] Show comments
-
This is because that label needs to contain users and not machines. - StockTrader 9 years ago
-
Ha now I am curious how I can create label with users based on software installed on users computers. That could be tricky - martinaam 9 years ago
Answers (1)
Please log in to answer
Posted by:
Hobbsy
8 years ago
Good luck with trying to match up a User label with a machine label to control the downloads, that is a step too far in my book ;o)
In the meantime my guess is that once you have the machine label that shows only the machines eligible for the update, it sort of makes sense to still restrict by machine, otherwise if you were able to restrict by user, an authorised user could log onto the portal on another machine and mistakenly download the update.
I suggest use the end user functionality that is there, group your eligible machines by label, create the download package and make it available on the end user portal but tick the "Also restrict by Device Label" box and add in your Machine label for authorised machines.
That will not filter by authorised user in the way you want but it will ensure that updates only go to eligible machines
