Retiring Oclist.exe
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
Anonymous
September 13, 2011
What about OCsetup.exe command? is it still available on Server Core R2?Anonymous
February 13, 2012
Yes, OCsetup.exe is still available on Server Core 2008 R2.Anonymous
June 21, 2012
The comment has been removedAnonymous
April 20, 2014
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.Anonymous
May 11, 2014
Pingback from Planning an Upgrade to Windows Server 2012/R2 | Free LessonsFree LessonsAnonymous
May 11, 2014
Pingback from Planning an Upgrade to Windows Server 2012/R2 | KASSAPOGLOUAnonymous
May 16, 2014
Pingback from Free Online Latest 2014 Pass4sure&Lead2pass Microsoft 70-648 Exam Questions (71-80) | CCNA Training | CCNA Practice Exam | CCNA DumpsAnonymous
May 16, 2014
Pingback from Free Online Latest 2014 Pass4sure&Lead2pass Microsoft 70-648 Exam Questions (71-80) | CCNA Training | CCNA Practice Exam | CCNA DumpsAnonymous
August 05, 2014
The comment has been removedAnonymous
March 01, 2015
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.Anonymous
March 02, 2015
To mslover: yeah but Powershell came from WMI which came from VBScript, etc. etc.Anonymous
March 02, 2015
The point which MooB and Curmudge0n21 were making and which mslover totally missed is that there is always a new NEW STANDARD.Anonymous
April 13, 2015
The comment has been removedAnonymous
April 12, 2016
Thanks for the information.
http://indguru.com