Tag: Gateway

Last updated by at .

Azure Remote Server Management Nano Server

Manage Nano Server and Windows Server from Azure using Remote Server Management Tools

Today Microsoft announced the preview of the Remote Server Management Tools hosted in Azure, written by Kriti Jindal, a program manager on the Server management tools team. This service allows you to manage your servers directly from Azure using a web-based HTML5 portal. I personally think that this could replace Server Manager and allows you to easily manage non-GUI servers such as Windows Server Core and Nano Server. This is the first public preview of the Remote Server Management Tools and it limited right now to manage Windows Server 2016 Technical Preview server, hosted on-prem or in Microsoft Azure. The Remote Server Management Tools today include the following features:

  • View and change system configuration
  • View performance across various resources and manage processes and services
  • Manage devices attached to the server
  • View event logs
  • View the list of installed roles and features
  • Use a PowerShell console to manage and automate

Overview

To remotely manage your Windows Server from Azure, you have to deploy a Remote Server Management Gateway into your network. This can be a Windows Server 2012 R2 Server running the WMF 5.0 (Windows Management Framework 5.0) or Windows Server 2016 with no additional preparation. You also need a Microsoft Azure subscription and an account.

Microsoft Azure Server Management Tools Topology

The gateway will handle the connection to Azure, so the Remote Server Management Gateway needs connection to the internet. The managed servers do not need a direct connection to the internet, the gateway will connect to the managed server. With that, the gateway need connection to the sever which will be managed by Azure.

Setup Server Management Tools

Well to set this up some steps are required, first create a new server for the Remote Server Management Gateway. In my case I installed a new Windows Server 2016 virtual machine. I made sure I could connect to the internet and it has the lastest updates installed.

Microsoft Azure Server Management Tools New Connection

After I created the virtual machine I logged in to the Azure portal and added a new Server Management Tools Connection. You can search “Server management tools” in Marketplace or navigate to it: Marketplace -> Management -> More -> Server management tools. This will also create the first Server Management Tools Gateway for your connection.

Microsoft Azure Server Management Tools Connection

After the connection is created you can see the connection and but you will get the information that the gateway is not ready. As the next step you will configure the gateway on the prepared server.

Microsoft Azure Server Management Tools Gateway

Under the Server Management Tools Gateway blade you can find a setup for the gateway which will generate a custom install package for your gateway. You can copy this link to the server and download this package and install it.

  1. Allow gateway updates to be installed automatically (recommended), or choose to install updates manually. You may change this later under gateway settings.
  2. Click the below to generate a customized gateway deployment package link.
  3. Use the generated link to download the gateway deployment package now, or copy the link URL to download the package later from the machine on which you intend to install the package.
  4. From the machine that you want to designate as the gateway, unzip the package and run GatewayService.MSI.
  5. Once the gateway installation completes, return to the Microsoft Azure portal and reopen your Server management tools connection.
  6. You should now be able to manage your Windows Server 2016 machine if the Microsoft Azure portal can reach it through the gateway.

Azure Remote Server Management Gateway Installer

After you have installed the Remote Server Management Gateway package on your gateway server you can see the connection in the Azure portal.

Azure Remote Server Management Nano Server

Now you start remote manage your server. As mentioned before, this is really handy if you want to manage Server Core or Nano Server.

Additional Stuff:

There are some additions for the configuration if you want to manage servers in a workgroup environment:

In order to manage workgroup machines (e.g. non-domain-joined Nano Servers), run this command as an administrator on the Server management tools gateway machine:

winrm set winrm/config/client @{ TrustedHosts=”<<IP address>>” }

When creating a Server management tools connection to the workgroup machine, use the machine’s IP address as the computer name.

Additional connectivity requirements

If you wish to connect using the local Administrator account, you will need to enable this policy on the target machine by running the following command in an administrator session on the target machine:

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1

If you wish to connect to a workgroup machine which is not on the same subnet as the gateway, run the following command in an administrator session on the target machine:

NETSH advfirewall firewall add rule name=”WinRM 5985″ protocol=TCP dir=in localport=5985 action=allow

Remote Management Server Tools Features

Azure Remote Server Management PowerShell

As mentioned the Remote Management Server Tools bring some really cool web-based management features. One of my favorites is the web-based PowerShell console.

  • Device Manager
  • PowerShell Console
  • Computer Configuration (Name, Domain,…)
  • Network Configuration
  • Task Manager
  • Process
  • Registry Editor
  • Roles and Features
  • Services
  • Local Administrators
  • Updates Management (coming soon)
  • Shutdown / Restart

More Information

 

 



System Center Logo

Summary: Update Rollup 8 for System Center 2012 R2 and Azure Pack now available

Yesterday Microsoft released Update Rollup 8 for System Center 2012 R2 and Windows Azure Pack. Again with the Update Rollups for Windows Azure Pack and System Center, Microsoft not only delivers bug fixes, they also release new features.

There are some really cool highlights in this Update Rollup:

  • Network Virtualization Improvements (Multiple External IP Addresses,…)
  • SCDPM bug fixes
  • Better Checkpoint Integration (Checkpoint Quotas,…)
  • Support for SQL Server 2014 SP1
  • Support of Tier Storage in VMM for Storage Spaces
  • Hyper-V ACL Support in VMM
  • New Network devices in SCOM

Here you can get a quick update on what’s new in Update Rollup 8:

  • Data Protection Manager (KB3086084)
    • The DPM Agent crashes intermittently during a backup.
    • If you are trying to recover data from an imported tape, DPM may crash with a “Connection to the DPM service has been lost” error.
    • If you try to back up a SharePoint site that uses SQL Always On as a content database, SQL logs are not truncated as expected.
    • You cannot verify tape library compatibility for tapes that use RSMCompatmode settings such as IBM 35xx, 2900, and so on.
    • If you have multiple SharePoint farms hosted on the same SQL cluster with different instances but the same database names, DPM cannot back up the correct SharePoint farm content.
    • If you run Update Rollup 7 for Data Protection Manager 2012 R2, and you have already configured online protection for one or more protection groups, trying to change the protection group populates the default DPM settings for the “Select long-term goals” wizard instead of the previous configured values.
    • When you try to protect a SQL failover cluster, the Data Protection Manager UI crashes for every backup or synchronization operation.
    • If you install Update Rollup 7 for Data Protection Manager 2012 R2, self-service recovery for SQL databases may not work.
  • Operations Manager (KB3096382)
    • Slow load of alert view when it is opened by an operator
      Sometimes when the operators change between alert views, the views take up to two minutes to load. After this update rollup is installed, the reported performance issue is eradicated. The Alert View Load for the Operator role is now almost same as that for the Admin role user.
    • SCOMpercentageCPUTimeCounter.vbs causes enterprise wide performance issue
      Health Service encountered slow performance every five to six (5-6) minutes in a cyclical manner. This update rollup resolves this issue.
    • System Center Operations Manager Event ID 33333 Message: The statement has been terminated.
      This change filters out “statement has been terminated” warnings that SQL Server throws. These warning messages cannot be acted on. Therefore, they are removed.
    • System Center 2012 R2 Operations Manager: Report event 21404 occurs with error ‘0x80070057’ after Update Rollup 3 or Update Rollup 4 is applied.
      In Update Rollup 3, a design change was made in the agent code that regressed and caused SCOM agent to report error ‘0x80070057’ and MonitoringHost.exe to stop responding/crash in some scenarios. This update rollup rolls back that UR3 change.
    • SDK service crashes because of Callback exceptions from event handlers being NULL
      In a connected management group environment in certain race condition scenarios, the SDK of the local management group crashes if there are issues during the connection to the different management groups. After this update rollup is installed, the SDK of the local management group should no longer crash.
    • Run As Account(s) Expiring Soon — Alert does not raise early enough
      The 14-day warning for the RunAs account expiration was not visible in the SCOM console. Customers received only an Error event in the console three days before the account expiration. After this update rollup is installed, customers will receive a warning in their SCOM console 14 days before the RunAs account expiration, and receive an Error event three (3) days before the RunAs account expiration.
    • Network Device Certification
      As part of Network device certification, we have certified the following additional devices in Operations Manager to make extended monitoring available for them:

      • Cisco ASA5515
      • Cisco ASA5525
      • Cisco ASA5545
      • Cisco IPS 4345
      • Cisco Nexus 3172PQ
      • Cisco ASA5515-IPS
      • Cisco ASA5545-IPS
      • F5 Networks BIG-IP 2000
      • Dell S4048
      • Dell S3048
      • Cisco ASA5515sc
      • Cisco ASA5545sc
    • French translation of APM abbreviation is misleading
      The French translation of “System Center Management APM service” is misleading. APM abbreviation is translated incorrectly in the French version of Microsoft System Center 2012 R2 Operations Manager. APM means “Application Performance Monitoring” but is translated as “Advanced Power Management.” This fix corrects the translation.
    • p_HealthServiceRouteForTaskByManagedEntityId does not account for deleted resource pool members in System Center 2012 R2 Operations Manager
      If customers use Resource Pools and take some servers out of the pool, discovery tasks start failing in some scenarios. After this update rollup is installed, these issues are resolved.
    • Exception in the ‘Managed Computer’ view when you select Properties of a managed server in Operations Manager Console
      In the Operations Manager Server “Managed Computer” view on the Administrator tab, clicking the “Properties” button of a management server causes an error. After this update rollup is installed, a dialog box that contains a “Heart Beat” tab is displayed.
    • Duplicate entries for devices when network discovery runs
      When customers run discovery tasks to discover network devices, duplicate network devices that have alternative MAC addresses are discovered in some scenarios. After this update rollup is installed, customers will not receive any duplicate devices discovered in their environments.
    • Preferred Partner Program in Administration Pane
      This update lets customers view certified System Center Operations Manager partner solutions directly from the console. Customers can obtain an overview of the partner solutions and visit the partner websites to download and install the solutions.
  • Orchestrator & SMA (KB3096381)
    • SQL Server 2014 Service Pack 1 (SP1) is now supported in Orchestrator 2012 R2.
    • After you export and then import a Runbook, the Password field of Run Program activity is corrupted.
    • SMA: SQL Server 2014 Service Pack 1 is now supported in Service Management Automation 2012 R2.
    • SMA: Service Management Automation 2012 R2 does not let you stop jobs that are in the queued state.
  • Service Provider Foundation (KB3096384)
    • Installing update rollups for Service Provider Foundation causes additional bindings to be created, and this makes a Service Provider Foundation website inaccessible.
    • Quotas for multiple NAT connections are not supported. For more information about this feature, see WAP Update Rollup 8 documentation.
  • Virtual Machine Manager (KB3096389)
    • Support for SQL Server 2014 SP1 as VMM database
      With Update Rollup 8 for SC VMM 2012 R2 you can now have Microsoft SQL Server 2014 SP1 as the VMM database. This support does not include deploying service templates by using the SQL profile type as SQL Server 2014 SP1. For the latest information about SQL Server requirements for System Center 2012 R2, see the reference here.
    • Support for VMWare vCenter 6.0 management scenarios
      With Update Rollup 7, we announced support for management scenarios for vCenter 5.5. Building on our roadmap for vCenter and VMM integration and supportability, we are now excited to announce support for VMWare vCenter 6.0 in Update Rollup 8. For a complete list of supported scenarios, click here.
    • Ability to set quotas for external IP addresses
      With Update Rollup 7, we announced support for multiple external IP addresses per virtual network, but the story was incomplete, as there was no option to set quotas on the number of NAT connections. With UR8, we are glad to announce end-to-end support for this functionality, as you can now set quotas on the number of external IP addresses allowed per user role. You can also manage this by using Windows Azure Pack (WAP).
    • Support for quotas for checkpoints
      Before UR8, when you create a checkpoint through WAP, VMM does not check whether creating the checkpoint will exceed the tenant storage quota limit. Before UR8, tenants can create the checkpoint even if the storage quota limit will be exceeded.
    • Ability to configure static network adapter MAC address during operating system deployment
      With Update Rollup 8, we now provide the functionality to configure static network adapter MAC addresses during operating system deployment. If you have ever done Bare Metal provisioning of hosts and ended up having multiple hosts with the same MAC addresses (because of dynamic IP address assignment for network adapters), this could be a real savior for you.
    • Ability to deploy extended Hyper-V Port ACLs
      With Update Rollup 8 for VMM, you can now:

      • Define ACLs and their rules
      • Attach the ACLs created to a VM network, VM subnets, or virtual network adapters
      • Attach the ACL to global settings that apply it to all virtual network adapters
      • View and update ACL rules configured on the virtual network adapter in VMM
      • Delete port ACLs and ACL rules
    • Support for storage space tiering in VMM
      With Update Rollup 8, VMM now provides you the functionality to create file shares with tiers (SSD/HDD).
    • Issue 1
      Creation of Generation 2 VMs fails with error 13206
    • Issue 2
      VMM does not let you set the owner of a hardware profile with an owner name that contains the “$” symbol.
    • Issue 3
      HA VMs with VLAN configured on the network sites of a logical network cannot be migrated from one host to another. Error 26857 is thrown when you try to migrate the VM.
    • Issue 4
      The changes that are made by a tenant administrator (with deploy permissions to a cloud) to the Memory and CPU settings of a VM in the cloud through VMM Console do not stick. To work around this issue, change these settings by using PowerShell.
    • Issue 5
      When a VM is deployed and put on an SMB3 file share that’s hosted on NetApp filer 8.2.3 or later, the VM deployment process leaves a stale session open per VM deployed to the share. When many VMs are deployed by using this process, VM deployment starts to fail as the max limit of the allowed SMB session on the NetApp filer is reached.
    • Issue 6
      VMM hangs because of SQL Server performance issues when you perform VMM day-to-day operations. This issue occurs because of stale entries in the tbl_PCMT_PerfHistory_Raw table. With UR8, new stale entries are not created in the tbl_PCMT_PerfHistory_Raw table. However, the entries that existed before installation of UR8 will continue to exist.
    • Issue 7
      In a deployment with virtualized Fiber Channel adapters, VMM does not update the SMI-S storage provider, and it throws an exception.
    • Issue 8
      For VMs with VHDs that are put on a Scale out File Server (SOFS) over SMB, the Disk Read Speed VM performance counter incorrectly displays zero in the VMM Admin Console. This prevents an enterprise from monitoring its top IOPS consumers.
    • Issue 9
      Dynamic Optimization fails, leaks a transaction, and prevents other jobs from executing. It is blocked on the SQL Server computer until SCVMM is recycled or the offending SPID in SQL is killed.
    • Issue 10
      V2V conversion fails when you try to migrate VMs from ESX host to Hyper-V host if the hard disk size of the VM on the ESX host is very large.
    • Issue 11
      Live migration of VMs in an HNV network takes longer than expected. You may also find pings to the migrating VM are lost. This is because during the live migration, the WNV Policy table is transferred (instead of only delta). Therefore, if the WNV Policy table is too long, the transfer is delayed and may cause VMs to lose connectivity on the new host.
    • Issue 12
      VMM obtains a wrong MAC address while generating the HNV policy in the deployments where F5 Load Balancers are used.
    • Issue 13
      For IBM SVC devices, enabling replication fails in VMM because there is a limitation in SVC in which the name of the consistency group should start with an alphabetical character (error code: 36900). This issue occurs because while enabling replication, VMM generates random strings for naming the “consistency groups” and “relationship” between the source and the target, and these contain alphanumeric characters. Therefore, the first character that’s generated by VMM may be a number, and this breaks the requirement by IBM SVC.
    • Issue 14
      In Update Rollup 6, we included a change that lets customers have a static MAC address even if the network adapter is not connected. This fix did not cover all scenarios correctly, and it triggers an exception when there’s a template with a connected network adapter, and then you later try to edit the static address in order to disconnect the network adapter.
    • Issue 15
      Post Update Rollup 6, as soon as a host goes into legacy mode, it does not come back to eventing for 20 days. Therefore, the VM properties are not refreshed, and no events are received from HyperV for 20 days.This issue occurs because of a change that’s included in UR6 that set the expiry as 20 days for both eventing mode and legacy mode. The legacy refresher, which should ideally run after 2 minutes, now runs after 20 days; and until then, eventing is disabled.Workaround:
      To work around this issue, manually run the legacy refresher by refreshing VM properties.
    • Issue 16
      Post-UR7, deleting a virtual network does not correctly clean up the cluster resources for the Network Virtualization Gateway. This causes the cluster role (cluster group) to go into a failed state when a failover of the HNV gateway cluster role occurs.
  • Windows Azure Pack (KB3096392)
    • Administrators cannot offer and tenants cannot use multiple external IP addresses through a Network Address Translation (NAT) connection.
      Even though Microsoft System Center Virtual Machine Manager (VMM) has functionality to allocate IP addresses for this purpose, the WAP administrator and tenant experiences do not provide such functionality. Administrators can now allocate a set of external IP addresses for tenants to use when you create NAT rules. The administrator can set up the IP address quota through the Administrator Portal virtual machine (VM) extension.
    • Tenants can create only one checkpoint per virtual machine.
      Administrators can create plans that include quotas that let tenants create multiple VM checkpoints.
    • An unexpected exception is generated by the PowerShell command “Get-MgmtSvcSqlDatabase.”
      The command Get-MgmtSvcSqlDatabase does not retrieve SQL database information. The following examples return exception “Object reference not set to an instance of an object”:

      • Get-MgmtSvcSqlDatabase -AdminUri $AdminUri -Token $Token -HostingServerId “someid” -DisableCertificateValidation
      • Get-MgmtSvcSqlDatabase -AdminUri $AdminUri -Token $Token -HostingServerId $hostserver.ServerId -Name “somename” -DisableCertificateValidation
      • Get-MgmtSvcSqlDatabase -AdminUri $AdminUri -Token $Token -HostingServerId ” someserverid” -Name “datatest” -DisableCertificateValidation
    • An unexpected exception is generated by the PowerShell command “Remove-MgmtSvcMySqlHostingServer.” 
      This command fails with the exception “Index (zero-based) must be greater than or equal to zero and less than the size of the argument list” when you run statements such as the following:

      • Remove-MgmtSvcMySqlHostingServer -AdminUri $AdminUri -Token $Token -HostingServerId $HostServer[0].ServerId -DisableCertificateValidation
      • Remove-MgmtSvcMySqlHostingServer -AdminUri $AdminUri -Token $Token -HostingServerId “someserverid” -DisableCertificateValidation
    • When you create a virtual machine through the Tenant Portal, the menu dropdown boxes are not sorted.
      When a tenant tries to create a VM and the list of items is larger than some items, it becomes very difficult to find the necessary machine image or template.
    • Attaching ISOs in a generation 2 (gen 2) VM fails after three or four attach or detach operations.
      The attach and detach operations on ISO disks and VM gen 2 allocate adapters never releases the adapters for reuse.After you apply this update, detaching the disk adapter enables the adapter to be reused again.

