Tag: Server

Last updated by Thomas Maurer at August 18, 2018.

Mar022018March 2, 2018March 2, 20180 Commentby Thomas Maurer

Azure Stack Capacity Calculator Tool

Posted in Cloud, Hardware, HP, Microsoft, Microsoft Azure, Microsoft Azure Stack

One of the most common questions I get when a customer decided to buy Azure Stack is, how you can calculate the sizing of your Azure Stack. He also wants to know how larger the server should be for his workloads and which Azure Stack Hardware SKU he should go for. Microsoft just released the Azure Stack Capacity Calculator (Version 1801.01). This tool will assists customers in the pre-purchase capacity planning of the Azure Stack hardware configuration. This helps you decided on how large your Azure Stack solution should be configured. This sizes server configuration and amount of servers you need to run your workloads on a Azure Stack integrated system. This also helps you in your Azure Stack Pricing Calculation.

The Azure Stack capacity planner is intended to assist in pre-purchase planning to determine appropriate capacity and configuration of Azure Stack hardware solutions.
The Azure Stack capacity planner helps you make informed decisions with respect to planning capacity in two ways: either the by selecting a hardware offering and attempting to fit a combination of resources or by defining the workload that Azure Stack is intended to run to view the available hardware SKUs that can support it. Finally, the spreadsheet is intended as a guide to help in making decisions related to Azure Stack planning and configuration.
The spreadsheet is not intended to serve as a substitute for your own investigation and analysis. Microsoft makes no representations or warranties, express or implied, with respect to the information provided within the spreadsheet.

Azure Stack Capacity Planner

You can download the Azure Stack Capacity Planner from the TechNet Gallery. It is a simple to use Microsoft Excel file, where you enter your workload data. I will out put some information about the configuration you need and even allows you to compare different hardware SKUs. It will also indicate which one will be the best solution for you.

Download Azure Stack Capacity Calculator: TechNet Gallery Azure Stack Capacity Planner (Version 1801.01)

Oct172016October 17, 2016October 17, 20161 Commentby Thomas Maurer

How to create a Nano Server Image using PowerShell

Posted in Cloud, Containers, Hyper-V, Microsoft, Nano Server, PowerShell, Private Cloud, Virtualization, Windows, Windows Server, Windows Server 2016, Work

Last week Microsoft released Windows Server 2016 with the first GA release of Nano Server. A couple of months back I already wrote a blog post how you can create a new Nano Server Image in Technical Preview 4. This post is an updated version of that this post using Windows Server 2016 GA. In this post I will quickly show you how you can create a new VHD, VHDX or WIM file with your Nano Server configuration.

This is the PowerShell option, you can also use the Nano Server Image Builder.

First you have to download the latest Windows Server 2016 ISO file.

If you open the Windows Server 2016 ISO file you can see a folder called “NanoServer” on the medium. This folder includes:

NanoServer.wim – This is the Nano Server Image file
Packages – The Package folder includes the Nano Server Packages, Windows Roles and Features and some basic drivers
NanoServerImageGenerator – In this folder you can find the Nano Server Image Generator PowerShell Module

I usually create a folder on my C:\NanoServer to store all the things I need, which makes things a little simpler.

Base – This is a temporary folder where the images get mounted while updating or creating new images
Drivers – This is the folder where I copy all the drivers for a physical image
Files – This is the unpacked Windows Server 2016 ISO image (including, the sources folder, NanoServer folder, support, boot and efi folder as well as the setup.exe file)
Images – In this folder I store all the new created images
Updates – In this folder I store the Windows Server 2016 Update cumulative updates (.cab files)
XMLs – In this folder I store unattend.xml files if I need to do a extended configuration.

Of course you don’t have to use this folder structure, but it makes things easier.

If you have a look at the Packages folder you can find all the available packages for Nano Server:

A new Nano Server Image can be created using the New-NanoServerImage PowerShell cmdlet. This will create a new Nano Server Image in a VHDX including the VM Guest drivers and nothing more.

# Change Working Directory
cd C:\NanoServer

# Import Module
Import-Module .\NanoServerImageGenerator.psm1

# Create Nano Server Image VHDX
New-NanoServerImage -MediaPath .\Files -BasePath .\Base -TargetPath .\Images\NanoVMGA.vhdx -MaxSize 20GB -DeploymentType Guest -Edition Datacenter -ComputerName "Nano01"

