Transcript events.attachmate.com

Scott Drucker, Systems Engineer
Migrating to Microsoft Vista with WinINSTALL
Agenda
• PXE Technlogy
–
–
–
–
–
–
–
–
–
–
–
–
–
PXE Defined
PXE Overview
PXE Environment
DHCP Specifics
WinINSTALL PXE Server
PXE Clients
PXE Hardware
Installation of Windows Vista via PXE
WinINSTALL Architecture
Configuring WinINSTALL PXE
.sif File Details
Cmdlines.txt File Details
Product Walk-through
2
PXE defined
• Preboot eXecution Environment
– NIC as a bootable device
– Download and execute a boot program
– Executes after BIOS and before OS loads
• Specification created by Intel
– First version in 1998
– Most recent revision is 2.1 done in 1999
• Incorporated into Intel’s Wired for Management (WfM)
– Implemented by BIOS and Hardware vendors
– Supported in most PCs shipped after 2000
3
PXE Overview
DHCP
Server
PXE NIC
Broadcast
PXE Client
PC
DHCP
Response
PXE NIC
Request
PXE Server
Sends NBP
PXE
Server
PXE Environment
•
•
•
•
•
•
DHCP is required
Not possible with static IP environment
Generally use a PXE server per subnet
DHCP server must support server options
Windows 2000/2003 Svr DCHP Server is compatible
DHCP routers and firewalls such as Linksys, Netgear, DLink etc. are typically not compatible
DHCP specifics
• Two DHCP Server Options must be configured:
– Option 66: IP/Network Name of PXE Server
– Option 67: Path to boot program on PXE server
• WinINSTALL configures these automatically when possible
• In some cases, these options at a per Server level
• With VLANs or multiple scope configurations, they are set
at Scope level
WinINSTALL PXE Server
•
•
•
•
•
•
•
Responds to PXE NIC requests directs its way by DHCP
Contains a TFTP file server
Delivers Network Boot Program (NBP)
Delivers OS installation files, Drivers etc.
This does not have to be a dedicated machine
Deployed and managed from the WinINSTALL console
Runs as a sub-component of the WinINSTALL Server
Agent
PXE Clients
•
•
•
•
Must be PXE-capable
BIOS support for network booting
NIC support for PXE specification
Two versions: DHCP-based or RPL (Remote Program
Load)
– RPL used in NetWare environments
– NICS may vary in support – RPL-only NICS will not work in
Windows Networking environments
• Non-PXE-capable machines can supported using bootable
floppy disk image
PXE Clients
•
•
•
•
BIOS support for network booting enabled
NIC support for PXE and enabled/flashed boot ROM
BIOS boot order - Network Boot before hard drive
Two PXEs: DHCP-based or RPL
– Remote Program Load used in NetWare environments
– NICS may vary in support – RPL-only NICS will not work in
Windows Networking environments
• Non-PXE-capable machines can be supported using
bootable floppy disk image
PXE Hardware
• Nearly all machines sold after 2000 meet requirements
• PXE may be disabled in new PCs BIOS even if
supported
• Some NICs ship with boot ROM disables/unflashed
• These settings vary with different BIOS and NIC
vendors
• Refer to manufactures documentation for details
Installation of Windows Vista via PXE
•
•
•
•
Machine powers on, BIOS loads, checks devices etc.
BIOS give control to first device in boot order
PXE client queries for IP from DHCP Server
The client queries a 2nd time and receives the PXE Server
and Boot File name (DHCP Proxy Server)
• TFTP is used to download the boot file name
• The boot file is executed and queries the PXE Server on
port 4011 for what it should do
• The server then:
– Replies with a Reset Command
– Path to the WinPE on the PXE Server
Installation of Windows Vista via PXE cont
• The client TFTP’s WinPE
• WinPE connect to the PXE Server using RPC
• Through RPC, it receives
– Credentials
– Unattended.xml
– Path to the image file
• The image file is transferred to the client using Windows
Networking (SMB)
• After the image is downloaded, the client reboots
Installation of Windows Vista via PXE cont
• Unattended.xml file settings are applied
Differences with Windows Vista Install
• The main difference is that the unattended file used for
Windows XP Installation, .sif is replaced by the
unattended.xml file
• Additionally, where WinINSTALL installs Windows XP by
copying down the i386 OS Install files, Vista uses an image
Windows Vista Unattended.xml File
• The unattended.xml file contains all the same kind of
information as you would see in the traditional WINNT.sif or
unttend.txt file
–
–
–
–
–
–
–
–
–
Full Name, Organization, Key
Network Location, Protecting your PC, Time Zone
User Accounts
Computer Name
Registered Organization
Registered
OwnerResolution
Refresh Rate
Color Depth
Windows Vista Unattended.xml File
–
–
–
–
–
–
–
–
–
Enable AutoLogon
AutoLogon Username
AutoLogon Password
AutoLogon Logon Count
Component Configuration
Enable Domain
Unattend Join
Domain Add Username
Domain Add Password
Just a few items, here is a copy of a completed XML File to view
WinINSTALL Console
WinINSTALL Architecture
PC / PXE
Client
PC / PXE
Client
PC / PXE
Client
DHCP
Server
WinINSTALL
Agent
WinINSTALL
Database
WinINSTALL
Server/Share
PXE Server
Reporting
Scheduling
WinINSTALL
Management Console
Configuring WinINSTALL PXE
• Configuring a WinINSTALL PXE Server
– Upload OS installation files, device drivers, utilities etc.
– Upload Windows Hotfixes
– Configure PXE Server settings
• Creating PXE Client Reset Templates
–
–
–
–
Installation behavior
Locale settings
Configure software installations
Configure user Personality/Data restoration
• Reusable Templates apply to all hardware systems
Product Walk-through
Remediate
& Update
User
Zero-Touch OS
Install
Add Machine
to
Network/Domain
IT / Help Desk
Restore Required
Troubleshoot
Guidelines
Software
Inventory
Centralized
Console
Remote
Management
Package &
Deploy Apps
Template Reuse
Restore Data
& PC
Personality