An Inventory that Updates Itself (NEWLY ADDED SESSION)

Cosmo Martinez
-
Proctor

Let's say that your pool of licenses won't stretch across your fleet. Let's say that the vendor requires a username and password for each seat. How do you handle the provisioning of vendor specific accounts? How can you keep track of who needs software and who suddenly no longer does? Let's face it, serialized software could soon become a thing of the past.
Configuration management tools hold the answers to these questions. You have OU’s, Smart Groups, Relevance, tools that allow IT to automatically scope software according to policy. There are times, however, when these tools fall short of what we need from them.
Where are the buttons that integrate with vendor account provisioning systems? Where are the smart computer groups that update according to metadata mined from web services instead of local attributes?
Cirrup and Mudwork are two such tools for filling the gap above. Cirrup manages groups of computers based off of the attributes of the unique person id’s that they are assigned to. Mudwork provisions Adobe Federated ID’s and manages Adobe Named User License entitlements. Together, these tools form a system that automatically manages entitlements and revokes unused software licenses.

Previous Knowledge
  • Jamf Pro
  • System Administration
Software Installation Expectation

No software required for the presentation.

Session Files