# Change Working Directory

cd C:\NanoServer

# Import Module

Import-Module .\NanoServerImageGenerator.psm1

# Create Nano Server Image VHDX

New-NanoServerImage -MediaPath .\Files -BasePath .\Base -TargetPath .\Images\NanoVMGA.vhdx -MaxSize 20GB -DeploymentType Guest -Edition Datacenter -ComputerName "Nano01"

MediaPath – The location with the Windows Server 2016 files
BasePath – Temporary folder to mount the WIM file
TargetPath – Where the new Image file gets stored. You can create a .wim, .vhd or .vhdx file
- .vhd creates a Image for a Generation 1 VM (BIOS boot)
- .vhdx create a Image for a Generation 2 VM (UEFI boot)
DeploymentType allows you to choose between Guest and Host
- Guest creates a Virtual Machine
- Host creates a Physical Image
Edition can be Standard or Datacenter
ComputerName adds the server name of the Nano Server
MaxSize changes the Partition size, if you are not using this parameter it will create a default partition of 4GB

You can now copy the VHDX file from the Images folder, attach this to a new Hyper-V virtual machine and boot.

This will show the Nano Server recovery console:

There are more parameters to add roles and features, updates, drivers and additional configuration like IP addresses and more

For example if you want to add some updates to the Nano Server Image you can use the following cmdlet:

# Create Nano Server Image VHD with updates
New-NanoServerImage -MediaPath .\Files -BasePath .\Base -TargetPath .\Images\NanoVM.vhd -MaxSize 20GB -DeploymentType Guest -Edition Datacenter -ComputerName "Nano01" -ServicingPackagePath ".\Updates\Windows10.0-KB3176936-x64.cab", ".\Updates\Windows10.0-KB3176936-x64.cab"

# Create Nano Server Image VHD with updates

New-NanoServerImage -MediaPath .\Files -BasePath .\Base -TargetPath .\Images\NanoVM.vhd -MaxSize 20GB -DeploymentType Guest -Edition Datacenter -ComputerName "Nano01" -ServicingPackagePath ".\Updates\Windows10.0-KB3176936-x64.cab", ".\Updates\Windows10.0-KB3176936-x64.cab"

To add a fixed IP address you can for example use the following cmdlet:

# Create Nano Server with IP address
New-NanoServerImage -MediaPath .\Files -BasePath .\Base -TargetPath .\Images\NanoVMSetupUI.vhdx -MaxSize 20GB -DeploymentType Guest -Edition Datacenter -ComputerName "Nano01" -Ipv4Address "172.21.22.101" -Ipv4SubnetMask "255.255.255.0" -Ipv4Gateway "172.21.22.1" -Ipv4Dns "8.8.8.8"

# Create Nano Server with IP address

New-NanoServerImage -MediaPath .\Files -BasePath .\Base -TargetPath .\Images\NanoVMSetupUI.vhdx -MaxSize 20GB -DeploymentType Guest -Edition Datacenter -ComputerName "Nano01" -Ipv4Address "172.21.22.101" -Ipv4SubnetMask "255.255.255.0" -Ipv4Gateway "172.21.22.1" -Ipv4Dns "8.8.8.8"

If you have some advanced deployment you can use for example the following thing, which helps you to set different configuration options. This example here is designed for a physical Hyper-V host

# Nano Server Packages for Image
$NanoPackages = "Microsoft-NanoServer-Compute-Package",
"Microsoft-NanoServer-DCB-Package",
"Microsoft-NanoServer-DSC-Package",
"Microsoft-NanoServer-FailoverCluster-Package",
"Microsoft-NanoServer-OEM-Drivers-Package",
"Microsoft-NanoServer-Storage-Package"

$ServicingPackagePath = ".\Updates\Windows10.0-KB3176936-x64.cab", ".\Updates\Windows10.0-KB3176936-x64.cab"

$UnattanedXML = ".\XMLs\unattend.xml"

$MaxSize = 20GB

$Edition = "Datacenter"

$VHDXName = ".\Images\NanoHost01.vhdx"

$DeploymentType = "Host"

$DriverPath = ".\Drivers"

$MediaPath = ".\Files"

$BasePath = ".\Base"

$ComputerName = "Nano01"
$DomainName = "thomasmaurer.ch"

