Tag: Windows Server Core

Last updated by at .

Windows Server 1709 Server Core Sconfig

How to install Windows Server 1709

Microsoft just released the new Windows Server version 1709 in the Semi-Annual Channel. This blog post is for beginners which want to do their first step setting up Windows Server Core.

First you boot your server or virtual machine form the Windows Server 1709 ISO file. and select which Operating System you want to install. You can choose between Windows Server Standard or Windows Server Datacenter. As you might see, there is only Server Core available. The Server with Desktop Experience or Full Server is only available in the LTSC (Long-Term Servicing Channel) in Windows Server 2016.

Windows Server 1709 Operating System

After accepting the license terms, you can choose the installation type. Even there is an upgrade option, you should choose Custom which will be a new install. Since an in-place upgrade from older Windows Server versions is not supported.

Windows Server 1709 Installation Type

Choose which drive you want to install and the partitioning you want to use

Windows Server 1709 Choose Disk

After that Windows Server will install itself, and reboot for a couple of times.

Windows Server 1709 Installation

After the installation is finished you have to set the default Administrator password.

Windows Server 1709 Admin Password

When you login for the first time, it runs the Windows command prompt with the common Windows commands, or you can run PowerShell, or if you need the magic key to the server core configuration you can run “sconfig” which allows you quickly to do configuration changes, install updates and more.

Windows Server 1709 Server Core Sconfig



Docker Windows Server Container Images

Docker Container Images for Windows Server 1709 and new tagging

Last week Microsoft announced new Windows Server 1709 and the new Windows Server 1709 container images. The new container images in Windows Server version 1709 are highly optimized, especially in size. So for example the new Nano Server Container Image in 1709 is 5x smaller than the Nano Server Container Image in Windows Server 2016.

Microsoft also made some changes to tagging which is interesting.

If you want to use the latest images of the container images based on the Windows Server 2016 (which is in the Long-Term Servicing Channel, LTSC) you just run:

This will give you the latest images of the Windows Server and Nano server container images. If you want to run a specific patch level of the Windows Server 2016 (LTSC)m images, you can run the following:

Docker Windows Server Container Images Size

If you want to use the new Windows Server 1709 container images from the Semi-Annual Channel you can run the following

and again you cans also add a specific base OS container image by using a KB number:

If you already tried out the new container images during the development using the insider images, they still existing:

However, I am not sure what the plan for the insider images is going forward.



Project Honolulu Server Overview

Microsoft Project Honolulu – The new Windows Server Management Experience

Last week Microsoft introduced the world to Project Honolulu, which is the codename for a new Windows Server management experience. Project “Honolulu” is a flexible, locally-deployed, browser-based management platform and tools to manage Windows Server locally and remote.

Microsoft today launched the Hololulu Technical Preview for the world, I had the chance to already work with Microsoft during the last couple of months in a private preview. Project Honolulu helps you to managed your servers remotely as a new kind of Server Manager. This is especially handy if you run Windows Server Core, which I think is the new black, after Microsoft announced that Nano Server is only gonna live as a Container Image with the next version of Windows Server.

Project Honolulu took many features for the Azure Server Management Tools which were hosted in Azure, and allowed you to manage your servers in the cloud and on-premise. But the Feedback was simple, People wanted to install the Management expierence on-prem, without the dependency to Microsoft Azure. Microsoft listened to the feedback and delivered the with Project Honolulu a web-based management solution, which you can install on your own servers.

Honolulu Management Experience

Project Honolulu Server Overview

Project Honolulu has different solutions which give you different functionality. In the technical preview there are three solutions available, Server Manager, Failover Cluster Manager and Hyper-Converged Cluster Manager.

Server Manager

The server manager lets you is kind of like the Server Manager you know from Windows Server, but it also replaces some local only tools like Network Management, Process, Device Manger, Certificate and User Management, Windows Update and so on. The Server Manager Solution also adds management of Virtual Machines, Virtual Switches and Storage Replica.

Failover Cluster Manager

As you might think, this allows you to manage Failover Clusters.

Hyper-Converged Cluster Manager

The Hyper-Converged Cluster Manager is very interesting if you are running Storage Spaces Direct clusters in a Hyper-Converged design, where Hyper-V Virtual Machines run on the same hosts. This allows you to do management of the S2D cluster as well as some performance metrics.

Honolulu Topology

Project Honolulu On-Premise Architecture

Project Honolulu leverages a three-tier architecture, a web server displaying web UI using HTML, a gateway service and the managed nodes. The web interface talks to the gateway service using REST APIs and the gateway connected to the managed nodes using WinRM and PowerShell remoting (Similar like the Azure Management Tools).

