I have a list of Windows Feature I want to install with DISM but I only know what their names are when using PowerShell.
Is there a way to quickly "translate" these names? It's more than a handful:
- NET-Framework-45-Features
- RPC-over-HTTP-proxy
- RSAT-Clustering
- RSAT-Clustering-CmdInterface
- RSAT-Clustering-Mgmt
- RSAT-Clustering-PowerShell
- Web-Mgmt-Console
- WAS-Process-Model
- Web-Asp-Net45
- Web-Basic-Auth
- Web-Client-Auth
- Web-Digest-Auth
- Web-Dir-Browsing
- Web-Dyn-Compression
- Web-Http-Errors
- Web-Http-Logging
- Web-Http-Redirect
- Web-Http-Tracing
- Web-ISAPI-Ext
- Web-ISAPI-Filter
- Web-Lgcy-Mgmt-Console
- Web-Metabase
- Web-Mgmt-Console
- Web-Mgmt-Service
- Web-Net-Ext45
- Web-Request-Monitor
- Web-Server
- Web-Stat-Compression
- Web-Static-Content
- Web-Windows-Auth
- Web-WMI
- Windows-Identity-Foundation
- RSAT-ADDS
So I would like something other than toggling the feature with PowerShell and check for changes in the dism command's output. Hopefully there's a better way... :)
It's usually a bad idea to install Server Features with DISM. Install-WindowsFeature can target offline images if that's what you're trying. Online, Install-WindowsFeature integrates with plug-ins from the various role and feature teams that may do additional configuration or checks to ensure your server stays healthy.
That said, to answer your specific question and keeping in mind the "buyer beware" comments above...
I was the dev manager for this feature area, so please trust me when I there are very few reasons to go the DISM route - but let's discuss in comments if you're in that category. I do also have a code snippet someplace that will capture before and after doing an install, and can create the equivalent DISM command line.
You might be able to map them by toggling them in PowerShell and then checking
Not sure if there is an automatic mapping though. Sorry, that doesn't cover the 'quickly'.