revmor.blogg.se - Part of windows desktop

VirtualNetworkResourceGroupName = $virutalNetworkResoureGroupīecause of splatting parameters instead of using a parameter file you will need at least PowerShell module Az.Resources version 2.5.1. VmDiskType = $.StorageAccountTypeĮxistingSubnetName = $virtualNetworkSubnet VmNumberOfInstances = $sessionHostsNumber VmResourceGroup = ($resourceGroup).ToUpper() It is unnecessary filling a lot of parameters which are mostly known by the system, with all its consequences.ĪdministratorAccountUsername = $administratorAccountUsernameĪdministratorAccountPassword = (ConvertTo-SecureString $administratorAccountPassword -AsPlainText -Force) In most situations you will use a JSON template file in combination with a JSON parameter file. function create-wvdHostpoolToken($hostpoolName,$resourceGroup,$hostpoolSubscription) Virtual Machine Tags Network Interface TagsĪfter setting all the variables the template parameter will be created.

After running the function you will receive the whole registration info. To make code nice and clean I wrote a function for creating a WVD Hostpool registration key. You need a registration key before you are able to add sessionhosts to a hostpool. Import-module az.resources #At least version 2.5.1

drainmode to on at the old sessionshosts.

the number of instances you like to create (optional).

administrator credentials (needed to join the sessionhosts into the domain),.

I assume you know how to update PowerShell modules. ( See github issue securitystring broken) There is a bug fixed about passing a securestring into a templateParameterObject.

There are some few requirements which are important.īefore continuing make sure have at least module version 2.5.1 of AZ.Resources in PowerShell. In this part we deploy new WVD sessionhosts and add it to an existing hostpool. The situation so far: we have created a new image, did a Sysprep, set the image as a version into the Shared Image Gallery.

Enroll MSIX packages automated – Part 6 – (coming soon).

Monitor Image Versions with Azure Monitor – Part 5.

WVD housekeeping, removing all unused sessionhosts, disks and images – Part 4.

Create WVD Sessionhosts based on Shared Image Gallery version – Part 3.

Save WVD image with Sysprep as Image Gallery version – Part 2.

Create WVD image version based on existing config with PowerShell – Part 1.

This post is a part of the series Windows Virtual Desktop Image Management Automated. In this part we are going to add new sessionhosts to an existing WVD hostpool based on a ARM template. This article is serie of posts about WVD Image Management Automated. Last updated 1 year ago by Sander Rozemuller