Web version of Server Management Tools for TP 2016
New Server Management Tools are available on the web (on the new Azure portal), so far in the preview.
This “utility” allows you to get information and manage the server through the Azure website (both virtual machines in Azure and on the ground). Works for all versions \ editions ( including Nano ) 2016 TP4, the utilities themselves are currently located in Azure.
Architecture:
As you can see from this picture, the architecture is simple and simple, you need a browser, a gateway server, an Azure subscription, and a server (s) that you need to manage (and).
Server management tools Gateway can be installed on an OS in Azure or “on the ground”; after its configuration, it can be connected to a server or many servers that need to be managed. Gateway server needs internet to communicate with Azure. Gateway server may be 2012 r2, but then you need to install WMF 5.0 . For ideas and suggestions there is a UserVoice .
Functional:
1. View and change the OS configuration;
2. View various OS metrics;
3. OS device management (for this, the device manager was rewritten in TP);
4. View OS events;
5. View a list of installed roles and components;
6. The powershell console.
')
Testing:
To get started, you need to create a new Server Management Tools object in the Azure portal (new> in the search bar Server management tools> fill in all the fields). When you first create, you will need to create a new Server management tools Gateway, I chose a virtual machine in Azure (indicated its internal IP when creating). Ideally, the Gateway server and the managed server should be on the same network. After the gate is created, it will tell you that it cannot find the Server management tools Gateway, this is normal, because You have not installed it yet. :)
Zmakayte in this line, follow the instructions that you provide (in fact, just download and install the MSI file, then further below and further). If you did everything correctly the picture will change.
Now you only need to specify the username / password to manage the server (with local administrator rights on the target server).
Here are a couple of screenshots for the seed:
Device manager
Event viewer
Process explorer
Registry
Nuances!
To manage servers in the Workgroup, you need to add them to the Trusted hosts on the Server management tools Gateway:
This “utility” allows you to get information and manage the server through the Azure website (both virtual machines in Azure and on the ground). Works for all versions \ editions ( including Nano ) 2016 TP4, the utilities themselves are currently located in Azure.
Architecture:
As you can see from this picture, the architecture is simple and simple, you need a browser, a gateway server, an Azure subscription, and a server (s) that you need to manage (and).
Server management tools Gateway can be installed on an OS in Azure or “on the ground”; after its configuration, it can be connected to a server or many servers that need to be managed. Gateway server needs internet to communicate with Azure. Gateway server may be 2012 r2, but then you need to install WMF 5.0 . For ideas and suggestions there is a UserVoice .
Functional:
1. View and change the OS configuration;
2. View various OS metrics;
3. OS device management (for this, the device manager was rewritten in TP);
4. View OS events;
5. View a list of installed roles and components;
6. The powershell console.
')
Testing:
To get started, you need to create a new Server Management Tools object in the Azure portal (new> in the search bar Server management tools> fill in all the fields). When you first create, you will need to create a new Server management tools Gateway, I chose a virtual machine in Azure (indicated its internal IP when creating). Ideally, the Gateway server and the managed server should be on the same network. After the gate is created, it will tell you that it cannot find the Server management tools Gateway, this is normal, because You have not installed it yet. :)
Zmakayte in this line, follow the instructions that you provide (in fact, just download and install the MSI file, then further below and further). If you did everything correctly the picture will change.
Now you only need to specify the username / password to manage the server (with local administrator rights on the target server).
Here are a couple of screenshots for the seed:
Device manager
Event viewer
Process explorer
Registry
Nuances!
To manage servers in the Workgroup, you need to add them to the Trusted hosts on the Server management tools Gateway:
winrm set winrm/config/client @{ TrustedHosts="<>" }
:
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "*"
, :
REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1
: NETSH advfirewall firewall add rule name="WinRM 5985" protocol=TCP dir=in localport=5985 action=allow
15 , !
.
. , , ( powershell).
. Server Management tools .Source: https://habr.com/ru/post/276931/
All Articles