social pharmacy d-pharm 1st year by Pragati K. Mahajan
SMS
1. Effective managing operating system
images with
SMS 2003
Operating System Deployment
Feature Pack
Ampiga Jantarapagdee, ITIL
Technology Specialist – Infrastructure Management
Microsoft (Thailand) Ltd
2. Agenda
SMS 2003 Overview
OSD Overview of key features &
scenarios
Imaging process
Capturing an operating system image
Installation of the image on the client
Positioning Automated Deployment
Services (ADS), Remote Installation
Service (RIS) and Operating System
Deployment Feature Pack (OSD)
3. Systems Management
Server 2003
Desktop Administration
New …
Product of the Year
SMS 2003 Inventory Tool
for Microsoft Updates
20,000+ customers
Desired Configuration
Monitoring
83,000+ SP1 downloads
4. SMS 2003 Capabilities
Asset Security
Management Patch
Management
Application Support for
Deployment the Mobile Workforce
Leveraging
Windows
Management Services
5. SMS Supporting the Desktop
Free Feature Packs
Operating System Deployment Feature Pack
Administration Feature Pack
Device Management Feature Pack
Other Free Tools
AdminStudio SMS Edition
Client Health Monitoring Tool
Toolkit 2
Capacity Planner
Package Definition Files
Installer with Installer Step-up Utility
Scanning Tools
IBM Systems Update tool for Microsoft SMS Image Technology built
Inventory Tool for Microsoft Updates into SMS License
Software Update Scanning Tools
Model
Inventory Tool for Dell Updates Version 3
Extended Security Update Inventory Tool
Client Packs
Advanced Client for Windows XP embedded
Software Development Kit v3.1
6. SMS OS Deployment Feature Pack
Image capture management
Steps administrators through the process of capturing an image of a
reference computer in the new Microsoft Imaging format.
OS package management
Customizes and manages the settings for individual deployments,
including notifications, distribution settings, or network settings.
User state migration
Integrates with the User State Migration Tool 2.6 to preserve user profiles
when installing new OSs.
Image deployment
Deploys OS images using the highly customizable task-based SMS 2003
infrastructure.
Reporting
Reports on specific deployments to help troubleshoot and demonstrate
deployment success.
7. SMS OS Deployment Feature Pack
Key Features
Integrated with SMS 2003
Inventory based planning/targeting
Uses SMS software distribution
SMS management of replication of images
throughout distributed enterprises
Centralized tracking and status
Advanced desktop imaging format
(Microsoft Imaging file - .WIM)
File-based and non-destructive
Eliminates duplicate files
Smaller images / high compression
(3:1 compression)
8. SMS OS Deployment Feature Pack
Key Features(2)
Advanced image installation task sequencing
User Notification balloons
State capture and restore
USMT or custom
Optional SMS advertisement
Executed during State Restore phase
Custom actions
Ability to include and execute custom installation scripts
SMS packages can be executed as part of installation
sequence
9.
10. Scenarios
Refreshed PC
(In-Place)
Help Desk Recovery
(break/fix)
Upgrade PC –
Transfer User
New PC –
No User State
11. Client Requirements
Reference computer (capturing the
image):
Windows 2000, XP, Server 2003
All must be running the SMS 2003 SP1
Advanced Client
Must be a member of a workgroup
Sysprep must be installed
Operating system must be on C:
C: must be primary and NTFS
12. Client Requirements (2)
Destination computer (deploying the image):
Through SMS software distribution
Windows NT 4.0 SP6a
Windows 2000 and later
Must be running the SMS 2003 SP1 version of the
Advanced or Legacy Client
C: must be primary and NTFS; no hidden partitions
Through RIS or Image Installation CD
Windows 98 (wipe and load)
All others
Must be configured to use DHCP
13. Client Requirements (3)
Destination computer (deploying the image):
Advanced Clients require the Advanced Client
Network Access account
Legacy Clients require the Legacy Client Software
Installation account
The hardware abstraction layer (HAL) must be the
same as the reference computer
Need a different image for each HAL type you need to
deploy images to
You can add additional hardware drivers to the
Image Capture CD and as custom actions for
image deployment
14. Technologies Used
WIM – Microsoft Imaging file
Captured image file based format
Windows Preinstallation Environment
(Windows PE 2004)
Reference computer preparation
Destination computer configuration
Boot from CD or RIS
Diskpart
Partitioning option for installation
USMT v2.6 – User State Migration Tool
Integration for user state capture and restore
Unattended operation, multi-user profiles
Not part of OSD, available as web download
15. Image Capture Process
1. Admin creates Image 2. Admin configures 3. Insert Image
Capture CD Reference computer Capture CD
Create Image Capture OS + Service Packs Capture settings
CD Wizard Applications (Office, etc) Output options
Must be bootable CD SMS Advanced Client Click “Capture”
Sysprep, etc
Prepare Begin
Machine Capture
4. Image Capture Wizard 5. Computer boots from 6. Capture image
prepares computer Image Capture CD Generate WIM
Sysprep Boot into WinPE image
Shutdown Capture wizard continues
16. Capturing An OS Image
Preparing the reference computer
Creating an Image Capture CD
Capturing the OS image
17. Image Distribution Process
OS.WIM
1. Create image package from 2. Create an image
captured .wim file program and configure
deployment settings
3. Deploy package to 4. Create collection of
distribution points destination computers
to advertise to
18. Creating And Distributing
An OS Image Package
Create OS Image Package
Create OS Image Program
Distribute to a distribution point
Advertise the OS Image Program
19. Introduction to OSD
How OS Deployment Works
SMS inventory is used to create
1 a “collection.” Computers are Target Machine Compressed WIM OS
targeted for refresh. 5 image is downloaded
Client receives and installed.
2 advertisement for OS Image is personalized
refresh, saves user state. 6 and boots to full OS with
SMS Client SMS agent.
SMS delivers bootable
3 Windows PE image using Agent Pre-OS SMS Advanced Client
WIM to existing OS
7 agent starts up.
partition.
SMS delivers role-
Bootable
Hard
Boot files are modified, OS 8 based applications and
Windows PE
4 reboots to Windows PE
SMS Disk post-OS configuration.
on hard disk, then
Server User state is restored.
cleans disk. Windows PEDelivery
OS Image Delivery Delivery
Application Image
SMS Advanced Client Agent
MOM Windows-Present
Logs all
activity
20. User State Migration
USMT in OS Deployment
SMS inventory is used to create
1 a “collection.” Computers are
Target Machine
5 Compressed WIM OS
targeted for refresh. image is downloaded
and installed.
Client receives Image is personalized
2 advertisement for OS 6 and boots to full OS with
refresh, saves user state. SMS agent.
SMS delivers bootable SMS Client SMS Advanced Client
3 Windows PE image using Agent Pre-OS 7 agent starts up.
WIM to existing OS SMS delivers role-
partition. 8 based applications and
Boot files are modified, post-OS configuration.
4 reboots to Windows PE
OS User state is restored.
on hard disk, then
Windows PE Image Delivery
cleans disk.
SMS SMS Advanced Client Agent
Server Windows-Present
MOM
Logs all
activity
21. Deploying An OS Image On
A Destination Computer
Force advertisement retrieval
Respond to user notification
Initiate image install
22. Comparing ADS, RIS, And OSD
Typical use of each
Automated Deployment Services (ADS):
Large-scale, administrator-initiated, high-speed,
task sequence-driven deployments of servers in
data centers or corporate environments
Remote Installation Services (RIS):
User-initiated, Active Directory configuration
based deployments in corporate environments
Operating System Deployment (OSD):
Large scale, administrator-initiated, task
sequence-driven deployments of desktops in
corporate environments
23. Comparing ADS, RIS, And OSD
Choosing which to use
For desktop deployments:
Administrator scheduled/managed desktop
deployments: OSD
Self-service deployments: RIS
For server deployments:
Simple server deployment: OSD
Complex server deployment: ADS
Self-service server image deployment: RIS
24. Summary
SMS adds operating system image
deployment with the OS Deployment
Feature Pack
Requires SMS 2003 SP1
Deploys Windows 2000, Windows XP,
and Windows Server 2003 images
Image includes the Advanced Client
Target systems can be Windows 98
or higher
SMS clients or bare metal systems
28. Installing OS Deployment
Feature Pack
Requires SMS 2003 SP1
Does not operate stand alone
Download from the public SMS Web site
http://www.microsoft.com/smserver/downloads/
2003/osdfp.asp
75 MB download
Extract SMS2003OSDFP_Enu
Six files are extracted, including user’s guide
Run OSDeployment_Setup.exe to install on
site server
29. Microsoft TLA Decoding
TLA – Three-letter acronym HAL – Hardware Abstraction Layer
BDD – Solution Accelerator for SA – Software Assurance
Business Desktop Deployment SA – Select Agreement
OSD – SMS 2003 OS Deployment LIS – Local Install Source
Feature Pack
ZTI – Zero Touch Installation RIS – Remote Installation Server
CIS – Computer Imaging System WSH – Windows Scripting Host
ZTP – Zero Touch Provisioning VBS – Visual Basic Script
WinPE – Windows Pre-Installation WMI – Windows Management
Environment Instrumentation
WIM – Windows Imaging PXE – Preboot eXecution-
Environment
ACT – Application Compatibility
Toolkit MCS – Microsoft Consulting
Services
ACT – Access Conversion Tool
ORK – Office Resource Kit MSI – Windows Installer Software
Packages
SMS – Systems Management
Server BITS – Background Intelligent
CIW – Custom Installation Wizard Transfer Service
GPO – Group Policy Object CER – Corporate Error Reporting
USMT – User State Migration Tool
30. Log Files – And What They Do
Log File Location Associated with Description and use for
which OSD process troubleshooting
OSDAgent.log c:minintsmsosdosdlogs
c: minint smsosd All Deployments Main log. This should be the first
place you look to determine what
step failed.
OSDEnv.log c:minintsmsosdosdlogs
c: minint smsosd All Deployments Indicates when OSD Environment
variables are set.
OSDWinLogon.log c:minintsmsosdosdlogs
c: minint smsosd All Deployments Created at the start of the State
Restore phase.
OSDInstallWIM.log c:minintsmsosdosdlogs
c: minint smsosd All Deployments Logs image installation operations.
IDUser.log c:minintsmsosdosdlogs
c: minint smsosd In-place deployment
In- User notification log.
IDUserNotification.log c:minintsmsosdosdlogs
c: minint smsosd In-place deployment
In- User notification log.
MachineState.log c:minintsmsosdosdlogs
c: minint smsosd In-place deployment
In- Logs machine state migration
information (machine name, IP
Address, Registered Owner/Org)
31. Log Files (2)
OSDLaunch.log c:minintsmsosdosdlogs
c: minint smsosd In-place deployment
In- OSD Bootstrap. May contain errors
if the Advanced Client Network
Access account is not configured
correctly.
SMSCMT.log c:minintsmsosdosdlogs
c: minint smsosd In-place deployments
In- Logs SMS Client migration
information (site code, client GUID)
WinPEInstall.log c:minintsmsosdosdlogs
c: minint smsosd In-place deployments
In- WinPE installation information.
OSDInstallWizard.log c:minintsmsosdosdlogs
c: minint smsosd LRIP deployments Logs startup operations when doing
a LRIP deploy.
OSDShell.log c:minintsmsosdosdlogs
c: minint smsosd LRIP deployments Launches the OSD Install Wizard.
OSDSWDProgramExec.log c:minintsmsosdosdlogs
c: minint smsosd Custom Action Logs Run SWD Program Actions.
OSDUsmtScanstate.log c:minintsmsosdosdlogs
c: minint smsosd Custom Action Logs Capture User State operations
OSDUsmtLoadstate.log c:minintsmsosdosdlogs
c: minint smsosd Custom Action Logs Restore User State operations
32. Log Files (3)
osdRebootSystem.log c:minintsmsosdosdlogs
c: minint smsosd Custom Action Logs Reboot System operations
osdConnectToUNCPath.log c:minintsmsosdosdlogs
c: minint smsosd Custom Action Logs Connect to UNC operations
scanstate.log c:minintsmsosdosdlogs
c: minint smsosd Custom Action USMT scanstate log.
loadstate.log c:minintsmsosdosdlogs
c: minint smsosd Custom Action USMT loadstate log. Nbnbn
setupapi.log %windir%
windir% Windows mini-setup
mini- Windows mini-setup log. Can be
mini-
viewed after deployment to see if
there were any problems with mini-
mini-
setup.
setupact.log %windir%
windir% Windows mini-setup
mini- Windows mini-setup log. Can be
mini-
viewed after deployment to see if
there were any problems with mini-
mini-
setup.
setuperr.log %windir%
windir% Windows mini-setup
mini- Windows mini-setup log. Can be
mini-
viewed after deployment to see if
there were any problems with mini-
mini-
setup.
33. Additional Resources
Documentation Locations
SMS Web site:
http://www.microsoft.com/smserver/techinfo/
Microsoft TechNet:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/
Business Desktop Deployment solution accelerator
http://www.microsoft.com/desktopdeployment
SMS FAQ for OSD
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/
techfaq/tfaq14.mspx
USMT 2.6 Download site
http://www.microsoft.com/downloads/details.aspx?FamilyId=4A
F2D2C9-F16C-4C52-A203-8DAF944DD555&displaylang=en
34. Additional Resources
Community Resources
Microsoft
http://www.microsoft.com/communities/default.mspx
MYITForum
http://www.myitforum.techtarget.com
Duncan McAlynn’s Microsoft Management Blog
http://msmvps.com/lduncan/articles/19685.aspx
Most Valuable Professional (MVP)
http://mvp.support.microsoft.com/
John Savill’s FAQ for Windows
http://www.windowsitpro.com/windowsnt20002003faq/
OSD Branch Solution from 1E (Booth 623)
http://www.1e.com/SoftwareProducts/OSDBranch/Index.aspx
OS Migration Solution (Swimage) from Intrinsic
http://www.intrinsic.net/services/expertise/os_migration.html
