Category: Web

Last updated by at .

Surface Precisiaon Mouse Box

Microsoft Surface Precision Mouse Review

Last week I got the Microsoft Surface Precision Mouse delivered. The Surface Precision Mouse will become the replacement mouse for my Microsoft Sculpt Mouse, which I used for the last couple of years. Now I want to give you some impressions about the Surface Precision Mouse, since I am very happy and very surprised about the feature set.

Surface Precision Mouse

First of all the Microsoft Surface Precision Mouse feels awesome, very high quality and it is very comfortable in your hand. It feels very precise and you get very quickly used to it.

Now let me write about some extra features you might didn’t know about. You first get a button to configure the scroll wheel in two different speeds, one feels very light and fast and the other one is slower and is more resistant, so you can choose what you like more and switch between them, depending on your task.

Microsoft Surface Percision Mouse Settings

Of course you get some extra buttons which you can customize with different shortcuts, for example to open the Windows 10 Tasks View or other applications. You can also customize the buttons depending on the application you are working with.

Surface Precision Mouse Bottom

By already having the perfect mouse, in terms of feeling, comfort, precision and customizability, you get a really cool extra feature. The Surface Precision Mouse gives you more multi-tasking power by allowing you to work seamlessly across up to three computers, supports both Bluetooth and wired USB connections. You can pair your Surface Precision Mouse with three different devices and you can manually switch between them with the button on the bottom of the mouse, or you can use something called Smart Switch.

Microsoft Surface Percision Mouse Smart Switch

Smart Switch on the Surface Precision Mouse can be enabled by using the Microsoft Mouse and Keyboard Center. It allows you to setup the workplace layout in the app and now you can move the cursor to the border of the screen and the mouse will seamlessly switch to the other device. So if you are working on your desktop and you have your notebook right next to it, you can easily move the mouse from one device to the other.

Overall I am super happy with the new device!

 

Tech Specs

The mouse also works with Windows 7, Windows 10, Windows 8.1 and macOS devices as long as they support Bluetooth 4.0 or higher.

 
Interface USB 2.1, Bluetooth® Low Energy 4.0/4.1/4.2 Dimensions 4.8 x 3.05 x 1.7 (122.6 mm x 77.6 mm x 43.3 mm)
Wireless Frequency 2.4GHz frequency range Weight 4.76 ounces (135 grams) including rechargeable batteries
Buttons 6 buttons, including right and left click and scroll wheel button Battery Rechargeable lithium ion battery (included)
Design Ergonomic design with side grips Battery Life Up to 3 months
Scrolling Smooth or magnetic detent customizable horizontal and vertical scrolling1 Color Gray


Windows Server Semi-annual Channel Overview

Windows Server – Semi-Annual Channel (SAC) vs Long-Term Servicing Channel (LTSC)

I was already blogging about the new Windows Server servicing options including the Long-Term Servicing Channel (LTSC) and the new Semi-Annual Channel (SAC) options. It seems that there is a lot of confusion about what the purpose and the advantages of the Semi-Annual Channel releases. With that blog post I will try to explain what both servicing options are and when which servicing option should be used. Especially since SAC releases, like Windows Server 1709, will only be available as Windows Server Core. Spoiler alert: Windows Server Semi-Annual Channel releases are not for everyone and everything.

Windows Server Long-Term Servicing Channel (LTSC)

The Long-term Servicing Channel is the release model you’re already familiar with (currently called the “Long-term Servicing Branch”) where a new major version of Windows Server is released every 2-3 years. Users are entitled to 5 years of mainstream support, 5 years of extended support, and optionally 6 more years with Premium Assurance. This channel is appropriate for systems that require a longer servicing option and functional stability. Deployments of Windows Server 2016 and earlier versions of Windows Server will not be affected by the new Semi-annual Channel releases. The Long-term Servicing Channel will continue to receive security and non-security updates, but it will not receive the new features and functionality.

Example for Long-Term Servicing Channel releases

  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016

Long-Term Servicing Channel installation options

  • Windows Server Core
  • Windows Server with Desktop Experience
  • Windows Server Core as a container Image

Use cases for Long-Term Servicing Channel releases

