Demos / IT admins and script authors
Demo · 1:37
Make a catalog script your own
Alan changes one default in a catalog script; the help desk runs his version without seeing the code.
Recorded on the real product against our demo company, Lakefront Works. The people and data are fictional.
Transcript
This is Alan, the PowerScripts administrator at Lakefront Works. His job is to decide which scripts his team can run, and how they behave. Lakefront wants a standard way to offboard contractors. Alan starts from the catalog's Disable AD user account script, and makes Lakefront's own copy of it. One small edit makes it Lakefront's own: the holding OU now defaults to Disabled Users, so every offboarded account is filed away the same way. He saves it. The diff against the catalog shows exactly what Lakefront changed, and the history keeps every version.
Because it's an Active Directory script, Alan's copy joined the Active Directory role automatically. Harry is in that role, so Harry can run it now, and nobody outside that role can.
Over on the help desk, Harry has a ticket: Howard the Duck's contract has ended. Harry searches for Howard, right-clicks his Active Directory account, and picks Disable AD user account. It's Alan's version: the holding OU is already filled in.
He adds the reason and the ticket number, and runs it. Howard is disabled, the reason is stamped on the account, and he's moved to Disabled Users. Exactly the way Alan defined it. It's all on the audit trail, under Harry's name and the ticket. If Howard's contract is extended, Reverse re-enables him with one click.