MCDST 70272: Supporting Users and Troubleshooting Desktop Applications on a Microsoft Windows XP Ope

1
MCDST 70-272 Supporting Users and
Troubleshooting Desktop Applications on a
Microsoft Windows XP Operating System
Chapter 6 Installing Office 2003
2
Objectives

• Install Microsoft Office 2003
• Troubleshoot application installation problems
  using the Setup.exe log file
• Troubleshoot application installation problems
  using the Installer Log file

3
Installing Microsoft Office 2003

• Skills required to support Office installations
• Verify that a particular computer conforms to
  Microsofts requirements for Office
• Use the Setup and Installer programs to install
  Office
• Explore the setup sequence for the installation
  of Office
• Use local installation sources to install Office
  and to add features to an existing Office
  installation
• Use Microsoft Product Activation antipiracy
  technology to verify licensing

4
Installing Microsoft Office 2003 (continued)

• Skills required to support Office installations
  (continued)
• Use the On First Use feature that permits users
  to install additional features on demand
• Use the Self-Healing feature to reinstall missing
  or corrupt program files
• Add applications with Add or Remove Programs
• Use the Rollback feature to remove a failed
  installation

5
Installing Microsoft Office 2003 (continued)

• Skills required to support Office installations
  (continued)
• Create an administrative installation point to
  place the Office program on a server
• Install Office from a shared image
• Assist with the installation of Office using
  Group Policy
• Create log files
• Verify the local installation source

6
Verifying Installation Requirements
Table 6-1 Minimum requirements for Office
7
Verifying Installation Requirements (continued)

• My Computer Properties
• Used to verify
• Processor speed
• Installed memory (RAM)
• Windows operating system
• Service packs
• Local Disk Properties, General tab
• Used to verify the available free space for
  Office and installation files

8
Verifying Installation Requirements (continued)
Figure 6-1 My Computer Properties
9
Verifying Installation Requirements (continued)
Figure 6-2 Local Disk (C) Properties
10
Verifying Installation Requirements (continued)

• Local Disk Properties, Hardware tab
• Used to verify the availability of a CD-ROM or
  DVD drive for the Office CD
• Display Properties
• Used to verify the screen resolution

11
Verifying Installation Requirements (continued)
Figure 6-3 Hardware tab showing DVD/CD-ROM
12
Verifying Installation Requirements (continued)
Figure 6-4 Display Properties showing Screen
resolution
13
Using Windows Installer

• Windows Installer service (or simply the
  Installer)
• A component of the Windows XP operating system
• Provides a standard method for installing
  applications
• Reads a .msi file and performs these tasks
• Copying files to the hard disk
• Making additions and updates to the registry
• Creating shortcuts on the desktop
• Displaying dialog boxes to query for user
  installation preferences

14
Using Windows Installer (continued)

• Benefits gained from using the Installer
• Transactional operations
• Installation on First Use
• Self-Healing
• Installation in locked-down environments
• Change or Modify
• Update

15
Using Windows Installer (continued)

• Installer allows you to choose from
• Run from My Computer
• Files are installed on the local hard drive and
  run locally
• Run from CD
• Program files are run from the CD
• Installed on First Use
• The feature or application shows up on the menu
  but is not installed until your user selects the
  function from the menu
• Not installed
• No files are copied and your user is not informed
  of the option

16
Exploring the Setup Sequence for Office

• Basic process of installing Office
• Insert the CD
• The Setup program runs
• Follow the on-screen instructions

17
Exploring the Setup Sequence for Office
(continued)
Table 6-2 Files used to install Office
18
Exploring the Setup Sequence for Office
(continued)

• Tasks performed by Setup at the start of the
  install process
• Reads the Setup.ini file and passes this
  information to the Installer
• Installs ose.exe to copy the required
  installation files to the hard disk on the local
  computer
• This occurs only when you are installing from the
  Office CD or a compressed CD image on the network
• Calls the Installer (Msiexec.exe) to finish the
  installation and creates the Setup log file

19
Exploring the Setup Sequence for Office
(continued)

• Tasks performed by the Installer
• Reads the contents of the .msi file for specific
  information defined for the installation
