To install and configure Remote Desktop Services, open Server Manager and click on “ Add roles and features” to install the role of remote desktop services.Ģ.
How to setup remote desktop server 2012 windows#
Steps to install and configure Remote Desktop Services (RDS) in Windows Server 2012 R2ġ. I’d not recommend to enable this port on Domain Controller because of security issues. Please ensure this port is enable in the Firewall between the RDS server and client machine. RDP uses TCP port number 3389 and UDP port number 3398. Nowadays RDS is primarily used by all the Organizations that are providing remote support or manage their Servers and environment remotely. By using RDP, administrators can diagnose and resolve problems remotely.
It is previously known as “Terminal Services”. Remote Desktop Protocol (RDP) is a technology of Microsoft, it enables users to connect to another computer over a network using graphical interface. In this post, we’ll learn the steps to install and configure Remote Desktop Services (RDS). Wikipedia has updated the remake section since the original version of this post was published.How to Install and Configure Remote Desktop Services (RDS) Hopefully this will be better than the proposed Highlander reboot…… ** PS – Looks like a third film is still planned. PowerShell will show you the name of the feature, and now you can add it remotely and also restart the target machine when the installation is complete. You could change the Get-WindowsFeature to suit your requirements. One little cmdlet, but it’s so very powerful. The 2012 version of this post has an additional section about a specific issue to allow Installing PowerShell On Upgraded 2008 R2 Core Server. In the example below DC-1 is the local machine which then queries a remote computer called Server-1: Additionally we do not have to manually import the ServerManager module in Windows 2012 either. What makes this even more efficient is that Windows 2012 R2 has a ComputerNameparameter so we can directly query a remote machine. Using wildcards is neat, and can make administration quicker and faster. We can see this with the Get-Aliascmdlet: Add-WindowsFeature is an alias to Install-WindowsFeature. This is because the 2012 R2 cmdlet is Install-WindowsFeature. Install-WindowsFeature Desktop-Experienceįor those folks out there who used the Windows 2008 R2 cmdlets, you will have noted Install-WindowsFeature was used rather than Add-WindowsFeature. 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 R2: 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 newer versions of Windows are the Get-WindowsFeature and Install-WindowsFeaturecmdlets. 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 So yes, it’s a little bit more hidden but you don’t have to be Indiana Jonesto 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 my colleague in 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 which is highlighted below. The genesis of which was an application requirement to install Media Player onto a couple of servers. This is an updated version of the original Windows Server 2012 post.
0 kommentar(er)