As use cases for the Long-Term Servicing Channel releases you can basically count everything in which need predictable long term support, do not support Windows Server Core and where you don’t use the new features included in the Semi-Annual Servicing Channel releases and you prefer less updating.

  • General Purpose File Server – Traditional information worker file server which need long term support
  • Legacy Software – Legacy software which do not support server core
  • Static Software – Software which does not leverage any of the new features of Semi-Annual Channel releases, which need predictable long term support
  • Legacy Hardware – End of life hardware
  • SQL Server – Traditional databases with long lifecycles which need predictable long term support
  • Active Directory and other infrastructure roles – which benefit from long term support

Semi-Annual Channel (SAC)

Windows Server 1709

The Semi-annual Channel releases will deliver new functionality for customers who are moving at a “cloud cadence,” such as those on rapid development cycles or service providers keeping up with the latest Hyper-V and Storage investments. Windows Server products in the Semi-annual Channel will have new releases available twice a year, in spring and fall. Each release in this channel will be supported for 18 months from the initial release.

Most of the features introduced in the Semi-annual Channel will be rolled up into the next Long-term Servicing Channel release of Windows Server. The editions, functionality, and supporting content might vary from release to release depending on customer feedback.

The Semi-annual Channel will be available to volume-licensed customers with Software Assurance, as well as via the Azure Marketplace or other cloud/hosting service providers and loyalty programs such as MSDN.

Example for Semi-annual Channel releases

  • Windows Server 2016 Nano Server
  • Windows Server 1709
  • Windows Server 1803

Semi-annual Channel installation options

  • Windows Server Core
  • Windows Server Core Container Image
  • Windows Server Nano Server Container Image

Use cases for Semi-annual Channel releases

Use cases for the Semi-annual Channel releases right now are application and services which leverage new feature very quickly and go with cloud cadence.

  • Lift and Shift applications into Containers
  • New cloud-based applications
  • Applications which can be quickly and easily redeployed
  • Linux containers on Windows Server
  • Hyper-V and Cluster nodes for Hyper-converged scenarios
  • Hyper-V hosts which are benefiting from continuous innovation

Semi-Annual Channel (SAC) vs Long-Term Servicing Channel (LTSC) Overview

To make it a little easier, here is a quick overview of the two servicing channels:

 Long-Term Servicing ChannelSemi-Annual Channel
Recommend ScenariosGeneral purpose File Servers, SQL Servers, Active Directory and other infrastructure rolesContainerized applications and container hosts, Hyper-converged hosts benefiting form faster innovation
New ReleasesEvery 2-3 yearsEvery 6 months
Support5 years of Mainstream support +5 years of Extended support18 months
EditionsAll available Windows Server editionsStandard and Datacenter
Installation OptionsServer Core and Server with Desktop ExperienceServer Core only
LicensingAll customer through all channelsSoftware Assurance and Cloud customers only

Conclusion

As you can see, Windows Server Semi-annual channel are not designed for everyone. And if you don’t feel comfortable with Windows Server Core (btw you should check out Microsoft Project Honolulu), the fast release cadence or the short support life cycle you should go with the Windows Server Long-Term Servicing Channel. You will not lose anything you had today, you still will get new versions every 2-3 years with all the options you had today. If you need the fast innovation and you get something out of the new features the Semi-annual channel will provide you with 2 releases a year. But make sure, that your deployment, configuration and management is automated, otherwise you will suffer from the fast release cadence. I have three other very important points I want to make sure you know about:

  • Not all your servers have to go with LTSC only or SAC only – as long as you have the right licensing in place you can choose for each server, which ever fits your needs best.
  • You don’t have to switch now – you can also decided to go with LTSC today and switch to a SAC release as soon as you benefit from it. You can also switch back to LTSC from SAC if you don’t like it. (With Switch I mean redeploy)
  • Upgrades are not in-place – It doesn’t matter which servicing channel you are using, servers need to be redeployed. (Not like in Windows 10 where you can leverage in-place upgrades)

I hope this helps to understand the point about Windows Server Semi-Annual Channel (SAC) vs Long-Term Servicing Channel (LTSC). The Semi-Annual Channel releases are a new offer from Microsoft for customers to get their hands on new features much quicker, this offers a huge benefit if you can make use of it. But Microsoft is not forcing you to use SAC, LTSC for some scenarios and customers is still the better option. So both solutions are having huge value in different scenarios.



Microsoft Azure Backup Agent

Download the Azure Backup Agent

Microsoft works heavily on their Microsoft Azure Recovery Services and releases new features for its Azure Backup software. Some of these new features need a new version of the Azure Backup Agent, or MARS Agent, to work.

Now if you install a new recovery vault in Azure to get started with Azure Backup you will find a link to download the Azure Backup Agent or sometimes you will see warnings in the Azure Backup MMC console with a link to a newer version of the Azure Backup Agent. But if you just want to download the latest MARS Agent, sometimes it is pretty hard to find, so let me help you with this link:

Download Azure Backup Agent

You can also use that file to updated an existing Azure Backup Agent.

By the way, Microsoft Azure Backup now supports Windows System State Backups to Azure.



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.



Docker for Windows Update Linux Containers

How to run Docker Linux Container on Windows 10 Fall Creator Update

I just blogged about how to run a Docker Linux Container natively on the new Windows Server version 1709. Docker today released a new update for Docker on Windows which also enables this scenario a little bit easier on your Windows 10 machine. It will ask you if you want to use the new feature to run Linux Containers natively on a Hyper-V Container running on Windows 10 (without the Moby VM).

As you can see the only thing right now you have to turn the feature on and off, since in this technical preview it is not yet possible to run Linux and Windows containers in parallel. But I guess soon that will be the case.

What you need is:

  • Windows 10 Fall Creators Update (Build 16299, Version 1709, RS3)
  • Docker for Windows 17.10.0-ce-win36 (13788) or higher

Enable Linux Containers on Windows

You can change the settings in the Docker Settings:

Docker for Windows Settings Enable Linux contianers on Windows

With hat setting on you can now run Linux Containers such as ubuntu on Windows directly, without having a Linux Virutal Machine running in the background to host the Linux containers.

Docker Run Ubuntu on Windows 10 Verions

Now you can also do some other fancy things like run the Azure CLI in a Linux Container on Windows 10.

Docker Azure CLI on Linux on Windows 10 Container

Simple and effective, and it will be even more powerful when you can run Linux and Windows Container in parallel on Windows Sever and on Windows 10.



How to run Docker Linux Container on Windows Server 1709

As mentioned Microsoft released the final version of Windows Server 1709 in the last week. Windows Server 1709 brings a couple of new improvements, especially in the container space. Microsoft and Docker are working on bringing Linux Container support to Windows Server, so you can now run Windows and Linux Container at the same time on a Windows Server Container Host running Windows Server 1709 or Windows 10 with the Fall Creators Update (1709).

In this post I want to show you how you setup up a Container Host to run Windows and Linux Containers at the same time using Docker.

Create Container Host Virtual Machine

Enable Nested Virtualization

If you run Docker on a physical server you can skip this step. If you want to run Docker Containers using Linux inside a Virtual Machine running on Hyper-V you should enable Nested Virtualization for the Container Host Virtual Machine. You can do this by running the following command:

if you want to do this on a Hyper-V Server in Azure, check out this post: How to setup Nested Virtualization in Microsoft Azure

Install Docker Enterprise Edition Preview on Windows Server 1709

First you have to install Docker Enterprise Edition Preview on your Windows Server 1709 container host. You can install the Docker EE preview using PowerShell package management, using the following commands:

As mentioned this is a preview version of Docker EE which enables a bunch of new features, to run Docker in production environments please use Docker EE 17.06.

Enable Docker Linux Containers on Windows

The preview Docker EE package includes a full LinuxKit system (13MB) for use when running Docker Linux containers. To enable this use the following command:

to disable it again use the following:

Run Linux Docker Container on Windows Server

Docker Ubuntu Container on Windows Server

Now you are able to run Linux Containers on Windows Server 1709.

for fun you can also run Nyancat!

Docker Nyan Cat on Windows Server

Things are still in preview, so don’t expect to work 100% 🙂