We ship automation systems with windows based operator station. They have a plethora of various components with long manual installation scripts. 15 years worth of legacy components and various procedures.
- computer settings
- security settings
- windows services settings
- Windows version.
- Various security patches
- Multi core enabled.
- Registry settings.
- Free disk space req.
- Third party components.
- Proprietary components.
- Network settings, Security settings etc
- Network IP/ settings
- Plant/Plant type/Station specific extensions.
- Plant specification.
- Various settings in various ini-files.
I wish to automate the installation process as well as producing a verification report to attest that requirements are satisfied. As I see it, all(?) such steps I can think of are feasible and verifiable through the powershell engine. I suppose that I will be composing a pre-install environment containing powershell and a powershell based application that will be able to check that requirements are satisfied and, if possible, correct them.
I was thinking of using PSake for this. It is strictly a powershell based software build tool, but its concept of dependencies seems to be what is missing from powershell out of the box to suit my needs.
Any opinion on this approach would be appreciated.