You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2020. It is now read-only.
@pcgeek86 is there a reason for having multiple Discover/Generate steps, each for an explicit Windows Feature? Could we have a generic step that discovers all installed features with Get-WindowsFeature ... | Where Installed and a generic generate which does Add-WindowsFeature for all the installed features?
I think those commands are also available for 2008R2 so potentially gives the tool a wider reach.
The text was updated successfully, but these errors were encountered:
@sixeyed Good question. There are certainly multiple ways of approaching this. However, certain Windows Features actually have deeper configuration that goes into them.
Right now, I see a couple of different options available to move forward:
Option 1: Generalize all Windows Server Features as a single artifact
Option 2: Keep Windows Server Features as separate artifacts, and include deeper inspection of each Windows Server Feature in its corresponding artifact.
I would incline to do both. Option 1 gives a lot of value quickly with a
horizontal sweep. Then we can add more depth incrementally with new
features - IIS website setup, MSMQ queues etc, which we could prioritise
separately.
Also I think listing all the features in one hit in the Dockerfile puts
users in a good place to trim out anything they're not using.
@sixeyedhttps://github.com/sixeyed Good question. There are certainly
multiple ways of approaching this. However, certain Windows Features
actually have deeper configuration that goes into them.
Right now, I see a couple of different options available to move forward:
Option 1: Generalize all Windows Server Features as a single
artifact
Option 2: Keep Windows Server Features as separate artifacts, and
include deeper inspection of each Windows Server Feature in its
corresponding artifact.
@pcgeek86 is there a reason for having multiple Discover/Generate steps, each for an explicit Windows Feature? Could we have a generic step that discovers all installed features with
Get-WindowsFeature ... | Where Installed
and a generic generate which doesAdd-WindowsFeature
for all the installed features?I think those commands are also available for 2008R2 so potentially gives the tool a wider reach.
The text was updated successfully, but these errors were encountered: