Deciphering the oclist.exe output?


on full install of server 2008, servermanagercmd.exe provides output easy understand, separating server roles, role services, , features, this:

 

----- roles -----

[ ] active directory domain services
    [ ] active directory domain controller  [adds-domain-controller]
    [ ] identity management unix  [adds-identity-mgmt]
        [ ] server network information services  [adds-nis]
        [ ] password synchronization  [adds-password-sync]
        [ ] administration tools  [adds-idmu-tools]

 

----- features -----

[ ] .net framework 3.0 features  [net-framework]
    [ ] .net framework 3.0  [net-framework-core]
    [ ] xps viewer  [net-xps-viewer]
    [ ] wcf activation  [net-win-cfac]
        [ ] http activation  [net-http-activation]
        [ ] non-http activation  [net-non-http-activ]
[ ] bitlocker drive encryption  [bitlocker]
[ ] bits server extensions  [bits]

oclist.exe on server core, however, not make distinction cannot tell role (in cases), role service, or feature. output this:

 

microsoft-windows-servercore-package
bitlocker -
bitlocker-remoteadmintool -
clientfornfs-base
dfsn-server
dfsr-infrastructure-serveredition
dhcpservercore

 

how can tell role versus role service versus feature on core? example, have not seen "clientfornfs-base" documented anywhere yet. can updated list of server roles, role services, , features server core?

 

thank you!

hi,

 

the reason difference in output on server core, oclist has use lower level api doesn't know difference between roles , optional features. since wanted keep oclist flexible enough more roles in without changing it, didn't hard code logic roles , features it.

 

the step step guide covers role, , role feature, optional features. see announcement in forum thomas lee link. in case of nfs, feature of file server role.

 

andrew



Windows Server  >  Server Core



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607