Brian,
I've been talking with some co-workers who use AutoSPInstaller. We love the project, and in general we love the UX of the scripts. I'm going to steal several of your ideas for my own PowerShell libraries.
The only nitpick we have is that for the "progress bar" and a couple of other sections the ForegroundColor is Blue, and it's very difficult to read against the dark blue background that's the default for many (most?) people's PowerShell CLI.
Obviously this is a trivial change, and we can do it from our end, but the statements (currently 68) are sprinkled throughout the scripts, so it's a bit of a hassle to sync up whenever there's a new release. Is there any way you can work in a different ForegroundColor, or specify the BackgroundColor?
FWIW, if this were a Git repository you'd already have a pull request from us. Looks like you're the only committer for this project (#respect). If there's any way we can help with this (and other issues), just let us know.
Keep up the great work!
[Sean](http://www.threewill.com/team/sean-hester/)
Senior Research Engineer, [ThreeWill Labs](http://www.threewill.com/company/threewill-labs/)
[@seansageek](https://twitter.com/seansageek)
Comments: Resolved with changeset 110840: Changes in this release:
- Fairly minor UX changes WRT colours & status messages. Should make the script output more readable and less eye-straining!
- Fixed syntax issue as reported in issue 21161
- Added some lines of script to add groups to site collections that are for some reason missing by default (issue 20605)
- Fixed Get-FarmServers function to properly detect search servers with ALL possible roles including new ones in SP2013
- Added super-preliminary support for Windows Server 10 or whatever it will be called. However it likely won't work at all until updates SharePoint binaries & prerequisite installer are made available
- Minor change to default central admin content database name in AutoSPInstallerInput.xml
I've been talking with some co-workers who use AutoSPInstaller. We love the project, and in general we love the UX of the scripts. I'm going to steal several of your ideas for my own PowerShell libraries.
The only nitpick we have is that for the "progress bar" and a couple of other sections the ForegroundColor is Blue, and it's very difficult to read against the dark blue background that's the default for many (most?) people's PowerShell CLI.
Obviously this is a trivial change, and we can do it from our end, but the statements (currently 68) are sprinkled throughout the scripts, so it's a bit of a hassle to sync up whenever there's a new release. Is there any way you can work in a different ForegroundColor, or specify the BackgroundColor?
FWIW, if this were a Git repository you'd already have a pull request from us. Looks like you're the only committer for this project (#respect). If there's any way we can help with this (and other issues), just let us know.
Keep up the great work!
[Sean](http://www.threewill.com/team/sean-hester/)
Senior Research Engineer, [ThreeWill Labs](http://www.threewill.com/company/threewill-labs/)
[@seansageek](https://twitter.com/seansageek)
Comments: Resolved with changeset 110840: Changes in this release:
- Fairly minor UX changes WRT colours & status messages. Should make the script output more readable and less eye-straining!
- Fixed syntax issue as reported in issue 21161
- Added some lines of script to add groups to site collections that are for some reason missing by default (issue 20605)
- Fixed Get-FarmServers function to properly detect search servers with ALL possible roles including new ones in SP2013
- Added super-preliminary support for Windows Server 10 or whatever it will be called. However it likely won't work at all until updates SharePoint binaries & prerequisite installer are made available
- Minor change to default central admin content database name in AutoSPInstallerInput.xml
