mountainss Cloud and Datacenter Management Blog

Microsoft SystemCenter blogsite about virtualization on-premises and Cloud


Leave a comment

#Microsoft MAP Toolkit 9.6 Now Available! #Winserv #SQL2016 #Azure #Office365 #Cloud #Tool

maptoolkit-9-6

Microsoft MAP Toolkit 9.6

The Microsoft Assessment and Planning Toolkit (MAP) is an agentless, automated, multi-product planning and assessment tool for quicker and easier desktop, server and cloud migrations. MAP provides detailed readiness assessment reports and executive proposals with extensive hardware and software information, and actionable recommendations to help organizations accelerate their IT infrastructure planning process, and gather more detail on assets that reside within their current environment. MAP also provides server utilization data for Hyper-V server virtualization planning; identifying server placements, and performing virtualization candidate assessments. More information about MAP Toolkit can you find here

Software Requirements:
        • Operating system. Any of the following:
          • Windows 10 (Professional, Enterprise and Ultimate editions only)
          • Windows 8.1 (Professional and Enterprise editions only)
          • Windows 8 (Professional and Enterprise editions only)
          • Windows 7 with Service Pack 1 (Professional, Enterprise, and Ultimate editions only)
          • Windows Server 2012 R2
          • Windows Server 2012
          • Windows Server 2016
          • Windows Server 2008 R2 with Service Pack 1
        • .NET Framework 4.5 (download from http://go.microsoft.com/fwlink/?LinkId=389161)
        • Installation of all updates for the operating system. Note: In some cases updates may not install automatically. To download updates for your computer manually, go to http://update.microsoft.com/.
        • By default, the MAP Toolkit will install SQL Server 2012 Express LocalDB during setup. You may also use an existing installation of SQL Server 2008, SQL Server 2008 R2, or SQL Server 2012 if you create an instance named “MAPS” before running the MAP Toolkit installer. The MAP Toolkit requires the collation order of the database engine to be set to “SQL_Latin1_General_CP1_CI_AS”.

Notes:

        • Some of these prerequisites require restarting your computer. You may have to restart multiple times if all the prerequisites are not met prior to running Microsoft Assessment and Planning Toolkit setup.

Scenario-dependent requirements:

    • For machines that will be used to run the Forefront Endpoint Protection Usage Tracking, Lync Usage Tracking, Exchange Server Usage Tracking, or Volume Licensing scenarios, please note: PowerShell 2.0 or higher must be installed.
    • For machines that will be used to collect Oracle schema information, please note: The 64 bit Oracle client must be installed on the MAP machine to collect the schema information. If the 64 bit client is not installed, MAP will only be able to collect instance information. MAP will not collect schema information if the 32 bit Oracle client is installed.

windows-server-2016-assessment

Export results in Excel for Windows Server 2016 Assessment Example

azure-virtual-machine-sizing

Microsoft Azure Virtual Machine Sizing Example in Excel

map-toolkit-training

With MAP Toolkit Training available 😉

You can download MAP Toolkit 9.6 here

microsoft-mvp-cdm-azure-advisor-banner


Leave a comment

Running #NanoServer in a #Container on Windows Server 2016 with #Docker in Powershell #DevOps

windows-containers

What are Containers

They are an isolated, resource controlled, and portable operating environment. 

Basically, a container is an isolated place where an application can run without affecting the rest of the system and without the system affecting the application. Containers are the next evolution in virtualization. 

If you were inside a container, it would look very much like you were inside a freshly installed physical computer or a virtual machine. And, to Docker, a Windows Server Container can be managed in the same way as any other container.

Windows Container Types

Windows Containers include two different container types, or runtimes. 

Windows Server Containers – provide application isolation through process and namespace isolation technology. A Windows Server container shares a kernel with the container host and all containers running on the host.

Hyper-V Containers – expand on the isolation provided by Windows Server Containers by running each container in a highly optimized virtual machine. In this configuration the kernel of the container host is not shared with the Hyper-V Containers. 

hyper-v-containers

Container Fundamentals

When you begin working with containers you will notice many similarities between a container and a virtual machine. A container runs an operating system, has a file system and can be accessed over a network just as if it was a physical or virtual computer system. That said, the technology and concepts behind containers are very different from that of virtual machines.

The following key concepts will be helpful as you begin creating and working with Windows Containers.  

Container Host: Physical or Virtual computer system configured with the Windows Container feature. The container host will run one or more Windows Containers.

Container Image: As modifications are made to a containers file system or registry, such as with software installation they are captured in a sandbox. In many cases you may want to capture this state such that new containers can be created that inherit these changes. That’s what an image is – once the container has stopped you can either discard that sandbox or you can convert it into a new container image. For example, let’s imagine that you have deployed a container from the Windows Server Core OS image. You then install MySQL into this container. Creating a new image from this container would act as a deployable version of the container. This image would only contain the changes made (MySQL), however would work as a layer on top of the Container OS Image.

Sandbox: Once a container has been started, all write actions such as file system modifications, registry modifications or software installations are captured in this ‘sandbox’ layer.

Container OS Image: Containers are deployed from images. The container OS image is the first layer in potentially many image layers that make up a container. This image provides the operating system environment. A Container OS Image is Immutable, it cannot be modified.

Container Repository: Each time a container image is created the container image and its dependencies are stored in a local repository. These images can be reused many times on the container host. The container images can also be stored in a public or private registry such as DockerHub so that they can be used across many different container host.

You have to install these Windows Server 2016 Rolls and Feature first before you start with Containers :

  • Hyper-V
  • Containers

system

My Windows 2016 Server Build version.

hyperv-install

Install Hyper-V

container-feature-installed

Install Containers

Here is an example on my Windows 2016 Server to get started with Windows Containers :

containers1

Install-Module -Name DockerMsftProvider -Repository PSGallery -Force

containers2

Install-Package -Name docker -ProviderName DockerMsftProvider

containers3

containers4

Restart-Computer -Force

containers5

Here we pull out of the Docker Hub the Microsoft Nanoserver Container.

containers6

Downloading the Image.

containers7

Automatically extract the image.

containers8 Docker Container Image Microsoft/nanoserver is downloaded.

run-container

Docker run -i -t microsoft/nanoserver

docker-container-session

docker ps
( you will see the container with Nanoserver is running)

container-nic

Inside the container.

powershell-nanoserver-from-docker-container

Running Powershell inside the container.

Containers for Developers

From a developer’s desktop to a testing machine to a set of production machines, a Docker image can be created that will deploy identically across any environment in seconds. This story has created a massive and growing ecosystem of applications packaged in Docker containers, with DockerHub, the public containerized-application registry that Docker maintains, currently publishing more than 180,000 applications in the public community repository.  

When you containerize an app, only the app and the components needed to run the app are combined into an “image”. Containers are then created from this image as you need them. You can also use an image as a baseline to create another image, making image creation even faster. Multiple containers can share the same image, which means containers start very quickly and use fewer resources. For example, you can use containers to spin up light-weight and portable app components – or ‘micro-services’ – for distributed apps and quickly scale each service separately. 

Because the container has everything it needs to run your application, they are very portable and can run on any machine that is running Windows Server 2016. You can create and test containers locally, then deploy that same container image to your company’s private cloud, public cloud or service provider. The natural agility of Containers supports modern app development patterns in large scale, virtualized and cloud environments.

With containers, developers can build an app in any language. These apps are completely portable and can run anywhere – laptop, desktop, server, private cloud, public cloud or service provider – without any code changes.

Containers helps developers build and ship higher-quality applications, faster.

Containers for IT Pro’s

IT Professionals can use containers to provide standardized environments for their development, QA, and production teams. They no longer have to worry about complex installation and configuration steps. By using containers, systems administrators abstract away differences in OS installations and underlying infrastructure. Containers help admins create an infrastructure that is simpler to update and maintain

microsoft-containers

Lot of Success with Containers and Nanoserver
#MVPbuzz


Leave a comment

NEW Free #Microsoft Windows Server 2016 Ebook Available #Winserv #Hyperv #NanoServer #Containers

windows-server-2016-ebook-cover

Windows Server has powered a generation of organizations, from small businesses to large enterprises. No matter what your role in IT, you can be guaranteed you that have touched Windows Server at some point in your career or at very least you have seen it from afar! This book introduces you to Windows Server 2016, which is the next version of Windows Server. No matter what your area of expertise, this book will introduce you to the latest developments in Windows Server 2016.

Here you can download the Free Microsoft Windows Server 2016 Ebook

SCUG Banner

 


Leave a comment

#Microsoft Windows Server 2016 TP5 Comparison Guide for Download and Try #Winserv #Hyperv #NanoServer

Features Comparison Windows Server 2016 TP5

This feature comparison guide compares selected features of Microsoft Windows Server 2008 R2, Windows Server 2012 R2, and Windows Server 2016. Its goal is to help customers understand the differences from the version they are running today and the latest version available from Microsoft.
The comparison table includes comments about each feature, as well as notation about how well each feature is supported in each release.

Download this Awesome Feature Comparison guide here

Windows Server BannerHere you can Try Microsoft Windows Server 2016 TP5

Or

Windows Server 2016 on AzureHere you can Try Windows Server 2016 on Microsoft Azure


Leave a comment

#NanoServer TP5 IaaS Image in the #Azure Gallery

TP 5 NanoServer 1a

Select Windows Server 2016  Technical Preview 5 NanoServer

TP 5 NanoServer 2

Click Create

TP 5 NanoServer 3a

TP 5 NanoServer 4

Choose your Server by clicking on view all

TP 5 NanoServer 5a

Configure your settings.

NanoServer running

Here you find an awesome blogpost about Nano Server TP5 IaaS Image in the Azure Gallery and Powershell CMD’s

Powershell for NanoServer