#IP Configuration if not DHCP
#$Ipv4Address = "172.21.22.101"
#$Ipv4SubnetMask = "255.255.255.0"
#$Ipv4Gateway = "172.21.22.1"
#$Ipv4Dns = "8.8.8.8"
# Nano Image
New-NanoServerImage -MediaPath $MediaPath -BasePath $BasePath -TargetPath $VHDXName -DriversPath $DriverPath -DeploymentType $DeploymentType -Edition $Edition -Packages $NanoPackages -MaxSize $MaxSize -ServicingPackagePath $ServicingPackagePath -UnattendPath $UnattanedXML -ComputerName $ComputerName -DomainName $DomainName

# Nano Server Packages for Image

$NanoPackages = "Microsoft-NanoServer-Compute-Package",

"Microsoft-NanoServer-DCB-Package",

"Microsoft-NanoServer-DSC-Package",

"Microsoft-NanoServer-FailoverCluster-Package",

"Microsoft-NanoServer-OEM-Drivers-Package",

"Microsoft-NanoServer-Storage-Package"

$ServicingPackagePath = ".\Updates\Windows10.0-KB3176936-x64.cab", ".\Updates\Windows10.0-KB3176936-x64.cab"

$UnattanedXML = ".\XMLs\unattend.xml"

$MaxSize = 20GB

$Edition = "Datacenter"

$VHDXName = ".\Images\NanoHost01.vhdx"

$DeploymentType = "Host"

$DriverPath = ".\Drivers"

$MediaPath = ".\Files"

$BasePath = ".\Base"

$ComputerName = "Nano01"

$DomainName = "thomasmaurer.ch"

#IP Configuration if not DHCP

#$Ipv4Address = "172.21.22.101"

#$Ipv4SubnetMask = "255.255.255.0"

#$Ipv4Gateway = "172.21.22.1"

#$Ipv4Dns = "8.8.8.8"

# Nano Image

New-NanoServerImage -MediaPath $MediaPath -BasePath $BasePath -TargetPath $VHDXName -DriversPath $DriverPath -DeploymentType $DeploymentType -Edition $Edition -Packages $NanoPackages -MaxSize $MaxSize -ServicingPackagePath $ServicingPackagePath -UnattendPath $UnattanedXML -ComputerName $ComputerName -DomainName $DomainName

You can for example use this VHDX file now to create a boot from VHDX scenario:

# Boot from VHDX
Mount-VHD C:\VHDX\NanoHost01.vhdx -Passthru | get-disk | Get-Partition | where Size -GE 3GB | Set-Partition -NewDriveLetter V

# Set Boot Partition
cd v:\windows\system32
bcdboot v:\windows

# Unmounted
Get-VHD C:\VHDX\NanoHost01.vhdx | Dismount-VHD

# Boot from VHDX

Mount-VHD C:\VHDX\NanoHost01.vhdx -Passthru | get-disk | Get-Partition | where Size -GE 3GB | Set-Partition -NewDriveLetter V

# Set Boot Partition

cd v:\windows\system32

bcdboot v:\windows

# Unmounted

Get-VHD C:\VHDX\NanoHost01.vhdx | Dismount-VHD

I hope this helps you to get started with Nano Server in Windows Server 2016. I also prepared a blog post how you can create a Nano Server Image using the Nano Server Image Builder tool.

Aug092016August 9, 2016August 9, 20160 Commentby Thomas Maurer

Microsoft a leader in Gartner x86 Server Virtualization Infrastructure 2016 Magic Quadrant

Posted in Cloud, Containers, Hyper-V, Microsoft, Microsoft Azure, Nano Server, Private Cloud, Server Core, System Center, Virtualization, VMware, Web, Windows, Windows 10, Windows Server, Windows Server 2012 R2, Windows Server 2016, Work

Year over year Microsoft is named as a leader in the Gartner x86 Server Virtualization Infrastructure Magic Quadrant and it gets closer and closer to VMware. Microsoft now is named again as a leader in Gartner x86 Server Virtualization Infrastructure 2016 Magic Quadrant. Especially the integration with System Center and Microsoft Azure as well as the new security features in Windows Server 2016 Hyper-V, makes Hyper-V a strong player in the hypervisor space. Check out the Microsoft Blog post for more information or my blog post about What’s new in Windows Server 2016 Hyper-V.

