Retiring Oclist.exe

Retiring Oclist.exe

  • Comments 13
  • Likes

For those of you that used Server Core in Windows Server 2008 you may be familiar with the Oclist.exe tool. This tool was included in Server Core to provide a way to obtain a list of roles and features on Server Core and their installation state. In Windows Server 2008 R2 a new tool, Dism.exe, was introduced for adding/removing roles and features and included the capability to provide the list of roles and features as well as installation state by running:

Dism /online /get-features /format:table

In the Server Core documentation we changed to using Dism.exe for Windows Server 2008 R2. Because Dism.exe is an integrated command line tool for all tasks related to optional roles and features and provides additional formating options for its output, in the next release we are planning to remove Oclist.exe from Server Core.

If there are any concerns with this change, please post a comment or email srvcfdbk@microsoft.com.

Comments
  • What about OCsetup.exe command? is it still available on Server Core R2?

  • Yes, OCsetup.exe is still available on Server Core 2008 R2.

  • What about establishing a command line standard and staying with it. Over time this will give MS more loyalty. Having to learn a new set of commands with each major release is a major pain in the script.

  • Oclist is still available on Windows Server Core 2008 R2 but NOT on Windows Server Core 2012 /2012 R2. Ocsetup is deprecated. Microsoft recommends using DISM.exe to add/remove roles & features in Windows 2012 (R2) Server.

  • +1. Seems I have to learn the new/current way of doing things in Microsoft - as well as all the deprecated ways if I ever want break-in to the inner circle of users who can comfortably operate these needlessly complicated OSs... I certainly hope Linux will dominate in the near future so we can be done with these Goons from Redmond. How many billionaires do we need to keep rewarding for their inferior software and their stranglehold on the world's computers?

    Curmudge0n 21 Jun 2012 5:34 PM
    What about establishing a command line standard and staying with it. Over time this will give MS more loyalty. Having to learn a new set of commands with each major release is a major pain in the script.

  • To be fair the new "standard" is Powershell, I'm not aware of many Powershell commands deprecated from 2008 to 2012, only extra ones added. But yeah, it has been a nightmare up to now.

    Hopefully more and more tools get a Powershell front end that will be stable, even if they have to make work for some devs by rewriting the core every cycle.

  • To mslover: yeah but Powershell came from WMI which came from VBScript, etc. etc.

  • The point which MooB and Curmudge0n21 were making and which mslover totally missed is that there is always a new NEW STANDARD.

  • Only time will tell whether Powershell is the end-all command line standard for Windows, but I think they got it right. Personally, I don't understand why DISM is even around. Why not just leave this natively to Powershell and be done with it? (in Windows 2012R2 SC, /get-features isn't even listed as an option when you run dism /? ... oops)

    Import-Module servermanager ... Get-WindowsFeature, Add-WindowsFeature, and Remove-WindowsFeature

    Hopefully it won't be too much longer until cmd.exe is entirely replaced by powershell.exe.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment