mountainss Cloud and Datacenter Management Blog

Microsoft SystemCenter blogsite about virtualization on-premises and Cloud


Leave a comment

Happy Learning with #Microsoft Self Paced LABS Online #Education #Azure #Winserv #SDN #SQL #Cloud

STEP 1

Here you go to the Microsoft Self-Paced-LABS

STEP 2

Happy Learning with your online LAB


Leave a comment

JOIN The #Microsoft Tech Community Today #MStechSummit #Azure #MSOMS #AzureStack #Sysctr #Winserv

Sign Up Here for the Microsoft Tech Community

Jeff Woolsey in action Talking about Windows Server 2016 Security and Containers
Thanks Jeff Great Sessions !

Of course It’s a tradition that @ClusterMVP & @WSV_GUY  & @Jamesvandenberg are on a Picture 😉
Cloud and Datacenter Management Rocks

#MVPbuzz Time with Ask Me Anything (AMA) sessions at the Microsoft Tech Summit 2017
Great questions and feedback on Microsoft :

Azure
AzureStack
Windows Server 2016
Hyper-V
System Center
Operations Management Suite (OMS)
Containers

Microsoft Tech Summit 2017 Amsterdam Dutch MVP’s at the Booth
#MVPbuzz

Multitasking showing of the Microsoft Surface Studio and supporting the Microsoft Tech Community
Thanks Ladies !

Microsoft Tech Summit 2016-17

Build your cloud and infrastructure skills with a two-day free technical training event
Here you can see in which cities the Microsoft Tech Summit 2017 is

Thank you Microsoft and Community for these Awesome two Cloud and Infrastructure Days in Amsterdam !  😉


Leave a comment

Are you Ready for #TechDaysNL 4 and 5 October 2016 #Azure #HybridCloud #DevOps #Linux

techdays-2016

Join Microsoft TechDays 2016 in Amsterdam !

Use the Cool TechDays app 2016 for all the information and sessions of this Awesome Event :

windowsstoreapple-storegoogle-play-store-icon

 

 

 

 

 

There will be Great Speakers to Join and Corey Sanders will do the Keynote and Cool sessions about Microsoft Azure.

corey-sanders

 

Here you find all the great TechDays 2016 Sessions

Hope to Meet you all at Microsoft TechDays 2016 in Amsterdam 😉

mvp-hybridcloud4you

SCUG Banner

 


Leave a comment

Proud to receive the 6th #Microsoft MVP Award for #Cloud and Datacenter Management #Sysctr #MSOMS #Azure

MVP Award 2016 CDM James

Thank you Microsoft and Community for this Awesome MVP Global Award !

#PROUD

🙂


Leave a comment

Free #Windows10 IT Pro Essentials Top 10 Tools E-book by @Edbott

Windows10 Ebook Top10 tools

Dive in to Windows 10 with award-winning journalist and Windows Expert Ed Bott in this highly curated free eBook covering the top apps, accessories, and utilities included in the box with Windows 10.

The sheer volume of Windows programs and accessories says a lot about the power and complexity of Windows—a fact that every IT pro knows from firsthand experience. There’s a tool for nearly every task, and a large part of the process of becoming a Windows expert is knowing how to find the appropriate one when you need it.

This eBook contains descriptions and hands-on advice to help IT Pros work faster and smarter. Some of these tools are for everybody—end users and experts alike—whereas some are strictly for professionals. A few are so specialized that you’ll only need them once in a blue moon. Collectively, though, they make up a toolbox that can save you (and your company) time and money.

You can download the Free Windows 10 IT Pro Essentials Top 10 Tools E-book here

Thank you Ed Bott for this Awesome E-book 😉


Leave a comment

Microsoft Azure Stack Single Server POC Deployment part1 #Azure #AzureStack #HybridCloud

Dell PowerEdge R710-240GB-Dual QuadCore 2.26GHz

Dell Power Edge R710 Server for Microsoft AzureStack TP1 POC

Hardware Requirements

These requirements apply to the Azure Stack POC only and might change for future releases.

Component Minimum Recommended
Compute: CPU Dual-Socket: 12 Physical Cores Dual-Socket: 16 Physical Cores
Compute: Memory 96 GB RAM 128 GB RAM
Compute: BIOS Hyper-V Enabled (with SLAT support) Hyper-V Enabled (with SLAT support)
Network: NIC Windows Server 2012 R2 Certification required for NIC; no specialized features required Windows Server 2012 R2 Certification required for NIC; no specialized features required
Disk drives: Operating System 1 OS disk with minimum of 200 GB available for system partition (SSD or HDD) 1 OS disk with minimum of 200 GB available for system partition (SSD or HDD)
Disk drives: General Azure Stack POC Data 4 disks. Each disk provides a minimum of 140 GB of capacity (SSD or HDD). 4 disks. Each disk provides a minimum of 250 GB of capacity.
HW logo certification Certified for Windows Server 2012 R2 Certified for Windows Server 2012 R2

Data disk drive configuration: All data drives must be of the same type (SAS or SATA) and capacity. If SAS disk drives are used, the disk drives must be attached via a single path (no MPIO, multi-path support is provided)

HBA configuration options: 1. (Preferred) Simple HBA 2. RAID HBA – Adapter must be configured in “pass through” mode 3. RAID HBA – Disks should be configured as Single-Disk, RAID-0

Supported bus and media type combinations

  • SATA HDD
  • SAS HDD
  • RAID HDD
  • RAID SSD (If the media type is unspecified/unknown*)
  • SATA SSD + SATA HDD
  • SAS SSD + SAS HDDExample HBAs: LSI 9207-8i, LSI-9300-8i, or LSI-9265-8i in pass-through mode
  • Sample OEM configurations are available.
  • * RAID controllers without pass-through capability can’t recognize the media type. Such controllers will mark both HDD and SSD as Unspecified. In that case, the SSD will be used as persistent storage instead of caching devices. Therefore, you can deploy the Microsoft Azure Stack POC on those SSDs.

Deploy Azure Stack POC

  • Before you deploy, prepare the Azure Stack POC machine and make sure it meets the minimum requirements.
    1. Install Windows Server 2016 Datacenter Edition Technical Preview 4 EN-US (Full Edition).
    2. Download the Azure Stack POC deployment package to a folder on your C drive, (for example, c:\AzureStack).
  • Run the Microsoft Azure Stack POC.exe file.

AzureStack1

 

This creates the \Microsoft Azure Stack POC\ folder containing the following items:

  • DeployAzureStack.ps1: Azure Stack POC installation PowerShell script
  • MicrosoftAzureStackPOC.vhdx: Azure Stack data package
  • SQLServer2014.vhdx: SQL Server VHD
  • WindowsServer2012R2DatacenterEval.vhd
  • WindowsServer2016Datacenter.vhdx: Windows Server 2016 Data Center VHD (includes KB 3124262)

AzureStack8

Important: You must have at least 128GB of free space on the physical boot volume.

  • Copy WindowsServer2016Datacenter.vhdx and call it MicrosoftAzureStackPOCBoot.vhdx.
  • In File Explorer, right-click MicrosoftAzureStackPOCBoot.vhdx and click Mount.
  • Run the bcdboot command:

bcdboot <mounted drive letter>:\windows

AzureStack9

 

AzureStack10

  • Reboot the machine. It will automatically run Windows Setup as the VHD system is prepared.
  • Configure the BIOS to use Local Time instead of UTC.
  • Verify that four drives for Azure Stack POC data:

AzureStack11

  • Are visible in disk management
  • Are not in use
  • Show as Online, RAW
  • Verify that the host is not joined to a domain.
  • Log in using a local account with administrator permissions.
  • Verify network connectivity to Azure.com.

 

AzureStack12

Important: Only one NIC is allowed during the deployment process. If you want to use a specific NIC, you must disable all the others.

Run the PowerShell deployment script

  1. Open PowerShell as an administrator.
  2. In PowerShell, go to the Azure Stack folder location (\Microsoft Azure Stack POC\ if you used the default).
  3. Run the deploy command:

AzureStack Deploy script cmdI’m running the script with Proxy settings.

 

Deployment starts and the Azure Stack POC domain name is hardcoded as azurestack.local.

AzureStack18

 

  1. At the Enter the password for the built-in administrator prompt, enter a password and then confirm it. This is the password to all the virtual machines. Be sure to record this Service Admin password.AzureStack19
  2. At the Please login to your Azure account in the pop-up Azure authentication page, hit any key to open the Microsoft Azure sign-in dialog box.AzureStack20
  3. Enter the credentials for your Azure Active Directory Account. This user must be the Global Admin in the directory tenantAzureStack21
  4. Back in PowerShell, at the account selection confirmation prompt, enter y. This creates two users and three applications for Azure stack in that directory tenant: an admin user for Azure Stack, a tenant user for the TiP tests, and one application each for the Portal, API, and Monitoring resource providers. In addition to this, the installer adds consents for the Azure PowerShell, XPlat CLI, and Visual Studio to that Directory Tenant.AzureStack22
  5. At the Microsoft Azure Stack POC is ready to deploy. Continue? prompt, enter y.AzureStack24
  6. The deployment process will take a few hours, during which several automated system reboots will occur. Signing in during deployment will automatically launch a PowerShell window that will display deployment progress. The PowerShell window closes after deployment completes.AzureStack25
  7. On the Azure Stack POC machine, sign in as an AzureStack/administrator, open Server Manager, and turn off IE Enhanced Security Configuration for both admins and users.

There are two ways to log in to the Azure Stack POC.

Log in as a service administrator

