Software Metering Deep Dive and Automation Part 3: Use It Or Lose It - The Orchestrator Runbook Automation

re: Software Metering Deep Dive and Automation Part 3: Use It Or Lose It - The Orchestrator Runbook Automation

Peter C — Tue, 30 Apr 2013 11:03:08 GMT

Hi,

If the user had initially got the application from the Application Catalog, and approval was granted.

Would that approval still remain? i.e. when app is removed, then the user could simply reinstall as approval was previously granted.

Would a different runbook need to remove that approval?

Peer

re: Software Metering Deep Dive and Automation Part 3: Use It Or Lose It - The Orchestrator Runbook Automation

T.J.M. Klaver — Thu, 18 Apr 2013 20:50:40 GMT

Hi Neil,

There is an error in the databasename. In the runbook the database is called "OrchestratorOperation" and in your blog post you create the database with "CREATE DATABASE OrchestratorOperatons" with a S at the end.

Regards

Tom

re: Software Metering Deep Dive and Automation Part 3: Use It Or Lose It - The Orchestrator Runbook Automation

Dave J. — Wed, 10 Apr 2013 18:01:24 GMT

Neil,

Great post! Any chance you can post the runbooks for download?

Regards,

Dave