Announcing the Windows Server Summit 26 of June

On the 26 of june Microsoft will have a half of a day summit on Windows Server that you do not want to miss!

The agenda will have four different tracks

  • Hybrid: We’ll cover how you can run Windows Server workloads both on-premises and in Azure, as well as show you how Azure services can be used to manage Windows Server workloads running in the cloud or on-premises.
  • Security: We know security is top of mind for many of you and we have tons of great new and improved security features that we can’t wait to show and help you elevate your security posture.
  • Application Platform: Containers are changing the way developers and operations teams run applications today. In this track we’ll share what’s new in Windows Server to support the modernization of applications running on-premises or in Azure.
  • Hyper-convergent Infrastructure: This is the next big thing in IT and Windows Server 2019 brings amazing new capabilities building on Windows Server 2016. Join this track to learn how to bring your on-premises infrastructure to the next level.

Agenda with times and speakers:

here you can find the link to the summit and download a reminder

Set powerplan to High Performance on VM´s

The recommendation stated is that for virtual machines running on either VMware or Hyper-V should be configured with a High Performance power plan.

Looking at Microsoft Azure VM´s they are set as High Performance by default:

In my Hyper-V lab you can see that I have balanced set and when using the powerplan powershell module I created you can also change it to high perf

If you save the following powershell functions in a folder on c:\program files\windowspowershell\modules\powerplan you can then import it as the screendump and utilize it either on a local server or remote server.

 

Azurestack 1804 admin subscriptions

Last week I updated my Azurestack Devkit to 1804, well with the devkit I have to do a redeploy, during the deployment it got stuck on creating the ADFS VM so i did a reset on that one and -rerun and it got into happyland!

After the deployment was successful I logged into the admin portal and found this, the default subscription have two pals now.

Upgrading our multinode stack did though not give the same view

The docs release notes have been updated to clarify about this and it also states that you should not use the new subscriptions yet

Here you can read more about this.


Azure and Azurestack alternative RDP port for VM

I have been exploring a bit with both Azure and Azurestack and when you onboard your VM´s to Log Analytics and the security center you soon get noticed about 100s of drilions attempts to log on to your mashine if you have made it available through RDP. Although there now is a way to take care of this in a better way using the Security Center JIT Access giving a timespan for opening the port and also limiting to certain IP/networks! Some times an JIT access is not what you can live with but an alternative port could be utilized then the following can be applied.

A recent update to the Azure portal have now surfaced where you get the option to dowload the RDP file with an alternative port instead of the standard 3389, that does not

  1. set the NSG to allow for the new port
  2. set the VM´s internal RDP service to respond to it

So to get the possibility to connect to the virtual machine we need to update the NSG and also reconfigure the virtual machine to actually listen on the new rdp port

First I add a row on the NSG

and then i utilize the custom script extension and change the listener on the virtual machine for RDP

Azurestack:

If I am utilizing an AzureStack all above can be achieved but in the portal the connect button will be greyed out so you can still connect to it but you need to manually enter the public IP and custom port: