REFERENCES:
AUDIO
VIDEO
IT
JOBS
COMPANIES
ENTERTAINMENT INDUSTRY
Certification MCSE
:: Installing Windows 200 over
the Network ::
Setup Manager Options (Setupmgr.exe):
(deploy.cab on Win 2k CD-ROM/Support/Tools)
- Create A New Answer File
- Create An Answer File That Duplicates This Computer's Configuration
- Modify An Existing Answer File
-->Create A New Answer File option:
- Windows 200 unattended installatino
- Sysprep Install
- Remote Installation Services (RIS)
Sysdiff.exe utility: Used with Setup Manager to install Windows using difference files. Same as in Win NT 4.0.
User Intervention Level page:
- Provide Defaults: admin provides default values, user can see, accept, and change values.
- Fully Automated: fully automated; user doesn't review or change the answers supplied by the script.
- Hide Pages: any page which the script supplies all answers is hidden from the user; can't view or change.
- Read Only: user can view answers, on non-hidden pages, but cannot change.
- GUI Attended: text-mode automated; user must supply the answer fro the GUI-mode portion of the install.
Computer Names page:
- Enter series of names, or
- Name of a txt file to import (one comptur name per line listed)
- "Automatically Generate Computer Names Based ON Organization Name"
C:\Deploy\Unattend.txt
--
Prepare for Network Installation:
(Over-the-network installation method)
Target must have: 1) Pre-Boot Execution Environment
(PXE) boot ROM, or 2) Net PC Spec config, or 3) a NIC supporting this
with a remote installation boot disk
Network Services Required for RIS (add/remove
Windows Components):
DNS Service, DHCP Service, Active Directory directory services
Shared volume on same drive running Windows 2000 Server, and formatted
with NTFS
Remote Installation Services Setup Wizard
Rbfg.exe (RemoteINstall/admin/i386): Windows
2000 Remote Boot Disk Generator.
distribution server.
Distribution Server: Contains installation files from
the i386 folder on the Windows 2000 Pro CD-ROM.
Requirements for Network Installation:
- Distribution server - shared folder with contents of i386 folder
- FAT partition on the target computer (atleast 650 MB)
- Network client - software which allows the target computer to connect to the distribution software
You can create multiple distribution points for different HW configs.
It is possible to create one set of distribution folders and use them
with different answer files to install different hardware configurations.
Installing Win 2k on Win 95/98/NT, use:
Winnt32.exe - allows you to specify up to eight locations for
distribution folers.
Winnt.exe - for pre Win 95 target computers:
- creates the $Win_nt$.~1s temporary folder on the target
- copies Win 2k install files from the shared distribution folder to
the $Win_nt.~1s folder on the target.
Sample naming conventions for distribution folders: - W2000P (Windows 2000 Professional)
- W2000P1 (another Windows 2000 Professional)
- W2000S (Windows 2000 Server)
- W2000AS (Windows 2000 Advanced Server)
Creat Distribution Server:
- Connect to server where you want to install a distribution folder
- Creat folder called W2000P1
- Copy i386 folder contents to W2000P1 (distribution folder)
- Create an $OEM$ subfolder in W2000P1
$OEM$ subfolder : If located in the root of the distribution folder, it copies all the files to a temporary directory created during the text portion of the Windows 2000 Setup program.
OEMFILESPATH key: Located in the answer
file. Will allow you to create a $OEM$ subfolder located outside of the
distribution folder.
Initiating Win 2k INstallation over Network *:
- Boot from PXE enabled network clinet on target computer
- Connect to distribution folder
- Run Winnt.exe or Winnt32.exe (necessary temp files create)
- Run Win 2k Setup
Action Log: Provides a description of the actions that Setup performs. Include actions as copying files and creating registry entries. Also includes any entries that are written to the error log. Stored in the file Setupact.log.
Error Log: Contains a description of any errors that occur during setup, along with an indication of the severity of each error. The log viewer shows the suer the error log at the end of setup. Stored in the file Setuperr.log.
windir\comsetup.log = Outlines installation for Optional
Component Manager and Com+ components.
windir\mmdet.log = As a detection log for multimedia
devices, details port ranges for each device.
windir\setupapilog = Logs an entry each time a line from
an .INF file is implemented.
windir\debug\NetSetup.log = Logs activity for joining
a domain or workgroup.
--
Deploy Win 2k : Disk Duplication Method
Basics of Disk Duplication Process:
- Install and configure the OS on a test computer
- Install and configure applications and updates on test computer
- Run Sysprep.exe on the test computer to prepare for
duplication
| Table 1 | ||
| Available Switches for Winnt.exe | ||
| Switch | Description | |
| /a | Enables accessibility options | |
| /e[:command] | Specifies a command to be executed at the end of Setup's GUI mode | |
| /r[:folder] | Specifies optional folder to be installed and retained after install | |
| /rx[:folder] | Specifiel optional folder to be copied and deletes the folder after. | |
| /s[:sourcepath] | Specifies the source location of Windows 2000 files. The location must be a full path of the form x:\[path] or \\server\share\[path]. The default is the current folder. | |
| /t[:tempdrive] | Specifies a drive to contain temporary setup files. If not specified, Setup attempts to locate a drive for you | |
| /u[:answer file] | Performs an unattended setup using an answer file. The answer file provides answers to some or all of the prompts that you normally respond to during Setup. (Requires /s) | |
| /udf:id[,UDF_file} | Establishes an ID that Setup uses to specify how a UDF modifies an answer file. This switch overrides answer-file values, and the identifier determines the values in the UDB file that are used. If you don't specify a UDB file, Setup prompts for the disk containing the #Unique$.udb file. | |
| Table 1.1 | ||
| Available Switches for Winnt32.exe | ||
| Switch | Description | |
| /checkupgradeonly | Checks the computer for upgrade compatibility with Windows 200; for upgrade installations, it creates a report | |
| /copydir:folder_name | Creates another folder within the systemroot folder for Win 2k system files. ie. /copydir:My_drives to copy My_drives to system folder |
|
| /copysource:folder_name | Creates another folder within the systemroot folder, setup deletes files created with /copysource after installation. | |
| /cmd: command_line | Executes a command before the final phase of Setup | |
| /cmdcons | Adds a Recovery Console option to the OS selection screen | |
| /debug[level] [:file_name] |
Creates a debug log at the specified level. By default, it creates C:\Winn32.log at level 2 (warning) | |
| /m:folder_name | Forces Setup to copy replacement files from another location and to look in that location first. If files are present, this switch tells Setup to use those files instead of files from the default location. | |
| /makelocalsource | Forces Setup to copy all installation files to the local hard disk. Use this switch when installing Windows 200 from a CD-ROM if you want to access installation files when the CD-ROM drive isn't available later int he installation |
|
| /noreboot | Forces Setup to not restart the computer following the file copy phase, which enables a command to be entered by the user prior to completing setup | |
| /s:source_path | SPecifies the source location of Win 2k install files | |
| /syspart:drive_letter | Copies Setup startup files to HD | |
| /tempdrive:drive_letter | Places temp files on the specified drive and installs Win 2k on that drive | |
| /unattend [number] [:answer_file] |
Performs an unattended installation. | |
| /udf:id[,udf_file] | Indicates an ID that Setup uses to specify how a UDF modifies an answer file. The .UDF file overrides values in the answer file, and the identifier determines which values in the .UDG file are used. | |
Sysprep.exe (extract from Deploy.cab):
Adds a system service to the master image that will create a
unique local domain SID the first time the target computer is started
with the disk image loaded. The HD Controller device driver and the HAL
on the target and the original must be identical.
System Preparation Tools installs a Mini-Setup wizard to the master image.
Mini-Setup Wizard: Runs the 1st time the target computer
is started. Provides: End-User license agreement, Product ID, Regional
Settings, User Name, Company, Network Config, Workgroup/Domain, Time Zone)
Sysprep.inf: Provides answers to the Mini-Setup wizard
on the target computer; can specify customized drivers.
Sysprep folder: By default created at the root of the
drive image on target and plases Sysprep.inf in this folder.
----------
Upgrading To Windows 2000:
Win NT 3.1 or 3.5 must upgrade to Win NT 3.51 or NT 4.0 first
Generate a Hardware Compatibility Report:
- run Winnt32/checkupgradeonly
- run the Chkupgrd.exe utility "Readiness Analyzer"
Directory Service Client upgrades: Upgrade for Win 95/98
computers that do not support Active Directory features. Installing Active
Directory services will allow:
Clinets/Win9x folder on Win 2k Server or AS CD-ROM, run Dsclient.exe
- User fault-tolerant Dfs
- Search Active Directory directory services
- Change your password on any domain controller
Slipstreaming Servie Packs:
So service packs can be integrated with Win 2k Pro installation files.
Update.exe with -:distribution_folder
switch, to apply a new service pack
a place where computer technology and media converge
Copyright 2003 © DropTheScience.com All rights reserved.
Design by TemplatesBox.com