Project Honolulu On-Premise and Public Cloud Architecture

You can basically access the Web UI from every machine running modern browsers like Microsoft Edge or Google Chrome. If you publish the webserver to the internet, you can also manage it remotely from everywhere. The installation and configuration of Project Honolulu is straight forward, but If you want to know more about the installation check out, my friend and Microsoft MVP colleague, Charbel Nemnom’s blog post about Project Honolulu.

Project Honolulu Gateways Service can be installed on:

  • Windows Server 2012 R2
  • Windows Server 2016

You can manage:

  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016 and higher

Conclusion

In my opinion Microsoft Project Honolulu provides us with the Windows Server Management Tool we need so much. It helps us to manage our servers from a centralized HTML5 web application, and really makes management of GUI less servers easy. Deployment and configuration is very easy and simple and doesn’t take a lot of effort, while drastically removing the need to locally logon to a server for management reasons. I hope with that we will see a higher deployment of Windows Server Core installations, since we don’t need the GUI on every single server anymore.

You can download the Project Honolulu Technical Preview here: Project Honolulu Technical Preview

You can give feedback to Project Honolulu here: User Voice Project Honolulu

 



Windows Defender PowerShell

How to disable and configure Windows Defender on Windows Server 2016 using PowerShell

Windows Server 2016 comes standard with built-in Anti-Malware called Windows Defender like Windows 10 Client. And per default, Windows Defender is active and has also turned on Real-Time Protection by default. In Windows Server 2016 Desktop Experience you can disable and configure Windows Defender using the UI or PowerShell, in the Windows Server 2016 Core version or on Nano Server you only have PowerShell available. Here are some quick command how you can do this:

Check the Windows Defender Configuration and Settings:

Turn off Windows Defender Real-Time Protection using PowerShell

Turn onWindows Defender Real-Time Protection using PowerShell

Add a File path exclusion:

Add process exclusion

 

I hope this helps you to easily configure Windows Defender on Windows Server 2016. Btw. This also works on Windows Defender on Windows 10.



Exam 70-410: Installing and Configuring Windows Server 2012 (Beta)

Windows Server 2012 RC Logo

Last week I took the Microsoft Private Cloud Exam 70-246: Monitoring and Operating Private Cloud with System Center 2012 and got with this the MCSE: Private Cloud certification. I also did the beta exam 70-410: Installing and Configuring Windows Server 2012.

Now to my experience with the this exam. First of all you can see that Hyper-V is one of the new key features in Windows Server 2012 and you will get a lot of questions about Hyper-V. I got something round 45 questions. The question do pretty much match the list on the exam site. And I would recommend that you check out the new TechNet articles about Windows Server 2012. But I am sure it is much easier to pass the exam if you have worked with the new release of Windows Server 2012. Download the evaluation versions of Windows Server 2012 Release Candidate and test the new features.

You as mentioned on the exam site you should check out the following topics:

You can get more information on the official Microsoft Certification site for exam 70-410: Installing and Configuring Windows Server 2012.

 



Remote Disk Management with “RPC server is unavailable” Error

If you have a Windows Server 2008 R2 Core Server or a Hyper-V R2 Server, which is also managed like a Core Server, you are really happy if you can use the Server Manager for this Remote Machine. Basiclly I had the the Remote Setup done. I could connect to the remote Machine with the Server Manager but when I tried to use the Disk Management on a remote Server and I got the following error “RPC server is unavailable”. After checking it I found the solution. The Problem is that the Firewall blocks the remote communication to virtual disk service. So you have to open the Firewall on the Management Machine

  1. First make sure you activated all the Remote Management options on the Remote Machine. I had all done this but its good to check that.
  2. Now you can run the following Command in cmd on the Management Machine to add the a new firewall rule

firewall



How to add a Windows Server 2008 R2 Core as Secondary DNS Server

This shows you how you can add a secondary DNS Server to your Network on a Windows Server 2008 R2 Core.

  1. As usual you configure the Windows Server 2008 R2 Core with Sconfig
  2. Now install the DNS Server role on the Windows Server 2008 R2 Core
    Windows Server 2008 R2 Core DNS Serverstart /w ocsetup DNS-Server-Core-Role
  3. On the primary DNS Server open the DNS Server MMC
  4. Right click properties on the DNS zones you wanna transfer to the new core server
  5. Add the new DNS Server in the Name Server Tab. In this case this is server04.corp.pepsi.local
    Windows Server 2008 R2 DNS Server
  6. Allow Zone Transfers to this Server or Server in the Name Servers Tab
    Windows Server 2008 R2 DNS Server