Difference between revisions of "WimAsAService Tutorials"

Revision as of 07:28, 22 November 2021

General Solution Overview

There is a short overview Video, showing you the basic handling of the Website:

Generate a WIM File

The following graphic shows how your Image Types will be generated:

1	You can access the WimAsAService Web interface through a usual Browser like Edge, Internet Explorer, Chrome or Firefox.
2	On the Web interface create a new Image Type.
3	Before the Image can be created it has to be configured. First of all, give it a Name.
4	Choose one of the Images, which is available in our Image Repository.
5	Specific configuration can be applied to the chosen Operation System. Self-Created PPKG Files can be uploaded, Modern Apps can be uninstalled, Windows Features can be activated or deactivated, even undesired Windows Updates can be excluded. There are applications placed at the disposal by baseVISION AG, or you can upload your own Applications. Insert the language packages you want into your WIM (Multiple can be added). PowerShell scripts can also be implemented into the WIM file. If you have some special desires during the WIM creation your PowerShell scripts can be added to the Task sequence steps “Before Apps, After Apps and Before Sysprep”. Last of all you can define a schedule for automatic WIM creation. When you’re done save your Image Type.
6	If you press the Button “Generate Wim” all essential Information will be prepared for the MDT Server. If the MDT Server is busy, the Task will be queued or otherwise it will start immediately. You will be informed with an E-Mail when your creation process has been started or queued.
7	The MDT Server starts the creation process. The default Task Sequence is adjusted based on your configuration. With aid of a Virtual Machine your deployment process will be started.
8	The WIM file will be finished with the configuration you set.
9	At the End of the deployment Process your Image will be available through the Webinterface.
10	If everything is done you receive an E-Mail. In there is stated, that the WIM File is ready to download.

Adding an Application

There is a short Video, showing you how to add an Application:

You can trigger any kind of Application Installation, as long that it can be executed silently.
If you want to add an Application, you first need to create a ZIP File that contains the Application Files. The File you want to execute needs to be in the Root Folder of your ZIP File.

How to fill out the “Add new Application” Form:

Manufacturer = The Name of the Manufacturer (example Microsoft)
Product Name = The Name of the Application (example OfficeProPlus)
Version = The Version of the Application (example 2016)
Package Version = You can have Multiple Versions of a Package for the same Application. Select the Package Version
Architecture = The Architecture of the Application. x99 stands for an Application that can be installed on both platforms (x86 and x64)
Type =P stands for a physically installed Application (MSI, EXE, etc.). V stand for a Virtual Application (App-V, ThinApp, etc.)
Language = The Language of the Application. Select ML if the Application can be used in more than one Language.
Command Line = The Command Line Parameters required to install the Application silently and without User interaction.

Example Command line for the installation of an MSI-File:
msiexec /i Microsoft-CMTrace-5.0.7782.1000.msi /qn REBOOT=ReallySuppress /L*V "C:\Windows\Logs\Microsoft-CMTrace-5.0.7782.1000.log"

Example Command line for the execution of a VBS:
cscript install.vbs

Example Command line for the execution of a PowerShell Script:
powershell -executionPolicy bypass -file install.ps1

Example Command line for the execution of a Batch:
install.bat

Configure your Azure Storage Account

	If you do not already have a storage account or want to create a dedicated storage account for your WimAsAService Images, create a new storage account in the Azure Portal. Choose your already existing resource group or create a new one. Choose a fitting storage account name (lower case no special symbols and unique) and click "Review + Create" on the bottom of the screen. All other settings can be left on default or modified to your liking.
	After you have successfully created your storage account, navigate to the new resource (1) and add a container (2). Choose a fitting name and leave the rest of the settings to default.
	Now you have a storage account with a container where we will copy your images to. To allow our copy access, we need to generate an SAS token. To do so, navigate to "Shared Access Signature" on your storage account and configure the shared access signature as depicted in the screenshot. This is the minimum set of permissions that we need. We suggest that you have the images in a separate container or storage account so access over the SAS token is kept to a small scope. We also advice that you set the expiry date for a year and track the date with the SAS token like a certificate for annual renewal. You cannot retrieve the SAS token at a later date over the portal.
	Navigate to your image type in WimAsAService and input all the necessary information at the bottom of the configuration page. Please note that if you select one of the "Copy to Azure" checkboxes, inputting this data is required.
	After you have input all the data you need to validate the settings. If done so correctly, the validation should pass and you can start to generate or copy your images directly to Azure.
	After an image creation process or copy job over "manage files" has finished, you should see the WIM, VHD and or ISO files in your storage account. The "connectionvalidation.txt" files are created by the validation process. We cannot delete these files because we do not require delete permissions on your storage account. These can be deleted manually if needed.

Create an Azure Shared Image

	After you have successfully generated an Image and copied the VHD-file to your Azure Storage Account, there might arise a question. What to do next with this file in Azure? There are different kinds of use cases. You can use the file as a source of new host pools in WVD or new VMs that you want to host in the cloud. One recommended action is, to create an Azure Image. You can use this Image to create new VMs or host pools for WVD. Adding the Images to a Shared Image Gallery, you can enable further functionality like version and access control. To create a new image, search for "Images" in Azure and select "Create an Image". Here you can input the necessary data and select the VHD file from your storage account under "Storage blob". Of course, you could also copy the URI directly from the VHD-file.
	Now you can use your custom image, instead of the Microsoft Marketplace images, as a basis for your new host pool or virtual machine. With this you can easily customize your WVD or VM deployment with the numerous options delivered by WimAsAService.

Manage File Tab

With the release of WimAsAService 4.0 we have reworked the "Manage Files" site and added some new functionality to help accommodate the possibilities of our new delivery options. You will find the "new" site where you have previously downloaded your image.

Here we will quickly walk you through all the options you have:

	1. Download the documentation of your image 2. Download your image in the available format (unavailable types are greyed out) Download Icon: Download WIM file Disk Icon: Download ISO file Harddisk Icon: Download VHD file 3. Upload files to your configured Azure Storage Account. In a popup you can choose which file types should be uploaded 4. Delete the image version. This deletes all files associated with this image version!

Copy an existing Image Type

	An Image Type can be created in different ways. If you want to create a Image Type, which is similar to a already existing one, but with minor changes, you can copy the Image Type. The desired image can be copied in two ways. Either by clicking the copy button in the Image Type overview or by pressing the copy Image Type button in the Image Type settings. Once you copied the Image Type you'll be redirected to the add Image Type page with already pre-filled values from the Image Type you selected in advance.

Filter for Base WIM

	There are many Base WIMs available which makes it difficult to find the right one at some point. To avoid searching too long and make searching more comfortable, you can use the filters. Filters can be found in the image type settings right above the Base WIM selection. The filters can be combined in any different ways to only show the images you want.

Use WebHooks for notifications

	We offer you to get notifications directly to your preferred webhook as well. Webhooks can be used for various purposes. For example, to automate processes in AVD after a new image has been uploaded or automatically download WIM files from Azure and then import them into Config Manager and much more. Therefore, navigate via "Manage" to "User / Tenant Settings". In the "Tenant Settings" you can enter the webhook address under "Webhook URL" and verify the URL with the Test Webhook button. If the test is successful, the following message appears under the enterd URL: "Webhook URL configuration is valid. If you would like to get notifications to the previously validated Webhook, you have toggle the "Notification to Tenant Webhook" check box. Save the configuration with the Save button and your settings will be applied.

Activate multi-factor authentication

	To make the sign-in more secure, you can activate MFA (multi-factor authentication). Navigate via "Manage" to "User / Tenant Settings". In the "Tenant Settings" you can then simply check the "Multi-factor authentication" checkbox. Save the configuration with the Save button and your settings will be applied. The next time someone wants to sign in to your tenant, another page will appear after entering the username and password, asking for the numerical code that was sent to you by email.

Use a custom autounattend.xml

For now if you would like to use a custom autounattend.xml you could send us that file per e-mail to support@basevision.ch we will then putt it on the server for you.

If you would like to get an example of suche a file please send us also an e-mail.

Uninstall Modern Apps (Appx / Store Apps)

	With WimAsAService 4.0 we provide you an easier way, to uninstall unwanted metro apps. We create a list of available Metro Apps to uninstall for all supported images based off the lists down below. You can select apps to be uninstalled like you would select your applications. Only Apps that can be uninstall in this specific type of base image will show up on your list to not create any compatibility errors while generating your image.

Install Windows Features or Uninstall Windows Features

OnPremises Customer Documents

If you are a WimAsAService OnPremises Customer you can find here some helpful Documentation:

Adding baseWIMS,LanguagePacks and FeaturesOnDemand
File:Adding baseWIMS,LanguagePacks and FeaturesOnDemand to WimAsAService.pdf

Additional Information to Add Windows 11 BaseWIMs, Language Packs and Features on Demand
File:Additional Information to Add Windows 11 BaseWIMs, Language Packs and Features on Demand.pdf

Additional Information to Add Windows 10 21H1 BaseWIMs, Language Packs and Features on Demand
File:Additional Information to Add Windows 10 21H1 BaseWIMs, Language Packs and Features on Demand.pdf

Additional Information to Add Windows 10 20H2 BaseWIMs, Language Packs and Features on Demand
File:Additional Information to Add Windows 10 20H2 BaseWIMs, Language Packs and Features on Demand.pdf

Additional Information to Add Windows 10 1909 BaseWIMs, Language Packs and Features on Demand
File:Additional Information to Add Windows 10 1909 BaseWIMs, Language Packs and Features on Demand.pdf

Additional Information to Add Windows 10 1709 BaseWIMs, Language Packs and Features on Demand
File:Additional Information to Add Windows 10 1709 BaseWIMs, Language Packs and Features on Demand.pdf

@@ Line 174: / Line 174: @@
 |}
 Lists of the Modern App Names and if they can be uninstalled:<br><br>
+'''10.0.19044.0 /21H2 '''<br>
+[[File:InstalledAppxPackages 10.0.19044.0 Windows-10-Education 32-bit.xlsx]]<br>
+[[File:InstalledAppxPackages 10.0.19044.0 Windows-10-Education 64-bit.xlsx]]<br>
+[[File:InstalledAppxPackages 10.0.19044.0 Windows-10-Enterprise 32-bit.xlsx]]<br>
+[[File:InstalledAppxPackages 10.0.19044.0 Windows-10-Enterprise 64-bit.xlsx]]<br>
+[[File:InstalledAppxPackages 10.0.19044.0 Windows-10-Enterprise-for-Virtual-Desktops 64-bit.xlsx]]<br><br>
 '''10.0.22000.0 /W11 '''<br>
 [[File:InstalledAppxPackages 10.0.22000.0 Windows-10-Education 64-bit.xlsx]]<br>