Gartner published the Gartner x86 Server Virtualization Infrastructure MQ with Microsoft landing in the Leader Quadrant for the sixth year in a row. Microsoft moved up in the ‘ability to execute’ and to the right in the ‘completeness of vision’ assessment compared with 2015. Gartner defines leaders as having a clear strategy and roadmap for offerings, understanding virtualization’s role in infrastructure and operations transformation, and having a clear vision with respect to private cloud, hybrid cloud and public cloud computing.

Microsoft offers you to have a look at the Gartner Document here:

Download the Gartner x86 Server Virtualization Infrastructure 2016 Magic Quadrant

Dec012015December 1, 2015December 1, 20152 Commentsby Thomas Maurer

How to create a Nano Server Image

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

Last week Microsoft released Windows Server 2016 Technical Preview 4, which includes a lot of changes and fixes. Since I had some presentations on Nano Server in the past weeks I will quickly cover how you can create a Nano Server VHD or VHDX file.

If you download the ISO with Windows Server 2016 ISO you and mount this file you can see a folder called Nano Server. In this folder you can find the NanoServer.wim file and some PowerShell scripts as well as a folder called Packages, which includes the features, roles, driver and agents for Nano Server.

I usually copy all the PowerShell scripts (and the new module) to C:\NanoServer, even if you don’t have to, but it makes it easier for me.

If you have a look at the Packages folder you can find all the available packages for Nano Server:

Now to create a new Nano Server VHD file you can use the following steps:

First go to the directory where you stored the PowerShell files, for me this would be C:\NanoServer

Import the PowerShell Module and use the command to create a new Nano Server Image

# Change Working Directory
cd C:\NanoServer

# Import Module
Import-Module .\NanoServerImageGenerator.psm1

# Create new Nano Server Image
New-NanoServerImage -MediaPath D:\ -BasePath .\Base -TargetPath '.\NanoImage\NanoVM.vhd' -GuestDrivers -EnableRemoteManagementPort

# Change Working Directory

cd C:\NanoServer

# Import Module

Import-Module .\NanoServerImageGenerator.psm1

# Create new Nano Server Image

New-NanoServerImage -MediaPath D:\ -BasePath .\Base -TargetPath '.\NanoImage\NanoVM.vhd' -GuestDrivers -EnableRemoteManagementPort

This will create a new Nano Server Image including the VM Guest drivers and nothing more. The D:\ drive still is the Windows Server Image (ISO), the Base folder is used to mount and create the temporary files and the TargetPath is where you can find the finished VHDX file. You can now create a new Virtual Machine using this VHD file.

Of course you can also create Nano Server including other roles:

Nano Server Container Host:

# Create new Nano Server Image
New-NanoServerImage -MediaPath D:\ -BasePath .\Base -TargetPath '.\NanoImage\NanoConHost.vhd' -EnableRemoteManagementPort -GuestDrivers  -ComputerName NanoConHost -Containers -Compute -MaxSize 60GB -ReverseForwarders

1 2	# Create new Nano Server Image New-NanoServerImage -MediaPath D:\ -BasePath .\Base -TargetPath '.\NanoImage\NanoConHost.vhd' -EnableRemoteManagementPort -GuestDrivers -ComputerName NanoConHost -Containers -Compute -MaxSize 60GB -ReverseForwarders

Nano Server for Apps and using a fix IP Address and Computername

# Set IP of Nano Server
$ip = "172.91.91.12"
# Create Nano Server Image
New-NanoServerImage -MediaPath D:\ -BasePath .\Base -TargetPath '.\NanoImage\NanoDev.vhd' -GuestDrivers -EnableRemoteManagementPort -ReverseForwarders -Ipv4Address $ip -Ipv4SubnetMask 255.255.255.0 -ComputerName NanoDev -InterfaceNameOrIndex Ethernet

# Set IP of Nano Server

$ip = "172.91.91.12"

# Create Nano Server Image

New-NanoServerImage -MediaPath D:\ -BasePath .\Base -TargetPath '.\NanoImage\NanoDev.vhd' -GuestDrivers -EnableRemoteManagementPort -ReverseForwarders -Ipv4Address $ip -Ipv4SubnetMask 255.255.255.0 -ComputerName NanoDev -InterfaceNameOrIndex Ethernet

