Archive for the ‘windows server 2016’ Category

#Azure Server Management Tools offers a set of web-GUI #tools to manage #AzureStack Servers #RSMT #ASMT

Azure Server management tools is currently in preview. Any data collected by Server management tools will be stored in the US.!

As this is a preview you can play with this and it is Cool a nice web management. With the Management server you can manage your on premise AzureStack or Deploy a Template with SCVMM. or just turnoff al your domain controllers.  Oh ok I must re-think my security Policy.

As many Azure is External in some cases it is handled just like a server in a DMZ site. So “real dangerous” this is the Cloud directly connected to the WEB.

This DMZ is now turned and be able to manage your internal servers, what is some one has my azure account that has this gateway…. Well I think this is a cool new feature with a lot of new options. In fact I created a cluster in the Azure GUI but it is running on premises.   

Server management tools enables you to remotely manage machines running Windows Server 2016 Technical Preview. Currently, the tools offer the following capabilities:

  • 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

The Server management tools connection is routed through a Server management tools gateway. When you create a new connection, you will have the opportunity to create a new gateway or select an existing gateway if one already exists in the same resource group. Click on Create to establish a connection to your Windows Server 2016 Technical Preview machine and start exploring the features available today.

Open your Azure management portal and search : Server management tools in the marketplace


Select the Server management tools and a new window opens with the network layout on how things are connected.


So Hit Create


The Create option opens a new menu with all kinds of options Name Subscription , Resourcegroup.


As this is my first server I create it all Fresh so no connections to other Resource Groups


Configuring a new Server management tools Gateway

If you are creating a new gateway, you will see the following status:


Click to open the Gateway Configuration page and read carefully and follow the directions to set up your on-premises machine or Azure VM as the gateway.

An Server management tools gateway is required to enable communication between the Microsoft Azure portal and your Windows Server 2016 machine. A gateway is typically deployed and configured on the same local network as the Windows Server machine(s) you wish to manage. The customized gateway deployment package below allows you to install the gateway software on a machine of your choice, and automatically configures the gateway profile to register with your Azure subscription. The deployment package must be run locally on the machine that you want to designate as the Server management tools gateway.

Steps to configure your gateway


Save the File on your Windows Server 2016


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.

  1. From the machine that you want to designate as the gateway, unzip the package and run GatewayService.MSI.

  2. Once the gateway installation completes, return to the Microsoft Azure portal and reopen your Server management tools connection.

  3. You should now be able to manage your Windows Server 2016 machine if the Microsoft Azure portal can reach it through the gateway.


The Extracted File is the installation file with the JSON config file.

A quick setup is needed on the Windows Server 2016.


As you can see there is an extra Services running on the Windows Server 2016


When I do a Refresh in the Azure Resource Group.


The manage as command is there just go to the Manage As and fill in the server admin account to manage this server



Fill in the account I us a Local Account as in this scenario I’ll not jumping thru my domain. 


You have established a remote connection to your resource and are now able to perform management tasks on it through the Azure Portal.


Some errors here with no surprise My local Firewall and Remote management WINRM is not configured as the text below described.

Unable to connect to the server ‘mvpmgt01’: WinRM cannot process the request. The following error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config.

Managing Workgroup machines

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:

This setting is different than in the guide in Azure

winrm set winrm/config/client’@{TrustedHosts="< NAME OR IP >"}’

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

Now it is play time



As you can see you can manage the local server, there are more options like powershell and event viewer but this is not easy to use in the web-GUI



Happy Stacking

Robert Smit

Twitter: @clustermvp

Cloud and Datacenter MVP

Posted February 12, 2016 by Robert Smit in windows server 2016

Tagged with

First hands-on Upgrading Windows Server 2016 TP2 to TP3 #easy #upgrade #ws2016 #WinServ

Now that Windows Server 2016TP3 is there we can test all the new stuff the in place upgrade was just 10 min downtime that is great. and my SCVMM and SQL server still worked. get the bits here:

At the heart of the Microsoft Cloud Platform, Windows Server brings Microsoft’s experience delivering global-scale cloud services into your infrastructure. Windows Server 2016 Technical Preview 3 provides a wide range of new and enhanced features and capabilities spanning server virtualization, storage, software-defined networking, server management and automation, web and application platform, access and information protection, virtual desktop infrastructure, and more.

As a reminder, these are early pre-release builds. Many of the features and scenarios are still in development. As such, these builds are not intended for production environments, labs, nor full evaluations. This is pre-released software; features and functionality may differ in the final release.

Need more information about the next version of Windows Server? See what’s new in Windows Server 2016 Technical Preview 3.


The upgrade is done in just a few steps I used a System center Virtual Machine Manager VM to upgrade ( with SQL2016 and SCVMM TP2 )

image  image

Want to keep or wipe the server. and


image image


Setup encountered a problem and was unable to determine whether Hyper-V features can be upgraded. For more information about Hyper-V upgrade requirements, see  VmConfigurationVersion vmname or vmobject



image image




image image

In just 10 Minutes Winking smile 

image and here is my VMM server


