- WINDOWS 10 CANNOT REMOTE DESKTOP TO SERVER 2012 R2 INSTALL
- WINDOWS 10 CANNOT REMOTE DESKTOP TO SERVER 2012 R2 UPDATE
Using wildcards is neat, and can make administration quicker and faster. We can see this with the Get-Alias cmdlet: Add-WindowsFeature is an alias to Install-WindowsFeature. This is because the cmdlet is Install-WindowsFeature. Install-WindowsFeature Desktop-Experienceįor those folks out there who used the Windows 2008 R2 cmdlets, you will have noted that I specified Install-WindowsComponent above and not Add-WindowsFeature.
WINDOWS 10 CANNOT REMOTE DESKTOP TO SERVER 2012 R2 INSTALL
So as an example, we could use the following PowerShell oneliner to install Desktop Experience: We could then install it via Install-WindowsFeature.
The same goes for the GUI options that are present in Windows Server 2012: That’s pretty neat, and we can then see exactly where the Desktop Experience feature is located. So in our case we can look for something called *Desktop* What makes these cmdlets even more powerful, is that they accept wildcards as input. Probably my favourite installation features in Windows Server 2012 are the Get-WindowsFeature and Install-WindowsFeature cmdlets. So that’s all nice, but what if we did not know that the Desktop Experience feature was located in that area? PowerShell to the rescue!!!! Installing Desktop Experience Using PowerShell
WINDOWS 10 CANNOT REMOTE DESKTOP TO SERVER 2012 R2 UPDATE
Update 28-10-2013: Added PowerShell example to install Desktop Experience So yes, it’s a little bit more hidden but you don’t have to be Indiana Jones to discover it. I’m sure there is an oxymoron in there if you look hard enough!! If you want to just drive the GUI to install the Desktop Experience feature through Server Manager you have to expand the User Interfaces and Infrastructure feature and select the Desktop Experience component.
This met with some muttering and cursing from the nearby fabric covered box as the option to install the Desktop Experience feature is not as obvious as it was on Windows 2008 R2, highlighted below. There was an application requirement to install Media Player onto a couple of the servers. While working with one of my consulting colleagues recently on some Windows Server 2012 installations.
0 kommentar(er)
