in Windows Server 2012 and Windows 8 When it comes to remote management of Windows Server 2012 and Windows 8, remember that when I was a rookie, it was narrowly understood to be equivalent to the RDP-based implementation of the system through Microsoft Terminal Services MSTSC. Remote Desktop Management, or Microsoft Management Console MMC; of course, the remote management method for Windows Server 2012 environment can be simply understood as implementing 1:1 or 1 for servers in the data center through Server Manager: Multi-graphics management, or remote automation management through Powershell. Server Manager is a graphical management tool built into the Windows Server 2012 non-Server Core mode environment (included in the Full GUI and Mini-Server graphical interface Mini Shell mode), which can be used to achieve data center Other Windows Server 2012 servers are remotely graphically managed. Currently, a single server manager can manage up to 100 remote servers. Server server roles need to be added and removed by modifying server roles and functions: 1. Uninstall Server Manager: For environments that have included Server Manager (non-Server Core mode) by default, a. can enter server core mode Ways to remove all server graphical shell and graphical management tool components using the graphical delete server roles and features included with Server Manager b. Use the graphical delete server roles and features included with Server Manager to remove only graphical Management Tools and Infrastructure c. Server Manager can also be disabled via Powershell by Uninstall-WindowsFeature -name PowerShell-ISE, Server-Gui-Mgmt-Infra, Server-Gui-Shell (Enter Core Mode) Uninstall-WindowsFeature -name Server-Gui-Mgmt-Infra (Delete only the Server Manager graphical component) 2. For environments that enter the non-graphics management mode (such as Server core mode) to enable the Server Manager feature, you need to add it through the Powershell command. Add-WindowsFeature -name PowerShell-ISE,Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart In addition, the remotely managed server is enabled by default to allow remote management, or through a graphical interface or Powershell The cmdlet enables or disables remote management locally: 1. Modify the block or enable option via remote management properties in the local graphical interface server manager. 2. Enable via Powershell (which needs to be run as administrator) (this is also a one-stop configuration. Enable all required firewall exception rules at the same time.) Configure-SMRemoting.exe -Enable Server Manager This management component can also be installed on the Windows 8 host, which can be used on Windows 8 systems via
http://www. Microsoft.com/en-us/download/details.aspx?id=28972
Download and install this component separately; however, this component does not provide remote management of Windows 8, but only manages the version of the server. . Screenshot of RSAT remote server management tool installed under Windows 8 In fact, I feel that the interface of the server manager is still very powerful and very necessary. For the powerful functions of this management tool, please refer to http://windowsarchitecture.files. Wordpress.com/2012/12/windows-server-2012-server-manager.pdf
; it connects to the .NET Framework, Windows Management framework 3.0, Windows Remote Management (WinRM), and can quickly connect and generate Powershell scripts. With it, you can easily enable Powershell and Remote Desktop for managed remote hosts, so it is a very effective integrated remote management tool. As mentioned above, Windows Remote Management (WinRM) is known as Windows Remote Management. It is Microsoft's industry-standard Web Service Management Protocol WS-MAN (a kind of hardware and operating system that allows different vendors to interoperate and be firewall-friendly.) Standard SOAP-based protocols) Therefore, WinRM provides a firewall-friendly way to access remote systems in an interoperable manner. It is a remoting mechanism used by the new CIM cmdlets; it not only provides support for the aforementioned server manager, but also provides support for the powerful command line and scripting language Powershell.
I have no intention of starting a discussion on WinRM. For the time being, we need to know that this is the basis for remote hardware and software interoperability. In fact, remote management can be implemented by WinRM using the WinRM script object, the WinRM command line tool, or the Windows Remote Shell command line tool. BMC management data can be obtained to manage remote Windows operating systems such as Windows Server 2012. Management data can be provided by WMI; please note that only the underlying layer can be provided using WMI. Unlike WMI, DCOM communication is not used and data is processed. It is not object-oriented but based on serialized XML format; in addition, similar IPMI management can also be implemented and obtained by providing standard classes on WMI's Povider.