I'm looking for a coherent and comprehensive strategy for powershell deployment in the following environment:
- 80+ Windows servers (2003, 2008)
- vCenter + PowerCLI
- Exchange 2007/2010
- SQL Server 2008
- Citrix XenApp
Security is important but functionality comes first (production scripts should be signed).
Powershell will be used for:
- Provisioning (users, virtual machines, etc.)
- Analyzing (logs, best practices etc.)
Deployment should be centralized and allow for both local and remote script execution as well as using Powershell in logon scripts.
Modules and production scripts should run from a network share.
The puzzle has many pieces and some of them have multiple solutions:
- Script signing: Windows 2008 PKI or there are simpler solutions?
- Execution policy: set by group policy
- Remoting: how best to enable
- Logon scripts: can powershell be used?
- Task scheduling: is there an easy solution to schedule powershell scripts?
- Delegating: other admins should be able to use but not modify scripts
There are many questions, but maybe some of you can share your experiences and best practices.