WSL Archives - Thomas Maurer

Last updated by Thomas Maurer at September 1, 2018.

Apr122018April 12, 2018August 21, 20182 Commentsby Thomas Maurer

Install Windows Subsystem for Linux on Windows Server

Posted in Cloud, Containers, Hyper-V, Microsoft, Virtualization, Windows, Windows 10, Windows Server, Windows Server 1709, Windows Server 1803, Work

In 2017 Microsoft made it possible to run different Linux distribution on Windows 10, using a feature called the “Windows Subsystem for Linux“. With the latest official Semi-Annual Channel Windows Server release called Windows Server, version 1709 Microsoft also allowed to run the Windows Subsystem for Linux (WSL) on Windows Server. With the next release of Windows Server called Windows Server, version 1803, Microsoft will also add some improvements to the Windows Subsystem on Linux, which also apply to Windows 10 as well as Windows Server. This blog post shows you how you can do this.

First you have a Windows Server, version 1709 running. After that enable the Microsoft Windows Subsystem for Linux feature, running the following command (This will need a reboot)

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

1	Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

You can download the appx packages for you favorite Linux distribution, this can be today:

Ubuntu
OpenSUSE
Suse Linux Enterprise Server

If you are running on Windows Server Core (which is highly likely), you can use the following command to download the Linux distributions.

# For Ubuntu 16.04

Invoke-WebRequest -Uri https://aka.ms/wsl-ubuntu-1604 -OutFile ~/Ubuntu.zip -UseBasicParsing

# For Ubuntu 18.04

Invoke-WebRequest -Uri https://aka.ms/wsl-ubuntu-1804 -OutFile ~/Ubuntu1804.zip -UseBasicParsing

# For OpenSUSE 42

Invoke-WebRequest -Uri https://aka.ms/wsl-opensuse-42 -OutFile ~/OpenSUSE.zip -UseBasicParsing

# For SLES 12

Invoke-WebRequest -Uri https://aka.ms/wsl-sles-12 -OutFile ~/SLES.zip -UseBasicParsing

# For Ubuntu 16.04

Invoke-WebRequest -Uri https://aka.ms/wsl-ubuntu-1604 -OutFile ~/Ubuntu.zip -UseBasicParsing

# For Ubuntu 18.04

Invoke-WebRequest -Uri https://aka.ms/wsl-ubuntu-1804 -OutFile ~/Ubuntu1804.zip -UseBasicParsing

# For OpenSUSE 42

Invoke-WebRequest -Uri https://aka.ms/wsl-opensuse-42 -OutFile ~/OpenSUSE.zip -UseBasicParsing

# For SLES 12

Invoke-WebRequest -Uri https://aka.ms/wsl-sles-12 -OutFile ~/SLES.zip -UseBasicParsing

You can then unpack the file:

Expand-Archive ~/Ubuntu.zip C:\Distros\Ubuntu

1	Expand-Archive ~/Ubuntu.zip C:\Distros\Ubuntu

Now you can open that folder and run the installer for example ubuntu.exe. The first time this will do the setup where you also define the UNIX username and password as well as the root password.

After that you can run updates for your distro and you can start using Linux.

If you want to know more about the WSL, check out the Microsoft Documentation: Windows Subsystem for Linux Documentation and have a look at my WSL post in for Windows 10: Crazy times – You can now run Linux on Windows 10 from the Windows Store

You can also find the other Linux distro packages here: WSL distro packages.

Apr032018April 3, 2018April 3, 20180 Commentby Thomas Maurer

HVC – SSH Direct for Linux VMs on Hyper-V

Posted in Cloud, Hyper-V, Microsoft, PowerShell, Virtualization, Windows, Windows 10, Windows Server, Windows Server 1803, Windows Server 2019, Work

If you are running Hyper-V on Windows 10 or on Windows Server 2016, you probably know about a feature called PowerShell Direct. I also mentioned that PowerShell Direct is one of the 10 hidden features in Hyper-V you should know about. PowerShell Direct lets you remote connect to a Windows Virtual Machine running on a Hyper-V host, without any network connection inside the VM. PowerShell Direct uses the Hyper-V VMBus to connect inside the Virtual Machine. Of course this feature is really handy if you need it for automation and configuration for Virtual Machines. As this is great for Windows virtual machines, it does not work with Virtual Machines running Linux. In the latest Windows 10, Windows Server 1803 (RS4) and Windows Server 2019 (RS5) Insider Preview builds, Microsoft enabled a tool called HVC. HVC is at tool which allows you to do some command line VM management. HVC SSH is basically SSH Direct of Linux VMs.

