WimAsAService Tutorials

From baseVISION Wiki
Jump to: navigation, search

To help you start with our Service, we have recorded some Video Tutorials for you.

Generel 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:
Generate process WaaS v01.png

Step Description
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:

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 Windows Features or Uninstall Windows Features

When entering the Feature Names this must be done with case sensitivity.

Attention:When adding NetFx to a Server always make sure you add the corresponding ServerFeatures first
(e.g. NetFx3ServerFeatures,NetFx3)

Lists of the Feature Names and their default Install state you find here:
10.0.15063.0 /1703
File:FeaturesList from Windows 10.0.15063.0 Windows-10-Education 32-bit.xlsx
File:FeaturesList from Windows 10.0.15063.0 Windows-10-Education 64-Bit.xlsx
File:FeaturesList from Windows 10.0.15063.0 Windows-10-Enterprise 32-bit.xlsx
File:FeaturesList from Windows 10.0.15063.0 Windows-10-Enterprise 64-bit.xlsx

10.0.14393.0 /1611
File:FeaturesList from Windows 10.0.14393.0 Windows-10-Enterprise 32-bit.xlsx
File:FeaturesList from Windows 10.0.14393.0 Windows-10-Enterprise 64-bit.xlsx

File:FeaturesList from Windows 10.0.14393.0 Windows-Server-2016-Datacenter 64-bit.xlsx
File:FeaturesList from Windows 10.0.14393.0 Windows-Server-2016-Standard 64-bit.xlsx

Uninstall Modern Apps (Appx / Store Apps):

Lists of the Modern App Names and if they can be uninstalled:
10.0.15063.0 /1703
File:InstalledAppxPackages 10.0.15063.0 Windows-10-Education 32-bit.xlsx
File:InstalledAppxPackages 10.0.15063.0 Windows-10-Education 64-Bit.xlsx
File:InstalledAppxPackages 10.0.15063.0 Windows-10-Enterprise 32-bit.xlsx
File:InstalledAppxPackages 10.0.15063.0 Windows-10-Enterprise 64-bit.xlsx

OnPremis Customer Documents

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

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