Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Configure remote Management in Server Manager
In this article
In Windows Server, you can use Server Manager to perform management tasks on remote servers. remote management is enabled by default on servers that are running Windows Server 2016. To manage a server remotely by using Server Manager, you add the server to the Server Manager server pool. You can use Server Manager to manage remote servers that are running older releases of Windows Server, but the following updates are required to fully manage these older operating systems. To manage servers that are running Windows Server releases older than Windows Server 2016, install the following software and updates to make the older releases of Windows Server manageable by using Server Manager in Windows Server 2016.
for detailed information about how to add servers that are in workgroups to manage, or manage remote servers from a workgroup computer that is running Server Manager, see add Servers to Server Manager. Enabling or disabling remote managementIn Windows Server 2016, remote management is enabled by default. Before you can connect to a computer that is running Windows Server 2016 remotely by using Server Manager, Server Manager remote management must be enabled on the destination computer if it has been disabled. The procedures in this section describe how to disable remote management, and how to re-enable remote management if it has been disabled. In the Server Manager console, the remote management status for the local server is displayed in the Properties area of the Local Server page. Local administrator accounts other than the built-in Administrator account may not have rights to manage a server remotely, even if remote management is enabled. The remote User Account Control (UAC) LocalAccountTokenFilterPolicy registry setting must be configured to allow local accounts of the Administrators group other than the built-in administrator account to remotely manage the server. In Windows Server 2016, Server Manager relies on Windows remote Management (WinRM) and the Distributed component Object model (DCOM) for remote communications. The settings that are controlled by the Configure remote Management dialog box only affect parts of Server Manager and Windows PowerShell that use WinRM for remote communications. They do not affect parts of Server Manager that use DCOM for remote communications. For example, Server Manager uses WinRM to communicate with remote servers that are running Windows Server 2016, Windows Server 2012 R2, or Windows Server 2012, but uses DCOM to communicate with servers that are running Windows Server 2008 and Windows Server 2008 R2, but do not have the Windows Management Framework 4.0 or Windows Management Framework 3.0 updates applied. Microsoft Management Console (mmc) and other legacy management tools use DCOM. For more information about how to change these settings, see To configure mmc or other tool remote management over DCOM in this topic. Note Procedures in this section can be completed only on computers that are running Windows Server. You cannot enable or disable remote management on a computer that is running Windows 10 by using these procedures, because the client operating system cannot be managed by using Server Manager.
To enable Server Manager remote management by using the Windows interface
To enable Server Manager remote management by using Windows PowerShell
To enable Server Manager remote management by using the command line
To enable Server Manager and Windows PowerShell remote management on earlier releases of Windows Server
To configure mmc or other tool remote management over DCOM
To disable remote management by using Group Policy
To disable remote management by using an answer file during unattended installation
Windows remote Management (WinRM) listener settingsServer Manager relies on default WinRM listener settings on the remote servers that you want to manage. If the default authentication mechanism or the WinRM listener port number on a remote server has been changed from default settings, Server Manager cannot communicate with the remote server. The following list shows default WinRM listener settings for managing by using Server Manager.
The default port number is 5985 for WinRM to communicate with a remote computer. for more information about how to configure WinRM listener settings, at a command prompt, type winrm help config, and then press ENTER. See AlsoAdd Servers to Server Manager Windows PowerShell: about_remote_Troubleshooting on the Windows Server TechCenter Description of User Account Control FeedbackSubmit and view feedback for Which of the following task must you perform before you can manage a remote server running Windows Server 2012 R2 using the Computer Management snap in?Which of the following tasks must you perform before you can manage a remote server running Windows Server 2012 R2 using the Computer Management snap-in? a. Enable WinRM on the remote server.
How do I remotely control a Windows server?On the computer that you want to manage remotely, open Server Manager, if it is not already open. On the Windows taskbar, click Server Manager. On the start screen, click the Server Manager tile. In the Properties area of the Local Servers page, click the hyperlinked value for the remote management property.
How do I remotely access a Windows 2012 server?Remote Desktop Services for Windows Server 2012. Open the Server Manager Dashboard.. Click Add Roles and Features.. Choose Role-based or feature-based installation.. Select current server from the pool.. Select Remote Desktop Services.. Select Remote Desktop Licensing and Remote Desktop Session Host.. What is the primary difference between the Server Manager in Windows Server 2012 and the previous versions?The primary difference between the Windows Server 2012 Server Manager and previous versions is the ability to add and manage multiple servers at once. Server Manager has been tested with as many as 100 servers added to the interface.
|