This allows to connect to a Linux VM using SSH over the Hyper-V VMBus. You are also able to copy file inside a virtual machines using scp.

How to connect to Linux VMs using SSH Direct

To connect to Linux VMs using SSH Direct (HVC) simply type hvc.exe into the command line or PowerShell. This will give you all the possible command options. Of course SSH has to big configured inside the Linux virtual machine.

hvc ssh Thomas@VMNAME

1	hvc ssh Thomas@VMNAME

To make this work, the SSH server inside the VM needs to be configured.

Final Thoughts

Pretty cool tool which will be available in the official releases of Windows 10 and Windows Server 1803, released this spring. Later this year this feature will also be included in Windows Server 2019. If you want to try it out today, give the Windows Insider Preview builds a spin.

Thanks to Ben Armstrong for pointing this out 😉

Jan302018January 30, 2018August 22, 20182 Commentsby Thomas Maurer

Setup an Azure Stack Cloud Operator and Developer Workstation Environment

Posted in Cloud, Containers, Hyper-V, Microsoft, Microsoft Azure, Microsoft Azure Stack, PowerShell, Windows, Windows 10, Windows Server, Work

If you are responsable to manage and operate Azure Stack, you will need to enable a couple of tools to manage Azure Stack. This post should give you a summary of what you should do to setup your Azure Stack Operator and Developer workstation environment.

Operating System

First of all you should setup a clean base system. I usually use the latest version of Windows 10, right now the latest Windows 10 version is the Fall Creators Update which give you some great features like the OpenSSH client or the Windows Subsystem for Linux build in, or I use Winodws Sevrer 2016 with Desktop Expierence. Make sure you install all the latest updates for Microsoft Update.

Install Visual Studio Code

Visual Studio Code is a new, free, lightweight cross-platform code editor for building modern web and cloud applications on Mac OS X, Linux and Windows. It is perfect for editing JSON files and even writing some code. And it has a built-in Terminal so you don’t have to switch between different windows.

I recommend you install the following Extensions:

code --install-extension ms-vscode.vscode-azureextensionpack
code --install-extension ms-vscode.powershell

code --list-extensions

code --install-extension ms-vscode.vscode-azureextensionpack

code --install-extension ms-vscode.powershell

code --list-extensions

Install SSH Client or Windows Subsystem for Linux (WSL)

To manage Linux Virtual Machines running on Azure Stack or if you need to manage the hardware switches in Azure Stack or your border switches where Azure Stack is connected, SSH is the way to access it. Windows 10 now comes with several builtin options like the OpenSSH Client which you can install as addtional feature or for example the Windows Subsystem for Linux (WSL) which allows you to run several linux tools on Windows directly. If you are using another version of Winodws, the thrid party application PuTTY is your friend.

You can also using PowerShell to install it:

Get-WindowsCapability -Online | ? Name -like 'OpenSSH*'

# Install the OpenSSH Client
Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0

# Install the OpenSSH Server
Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0

Get-WindowsCapability -Online | ? Name -like 'OpenSSH*'

# Install the OpenSSH Client

Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0

# Install the OpenSSH Server

Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0

Install Azure Stack PowerShell

Azure Stack compatible Azure PowerShell modules are required to work with Azure Stack. PowerShell commands for Azure Stack are installed through the PowerShell gallery, you can run the following commands to install it: (Make sure there are no other Azure PowerShell Modules installed, if there are, the commands will remove them). If you also install Visual Studio, install Visual Studio first before you install the Azure Stack PowerShell.

# Trust the PowerShell Gallery
Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted

# Remove Existing Azure PowerShell Modules
Get-Module -ListAvailable | where-Object {$_.Name -like “Azure*”} | Uninstall-Module

# Install the AzureRM.Bootstrapper module. Select Yes when prompted to install NuGet
Install-Module -Name AzureRm.BootStrapper

# Install and import the API Version Profile required by Azure Stack into the current PowerShell session.
Use-AzureRmProfile -Profile 2017-03-09-profile -Force

#Install Azure Stack Module
Install-Module -Name AzureStack -RequiredVersion 1.2.11

# Verify Installation
Get-Module -ListAvailable | where-Object {$_.Name -like "Azure*"}

# Trust the PowerShell Gallery

Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted

# Remove Existing Azure PowerShell Modules

Get-Module -ListAvailable | where-Object {$_.Name -like “Azure*”} | Uninstall-Module

# Install the AzureRM.Bootstrapper module. Select Yes when prompted to install NuGet

Install-Module -Name AzureRm.BootStrapper

# Install and import the API Version Profile required by Azure Stack into the current PowerShell session.

Use-AzureRmProfile -Profile 2017-03-09-profile -Force

#Install Azure Stack Module

Install-Module -Name AzureStack -RequiredVersion 1.2.11

# Verify Installation

Get-Module -ListAvailable | where-Object {$_.Name -like "Azure*"}

If you need to install it on a machine which does not have access to the internet. check outthe offical Microsoft page: Install PowerShell for Azure Stack

Install Azure Stack tools

AzureStack-Tools is a GitHub repository that hosts PowerShell modules that you can use to manage and deploy resources to Azure Stack. This brings you several functionalities for Azure Stack management:

Deployment of Azure Stack – Helps prepare for Azure Stack deployment.
Resource Manager policy for Azure Stack – Constrains Azure subscription to the capabilities available in the Azure Stack.
Connecting to Azure Stack – Connect to an Azure Stack instance from your personal computer/laptop.
Setting up Identity for Azure Stack – Create and manage identity related objects and configurations for Azure Stack
Azure Stack Service Administration – Manage plans and subscriptions in Azure Stack.
Azure Stack Compute Administration – Manage compute (VM) service in Azure Stack.
AzureRM Template validator – Validate Azure ARM Template Capabilities
Azure Stack Infrastructure Administration – Manage Azure Stack Infrastructure

You can get the Azure Stack tools from GitHub:

# Change directory to the root directory
cd \

# Download the tools archive
Invoke-WebRequest https://github.com/Azure/AzureStack-Tools/archive/master.zip -OutFile master.zip

# Expand the downloaded files
Expand-Archive master.zip -DestinationPath . -Force

# Change to the tools directory
cd AzureStack-Tools-master

# Change directory to the root directory

cd \

# Download the tools archive

Invoke-WebRequest https://github.com/Azure/AzureStack-Tools/archive/master.zip -OutFile master.zip

# Expand the downloaded files

Expand-Archive master.zip -DestinationPath . -Force

# Change to the tools directory

cd AzureStack-Tools-master

You can directly open that folder in Visual Studio Code:

code C:\AzureStack-Tools-master

1	code C:\AzureStack-Tools-master

Configure Azure Stack PowerShell environment

As an Azure Stack user, you can configure your Azure Stack PowerShell environment. After you configure, you can use PowerShell to manage Azure Stack resources such as subscribe to offers, create virtual machines, deploy Azure Resource Manager templates, etc.

For an Azure Stack deployment which is using Azure Active Directory (AAD) as an Identity provider, you can use the following commands:

# Navigate to the downloaded folder and import the **Connect** PowerShell module
Set-ExecutionPolicy RemoteSigned
Import-Module .\Connect\AzureStack.Connect.psm1

# For Azure Stack development kit, this value is set to https://management.local.azurestack.external. For a real Azure Stack solution this will be https://maangement.-region-.-fqdn-
$ArmEndpoint = "&lt;Resource Manager endpoint for your environment&gt;"

# For Azure Stack development kit, this value is set to https://graph.windows.net/.
$GraphAudience = "&lt;GraphAudience endpoint for your environment&gt;"

# Register an AzureRM environment that targets your Azure Stack instance
Add-AzureRMEnvironment `
-Name "AzureStackUser" `
-ArmEndpoint $ArmEndpoint

# Set the GraphEndpointResourceId value
Set-AzureRmEnvironment `
-Name "AzureStackUser" `
-GraphAudience $GraphAudience

# Get the Active Directory tenantId that is used to deploy Azure Stack
$TenantID = Get-AzsDirectoryTenantId `
-AADTenantName "&lt;myDirectoryTenantName&gt;.onmicrosoft.com" `
-EnvironmentName "AzureStackUser"

# Sign in to your environment
Login-AzureRmAccount `
-EnvironmentName "AzureStackUser" `
-TenantId $TenantID

# Navigate to the downloaded folder and import the **Connect** PowerShell module

Set-ExecutionPolicy RemoteSigned

Import-Module .\Connect\AzureStack.Connect.psm1

# For Azure Stack development kit, this value is set to https://management.local.azurestack.external. For a real Azure Stack solution this will be https://maangement.-region-.-fqdn-

$ArmEndpoint = "<Resource Manager endpoint for your environment>"

# For Azure Stack development kit, this value is set to https://graph.windows.net/.

$GraphAudience = "<GraphAudience endpoint for your environment>"

# Register an AzureRM environment that targets your Azure Stack instance

Add-AzureRMEnvironment `

-Name "AzureStackUser" `

-ArmEndpoint $ArmEndpoint

# Set the GraphEndpointResourceId value

Set-AzureRmEnvironment `

-Name "AzureStackUser" `

-GraphAudience $GraphAudience

# Get the Active Directory tenantId that is used to deploy Azure Stack

$TenantID = Get-AzsDirectoryTenantId `

-AADTenantName "<myDirectoryTenantName>.onmicrosoft.com" `

-EnvironmentName "AzureStackUser"

# Sign in to your environment

-EnvironmentName "AzureStackUser" `

-TenantId $TenantID

Install and configure CLI for use with Azure Stack

You can also use the Azure CLI 2.0 to manage Azure Stack.

Install Azure CLI on Windows using MSI

To install the CLI on Windows and use it in the Windows command-line, download and run the Azure CLI Installer (MSI).

Install with apt-get for Bash on Ubuntu on Windows (WSL)

Open the Bash shell.
Modify your sources list.

echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ wheezy main" | \ sudo tee /etc/apt/sources.list.d/azure-cli.list

1
2

echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ wheezy main" | \
sudo tee /etc/apt/sources.list.d/azure-cli.list

Run the following sudo commands:

sudo apt-key adv --keyserver packages.microsoft.com --recv-keys 52E16F86FEE04B979B07E28DB02C46DF417A0893
sudo apt-get install apt-transport-https
sudo apt-get update &amp;&amp; sudo apt-get install azure-cli

sudo apt-key adv --keyserver packages.microsoft.com --recv-keys 52E16F86FEE04B979B07E28DB02C46DF417A0893

sudo apt-get install apt-transport-https

sudo apt-get update && sudo apt-get install azure-cli

Run the CLI from the command prompt with the az command.

Connect to Azure Stack using the Azure CLI

If you are using Public Certificates for your Azure Stack, this is pretty staight forward, if you are using the Azure Stack Development Kit or an Internal CA, make sure your client trusts the Azure Stack CA root Certificate. You can find more here: Install and configure CLI for use with Azure Stack

Register as a cloud administrative environement:

To register the cloud administrative environment, use:

az cloud register \
-n AzureStackAdmin \
--endpoint-resource-manager "https://adminmanagement.-region-.FQDN-" \
--suffix-storage-endpoint "-region-.FQDN-" \
--suffix-keyvault-dns ".adminvault.-region-.FQDN-" \
--endpoint-active-directory-graph-resource-id "https://graph.windows.net/" \
--endpoint-vm-image-alias-doc &lt;URI of the document which contains virtual machine image aliases&gt;

az cloud register \

-n AzureStackAdmin \

--endpoint-resource-manager "https://adminmanagement.-region-.FQDN-" \

--suffix-storage-endpoint "-region-.FQDN-" \

--suffix-keyvault-dns ".adminvault.-region-.FQDN-" \

--endpoint-active-directory-graph-resource-id "https://graph.windows.net/" \

--endpoint-vm-image-alias-doc <URI of the document which contains virtual machine image aliases>

Set the active environment by using the following commands.

az cloud set \ -n AzureStackAdmin

1
2

az cloud set \
-n AzureStackAdmin
Update your environment configuration to use the Azure Stack specific API version profile. To update the configuration, run the following command:

az cloud update \ --profile 2017-03-09-profile

1
2

az cloud update \
--profile 2017-03-09-profile

Sign in to your Azure Stack environment by using the az login command. You can sign in to the Azure Stack environment either as a user or as a service principal.

az login \
-u &lt;Active directory global administrator or user account. For example: username@&lt;aadtenant&gt;.onmicrosoft.com&gt; \
--tenant &lt;Azure Active Directory Tenant name. For example: myazurestack.onmicrosoft.com&gt;

az login \

-u <Active directory global administrator or user account. For example: username@<aadtenant>.onmicrosoft.com> \

--tenant <Azure Active Directory Tenant name. For example: myazurestack.onmicrosoft.com>

Register the user environment, use:

To register the user environment, use:

az cloud register \
-n AzureStackUser \
--endpoint-resource-manager "https://management.local.azurestack.external" \
--suffix-storage-endpoint "local.azurestack.external" \
--suffix-keyvault-dns ".vault.local.azurestack.external" \
--endpoint-active-directory-graph-resource-id "https://graph.windows.net/" \
--endpoint-vm-image-alias-doc &lt;URI of the document which contains virtual machine image aliases&gt;

az cloud register \

-n AzureStackUser \

--endpoint-resource-manager "https://management.local.azurestack.external" \

--suffix-storage-endpoint "local.azurestack.external" \

--suffix-keyvault-dns ".vault.local.azurestack.external" \

--endpoint-active-directory-graph-resource-id "https://graph.windows.net/" \

--endpoint-vm-image-alias-doc <URI of the document which contains virtual machine image aliases>

Set the active environment by using the following commands.

az cloud set \ -n AzureStackUser

1
2

az cloud set \
-n AzureStackUser
Update your environment configuration to use the Azure Stack specific API version profile. To update the configuration, run the following command:

az cloud update \ --profile 2017-03-09-profile

1
2

az cloud update \
--profile 2017-03-09-profile

Sign in to your Azure Stack environment by using the az login command. You can sign in to the Azure Stack environment either as a user or as a service principal.

az login \
-u &lt;Active directory global administrator or user account. For example: username@&lt;aadtenant&gt;.onmicrosoft.com&gt; \
--tenant &lt;Azure Active Directory Tenant name. For example: myazurestack.onmicrosoft.com&gt;

az login \

-u <Active directory global administrator or user account. For example: username@<aadtenant>.onmicrosoft.com> \

--tenant <Azure Active Directory Tenant name. For example: myazurestack.onmicrosoft.com>

Install the Microsoft Azure Storage Explorer

To access and manage Azure Stack Storage Accounts you can also use the Microsoft Azure Storage Explorer tool. Microsoft Azure Storage Explorer (Preview) is a standalone app from Microsoft that allows you to easily work with Azure Storage data on Windows, macOS and Linux.

If you are running the Azure Stack Development Kit, you should again have a look how you get the certificates implace, you can find that here: Connect Storage Explorer to an Azure Stack subscription

Install the Microsoft Azure Storage Explorer
After Storage Explorer restarts, select the Edit menu, and then ensure that Target Azure Stack is selected. If it is not selected, select it, and then restart Storage Explorer for the change to take effect. This configuration is required for compatibility with your Azure Stack environment.
To connect to the Azure Stack account, select Add an account.
In the Connect to Azure Storage dialog box, under Azure environment, select Use Azure Stack Environment, and then click Next.
To sign in with the Azure Stack account that’s associated with at least one active Azure Stack subscription, fill in the Sign in to Azure Stack Environment dialog box.
The details for each field are as follows:Environment name: The field can be customized by user.
ARM resource endpoint: The samples of Azure Resource Manager resource endpoints:For cloud operator:
https://adminmanagement.-region-.-FQDN-
For tenant:
https://management.-region-.-FQDN-
Tenant Id: Optional. The value is given only when the directory must be specified.

This should help you quickly setup an Azure Stack Cloud Operator Workstation. What other tools do you need to manage and operator your Azure Stack? leave a comment.

Oct182017October 18, 2017August 27, 20180 Commentby Thomas Maurer

Microsoft released Windows Server 1709

Posted in Cloud, Containers, Hyper-V, Microsoft, Microsoft Azure, Microsoft Azure Stack, PowerShell, Private Cloud, Server Core, Virtualization, Web, Windows, Windows Server, Windows Server 1709, Windows Server 2016, Work

Microsoft just released the new Windows Server version 1709 which is the first release in the Semi-Annual Channel. The Semi-Annual Channel release cadence to deliver innovation at a faster pace, but you will also need to keep updating your systems to newer versions of Windows Server. As of today, you can download Windows Server 1709 from the Volume license portal or deploy it in Microsoft Azure, since it is available in the Azure Marketplace.

Windows Server 1709 Features and Improvements

Windows Server 1709 will drive innovation in the container space and in the Windows Subsystem for Linux, as well as some Cloud Host improvements in Hyper-V with new support for Storage Class Memory and more. Windows Server 1709 will be only available as Windows Server Core (Standard and Datacenter).

If you want to know more about the new features and improvements in Windows Server 1709, check out my blog post and check also out the Microsoft What’s new in Windows Server 1709 page.

Windows Server news from Microsoft Build 2017 – It is all about Container!

New Windows Server Management Experience

If you want to know more about the new Management Experience called Project Honolulu, check out my blog post:

Microsoft Project Honolulu – The new Windows Server Management Experience

Windows Server Servicing

For more information about the Semi-Annual Channel and Windows Server Servicing check out my blog posts:

Windows Server release information – Windows Server Semi-Annual Channel and LTSC

What is next for Windows Server and System Center with a faster release cadence

Windows Server, version 1709 is only the first step in this new world of faster release cadences. The most important aspect of having new releases twice a year is customer feedback will shape the product. You can try the preview builds of Windows Server in the Semi-Annual Channel and provide feedback by joining the Windows Insiders program. You can also join the conversation in the Microsoft Tech Community where we have tons of professionals and experts sharing their learnings and answering questions.

Jul112017July 11, 2017September 1, 20181 Commentby Thomas Maurer

Crazy times – You can now run Linux on Windows 10 from the Windows Store

Posted in Cloud, Containers, Hyper-V, Microsoft, PowerShell, Virtualization, Web, Windows, Windows 10, Windows Server, Work

In the past weeks some really crazy things are happening. Think you’re way back in the time of 2003, could you have ever imagined that Microsoft offers you to run Linux on Windows 10? Well this is exactly what is happening in the past months.

With one of the Windows 10 releases Microsoft added the Windows Subsystem for Linux, which basically allowed you to run a Ubuntu version on your Windows 10 devices. In the past few days and weeks Microsoft now announced that you can now download and install SUSE Enterprise Server, openSUSE Leap and Ubuntu (my guess there will be more to come) from the Windows Store. All you need today is the latest Windows Insider Build 16237 (it also works with a couple of older insider builds), and you will be able to install these versions. For the mainstream, this will be available in the Windows 10 Fall Creators Update arriving in the Fall of 2017. The Windows Subsystem for Linux will also be part in the next Windows Server RS3 release.

If you want to know more about how it works check out Scott Hanselman blog about Ubuntu now in the Windows Store: Updates to Linux on Windows 10 and Important Tips

One great thing, Scott describes in his blog, if you want to configure the different Windows Subsystems for Linux and for example configure the default one, you can use the command line with the wslconfig utility.

wslconfig

#Set default distribution to Ubuntu

wslconfig /s Ubuntu

wslconfig

#Set default distribution to Ubuntu

wslconfig /s Ubuntu

Tag: WSL

Install Windows Subsystem for Linux on Windows Server

HVC – SSH Direct for Linux VMs on Hyper-V

How to connect to Linux VMs using SSH Direct

Final Thoughts

Microsoft released Windows Server 1709

Windows Server 1709 Features and Improvements

New Windows Server Management Experience

Windows Server Servicing

Crazy times – You can now run Linux on Windows 10 from the Windows Store

Follow Me

About

Sponsor

Sponsor

Sponsor

Sponsor