The content of this article or any related information is under the Creative Commons license BY, you can republish this content freely but you must mention the author of this article: Kernel and indicate the URL of this page: https://www.exabyteinformatica.com/tienda/foro/windows-server-2016-introducing-server-administration-tools-t1403.html
Server administration equipment overview
Server management tools offers a collection of web-primarily based GUI and command line tools to control home windows Servers. This is above all valuable when managing headless servers similar to Nano Server and Server Core. These tools additionally deliver quick entry to your on premises infrastructure alongside your Azure elements. during this first unlock, the equipment can handiest be used to manage windows Server 2016 Technical Preview SKUs running on-premises in addition to in Azure. The equipment are hosted in Microsoft Azure.
Currently, the equipment offer the following capabilities:
• View and change system configuration.
• View efficiency across quite a few elements and manipulate techniques and capabilities.
• Control contraptions connected to the server.
• View event logs.
• View the record of put in roles and features.
• Use a PowerShell console to control and automate.
Here is a preliminary set of equipment that are required for fundamental server diagnostics. When you've got specific requests on what tools could be most effective to you, please let us know the use of the home windows Server administration tools UserVoice feedback site.
Setup and deployment
A Server administration tools gateway is required to enable conversation between the Microsoft Azure portal and your windows Server 2016 machines. A gateway is typically deployed and configured on the identical local network because the windows Server computing device(s) you want to manage. The computer need to have an online connection.
If the laptop internet hosting the gateway is a home windows Server 2012 R2 computer, please installation WMF 5.0. here is required to make use of PowerShell to manage windows Server 2016 Technical Preview or Nano Server machines from home windows Server 2012 R2. Use right here hyperlink to set up WMF 5.0: http://aka.ms/wmf5download
If the machine internet hosting the gateway is a windows Server 2016 Technical Preview computing device, no further instruction is required.
You’ll additionally want an Azure subscription to use Server administration equipment.
Now let’s talk about the way to setup the Server administration tools gateway and start managing your laptop(s).
Step 1: Create a new Server administration tools connection
Good enough so you have a desktop that you just are looking to be capable of manipulate by the use of Server management tools. To start your deployment, log in to your Azure portal account and search for “Server administration tools” in industry or navigate to it: https://portal.azure.com/#create/Micros ... es/preview.
Choose the Server management equipment, read the outline, evaluate the phrases of this Preview free up, and click “Create”.
This can open a kind prompting you to fill out the assistance for the connection you're setting up.
Please provide the name/IP/FQDN of the desktop you want to hook up with. if in case you have an existing useful resource group and gateway, you may additionally opt to select them here rather than to create a new group or gateway.
If this is the first Server management equipment connection you're creating, you'll additionally need to decide to create a brand new Server management tools gateway and give it a reputation. You might be induced to finish the gateway configuration after the Server management equipment connection is created.
As soon as the form has been accomplished, click on create at the bottom of the display and you'll be taken lower back to the Azure Startboard. Assuming “Pin to Startboard” become checked, you are going to see a tile appear so that you can indicate the deployment is in progress. Please note that you just are not definitely creating the connection to the machine however only a useful resource in Azure. The connection to the computing device is initiated once you deliver the credentials on the leading Server management equipment blade.
As soon as the deployment succeeds, you may be taken to the Server management equipment blade the place that you can supply the credentials and fasten to the machine. The consumer identify and Password aren't being created with the aid of the connection, and have to exist already on the computer and have appropriate permissions. I.e. use a consumer account which is a member of the native administrators group on the goal server you're connecting to.
Step 2: Configuring a brand new Server management equipment Gateway
If you are creating a new gateway, you'll see right here status:
Click on to open the Gateway Configuration web page and skim cautiously and observe the directions to deploy your on-premises computer or Azure VM as the gateway.
Observe: Please unzip the zip file and run the gateway MSI installer from the folder you unzipped to. if you run the MSI from the zip file without unzipping first, you are going to should also specify the profile.json file.
After installing the gateway MSI, return to the Azure portal, and click Refresh. You are going to now be triggered to enter the credentials to delivery managing the laptop. You will see the following repute:
Congratulations! You have centred a far flung connection to your useful resource and are now capable of operate administration tasks on it through the Azure Portal.
Managing Workgroup machines
With the intention to connect to workgroup machines (e.g. non-area-joined Nano Servers), run the following command in PowerShell or Command instantaneous as Administrator. TargetMachineNameOrAddress should be the NetBIOS identify, FQDN or IP tackle (IPv4 or IPv6) that you just’ve used when growing the Server administration tools connection in Azure (which is also the name displayed on the properly of the blade). That you could additionally add distinct machines through isolating them with commas.
winrm set winrm/config/customer @ TrustedHosts=”TargetMachineNameOrAddress” PowerShell: winrm set winrm/config/client ‘@ TrustedHosts=”TargetMachineNameOrAddress” ’
Notice: The instructions above will change any outdated checklist of registered relied on hosts with the host(s) you specify in the command. That you could use right here command in PowerShell with the Concatenate parameter to add a computer identify to an latest checklist of depended on hosts.
Set-item wsman:\localhost\customer\TrustedHosts TargetMachineNameOrAddress –Concatenate
Extra connectivity requirements
In case you need to connect using the local Administrator account, you'll deserve to allow this policy on the goal machine by running the following command in an administrator session on the goal machine:
REG ADD HKLMSOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1
In case you wish to connect to a workgroup desktop which is not on the equal subnet because the gateway, run right here command in an administrator session on the target computing device:
NETSH advfirewall firewall add rule name=”WinRM 5985” protocol=TCP dir=in localport=5985 action=allow
The Server administration equipment crew is looking forward to your comments on the general public preview. You can give remarks on the tools directly via the feedback button in the Azure portal. We additionally automatically monitor the home windows Server management equipment UserVoice remarks website for information on improvements and inspire you to submit your concepts there.
No te pierdas el tema anterior: Implementación de Terminal Server en Windows Server 2016
Salta al siguiente tema: How to build a home FTP server with FileZilla Server
Quizás también te interese: