mountainss Cloud and Datacenter Management Blog

Microsoft SystemCenter blogsite about virtualization on-premises and Cloud


Leave a comment

Awesome #Microsoft Azure 101 Cards and Interactive Sites #Azure #Cloud

Microsoft Azure Services 101 Cards

From here you can get the Azure Container Instances Information

Go and see for your self the Microsoft Azure 101 Cards

Microsoft Interactives :

  • Azure Products
  • Cloud Design Patterns
  • Azure Security and Operations Management

Microsoft Azure Security Interactive

Advertisements


Leave a comment

Registration is open for #Microsoft Tech Summit Amsterdam 2018 #Azure #Cloud #MSTechSummit

Build your cloud skills
Free technical learning event with Microsoft’s top cloud engineers across Azure and Microsoft 365. Whether you’re developing innovative apps or delivering optimized solutions, Microsoft Tech Summit can help evolve your skills, deepen your expertise, and grow your career.

Customize your learning
Whether you’re already cloud-savvy or just getting started, there is something for everyone. Discover the latest trends, tools, and product roadmaps at more than 80 sessions covering a range of focus areas and topics – from keynotes and breakouts to hands-on labs.

Connect with experts
Take advantage of the event Hub, a gathering place where you can learn, network, meet partners, visit the community theater, and more! You’ll also have access to experts who can help you get the most out of the cloud – ask your toughest questions, share best practices, and provide feedback.

Get inspired
The cloud is changing expectations – and transforming the way we live and work. Learn how Microsoft’s cloud platform can help you lead your organization through real digital transformation – and shape your future.

Build your cloud skills with the latest in Azure and Microsoft 365 at a free, technical learning event for IT professionals and developers.
March 28-29, 2018
Register here

Here you find the Microsoft Tech Summit 2018 Catalog sessions

See you at this Awesome Microsoft Tech Summit Event in Amsterdam 😉 #MVPbuzz


Leave a comment

What’s New in Windows Server 2016 version 1709 #Winserv #Hyperv #Containers

Application containers and micro-services

  • The Server Core container image has been further optimized for lift-and-shift scenarios where you can migrate existing code bases or applications into containers with minimal changes, and it’s also 60% smaller.
  • The Nano Server container image is nearly 80% smaller.
    • In the Windows Server Semi-Annual Channel, Nano Server as a container base OS image is decreased from 390 MB to 80 MB.
  • Linux containers with Hyper-V isolation

For more information, see Changes to Nano Server in the next release of Windows Server and Windows Server, version 1709 for developers.

Modern management

Check out Project Honolulu for a simplified, integrated, secure experience to help IT administrators manage core troubleshooting, configuration, and maintenance scenarios. Project Honolulu includes next generation tooling with a simplified, integrated, secure, and extensible interface. Project Honolulu includes an intuitive all-new management experience for managing PCs, Windows servers, Failover Clusters, as well as hyper-converged infrastructure based on Storage Spaces Direct, reducing operational costs.

Compute

Nano Container and Server Core Container: First and foremost, this release is about driving application innovation. Nano Server, or Nano as Host is deprecated and replaced by Nano Container, which is Nano running as a container image.

For more information about containers, see Container Networking Overview.

Server Core as a container (and infrastructure) host, provides better flexibility, density and performance for existing applications under a modernization process and brands new apps developed already using the cloud model.

VM Load Balancing is also improved with OS and Application awareness, ensuring optimal load balancing and application performance. Storage-class memory support for VMs enables NTFS-formatted direct access volumes to be created on non-volatile DIMMs and exposed to Hyper-V VMs. This enables Hyper-V VMs to leverage the low-latency performance benefits of storage-class memory devices.

Storage-class memory support for VMs enables NTFS-formatted direct access volumes to be created on non-volatile DIMMs and exposed to Hyper-V VMs. This enables Hyper-V VMs to leverage the low-latency performance benefits of storage-class memory devices. Virtualized Persistent Memory (vPMEM) is enabled by creating a VHD file (.vhdpmem) on a direct access volume on a host, adding a vPMEM Controller to a VM, and adding the created device (.vhdpmem) to a VM. Using vhdpmem files on direct access volumes on a host to back vPMEM enables allocation flexibility and leverages a familiar management model for adding disks to VMs.

Virtualized Persistent Memory (vPMEM) is enabled by creating a VHD file (.vhdpmem) on a direct access volume on a host, adding a vPMEM Controller to a VM, and adding the created device (.vhdpmem) to a VM. Using vhdpmem files on direct access volumes on a host to back vPMEM enables allocation flexibility and leverages a familiar management model for adding disks to VMs.

Container storage – persistent data volumes on cluster shared volumes (CSV). In Windows Server, version 1709 as well as Windows Server 2016 with the latest updates, we’ve added support for containers to access persistent data volumes located on CSVs, including CSVs on Storage Spaces Direct. This gives the application container persistent access to the volume no matter which cluster node the container instance is running on. For more info, see Container Storage Support with Cluster Shared Volumes (CSV), Storage Spaces Direct (S2D), SMB Global Mapping.

Container storage – persistent data volumes with SMB global mapping. In Windows Server, version 1709 we’ve added support for mapping an SMB file share to a drive letter inside a container – this is called SMB global mapping. This mapped drive is then accessible to all users on the local server so that container I/O on the data volume can go through the mounted drive to the underlying file share. For more info, see Container Storage Support with Cluster Shared Volumes (CSV), Storage Spaces Direct (S2D), SMB Global Mapping.

Security and Assurance

Windows security baselines have been updated for Windows Server and Windows 10. A security baseline is a group of Microsoft-recommended configuration settings and explains their security impact. For more information, and to download the Policy Analyzer tool, see Microsoft Security Compliance Toolkit 1.0.

Network encryption enables you to quickly encrypt network segments on software-defined networking infrastructure to meet security and compliance needs.

Host Guardian Service (HGS) as a shielded VM is enabled. Prior to this release, the recommendation was to deploy a 3-node physical cluster. While this ensures the HGS environment is not compromised by an administrator, it was often cost prohibitive.

Linux as a shielded VM is now supported.

For more information, see Guarded fabric and shielded VMs overview.

Storage

Storage Replica: The disaster recovery protection added by Storage Replica in Windows Server 2016 is now expanded to include:

  • Test failover: the option to mount the destination storage is now possible through the test failover feature. You can mount a snapshot of the replicated storage on destination nodes temporarily for testing or backup purposes. For more information, see Frequently Asked Questions about Storage Replica.
  • Project Honolulu support: Support for graphical management of server to server replication is now available in Project Honolulu. This removes the requirement to use PowerShell to manage a common disaster protection workload.

 

SMB:

  • SMB1 and guest authentication removal: Windows Server, version 1709 no longer installs the SMB1 client and server by default. Additionally, the ability to authenticate as a guest in SMB2 and later is off by default. For more information, review SMBv1 is not installed by default in Windows 10, version 1709 and Windows Server, version 1709.
  • SMB2/SMB3 security and compatibility: Additional options for security and application compatibility were added, including the ability to disable oplocks in SMB2 for legacy applications, as well as require signing or encryption on per-connection basis from a client. For more information, review the SMBShare PowerShell module help.

 

Data Deduplication:

  • Data Deduplication now supports ReFS: You no longer must choose between the advantages of a modern file system with ReFS and the Data Deduplication: now, you can enable Data Deduplication wherever you can enable ReFS. Increase storage efficiency by upwards of 95% with ReFS.
  • DataPort API for optimized ingress/egress to deduplicated volumes: Developers can now take advantage of the knowledge Data Deduplication has about how to store data efficiently to move data between volumes, servers, and clusters efficiently.

Remote Desktop Services (RDS)

RDS is integrated with Azure AD, so customers can leverage Conditional Access policies, Multifactor Authentication, Integrated authentication with other SaaS Apps using Azure AD, and many more. For more information, see Integrate Azure AD Domain Services with your RDS deployment.

For a sneak peek at other exciting changes coming to RDS, see Remote Desktop Services: Updates & upcoming innovations

Networking

Docker’s Routing Mesh is supported. Ingress routing mesh is part of swarm mode, Docker’s built-in orchestration solution for containers. For more information, see Docker’s routing mesh available with Windows Server version 1709.

New features for Docker are available. For more information, see Exciting new things for Docker with Windows Server 1709.

Windows Networking at Parity with Linux for Kubernetes: Windows is now on par with Linux in terms of networking. Customers can deploy mixed-OS, Kubernetes clusters in any environment including Azure, on-premises, and on 3rd-party cloud stacks with the same network primitives and topologies supported on Linux without the need for any workarounds or switch extensions.

Core network stack: Several features of the core network stack are improved. For more information about these features, see Core Network Stack Features in the Creators Update for Windows 10.

  • TCP Fast Open (TFO): Support for TFO has been added to optimize the TCP 3-way handshake process. TFO establishes a secure TFO cookie in the first connection using a standard 3-way handshake. Subsequent connections to the same server use the TFO cookie instead of a 3-way handshake to connect with zero round trip time.
  • CUBIC: Experimental Windows native implementation of CUBIC, a TCP congestion control algorithm is available. The following commands enable or disable CUBIC, respectively.

netsh int tcp set supplemental template=internet congestionprovider=cubic

netsh int tcp set supplemental template=internet congestionprovider=compound

  • Receive Window Autotuning: TCP autotuning logic computes the “receive window” parameter of a TCP connection. High speed and/or long delay connections need this algorithm to achieve good performance characteristics. In this release, the algorithm is modified to use a step function to converge on the maximum receive window value for a given connection.
  • TCP stats API: A new API is introduced called SIO_TCP_INFO. SIO_TCP_INFO allows developers to query rich information on individual TCP connections using a socket option.
  • IPv6: There are multiple improvements in IPv6 in this release.
    • RFC 6106 support: RFC 6106 which allows for DNS configuration through router advertisements (RAs). You can use the following command to enable or disable RFC 6106 support:

netsh int ipv6 set interface <ifindex> rabaseddnsconfig=<enabled | disabled>

  • Flow Labels: Beginning with the Creators Update, outbound TCP and UDP packets over IPv6 have this field set to a hash of the 5-tuple (Src IP, Dst IP, Src Port, Dst Port). This will make IPv6 only datacenters doing load balancing or flow classification more efficient. To enable flowlabels:

netsh int ipv6 set flowlabel=[disabled|enabled] (enabled by default)

netsh int ipv6 set global flowlabel=<enabled | disabled>

  • ISATAP and 6to4: As a step towards future deprecation, the Creators Update will have these technologies disabled by default.
  • Dead Gateway Detection (DGD): The DGD algorithm automatically transitions connections over to another gateway when the current gateway is unreachable. In this release, the algorithm is improved to periodically re-probe the network environment.
  • Test-NetConnection is a built-in cmdlet in Windows PowerShell that performs a variety of network diagnostics. In this release we have enhanced the cmdlet to provide detailed information about both route selection as well as source address selection.

Software Defined Networking

  • Virtual Network Encryption is a new feature that provides the ability for the virtual network traffic to be encrypted between Virtual Machines that communicate with each other within subnets that are marked as “Encryption Enabled”. This feature utilizes Datagram Transport Layer Security (DTLS) on the virtual subnet to encrypt the packets. DTLS provides protection against eavesdropping, tampering and forgery by anyone with access to the physical network.

Windows 10 VPN

  • Pre-Logon Infrastructure Tunnels. By default, Windows 10 VPN does not automatically create Infrastructure Tunnels when users are not logged on to their computer or device. You can configure Windows 10 VPN to automatically create Pre-Logon Infrastructure Tunnels by using the Device Tunnel (prelogon) feature in the VPN profile.
  • Management of Remote Computers and Devices. You can manage Windows 10 VPN clients by configuring the Device Tunnel (prelogon) feature in the VPN profile. In addition, you must configure the VPN connection to dynamically register the IP addresses that are assigned to the VPN interface with internal DNS services.
  • Specify Pre-Logon Gateways. You can specify Pre-Logon Gateways with the Device Tunnel (prelogon) feature in the VPN profile, combined with traffic filters to control which management systems on the corporate network are accessible via the device tunnel.

Release Notes: Important Issues in Windows Server, version 1709


Leave a comment

Watch all those Awesome Microsoft #MSIgnite 2017 video sessions #Azure #AzureStack #MSOMS

Empower IT and developer productivity with Microsoft Azure with @scottgu

Microsoft Azure virtual machine infrastructure innovation and automation

Microsoft Azure Stack Development Kit and why it matters

Manage hybrid cloud and transform your workplace with PowerShell and Azure Automation

See here all the Microsoft Ignite 2017 video sessions

Thank you Microsoft and MVP’s for those Awesome sessions at Ignite 2017


Leave a comment

Create your first #Azure Container Instance in the #Cloud with #Docker #Containers

Microsoft Azure Container Instances

Containers are quickly becoming the preferred way to package, deploy, and manage cloud applications. Azure Container Instances offers the fastest and simplest way to run a container in Azure, without having to provision any virtual machines and without having to adopt a higher-level service. Azure Container Instances is a great solution for any scenario that can operate in isolated containers, including simple applications, task automation, and build jobs. For scenarios where you need full container orchestration, including service discovery across multiple containers, automatic scaling, and coordinated application upgrades, I recommend the Azure Container Service.

Here you see a quick example of making a Microsoft Azure Container Instance :

You can create an Microsoft Azure Container Instance with the Azure Portal or with Azure Cloud Shell (CLI 2.0)

From the Azure portal, you will create the Azure Container Instance Name, Container Image, Resource Group and Location.
For this quick example I used the public Docker HUB Image WordPress ( https://hub.docker.com/r/library/wordpress/)

Here you set the configuration of the Azure Container Instance, like how many Cores and Memory for the Container.
and Public IP Address yes or no with the port settings.

When you are almost finished in 3 steps, don’t hit OK but have a look at Download Template and Parameters first.

From here you can :

  • Download the Template for making Automation deployment scripts.
  • Save the template to the Library
  • And Deploy the script button.

Also have a look here !

It’s really powerful to work with Azure Resource Management Templates.

Deploying the Azure Container Instance with WordPress

Done,  just click here to see the running Container Instance

When you go to the IP-Address of the Azure Container Instance with your browser, you will see the WordPress site config.

Of course you can do this installation also from the Azure Cloud Shell :

Here you find an Overview of Microsoft Azure Cloud Shell and the Activation

Azure Cloud Shell is a browser-based shell experience to manage and develop Azure resources. Cloud Shell offers a browser-accessible, pre-configured shell experience for managing Azure resources without the overhead of installing, versioning, and maintaining a machine yourself. Cloud Shell provisions machines on a per-request basis and as a result machine state will not persist across sessions. Since Cloud Shell is built for interactive sessions, shells automatically terminate after 20 minutes of shell inactivity. 

Bash in Cloud Shell

Tools

Category Name
Linux shell interpreter Bash
sh
Azure tools Azure CLI 2.0 and 1.0
AzCopy
Batch Shipyard
Text editors vim
nano
emacs
Source control git
Build tools make
maven
npm
pip
Containers Docker CLI/Docker Machine
Kubectl
Draft
DC/OS CLI
Databases MySQL client
PostgreSql client
sqlcmd Utility
mssql-scripter
Other iPython Client
Cloud Foundry CLI

Language support

Language Version
.NET 1.01
Go 1.7
Java 1.8
Node.js 6.9.4
Python 2.7 and 3.5 (default)

Secure automatic authentication

Cloud Shell securely and automatically authenticates account access for the Azure CLI 2.0.

Azure Files persistence

Since Cloud Shell is allocated on a per-request basis using a temporary machine, files outside of your $Home and machine state are not persisted across sessions. To persist files across sessions, Cloud Shell walks you through attaching an Azure file share on first launch. Once completed Cloud Shell will automatically attach your storage for all future sessions. 

Learn more about attaching Azure file shares to Cloud Shell.

 

 Here you see in Azure Cloud Shell the Azure Container Instance (ACI)

See here more information about Microsoft Azure Container Instances

Hope this is helpful for you to start with Containers, here you can follow the Cloud Container Community


Leave a comment

JOIN #Microsoft Ignite 2017 Event and Download the Mobile App #Ignite #Ignite2017 @MS_Ignite

The Microsoft Ignite 2017 App s available

You can download the Microsoft Ignite 2017 App for your Mobile here

Don’t miss this Great Microsoft Ignite 2017 Event in Orlando Florida September 25-29, 2017 and Register for the last passes here

Have a look at the session Catalog and Choose your favorite topics at Microsoft Ignite 2017 here

Have lot’s of Fun and Great sessions to LEARN from with Awesome new Microsoft Technology !
#MVPbuzz

Follow Microsoft Ignite on Twitter => @MS_Ignite