Now I just realized something.   I was just about to go on about how to setup Core as s File server and something hit me.

I’ve been mentioning OCSETUP and OCLIST as the ways to determine and add features to your Core box.   But I neglected to mention you can also do this in Powershell.

In order to do this you DO have to add a feature to your Core box called “ServerManager-PSH-Cmdlets”.  So within Powershell execute a

START-PROCESS –wait ocsetup “ServerManager-PSH-Cmdlets”

That is the command required in Powershell to add this in to your Core features.  Once done you’ll have a small but powerful list of Commandlets added to your repertoire.

Execute an


and you’ll soon have access to these new commandlets


The names are wonderfully obvious as to what they will do.   Where I find this is a win over OCSETUP is I can have a much cleaner list about what is already installed by executing an

GET-WINDOWSFEATURE | where { $-.Installed –eq $TRUE }

Oclist (at least to my knowledge) does NOT have this ability.   I can also easily search for types of features available on CORE, such as adding in ASP to a Web Core Server.


Will show me all features where “ASP” is part of the feature name or Description.  No more digging!

If I have decided to remove all features that are based on IIS I could do this


And like every command that will remove something I can even tack on a –WHATIF to see what WILL happen when I execute this command.

But of course just as easily, I can say “Add in all the features tied to Active Directory” with a


What I did find ironic (and irritating) is it WON’T let me add/remove features from Powershell (Like additional modules).

I can understand that since potentially you’re disrupting the very base from which you’re doing the adding and removing, but it still irritates me 😛

NOW next time we’ll look at that Easy to deploy and Secure File Server on Core

The Power of Shell is in YOU

The Energized Tech