You perform a Server Core Installation of Windows Server 2012 on a server named Server1.
You need to add a graphical user interface (GUI) toServer1.
Which tool should you use?
A.
the dism.exe command
B.
the Add-WindowsFeaturecmdlet
C.
the imagex.exe command
D.
the setup.exe command
E.
the ocsetup.exe command
F.
the Add-WindowsPackagecmdlet
G.
the Install-Module cmdlet
H.
the Install-RoleServicecmdlet
Add-WindowsFeature – Applies To: Windows Server 2008 R2, Windows Storage Server 2008 R2 (http://msdn.microsoft.com/en-us/library/ee662309.aspx)-Updated: November 1, 2013
Therefore answer is A
Well Jo is correct but missed the answer the letter 🙂
B
🙂
Na, read his reply again bro. He is right
Answer – A. B not right, becouse cmdlet Install-WindowsFeatures (not Add)
Should be A if you restrict the answer to an actual cmdlet.
Add-WindowsFeature have been replaced by Install-WindowsFeature in 2012.
However Add-WindowsFeature is a working alias to Install-WindowsFeature.
So you could still use the command Add-WindowsFeature but it will call the Install-WindowsFeature cmdlet.
To some extent this would make it a trick question, unless you want to make a point that Add-WindowsFeature cmdlet doesn’t exist anymore.
Trick question. Add-WindowsFeature is mainly for Windows 2008 (it will work for Windows 2012 but it will be deprecated in the future), Install-WindowsFeature is the cmdlet to use. Answer is A (although I’m tempting to add B also)
hate questions like these. I looked at it and saw the the add feature so just click it. if I had read it properly I would of put A. as they say RTFQ
There is evidently big money to know relating to this. I believe you’ve made certain good points in features also.
rca ieftin online http://goo.gl/6GqA7S
The time to study or pay a visit to the material or web pages we have linked to below.
Sites of interest we have a link to.
Should be only A
Since the add-windwosFeature cmdlet is not for 2012
https://msdn.microsoft.com/en-us/library/ee662309.aspx
guys if you type and see the help of dism.exe:
Deployment Image Servicing and Management (DISM.exe) is a command-line tool that can be used to service a Windows® image or to prepare a Windows Preinstallation Environment (Windows PE) image. DISM can be used to service a Windows image (.wim) or a virtual hard disk (.vhd or .vhdx).
DISM replaces the ImageX tool which was deprecated in Windows 8. DISM also replaces Package Manager (Pkgmgr.exe), PEimg, and Intlcfg that were included in previous deployment toolkits. DISM also adds new functionality to improve the experience for offline servicing.
You can use DISM with .wim files to:
Capture and apply Windows images.
Append and delete images in a .wim file.
Split .wim files into several smaller files.
You can use DISM with .wim, .vhd, or .vhdx files to:
Add, remove, and enumerate packages.
Add, remove, and enumerate drivers.
Enable or disable Windows features.
Apply changes based on the offlineServicing section of an Unattend.xml answer file.
Configure international settings.
Upgrade a Windows image to a different edition.
Prepare a Windows PE image.
Take advantage of better logging.
Service earlier versions of Windows such as Windows 7, Windows Server 2008 R2, Windows Vista with the latest Service Pack, and Windows Server 2008.
Service all platforms (32-bit, 64-bit).
Service a 32-bit image from a 64-bit host, and service a 64-bit image from a 32-bit host. For more information, see the “Limitations” section later this topic.
Make use of old Package Manager scripts.
sorry guys but after reading this i cant see where is it written that you can add remove roles and features,, as gui is a feature in server manager…
my apologies dism command has capability to install gui
https://www.youtube.com/watch?v=mlbE998jp2Q