Monthly Archives: February 2013

Orchestrator Security Considerations: Section 2: Account Management

One of the practical problems that we come up against in Orchestrator is how effectively manage accounts. It seems easy to just run everything under one ‘super user’ account that has access to everything, i.e. provision an Orchestrator AD account,

Tagged with: , ,
Posted in General Information, Infrastructure

Runbooks not showing up

A very common problem I see on the Orchestrator forums is people noticing that their Runbooks are not showing up properly in their web service. This usually manifests itself when they are looking either in Service Manager (Runbooks not all

Tagged with: , , , , , ,
Posted in Infrastructure

Orchestrator Security Considerations Section 1: Global Configurations

Inside of Orchestrator there are two types of roles, for simplicity sake we will call them developer and analyst. The developer role is controlled by adding people or groups to the OrchestratorsUserGroup group on your environments management server, access to

Tagged with: , ,
Posted in General Information, Infrastructure

Orchestrator Security Considerations Introduction

We just completed an internal review about how to handle security in Orchestrator and a lot of good conversation was had around the topic that I think will be applicable to the larger Orchestrator community. There are quite a few

Tagged with: , ,
Posted in General Information, Infrastructure