So what to expect when upgrading  there a a whole lot of new things in 2016 new in this release :


Windows Server Containers

What’s new in Active Directory Domain Services (AD DS) in Windows Server Technical

What’s New in Failover Clustering in Windows Server Technical Preview.

What’s new in Hyper-V in Technical Preview.

What’s New in Windows Server Antimalware Overview for Windows Server Technical Preview.

What’s New in Remote Desktop Services in Windows Server 2016.

What’s New in File and Storage Services in Windows Server Technical Preview.

What’s New in Web Application Proxy in Windows Server Technical Preview.

What’s New in Networking in Windows Server Technical Preview.

Posted August 19, 2015 by Robert Smit in windows server 2016

Tagged with

Windows Server 2016 with Storage Spaces Direct. Building #SOFS with Storage Spaces Direct #winserv #win2016 #S2D #howtopics

Windows Server 2016 enables service providers to deploy Microsoft storage solutions using Storage Spaces Direct with Direct Attached Storage (DAS). Today’s Microsoft storage solutions are dependent on and require storage hardware that is inherently shareable, such as Fibre Channel, or iSCSI SAN, or Storage Spaces with Shared SAS. Storage Spaces with DAS hardware support in Windows Server 2016 enables Microsoft Storage Solutions to use hardware that is not shareable by design.

Windows Server 2016 with Storage Spaces Direct

The Microsoft Storage Solution in Windows Server 2016 is an evolution of the investments in Scale-Out File Server (SOFS), Clustered Shared Volume File System (CSVFS), Storage Spaces and Failover Clustering.

Windows Server 2016 with Storage Spaces Direct

What’s New in the Windows Server Technical Preview

What’s New in Failover Clustering in Windows Server Technical Preview

What do we need to create a Windows Server Storage Spaces Direct  ?

Well just a cluster based on windows server Technical preview and some local disks any disks ? no not just any disk it can’t be USB disk but this can be used with the normal storage spaces. as shown here

A basic cluster with a bunch of drives is al you need

In this case I have a two node cluster and  20 disks on node 1 and 9 disk on node 2.

Remember these are local disk and not clustered. We can transfer this in a Storage Space and use it for Hyper-v

Windows Server 2016 with Storage Spaces Direct

But Suppose we could use this for a cluster then our “old” disks would be use full to other functions.

Of course there are some question marks here  but let me show you how to build this and this could be helpful.

If I take a look at the disk storage on my first node I see 21 disk

image  image

and not that much storage on node 2

So on our two node cluster I can’t add local storage this will not work unless..

Unless we set an extra Cluster Property and then we can use this disk as cluster storage but with a star*

I’ll do this in the GUI in PowerShell it is way to easy ( did you hear that …odd a few years ago it was reversed )

If we take a look at the Cluster Property’s we will see that there is a new option in DASMODE

DASModeEnabled        0
DASModeBusTypes        134144
DASModeOptimizations        1
DASModeIOLatencyThreshold        10000


Windows Server 2016 with Storage Spaces Direct

When setting all the options we can use all the disks in the cluster nodes.

Setting the DASModeEnabled=1 will allocate all the local disk to the Storage Pool.


Windows Server 2016 with Storage Spaces Direct

in the enclosures there is a huge list with all the Disks, these disk are all local disks Winking smile

Windows Server 2016 with Storage Spaces Direct

Now we are creating Storage Spaces I’ll show you this in the GUI and this way you can see what is changed in the cluster. After this you can do this in PowerShell like in de blogs below

More info can be found here Deploy Clustered Storage Spaces

Step-by-step for Storage Spaces Tiering in Windows Server 2012 R2

Now that all my disk converted to a SES enclosure and as you can see this is published in the Cluster under the new Enclosure under storage.




Creating a new Storage spaces direct

Windows Server 2016 with Storage Spaces Direct 

As you can see I can create Multiple Spaces


You will need at least 3 disk to create a Storage Space.


Windows Server 2016 with Storage Spaces Direct

Selecting the Disks for the Storage Space



Next create a Virtual disk in the just created Storage Space




I have no storage tier so for this demo I choose a simple setup




Now that the disk is created we need to create a volume on the Disk.



As you can see there are several steps needed to create a disk/ volume in a Storage space. This has nothing to do with Storage spaces direct.

when look at the cluster I see now a Disk in the pool that I can use as a Cluster Disk for a Clustered Resource.


Windows Server 2016 with Storage Spaces DirectWindows Server 2016 with Storage Spaces Direct

In this case I used Only a simple setup but you can create a bigger setup and getting more lops or redundancy


Windows Server 2016 with Storage Spaces Direct

In this case I created a Scale out file server with Storage Spaces Direct. This is demo only!

Windows Server 2016 with Storage Spaces Direct

So these are the basic steps to use , you can use a tiered storage space direct.

If you want more info about this checkout the Techdays NL Agenda


Or view the Sessions from Ignite on Channel 9



Happy clustering

Robert Smit


Technorati Tags: ,,,,,,

Posted May 12, 2015 by Robert Smit in windows server 2016

Tagged with

  • Tag