MDT Installation - Importing Windows and Apps (Part 5)

Part 1, WDS and DHCP network dependencies for installing Windows systems over the network were installed and configured. 

Part 2, MDT, ADK and PE for ADK were downloaded and installed.

Part 3, the service account and share permissions are configured.

Part 4, Custom Settings and Bootstrap.ini are created.

Wow, when I started this series I didn't appreciate the number of screenshots and the how many pages it would take, thanks for persevering.

In part 5, Windows 10 x64 1909 will be imported as an 'Operating System' and Google Chrome as an 'Application'. 

Make the 'Deployment Workbench' open and browse to 'Operating System'.

I'm a little OCD and like folder structures to manage the content. Create a 'Windows 10' folder by right clicking and 'New Folder'. This folder will be used for any Windows 10 OEM imports, but not for any custom captures, they will get their own folder.

Right click on the new 'Windows 10' folder and click 'Import Operating System'.

Select 'Full set of source files' 

The Windows .iso mounted under F:\, likely a different drive on your systems.

Provide a descriptive name. 

Review the 'Summary'.

Wait while the files are imported into MDT.

View the script and save for later. 

The number of versions available will depend on the media, don't worry if only 1 version is list after the import. 

That's all that's required to import OEM media in to MDT.

The importing of an application follows a similar wizard driven process, however the unattended switches for differing applications can be different. Msi files tend to be broadly standardised. Even so, there can be additional switches so its always worth reviewing documentation first. Any problems then try installing the application from the command line and monitoring the event logs for success or failure events.

Not all applications support unattended installations, annoying yes, a problem no. Any application that does not silently install will prompt during the deployment. The deployment will pause whilst the installation wizard is completed.

 

Download 'Google Chrome Enterprise' and extract the .msi file and copy to a new folder, ensuring that nothing else is in the folder, or it will also be uploaded into MDT. 

Browse to 'Applications', right click 'New Folder', then right click 'New Application'.

Select 'Application with source files'.

Complete the application details. Its worth completing the version input, it makes future releases easier to import and manage.

Browse to the application installation files.

Check the 'Move the files to the deployment share instead of copying them', saves on duplication and disk space.

Update or accept the default name.

At this point the unattended command is required. If your not sure open the command prompt, cd to the .msi location, type the name of the file and add the '/?' switch. 

For Google Chrome and most other .msi the following should suffice.

msiexec.exe /i "GoogleChromeStandaloneEnterprise64.msi" /quiet /norestart /l C:\MININT\SMSOSD\OSDLOGS\_Chrome.log

The path may seem a bit different. During the deployment any *.log file written to that location will automatically be saved up to the MDT Logs Share upon completion. 

Review the 'Summary'

Google Chrome is now ready to be added to the current non-existent Task Sequence. One step at a time.

Review the newly created application

Part 6, Importing Packages and Drivers.