A service administrator manages resource providers, tenant offers, plans, services, quotas, and pricing.

  1. Log in to the Azure Stack POC physical machine.AzureStack25a
    AzureStack27
  2. Double-click the AzureStack.local.rdp desktop icon to open a Remote Desktop Connection to the client virtual machine. This automatically uses the AzureStack\AzureStackUser account that was created by the deployment script. Use the admin password you gave in step 5 of the script process at the Enter the password for the built-in administrator prompt.AzureStack28
  3. On the ClientVM.AzureStack.local desktop, double-click Microsoft Azure Stack POC Portal icon (https://portal.azurestack.local/).AzureStack29
  4. Log in using the service administrator account.AzureStack30Click on Accept

AzureStack31


Log in as a tenant

Tenants provision, monitor, and manage services that they subscribe to, like Web Apps, storage, and virtual machines. A service administrator can log in as a tenant to test the plans, offers, and subscriptions that their tenants might use. If you don’t already have one, Create a tenant account before you log in.

  1. Log in to the Azure Stack physical machine.
  2. Double-click the AzureStack.local.rdp desktop icon to open a Remote Desktop Connection to the client virtual machine. This automatically uses the AzureStack\AzureStackUser account that was created by the deployment script. Use the admin password you gave in step 5 of the script process at the Enter the password for the built-in administrator prompt.
  3. On the ClientVM.AzureStack.local desktop, double-click Microsoft Azure Stack POC Portal icon (https://portal.azurestack.local/).
  4. Log in using a tenant account.

RDP may restrict how many users can access the physical Microsoft Azure POC host. To enable multiple users, see Enable multiple concurrent user connections.

 

All Cloud

Next blogpost will be about Configuring Microsoft Azure Stack part 2


Leave a comment

#WindowsContainer Host Deployment on #NanoServer #HyperV nested Virtualization

Hyper-V-Containers-Nested-Virtualization

Windows Containers on Hyper-V NanoServer nested Virtualization

Deployment Steps

Install Container Feature

The container feature can be installed on Windows Server 2016, or Windows Server 2016 Core, using Windows Server Manager or PowerShell.

To install the role using PowerShell, run the following command in an elevated PowerShell session.

Install Containers

PS C:\> Install-WindowsFeature containers

The system needs to be rebooted when the container role installation has completed.

PS C:\> shutdown /r

After the system has rebooted, use the Get-ContainerHost command to verify that the container role has successfully been installed:

Get-Containerhost

PS C:\> Get-ContainerHost

Prepare Nano Server

Deploying Nano Server involves creating a prepared virtual hard drive, which includes the Nano Server operating system, and additional feature packages. This guide quickly details preparing a Nano Server virtual hard drive, which can be used for Windows Containers.

For more information on Nano Server, and to explore different Nano Server deployment options, see the Nano Server Documentation.

Create a folder named nano.

PS C:\> New-Item -ItemType Directory c:\nano

Locate the NanoServerImageGenerator.psm1 and Convert-WindowsImage.ps1 files from the Nano Server folder, on the Windows Server Media. Copy these to c:\nano.

#Set path to Windows Server 2016 Media
PS C:\> $WindowsMedia = "C:\Users\Administrator\Downloads\WindowsServerTP4"

PS C:\> Copy-Item $WindowsMedia\NanoServer\Convert-WindowsImage.ps1 c:\nano
PS C:\> Copy-Item $WindowsMedia\NanoServer\NanoServerImageGenerator.psm1 c:\nano

Run the following to create a Nano Server virtual hard drive. The –Containers parameter indicates that the container package will be installed, and the –Compute parameter takes care of the Hyper-V package. Hyper-V is only required if Hyper-V containers will be created.

Import-Module

PS C:\> Import-Module C:\nano\NanoServerImageGenerator.psm1
PS C:\> New-NanoServerImage -MediaPath $WindowsMedia -BasePath c:\nano -TargetPath C:\nano\NanoContainer.vhdx -MaxSize 10GB -GuestDrivers -ReverseForwarders -Compute -Containers

When completed, create a virtual machine from the NanoContainer.vhdx file. This virtual machine will be running the Nano Server OS, with optional packages.

Configure Nested Virtualization

If the container host itself will be running on a Hyper-V virtual machine, and will also be hosting Hyper-V Containers, nested virtualization needs to be enabled. This can be completed with the following PowerShell command.

The virtual machines must be turned off when running this command.

PS C:\> Set-VMProcessor -VMName <container host vm> -ExposeVirtualizationExtensions $true

Configure Virtual Processors

If the container host itself will be running on a Hyper-V virtual machine, and will also be hosting Hyper-V Containers, the virtual machine will require at least two processors. This can be configured through the settings of the virtual machine, or with the following PowerShell script.

PS C:\> Set-VMProcessor –VMName <VM Name> -Count 2

Enable Hyper-V Role

If Hyper-V Containers will be deployed, the Hyper-V role needs to be enabled on the container host. If the container host is a virtual machine, ensure that nested virtualization has been enabled. The Hyper-V role can be installed on Windows Server 2016 or Windows Server 2016 Core using the following PowerShell command.

PS C:\> Install-WindowsFeature hyper-v

Create Virtual Switch

Each container needs to be attached to a virtual switch in order to communicate over a network. A virtual switch is created with the New-VMSwitch command. Containers support a virtual switch with type External or NAT.

This example creates a virtual switch with the name “Virtual Switch”, a type of NAT, and Nat Subnet of 172.16.0.0/12.

PS C:\> New-VMSwitch -Name "Virtual Switch" -SwitchType NAT -NATSubnetAddress 172.16.0.0/12

Configure NAT

In addition to creating a virtual switch, if the switch type is NAT, a NAT object needs to be created. This is completed using the New-NetNat command. This example creates a NAT object, with the name ContainerNat, and an address prefix that matches the NAT subnet assigned to the container switch.

Finally, if the container host is running inside of a Hyper-V virtual machine, MAC spoofing must be enable. This allows each container to receive an IP Address. To enable MAC address spoofing, run the following command on the Hyper-V host. The VMName property will be the name of the container host.

PS C:\> Get-VMNetworkAdapter -VMName <contianer host vm> | Set-VMNetworkAdapter -MacAddressSpoofing On

Install OS Images

An OS image is used as the base to any Windows Server or Hyper-V container. The image is used to deploy a container, which can then be modified, and captured into a new container image. OS images have been created with both Windows Server Core and Nano Server as the underlying operating system.

Container OS images can be found and installed using the ContainerProvider PowerShell module. Before using this module, it needs to be installed. The following commands can be used to install the module.

PS C:\> Install-PackageProvider ContainerProvider -Force

Return a list of images from PowerShell OneGet package manager:

PS C:\> Find-ContainerImage

Name                 Version                 Description
----                 -------                 -----------
NanoServer           10.0.10586.0            Container OS Image of Windows Server 2016 Techn...
WindowsServerCore    10.0.10586.0            Container OS Image of Windows Server 2016 Techn...

To download and install the Nano Server base OS image, run the following.

PS C:\> Install-ContainerImage -Name NanoServer -Version 10.0.10586.0
Downloaded in 0 hours, 0 minutes, 10 seconds.

Likewise, this command downloads and installs the Windows Server Core base OS image.

Issue: Save-ContainerImage and Install-ContainerImage cmdlets fail to work with a WindowsServerCore container image, from a remote PowerShell session.
Workaround: Logon to the machine using Remote Desktop and use Save-ContainerImage cmdlet directly.

PS C:\> Install-ContainerImage -Name WindowsServerCore -Version 10.0.10586.0
Downloaded in 0 hours, 2 minutes, 28 seconds.

Verify that the images have been installed using the Get-ContainerImage command.

PS C:\> Get-ContainerImage

Name              Publisher    Version      IsOSImage
----              ---------    -------      ---------
NanoServer        CN=Microsoft 10.0.10586.0 True
WindowsServerCore CN=Microsoft 10.0.10586.0 True

For more information on Container management See Windows Containers Documentation

MSFT Containers