If you want to try Nano Server running in Microsoft Azure, you can also do this:

May242015May 24, 2015May 24, 20150 Commentby Thomas Maurer

Cisco UCS C200 M2 with Windows Server 2008 R2 and Windows Server 8 #HyperV

Cisco UCS and Hyper-V Enable Stateless Offloads with NVGRE

Posted in Cisco, Cloud, Hyper-V, Microsoft, Network, Private Cloud, Server, System Center, UCS, Virtualization, Windows Server, Windows Server 2012, Windows Server 2012 R2, Work

As I already mentioned I did several Hyper-V and Microsoft Windows Server projects with Cisco UCS. With Cisco UCS you can now configure stateless offloads for NVGRE traffic which is needed for Hyper-V Network Virtualization.

Cisco UCS Manager supports stateless offloads with NVGRE only with Cisco UCS VIC 1340 and/or Cisco UCS VIC 1380 adapters that are installed on servers running Windows Server 2012 R2 operating systems.

To use this you have to create Ethernet Adapter Policy, and set the Configuring an Ethernet Adapter Policy to Enable Stateless Offloads with NVGREin the Resources area:

Transmit Queues = 1
Receive Queues = n (up to 8)
Completion Queues = # of Transmit Queues + # of Receive Queues
Interrupts = # Completion Queues + 2

And in the Option area set the following settings:

Network Virtualization using Generic Routing Encapsulation = Enabled

Interrupt Mode = Msi-X

Make also sure you have installed eNIC driver Version 3.0.0.8 or later.

For more information, see http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/vic_drivers/install/Windows/b_Cisco_VIC_Drivers_for_Windows_Installation_Guide.html.

Jan112014January 11, 2014January 11, 20142 Commentsby Thomas Maurer

Enable SSH on VMware ESXi 5.5

Posted in Virtualization, VMware, Web, Work

I already wrote how you can enable SSH on a VMware ESXi 5.1, VMware ESXi 5.0 and VMware ESXi 4.1. This little guide shows you how you can enable on a VMware vSphere ESXi 5.5 box. As before for the other version it is pretty easy. This allows you to remote troubleshoot your VMware ESXi host and also coping files on your server.

On the start screen press F2 to “Customize System” and login with your administrator or root account.

After the login select Troubleshooting Options on the System Customization page.

Now you can enable SSH on your ESXi 5.5 server, and you can connect via your favorite SSH client.

If you want to enable SSH on your VMware ESXi host directly from the vSphere client you should have a look at the following post: Enable SSH on VMware ESXi 5.5 via vSphere Client.

Oct272013October 27, 2013October 27, 20131 Commentby Thomas Maurer

Microsoft Server Posterpedia Windows 8.1 App just updated

Posted in Active Directory, Cloud, Exchange Server, Hyper-V, IIS, InTune, Microsoft, Microsoft Azure, Office, Office365, PowerShell, Private Cloud, Sharepoint, Software, System Center, Virtual Machine Manager, Virtualization, Web, Windows, Windows 8, Windows 8.1, Windows Server, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Work

Some days ago Microsoft released some of the new architecture poster for Windows Server 2012 R2 Hyper-V. Today Microsoft released an update in the Windows App Store for their Server Posterpedia App including the new Hyper-V 2012 R2 posters and some design changes.

Server Posterpedia is an interactive app that uses technical posters as a reference for understanding Microsoft technologies. This app includes all the reference posters from different Microsoft Server Technologies such as Windows Server 2012 Hyper-V, Exchange or Windows Azure. The great thing about this App, you can not only checkout the different posters and zoom in, if you click on a specific topic for you get directly linked to the right TechNet article. This can help find some TechNet references really easy and fast.

You can get the Server Posterpedia App in the Windows Store. and you can get some more information about this awesome App on my blog: Microsoft Server Posterpedia Windows 8 App or on serverposterpedia.com.

Tag: Server

Azure Stack Capacity Calculator Tool

Azure Stack Capacity Planner

How to create a Nano Server Image using PowerShell

Microsoft a leader in Gartner x86 Server Virtualization Infrastructure 2016 Magic Quadrant

How to create a Nano Server Image

Cisco UCS and Hyper-V Enable Stateless Offloads with NVGRE

Enable SSH on VMware ESXi 5.5

Follow Me

About

Sponsor

Sponsor

Sponsor

Sponsor