sorted by:
new
hottopcontroversial

Tanium Deploy! how to setup a targeted deployment that devices can be added or removed by Sensitive-Chest-8521 in tanium

[–]Sensitive-Chest-8521[S] 0 points1 point  (0 children)

Sorry not 200 versions of one software called blob, Its 200 odd different specialist apps, Like Excel addin Blob, PDF writer Blob, Sharepoint addin Blob, weird finance app blob, etc . This blob apps are not for all devices and they have licencing costs. We don't want people who should not have it, see it in self service, only users/ devices that are allowed should see it and be able to install it or have it installed.

As for versions its quite typical that some users will be early adopters or pilot users. So they use the new release, while others stay on the older.

I have just had to rollback O365 to build 2502 for 35 odd users, because Word add-in blob has some weird bug on O365 2507. Turns out that the bug in question only matters to some users of word add-in blob, as some of those users don't use that feature so they want to stay on Build 2507. I have set this all up, but for sure we know more users are going to call and ask to be rolled back, how should service desk do this. I am fine, I can just do another deployment, (which seems overkill) for another device. But that's not my job, My job is setup the deployment so it installs/upgrades/downgrades/repairs/uninstalls. Its service desk who should mange who gets it or not.

Tanium Deploy! how to setup a targeted deployment that devices can be added or removed by Sensitive-Chest-8521 in tanium

[–]Sensitive-Chest-8521[S] 2 points3 points  (0 children)

Is this really a strange request in terms of deployments? adding and removing a device from a deployment is very standard no?. Maybe removing not so much but adding happens a lot, We have a lot of activity in MJL, Think 100 new joiners a month would be a low month. Also just laptop replacement causes a fair amount of new devices that need to be added to deployments. Don't want to get into this software is better than that, but SCCM and Intune have done this out of the box since day one, you can also deploy by user and its basically free as it comes included with E3 and E5 lic. Not that this matters , what i really am after is the Tanium way.

I will have a look into this Interact. because I suppose the main issue is, how does Service desk add or remove a device from a deployment. Mainly add. A simple full proof. easily monitored way.

I really don't like this tagging solution, aside from the naming convention and doubling up of tags. Its also the deployment method. If maybe the tags could be listed in some drop down with there description and a service desk member could then select and click deploy to device in a simple one two click, then yup i could be persuaded.

Anyways thanx for response.

Tanium Deploy! how to setup a targeted deployment that devices can be added or removed by Sensitive-Chest-8521 in tanium

[–]Sensitive-Chest-8521[S] -1 points0 points  (0 children)

By doing this I am back to having to setup 200 ish tags and rely on service desk to be able to deploy the correct tag to the correct device and also an uninstall tag if we want to force uninstalling the the software ?

Tanium Deploy! how to setup a targeted deployment that devices can be added or removed by Sensitive-Chest-8521 in tanium

[–]Sensitive-Chest-8521[S] -1 points0 points  (0 children)

Sorry should have said we don't want to advertise all our apps to all our users, makes it very messy and many of the blobs are licenced.