• Reads the contents of the .mst file, which
  customizes the installation
• Completes the installation of the application

20
Using Local Installation Sources

• During installation from the Office CD or an
  image of the CD on the network
• Setup installs the Ose.exe program on the drive
  on the local computer that has the most free
  space
• Ose.exe copies a single cabinet (.cab) file to
  the local computer and extracts the files to a
  hidden folder
• If there is enough space, Ose.exe also copies the
  entire install source to the local computer

21
Using Local Installation Sources (continued)

• Office 2003 can be installed by running the Setup
  program from either
• The Office CD
• A compressed image from a network share
• Create the compressed image on the network share
  by copying the files on the Office CD to the
  network share
• The local installation source on the local
  computer can be created from either the Office CD
  or the network share

22
Product Activation

• Microsoft Product Activation
• An antipiracy technology designed to verify that
  the product has been legitimately licensed
• Hardware hash
• A nonunique number generated by the activation
  process from the PCs hardware configuration
• Used to identify the physical computer
• Methods to activate Office
• Internet-based
• Telephone

23
Using the On First Use Feature

• On First Use feature
• The feature or application appears on the menu
  but is not installed until the user selects the
  function from the menu
• Allows the user to customize the features from an
  approved list without the intervention of a
  person with administrator privileges

24
Self-Healing Feature of Office

• Office can automatically repair itself if it
  detects a corrupt component or application
• A library of file names maintained in the
  registry helps the detection system determine
  what files should be replaced when a specific
  application or component cannot be started
• If required, Office calls the Installer and
  reinstalls only the affected files and registry
  entries

25
Adding Applications with Add or Remove Programs

• Add or Remove Programs can be used to
• Add programs
• If the Local Installation Point was created on
  the hard disk, the change proceeds without the
  need of the Office CD
• Remove programs
• To open Add or Remove Programs
• Click Start
• Click Control Panel
• Double-click Add or Remove Programs

26
Using the Rollback Feature

• Rollback feature
• Allows you to recover gracefully from a computer
  or power failure
• Can be used if an Office install fails or you
  cancel Setup before the process is completed
• When the Rollback feature is used to undo an
  installation
• All files and registry settings created by the
  Installer are removed
• Any files or registry entries that were removed
  are reinstalled

27
Using Administrative Installation Points

• When an Administrative Installation Point is
  used, the installation bypasses the Setup program
  and is managed by the Installer
• Organizations that use Group Policy use
  Administrative Installation Points
• An Administrative Installation Point is created
  when you run Setup with a switch from the Start
  and Run
• An Administrative Installation Point contains the
  extracted files from the Office CD

28
Installing from the Administrative Installation
Point

• From the Administrative Installation Point, you
  can run the Installer against the .msi file on
  the network share
• The Installer copies the extracted files directly
  using the Administrative Installation Point as
  the source
• When installing Office from an Administrative
  Installation Point, the Install on First Use
  feature automatically returns to the same
  location for the additional files

29
Installing Office Using Policy-based Installation

• Group Policy the policy used by Active Directory
  to manage the settings on desktop computers
• Using Group Policy to deploy Office can be a good
  choice for
• Small- or medium-sized organizations that have
  deployed Active Directory
• Organizations that cover a single geographic area
• Organizations with consistent hardware and
  software configurations on both desktop computers
  and file servers

30
Using Active Directory

• Active Directory provides the benefits of
  centralized administration of users and computers
• Entities that would typically be stored in Active
  Directory in a Microsoft Windows network
• User accounts
• Contain information about users, such as first
  name, last name, username, and password
• Computer accounts
• Contain information about computers, such as
  computer name, operating system, and description

31
Using Active Directory (continued)

• Entities that would typically be stored in Active
  Directory in a Microsoft Windows network
  (continued)
• Organizational Units (OUs)
• Simplify administration by allowing the
  organization of objects, such as user accounts or
  computer accounts
• Group Policy Objects (GPOs)
• Define what a system will look like and how it
  will behave for a defined group of users or
  computers
• 6

32
Organizational Units

• Network administrators can use OUs to organize
  user accounts and computer accounts
• Using OUs
• Makes it easier to locate and manage Active
  Directory objects
• Allows the network administrator to apply Group
  Policy settings to control events such as
  software deployment

33
Group Policy

• Group Policy
• Used to define and control how programs, network
  resources, and the operating system operate for
  users and computers in an organization
• Applied to users or computers on the basis of
  their membership in containers such as
  organizational units
• Group Policy Object (GPO) a collection of Group
  Policy settings
• The GPO is associated with an Active Directory
  container

34
Group Policy (continued)
Figure 6-30 Active Directory and Group Policy
35
Group Policy (continued)

• Ways of installing and managing Office
  applications by policy
• Assign Office to computers
• Assign Office to users
• Publish Office to users
• Assigning Office to computers
• Office is installed on the computer the next time
  the computer starts
• Applications appear on the Start menu of all
  users
• Assigned applications are resilient

36
Group Policy (continued)

• Assigning Office to users
• Information about the software is advertised at
  your users computer on the Start menu or Windows
  desktop the next time the user logs on
• When your user clicks an Office shortcut, the
  Installer installs the application, and starts
  the application
• An application will be available only to the user
  installing the application
• Assigned applications are resilient

37
Group Policy (continued)

• Publishing Office to users
• No shortcuts are added to the Start menu
• Published applications are available to be
  installed from the Control Panel, Add or Remove
  Programs
• Published applications may be installed by
  authorized users

38
Troubleshooting Application Installation Problems
Using Log Files

• Both the Office Setup and Installer generate log
  files during the Office install process
• Log files can be used to troubleshoot issues that
  may arise during the installation of Office

39
Creating Log Files

• Log files
• Created automatically when Office is installed
• Created in a hidden folder with a name similar
  to C\Documents and Settings\admin01\Local
  Settings\Temp
• Log file names are similar to the entries in
  Table 6-3
• Setup creates a log file name similar to what is
  listed in the first row of Table 6-3
• Each invocation of the Installer creates a log
  file name similar to what is listed in the second
  row of Table 6-3

40
Creating Log Files (continued)
Table 6-3 Sample Log file names
41
Troubleshooting with the Setup.exe Log File

• Setup.exe log files can provide useful
  information that you can use to troubleshoot
  failed installations
• Setup.exe performs tasks such as
• Read the Setup.ini file
• Verify that the correct operating system and
  service pack are being used
• Start Windows Installer
• Check for installed beta versions of Office 2003
• Check the version of the Tahoma and TahomaBD fonts

42
Verifying the Local Installation Source

• Local Installation Source
• Created by Setup in the following hidden folder
  on your users computers C\Msocache\Downloadcode
  
• The amount of free disk space for the Local
  Installation Source should be greater than 240 MB
• By default, Setup retains the Local Installation
  Source after the installation is complete

43
Troubleshooting with the Installer Log File

• Tips for working with the Installer log file
• If you receive an error during installation,
  search for the error in the log file
• All log files have one or more errors that can be
  ignored
• Search for the string Note
• The actual resolution for a problem may be
  located in a note several lines above the error

44
Troubleshooting with the Installer Log File
(continued)

• Tips for working with the Installer log file
  (continued)
• Search for the string Return Value 3
• If an action performed during Setup was
  successful, a return value of 1 is noted
• If an action performed during Setup failed, a
  return value of 3 is noted

45
Summary

• Prior to installing Office, verify that the
  desktop computer meets or exceeds the minimum
  requirements
• The Installer provides a standard method for
  installing Office and other Windows applications
• Where there is an additional free disk space of
  about 240 MB, Setup copies compressed Office files

46
Summary (continued)

• Installer features
• On First Use installs a feature on-demand
• Self-healing damaged or missing program files
  are replaced
• Rollback automatically removes a failed
  installation
• Office can be activated over the Internet or by
  using a telephone
• An Administrative Installation Point can be used
  for the installation of Office

47
Summary (continued)

• If your organization has deployed Active
  Directory, Group Policy can be used to trigger
  the installation of Office
• Assign Office to a computer
• Assign Office to a user
• Publish Office to a user
• You can troubleshoot failed Office installations
  with the log files that are created during the
  installation