This Update Rollup is one of the bigger one Microsoft released in terms of Azure Pack IaaS Scenarios. This update brings several great improvements to the implementation of Checkpoints and Network Virtualization. Update Rollup 8 finally bringing end to end support for multiple external IP Addresses for the NVGRE Gateways inside WAP as well as VMM. Also better support for Checkpoints on Hyper-V in the WAP Portal as well as VMM.

As always, before you deploy an update rollup in production, make sure, you have tested it in your test or lab environment.



Windows Server

List of Recommend Hotfixes and Updates for Hyper-V Network Virtualization (HNV)

I already made some post where I list the websites to recommended hotfixes and updates for Clusters, Hyper-V and File Server such as the Scale-Out File Server for Hyper-V over SMB. Now Microsoft also has an official list for Recommended hotfixes, updates, and known solutions for Windows Server 2012 and Windows Server 2012 R2 Hyper-V Network Virtualization (HNV) environments. Which will list hotfixes for Hyper-V, Windows Server and System Center related to Network Virtualization.

You can find the List here on the Microsoft Support Site: KB2974503 Recommended hotfixes, updates, and known solutions for Windows Server 2012 and Windows Server 2012 R2 Hyper-V Network Virtualization (HNV) environments



Hyper-V Network Virtualization Gateway VM Network Connectivity

Connect Microsoft Hyper-V Network Virtualization Gateway in System Center Virtual Machine Manager

If you are using Hyper-V Network Visualization you can use the Microsoft Hyper-V Network Virtualization Gateway for your Virtual Machines to leave the VM Networks or to connected inside these Virtual Networks. If you have deployed the Hyper-V Network Virtualization Gateway, which is basically a virtual machine which you can deploy with a Service Template inside SCVMM, you have to connect this Gateway inside System Center Virtual Machine Manager.

Microsoft Hyper-V Network Virtualization Gateway Service Template

First open the SCVMM console and navigate to Fabric and add a new Network Service. Enter a name fort the Network Service.

Microsoft Hyper-V Network Virtualization Gateway in Virtual Machine Manager

Choose the Microsoft Windows Server Gateway as a model.

Microsoft Windows Server Gateway

Setup the Run As account for the connection and enter the connection string for the Hyper-V Network Virtualization Gateway

Hyper-V Network Virtualization Gateway connection string

If your Gateway is not domain joined you have to use Certificate for the communication between Virtual Machine Manager and the Hyper-V Network Virtualization Gateway.

After that you can validate and test the network service configuration of the Gateway.

Validate Hyper-V Network Virtualization Gateway

After you have added the Gateway you have to do a final configuration step in the properties of the Gateway.

Hyper-V Network Virtualization Gateway

You have to map the network adapters for the frontend (Internet, Corpnet) with the NIC and the back end which would be the tenant network to the specific NIC.

Hyper-V Network Virtualization Gateway Configuration

 

After that you can now finally add connectivity to your VM Networks which are using Hyper-V Network Virtualization, such as Site-to-Site VPN, Routing or NAT.

Hyper-V Network Virtualization Gateway VM Network Connectivity