Start from the library. Write the rest yourself.
The Library holds the software and scripts your deployments draw on. Add software by name from the Windows Package Manager catalogue, or upload your own installers. Built-in PowerShell scripts cover diagnostics, maintenance, network, patching and preflight, and the Script Editor is there for writing your own.
Software by name
Add an application from the Windows Package Manager catalogue by typing its name.
Your own installers
Upload an MSI or EXE installer for software the catalogue does not carry, and deploy it the same way.
Built-in scripts
PowerShell scripts grouped as Diagnostics, Maintenance, Network, Patching and Preflight are there to use from the start.
An editor included
Read, change and write PowerShell in the Script Editor, without leaving Overseer.
Home-made install scripts are a job in themselves.
- Scripts scattered across toolsInstall scripts sit in shared folders, old tickets and one technician’s laptop, in several versions.
- Packaging every application yourselfEach new application means finding its silent install options and a way to tell it is there.
- Run once, never checkedThe script runs and exits. Nothing confirms that the software is installed or the setting took.
- Yesterday’s script, today’s installerA supplier changes an installer, and the script that worked last month fails without saying so.
Start from what is built in. Add your own.
- Global and LocalGlobal items are built in. Local items are yours. Both sit in the same Library and deploy the same way.
- Software and tasksSoftware is something to install, update or remove. A task is a PowerShell script that checks a setting and corrects it.
- Checked like everything elseA library item runs inside a maintenance session: detected first, acted on where needed, then verified.
- Failures that explain themselvesWhen a script fails, the session shows which item failed and the output it produced.
Three steps. From library to computer.
Find or add it
Pick a built-in item, add software by name, or upload your own installer.
Make it yours
Open a script in the Script Editor to read it, change it or write a new one.
Deploy it
Use it in a deployment and choose the state, the target and the enforcement.
Then put it to work.
A library item does nothing until a deployment uses it. Choose the state you want and where it applies, and the next maintenance session carries it out and verifies the result.
In development. Launch inquiries welcome.
Overseer is still being built and is not available yet. If you would like to hear when it launches, get in touch.