You perform a Server Core Installation of Windows Server 2012 R2 on a server named Server1.
You need to add a graphical user interface (GUI) to Server1.
Which tool should you use?
A.
the dism.exe command
B.
the Add-WindowsFeature cmdlet
C.
the imagex.exe command
D.
the setup.exe command
E.
the ocsetup.exe command
F.
the Add-WindowsPackage cmdlet
G.
the Install-Module cmdlet
H.
the Install-RoleService cmdlet
Explanation:
Add-WindowsFeature -The Add-WindowsFeature cmdlet allows you to install specified roles, role
services, and features on a computer that is running Windows Server 2008 R2.
Install-WindowsFeature -Installs one or more Windows Server roles, role services, or features on
either the local or a specified remote server that is running Windows Server 2012 R2. This cmdlet is
equivalent to and replaces Add-WindowsFeature, the cmdlet that was used to install roles, role
services, and features in Windows Server 2008 R2.
dism /online /get-features PS C:\> Install-WindowsFeature -Name Web-Server –
IncludeAllSubFeature -ComputerName Server1 –WhatIf
Add-WindowsFeature(2008) and Install-WindowFeature(2012) are equivalent.
2
0
B
0
0
So is the answer A or B?
0
0
B. It’s a bit strange, since other questions on this give you incorrect answer for Server 2008 cmdlets. But here it’s totally fine.
0
0
I would go with A
B is 2008 Install-WindowsFeature replaced it in 2012. At least that is the way I understand it.
0
0
I read from somewhere even the add windowsfeature cmdlet is a 2008 command, it is usable in 2012 as well and not actually been replaced
0
0
Like what Nikita say add-WindowsFeature(2008) and Install-WindowFeature(2012) are equivalent
0
0
Reason I lean with A was for the reason I stated…..thinking it is a trick from MS.
Doing more reading and talking with others….if faced with this question on Wed (taking exam then) I would go with B
0
0
after reading a bit I would have to go for A, in fact I think there was a similar question to this somewhere and the answer was dism.exe
http://blogs.technet.com/b/canitpro/archive/2012/10/02/from-server-core-to-gui-to-minshell.aspx
There are a couple of ways to install the GUI from the command prompt, although both use the same tool – DISM (Deployment Image Service Manager). When you are doing it for a single (local) server, the command is:
Dism /online /enable-feature /featurename:ServerCore-FullServer /featurename:Server-Gui-Shell /featurename:Server-Gui-Mgmt
While the Dism tool works fine, one of the features that will make you want Windows Server 2012 on all of your servers now is the ability to manage them remotely, and script a lot of the jobs. For that Windows PowerShell is your friend. The script in PowerShell would be nearly as simple:
Import-Module Dism
Enable-WindowsOptionalFeature –online -Featurename ServerCore-FullServer,Server-Gui-Shell,Server-Gui-Mgmt
It takes a few minutes, but once you are done you can reboot and presto, you have the full GUI environment.
1
0
It’s A because B has been replace for Install-WindowsFeature in Server 2012.
0
0
No doubts at all. A is the correct answer. DSIM can be used to add / remove GUI. no need to guess
http://cloudtidings.com/2012/08/09/windows-2012-converting-a-full-gui-version-to-server-core-and-vice-versa/
1
0
https://msdn.microsoft.com/en-us/library/ee662309.aspx
The Add-WindowsFeature cmdlet has been replaced, starting with Windows Server 2012, by the Install-WindowsFeature cmdlet.
I would go with A.
1
0
I am also commenting to inform you what a helpful discovery my cousin’s daughter obtained visiting your web page. She mastered numerous issues, which included what it really is like to have an incredible coaching mood to make others clearly know chosen complicated topics. You undoubtedly surpassed people’s expectations. I appreciate you for showing these effective, dependable, explanatory in addition to fun help with that topic to Mary.
rca ieftin online http://goo.gl/6GqA7S
0
0
Keep all the articles coming. I love reading your posts.All the best.
m.youtube.com/watch?v=MQc9pbcSAQQ
0
0