- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2023 07:02 AM
Hi
We are trying to establish the plugins/solutions/spokes etc. required to implement the automated revocation of unused software installations. These installations were deployed using SCCM / MECM, also we have successfully configured the Service Graph connector for SCCM and are collecting software usage data.
We are now looking to automate the removal of reclamation candidates using SCCM. Given the version of SCCM we have deployed we installed “Client Software Distribution (CSD) 2.0”.
My question is, to automate the removal of reclamation candidates using SCCM, do we need to install the Microsoft Endpoint Configuration Manager Spoke AND the Microsoft SCCM orchestration activity pack ?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2023 02:46 PM
For CSD 2.0 you do not need the SCCM Orchestration pack. That is for the old workflow activities for client software distribution.
For SCCM Software Removal you should only need CSD 2.0 and MECM installed.
FYI If you are licensed under SAM Pro vs an explicit license for CSD, you may have an issue deploying this to production. You may want to check your production instance to make sure you are allowed to install CSD 2.0. I just went through this issue with a client, since CSD 2.0 hasn't been mapped to the licensing under SAM Pro it put us a couple weeks behind for SN to allow CSD 2.0 to be installed in their production environment under the SAM Pro license.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
16 hours ago
Hey JasonS274316555
Yes we have a working system now. At the time CSD 2.0 supported application removal via SCCM collections only i.e. an SCCM installation / uninstall collection was required for every application you wished to install / uninstall - therefor the CSD 2.0 uninstall approach did not 'work' for us. What did, was creating our own custom subflow that removed the user of the device from the corresponding AD Application group. My advise would be to research the uninstall technologies already deployed and design and create a removal process around them.
