In this session we will cover the advantages and use cases for utilizing Scripted Installs when deploying Windows. We will look into how to create, modify, and deploy scripted installs also. Learn more: http://dell.to/1GDYpr8
4. Dell World User Forum
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
5. Dell World User Forum
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
7. Dell World User Forum
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. 8 ServicesRoom for textDell - Internal Use - Confidential
Volume Activation Models
Key Management Service (KMS)
Activate within your network
Default Volume Activation
• Reimaging
• Downgrade
• Transfer
Multiple Activation Key (MAK)
Activate Online
Volume Activation Management Tool (VAMT)
Active Directory Based
Activate when joining domain
9. Dell World User Forum
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
10. Dell World User Forum
Drivers Share
• Located at KBOXIPdriversKBE_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 KBOXIPdriversWINDOWS_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
11. Dell World User Forum
Driver Feed
• Best method to inject drivers into Scripted Installations
• Located at KBOXIPdrivers_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
12. Dell World User Forum
Setup.exe
All OS’s
Copy_drivers.vbs
All OS’s
PC uses on-board UNDI NIC driver
WinPe uses Nic drivers Windows
7/8 from the imported
KBE_Windows_86/64 folder
New 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
14. Dell World User Forum
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
15. Dell World User Forum
Exercise: Create a
Scripted Installation
16. Dell World User Forum
Scripted Installation Detail
• Customize Unattend with Wizard
• Cannot change uploaded Source Media
• Can change Installation Tasks
• Can duplicate build
18. Dell World User Forum
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
20. Dell World User Forum
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
21. Dell World User Forum
Exercise: Deploy a
Scripted Installation
22. Dell World User Forum
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
23. Dell World User Forum
User State Profiles
• Systems can be deployed with captured User States
• Integrates with KBE for Offline Scan
• Scheduled using Boot Actions
24. Dell World User Forum
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
27. Dell World User Forum
Enable Administrator Account
• Customize Unattend in Setup Configuration
• Click Show to access
• Find </RunSynchronousCommand> and add
28. Dell World User Forum
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
30. Dell World User Forum
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
31. Dell World User Forum
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
32. Dell World User Forum
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-
1234567
Variables
$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
34. Dell World User Forum
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?
36. Dell World User Forum
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
Hinweis der Redaktion
Differences in licensing types:
http://blogs.technet.com/b/uktechnet/archive/2013/05/14/what-s-the-difference-between-oem-retail-and-volume-licenses.aspx
Driver Feed
The “Driver Feed” tab however, is different from the “Drivers” tab in two main ways. First, upon downloading a feed for a specific Dell model and operating system the contents are stored in one of the other three visible samba shares, “Drivers_Postinstall”. The second main difference is how and when they are used by a deployment. The “Drivers” share can only used by boot environments and “Scripted Installations” whereas “Driver Feeds” can be used by any of the three Windows deployment options. The reason this is possible is because unlike the “Drivers” which are added to the uploaded source media as if it was part of the original source, “Driver Feeds” are added to the deployment on the fly using DISM.
IMAGE PLACEHOLDER. GET NEW IMAGE FROM 3.7.
IMAGE PLACEHOLDER. GET NEW IMAGE FROM 3.7.
If Kent’s tool is complete by DWUF, replace 2nd bullet with newer information about new tool.