Tag: install

Aug142018August 14, 2018September 7, 20181 Commentby Thomas Maurer

How to install and manage Azure Stack Updates

Posted in Cloud, Microsoft, Microsoft Azure, Microsoft Azure Stack, PowerShell, Private Cloud, Virtualization, Work

At itnetX, we help customers to implement as well as to operate Azure Stack. One part of operating Azure Stack is keeping it up-to-date. This means installing Microsoft Azure Stack Updates, hotfixes as well as OEM update packages like drivers and firmware. In this blog post I will cover all the information you need to keep your Azure Stack up-to-date.

Why should you update your Azure Stack

This may sound like a simple question, but a lot of people ask for it. First of all, Microsoft and the hardware vendors are obviously delivering quality fixes and security updates to keep Azure Stack stable and secure. But Microsoft also adds new functionality with their updates packages to keep up with the rapid cloud development on Azure. This is important if you want that your Azure Stack stays consistent with Azure in terms of functionality.

Another important reason to stay current is to stay supported. You are allowed to be behind two major versions of Azure Stack, which means 2-3 months. You basically should update monthly, to make sure that you are secure and stable, however there are reasons why you might have to defer an update. For example, this can happen for some companies, when they are in a freeze period where they are not allowed to do changes in their systems. If you are more than 3 major versions behind, your Azure Stack is considered out of support and will not be supported from Microsoft, until you have the at least required version installed.

You can read more about the Azure Stack servicing policy on the Azure Stack documentation site.

Updates for the Azure Stack Integrated System

As mentioned before, there are basically three types of updates to Azure Stack. The monthly Azure Stack Update Packages from Microsoft, Hotfixes and OEM updates.

Microsoft software updates – Microsoft is responsible for the end-to-end servicing lifecycle for the Microsoft software update packages. These packages can include the latest Windows Server security updates, non-security updates, and Azure Stack feature updates. These update packages are non-cumulative updates and need to be installed one after the other. These updates are fully automated and will update the complete Azure Stack infrastructure.
OEM hardware vendor-provided updates – Azure Stack hardware partners are responsible for the end-to-end servicing lifecycle (including guidance) for the hardware-related firmware and driver update packages. In addition, Azure Stack hardware partners own and maintain guidance for all software and hardware on the hardware lifecycle host.
Microsoft hotfixes – Microsoft provides hotfixes for Azure Stack that address a specific issue that is often preventative or time-sensitive. Each hotfix is released with a corresponding Microsoft Knowledge Base article that details the issue, cause, and resolution. Hotfixes are downloaded and installed just like the regular full update packages for Azure Stack. Other the the major updates, Azure Stack hotfixes are cumulative per iteration.

	Release	Cumulative	Where to find
Microsoft Software Updates	Monthly (4th Tuesday of very month)	No	Release Notes
OEM Hardware Vendor Updates	Depending on OEM	Depends	OEM Website
Microsoft Hotfixes	When needed	Yes	Knowledge Base article

By the way, you can only update Azure Stack multi-node systems, the Azure Stack Development Kit needs to be redeployed.

Aug012017August 1, 2017January 12, 20192 Commentsby Thomas Maurer

Install Hyper-V on Windows Server using PowerShell

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

If you want to install Hyper-V on Windows Server you can use the following PowerShell command to install the Hyper-V role. If you want to run Hyper-V, make sure your server does include the following requirements.

64-bit Processor with Second Level Address Translation (SLAT)
CPU support for VM Monitor Mode Extension (VT-c on Intel CPU’s)
Processors with Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) technology
Hardware-enforced Data Execution Prevention (DEP) must be available and enabled. Intel: XD bit (execute disable bit) AMD: NX bit (no execute bit)
Minimum of 4 GB memory

Install-WindowsFeature -Name Hyper-V -ComputerName HOSTNAME -IncludeManagementTools -Restart

1	Install-WindowsFeature -Name Hyper-V -ComputerName HOSTNAME -IncludeManagementTools -Restart

To check if Hyper-V is enabled, use the following command:

Get-WindowsFeature -Name Hyper-V -ComputerName HOSTNAME

1	Get-WindowsFeature -Name Hyper-V -ComputerName HOSTNAME

If you are looking for installing Hyper-V on Windows 10, check the following blog post: Install Hyper-V on Windows 10 using PowerShell

Aug012017August 1, 2017January 12, 20190 Commentby Thomas Maurer

Install Hyper-V on Windows 10 using PowerShell

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

On since Windows 8 you can run Hyper-V on your desktop, laptop or Windows tablet. To install or enable Hyper-V on your Windows 10 machine, you just need to have the following requirements:

Windows 10 Enterprise, Professional, or Education (Home does not have the Hyper-V feature included)
64-bit Processor with Second Level Address Translation (SLAT)
CPU support for VM Monitor Mode Extension (VT-c on Intel CPU’s)
Minimum of 4 GB memory

The easiest way to enable Hyper-V on Windows 10 is to run the following PowerShell command as an administrator:

Enable-WindowsOptionalFeature -Online -FeatureName:Microsoft-Hyper-V -All

1	Enable-WindowsOptionalFeature -Online -FeatureName:Microsoft-Hyper-V -All

or you can use the following CMD DISM command:

DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V

1	DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V

If you are looking for installing Hyper-V on Windows Server, check the following blog post: Install Hyper-V on Windows Server using PowerShell

May182016May 18, 2016January 9, 20190 Commentby Thomas Maurer

How to Install the Azure PowerShell Module

Posted in Cloud, Microsoft, Microsoft Azure, PowerShell, Virtualization, Web, Web, Windows, Windows 10, Windows Server, Windows Server 2016, Work

This blogs post describes how you can install the Azure PowerShell module. Microsoft a couple of weeks ago released version one of their new Azure PowerShell module on .NET Core called the Az module. The Az module will replace the AzureRM module over time. however, the AzureRM module is still supported. The new Az module is a cross-platform module.

Well if you are working with Microsoft Azure you may need the PowerShell Modules for automation and some settings which are only available in PowerShell. With the latest releases you can install the Azure PowerShell Module using the package management in PowerShell, and install the Azure PowerShell module form the PowerShell Gallery.

PowerShell Gallery Azure Az Module

Az module features

Az is a replacement for AzureRM and AzureRM.Netcore.
Runs on PowerShell 5.1 and PowerShell Core.
It is always up to date with the latest tooling for Azure services.
Az ships in Cloud Shell.
It shortens and normalizes cmdlet names. All cmdlets use “Az” as their noun prefix.
Az will simplify and normalize module names. Data plane and management plane cmdlets for each service will use the same Az module.
It ships with new cmdlets to enable script compatibility with AzureRM (Enable/Disable-AzureRmAlias).

Supported platforms

PowerShell 5.1 – Windows 7 or greater with .Net Framework 4.7.2 or greater installed
PowerShell Core 6.0 – Windows, Mac OS, Linux
PowerShell Core 6.1 – Windows, Mac OS, Linux

Install Azure PowerShell module

For me using the PowerShell Package Management and the PowerShell Gallery is may the easiest and fastest way to install it. In Windows 10 or a computer with the Windows Management Framework 5 installed, you can use the following PowerShell cmdlets to install it.

You should not install Az side-by-side with AzureRM. Remove all AzureRM modules before installing Az.

Install-Module Az

1	Install-Module Az

You can also update the AZ module using the following command:

Update-Module Az

1	Update-Module Az

And you can use the following command to login:

Connect-AzAccount

1	Connect-AzAccount

You can also see the Azure PowerShell Modules and versions using the PowerShell Package Management:

Find-Module -ListAvailable *Az*

1	Find-Module -ListAvailable Az

AzureRM compatibility

If you would like to run scripts developed for AzureRM using Az, use the Enable/Disable-AzureRmAlias cmdlets to add or remove aliases from AzureRM cmdlets to Az cmdlets.

This can be enabled and disabled:

Enable-AzureRmAlias

Disable-AzureRMAlias

Enable-AzureRmAlias

Disable-AzureRMAlias

Run Azure PowerShell from Cloud Shell

You can also run the latest Azure PowerShell module version directly from Cloud Shell, with no need to install it.

This blog post was updated with the release 1.0.0 of the Azure Az module based on .NET Core. You can find more about the new Azure PowerShell module on the GitHub repo.

Also check out my blog post: Mastering Azure using Cloud Shell

Dec122011December 12, 2011December 12, 20115 Commentsby Thomas Maurer

Automated Active Directory Deployment with PowerShell

Posted in Active Directory, Microsoft, PowerShell, Windows Server, Windows Server 2008 R2, Work

For a small presentation at KTSI I created a PowerShell script will automatically will deploys Active Directory Servers, adds other member servers, creates Organization Units and adds users via Powershell Remoting. As source there is a XML configuration file and CSV files for User Data.

This script is just for Lab deployments not for production, and it is not perfect, but I think maybe some people will enhance this script with their own code.

I do not support this script. it is just something I need to deploy my test environments and nothing more. More it shows diffrent

You can find more information about it works in this document.

XML Config file:

&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;lab&gt;
&lt;config&gt;
&lt;servers&gt;
&lt;server name="ADS01" ip="192.168.100.11" id="1" adminpw="passw0rd"/&gt;
&lt;server name="ADS02" ip="192.168.100.12" id="2" adminpw="passw0rd"/&gt;
&lt;/servers&gt;
&lt;ad&gt;
&lt;domain name="ktsi.local" netbiosname="ktsi" forestlevel="4" domainlevel="4" safemodepw="passw0rd" /&gt;
&lt;/ad&gt;
&lt;ous&gt;
&lt;ou name="UserAccounts" path="DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="BASEL" path="OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="CHICAGO" path="OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="NEWYORK" path="OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="SALES" path="OU=BASEL,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="IT" path="OU=BASEL,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="ADMINISTRATION" path="OU=BASEL,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="PRODUCTION" path="OU=BASEL,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="SALES" path="OU=CHICAGO,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="IT" path="OU=CHICAGO,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="ADMINISTRATION" path="OU=CHICAGO,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="PRODUCTION" path="OU=CHICAGO,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="SALES" path="OU=NEWYORK,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="IT" path="OU=NEWYORK,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="ADMINISTRATION" path="OU=NEWYORK,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;ou name="PRODUCTION" path="OU=NEWYORK,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;/ous&gt;
&lt;users&gt;
&lt;file name="users.csv" path="OU=ADMINISTRATION,OU=BASEL,OU=USERACCOUNTS,DC=KTSI,DC=LOCAL" /&gt;
&lt;/users&gt;
&lt;members&gt;
&lt;member name="PC101" ip="192.168.100.21" /&gt;
&lt;member name="PC101" ip="192.168.100.22" /&gt;
&lt;member name="PC101" ip="192.168.100.23" /&gt;
&lt;/members&gt;
&lt;/config&gt;
&lt;/lab&gt;

<?xml version="1.0" encoding="utf-8"?>

<lab>

</servers>

<ad>

</ad>

<ous>

</ous>

<users>

</users>

</members>

</config>

</lab>

The PowerShell Script:

Mar242011March 24, 2011March 23, 20115 Commentsby Thomas Maurer

HP Network Interface does not start.

Posted in HP, Microsoft, ProLiant Server, Windows Server, Windows Server 2008 R2, Work

I just installed two new HP ProLiant DL360 G6 with Microsoft Windows Server 2008 R2. Everything worked fine until I installed the HP Support Pack which includes Drivers and Firmware for the HP Server.

After I installed the HP ProLiant Support Pack one of my Network Interfaces could not start. I got the following error in the Device Manager:

HP NC382i DP Virtual Bus Device
This device cannot start. (Code 10)

I tried to uninstall the device and rebooted the server but this didn’t work. I had still the same error.

The problem was that just uninstalling the driver does not work, you also have to check the checkbox on “Delete the driver software for this device.”

After doing that you can rescan for new hardware and the system will find this adapter again and everything will work fine.

Dec202010December 20, 2010December 9, 20100 Commentby Thomas Maurer

Install HP Support Pack on Hyper-V R2 Core Server

Posted in HP, Hyper-V, Microsoft, ProLiant Server, Server Core, Software, Virtualization, Windows Server, Work

If you are using Microsoft Hyper-V R2 Core Server, installing the HP Support Pack is a little different. This post should show you how this is done.

Download the latest HP Support Pack for Windows Server 2008 R2 and extract that on your Management Server or PC.
Now copy the extracted folder to the Hyper-V Core Server. In my case i copied in the C:\ root of the Core Server via the administrative network share. If you have easy physical access to the server, you could also use a USB stick or something like that.
Now connect to the Core Server and use the cmd.exe to navigate to the folder with the HP Support Pack
Run the “hpsum.exe” to start the HP Smart Update Manager
When the HP Smart Update Manager is started you can use it like on a Full Server installation of Windows Server 2008