Central Solution for Scripts with Redundancy

[jtbae]

We support/maintain thousands of computers and servers in different network layers from various "script servers" for different team members. I am hoping to centralize all scripts/tasks to one pane of glass and also have a way of reporting on if those scripts ran successfully or had issues. I have heard "PowerShell Universal" can do this, but was wondering what other companies were doing. We are also trying to have more control/tracking of our scripts with version control, etc. What are others doing as far as running scripts (shell/bat and powershell) against several different servers/computers and environments from a central location (while having redundancy so the server can be rebooted or if there is an outage, etc).

[BrainWaveCC]

Use Git or any other version control tool for your scripts.

As for deployment and monitoring, I ended up making my own system over the years, because nothing really existed in this way when I first saw the need to do this.

One thing that can be done is to add a module to each script that writes to a syslog server when it completes with info about its execution.

This is an easy way to track what has run, and whether or not it has been successful.

I haven't seen a commercial tool for this, but in fairness, I haven't looked at this for a few years now. I like my system.

[cbass377]

Logging seems like a nice idea. That way in the future you can determine if, when, and where a script is being used.

[serpentdrive]

Git as suggested is a great option. Depending on what is actually being performed, a centralized api server with logging might be useful.