K2000 Scripted Installations

1Dell World User Forum

UFIL509: K2000 Scripted Installations

Jeff Plaza, Senior TrainerOlivier Herve, Senior Trainer

Dell WorldUser Forum


Agenda

• Introduction and Preparation

• Creating Scripted Installs (SI)

• Deploying Scripted Installs (SI)

• Beyond Basics

3 Dell World User Forum

Introduction


Introduction to Scripted Installs

• OS deployment via Windows source media

• Hardware Agnostic

• Utilizes Driver Share and Driver Feed

• Utilizes application library

• Unattended Installation

• No Sysprep using installation answer file


Preparation

• Media Manager uploads Source Media

• Name Descriptively (be specific)

• Follow a naming convention (i.e. OS name, Architecture, Updates, Build)

• Mount ISOs before uploading

Dell World User Forum

Exercise: Source Media Upload


Types of Media

• Full Packaged Product (FPP)– Retail Purchase– Limited License Rights– Full or Upgrade

• Original Equipment Manufacturer (OEM)– Pre-installed– OEM Support– Downgrade Rights

• Volume Licensing (VL)– Multiple Agreement Types– Multiple License Rights

8 ServicesRoom for text Dell - Internal Use - Confidential

Volume Activation ModelsKey Management Service (KMS)Activate within your networkDefault Volume Activation

• Reimaging• Downgrade• Transfer

Multiple Activation Key (MAK)Activate OnlineVolume Activation Management Tool (VAMT)

Active Directory BasedActivate when joining domain


WinPE

• Windows PE 3 (AIK)– Recommended for Windows 7 and below deployments– Included in WAIK

• Windows PE 4 (ADK 8.0)– not useful since users are on Windows 7 or 8.1

• Windows PE 5 (ADK 8.1)– Recommended for Windows 8 and above deployments– Included in WADK

• Driver Packs– KACE Driver Packs are PE build specific


Drivers Share

• Located at \\KBOXIP\drivers\KBE_Windows_x86– Holds KBE Drivers– Network and Storage drivers ONLY– RAW files only – no .zip or .exe packages– Adding drivers requires re-cache

• Located at \\KBOXIP\drivers\WINDOWS_OS– Network and Storage drivers ONLY– RAW files only – no .zip or .exe packages– Adding drivers requires re-cache– Slipstreamed into installation– Using drivers_postinstall preferred


Driver Feed

• Best method to inject drivers into Scripted Installations

• Located at \\KBOXIP\drivers_postinstall

• Library-> Driver Feed tab to enable and check for available feeds

• Provides plug and play drivers for certain Dell models

• Automatically leveraged by Scripted Installations

• Custom feeds can be created for models not found in Driver Feed tab


Setup.exeAll OS’s

Copy_drivers.vbsAll OS’s

NetworkPC uses on-board UNDI NIC driver

KBEWinPe uses Nic drivers Windows

7/8 from the imported KBE_Windows_86/64 folder

WindowsNew Windows uses NIC drivers added through

setup.exe, mid-level-task or install driver PO task for XP

- Install XP Drivers ** Run_dpinst.vbs

- Install Agent- Software installation

- Partitioning- Formating

Drivers Timeline


Creating Scripted Installations


Scripted Install Creation

Scripted Installations Types– Form Wizard (ease of use)– Upload Answer File (automated)– No Answer File (manual)

Form Wizard› Most Commonly used with SI› Unattended file makes the process automated› Very Customizable


Exercise: Create a Scripted Installation


Scripted Installation Detail

• Customize Unattend with Wizard

• Cannot change uploaded Source Media

• Can change Installation Tasks

• Can duplicate build


Deploying Scripted Installations


Updating Scripted Installations

• Official Source Media does not include all OS patches

• 3rd Party Tools to install patches - WSUSOffline

• Tasks to download and install patches

Patch 1

Patch 2

Patch 3


Exercise: Slipstream Patches


Deployment

• KACE Boot Environment (KBE) Architecture must match OS Architecture

• Deploy without an answer file for interactive or manual builds

• Use Wizard for zero touch deployments

• Always leverage Boot Actions


Exercise: Deploy a Scripted Installation


Task Engine

• Provides real time communication during deployments

• See exactly what is happening with each system during any deployment

• Optional Cancel Task button– Set on deployment detail page

• Handles complex deployment tasks, with multiple reboots, more elegantly


User State Profiles

• Systems can be deployed with captured User States

• Integrates with KBE for Offline Scan

• Scheduled using Boot Actions


Task Error Handling

• User Interface (UI) to troubleshoot errors– Command Prompt– Notepad editor– Edit Tasks.xml– Registry editor– Retry/Resume

• Default Task Error Prompt

• Ability to allow tasks to continue even if there is a non-fatal error

– Set on deployment detail page

• Error Logging– 0 = Success– Any other code = Failure


Exercise: Troubleshoot Tasks


Beyond the Basics


Enable Administrator Account

• Customize Unattend in Setup Configuration

• Click Show to access

• Find </RunSynchronousCommand> and add


Encrypting Administrator Password

• Passwords in Scripted Installations are Plain Text

• Use Windows System Image Manager to encrypt

• Overwrite contents and paste in new information

Unattend

File


Exercise: Encrypt Admin Password


Naming – WSName

• Built-in Naming Rules

• Changes computer name based on uploaded TXT file

• MAC=NAME

• Can be customized

• Runs as Postinstall task

• Requires Reboot

• Requires additional PO task to join domain

MAC Address and Name


Naming – Get/Set computer name

• Used to capture or create computer name

• Saves a file to petemp (MAC=NAME)

• Runs as Mid-Level Postinstall task

• Changes computer name prior to first boot

• Can be customized using variables

• Able to read a file or KACE DB to set name

• No restarts just first boot

• Requires additional PO task to join domain


Get/Set Computer name w/ Variables• Pre-installation Task "Get Computer Name x86“ – Run in KBE

• Post installation Task“ Set Computer Name x86 – Run in KBE prior to first boot (mid –level PO Task)

• Command line examples: setcomputername.exe /log /name:<desired text/variables>

• setcomputername.exe /name:$OS$Arch-$Serial will set the computer name to W7X64-1234567Variables

$Serial - The serial number of the client machine $Asset - The asset tag of the client machine

$Make - The manufacturer of the client machine or motherboard

$OS - The OS version of the client machine (W7,WXP,W2K8,etc)

$Model - The model of the client machine or motherboard

$Arch - The OS architecture of the client machine

$Chassis - The chassis type of the client machine $Mac - The MAC address of the active NIC


Exercise: System Name


Troubleshooting

• Windows Setup cannot install critical boot drivers– If you receive this message during a scripted installation of Windows 7 it means that there is a

driver in the driver share that is conflicting with a driver from the Windows 7 media.– Knowledge Article 113951

• If Scripted Installation fails after beginning deployment– Check Source Media – Did you upload ISO file?


Thank you.


KACE Support Portal Migrating to Dell Software Support Portal

• Starting in November, all KACE Support Portal material will be migrated to the Dell Software Support Portal

• All service requests will be submitted online or by phone

• Same great content– Knowledge base articles– Video tutorials– Product documentation– JumpStart training

• Check out the Support Portal Getting Started videos

https://support.software.dell.com/create-service-request