5. Installing Office 2003 Applications

transcript

Thomas LeeChief Technologist – QA plc

Office 2003 Live!

• Lots of Demos– Live deployment, beginning to end– Starting with nothing but product CDs– Some TV Cookery to avoid long waits!

• Demo configuration– Windows 2003 Server– Windows XP Professional

Custom Installation Wizard

pro11.msi

proplus.mst

Profile Wizard

xcopyCustomize Office

Templates

Add-ins

Office Setup Key Files

File Description

Setup.exe Office setup program

Setup.ini Setup settings file, located in Files\Setup folder

Ose.exe Office Source Engine installed by Setup.exe. Copies installation files from source to an LIS

Msiexec.exe Windows Installer. Called by Setup.exe to install Office

Msi File Windows Installer package. Used by Windows Installer to install Office

MST File Windows Installer transform. Used by Windows Installer to customize office.

Logfile_Taskn.txt Setup log file. Separate log file generated by Setup for each task.

Caching installation files locally

• Office Source Engine (OSE.exe) is installed as a service when Office 2003 is run– Copies install files to the local PC– Speeds up installation

• LIS can persist after installation

Setup.exe

• Reads the setup settings file• Determines which drive on the PC has

the most space• Verifies user has Administrative

privileges• Installs ose.exe to :

<Drive with most space>\MsoCache\Downloadcode

• If MsoCache folder already exists, setup uses that location.

Office Source Engine• OSE.exe copies a single CAB file to the

local PC and extracts the files into a hidden folder.

• This CAB has:– Office package (MSI file)– Files to support upgrades from previous

versions (Offcln.exe, Oclncore.opc, Oclncust.opc, Oclnintl.opc)

– Error reporting tools (DW.exe and Dwintl.dll)– Setup Help

Office Source Engine con’t…..

• If there is sufficient disk space OSE continues running in the background and caches the entire installation source.

• Setup can be customized to cache only CAB files required for features in your desired package.

• Post install users can (if allowed) install features on demand or run setup in Maintenance mode to add more features.

LIS Behaviour

• If Windows Installer cannot find files needed in the LIS when adding features in maintenance mode…..

………OSE runs again and copies additional CABs from original source to LIS source

• Additional sources can be specified in the MST or CMW by setting the SOURCELIST property

LIS Behaviour

• CABs require as much as 240Mb beyond what is needed for Office

• Setup can be configured to delete cache post install

• Keeping local cache helps repairs and updates– Required install files are always available

regardless of network presence

• LIS only supported on Corporate editions

LIS Options• LIS is a reliable, resilient source on the local PC• The creation and maintenance of LIS is managed

entirely by Office Setup and the OSE, not by Windows Installer.

• The entire source is cached by default• If insufficient disk space only features selected

are cached• Installing from a compressed CD image allows

Setup to create LIS• Compressed image can be copied to physical

media for offline users

Customize the LIS

• You can modify how Setup handles the LIS by customizing [Cache] section of the Setup.ini– LOCALCACHEDRIVE – a different drive for the local

installation source. – DELETEABLECACHE – Give users option to delete the

local install source at end of setup– CDCACHE – Enable or disable creation of an LIS. This

can:• Cache entire source• Cache installation files for only selected features• Or run install directly from the source and bypass LIS

Important

• Setup creates the LIS before applying the transform

• You should set the LIS properties in the Setup settings file, and not on the Modify Setup Properties page of the CIW

Creating the Administrative Share

• Setup /a• Sit and wait• You enter PID, so user doesn’t

• No longer best practice

Office 2003 Professional CD

• 3 MSI files, plus Setup.exe

• OWC1x.MSI are Office web components (XP, 2003)

• PRO11.MSI, Setup.exe install Office

Install – 1

Install – 2

Install – 3

Install – 4

Install – 5

Install – 6

Install – 7

Install – 8

What About Service Packs??

• With Office XP – you had to install SP1 first then SP2 , and update the Admin image on the server

• No SPs for Office 2003 yet• Office 2003 SP1 due May (?)

– Contains:• Bug Fixes• Updates for OneNote/InfoPath

OneNote – SP1

• Next version of OneNote• Many new features• Preview version downloadable

– http://www.microsoft.com/downloads/details.aspx?FamilyID=9107473a-74ca-4113-9392-0dfb092dfa72&displaylang=en

– http://tinyurl.com/ysh83

Administrative Share

• Created with SETUP /A• PID Pre-loaded• To install

– Run Pro11.msi from the share

• Generally not recommended– Use Compressed CD Image+MST

Administrative Install - 1

• Installed with Office Resource Kit Tools

• Creates a .MST Transform• Used to simplify subsequent

deployment• Demo coming!

When to use a Custom.ini

• Change How LIS is configured– in the [Cache] section

• Chain Windows installer packages like MUI– in the [ChainedInstall_n] section(s)

• Run Setup.exe direct from the install image– no .bat or shortcut

• Set unique settings for chained installs

Beware

• When using a custom INI file, you can also specify options on the command line

• If a command line option conflicts with an INI value, Setup uses the command line!

Transforms• Used to:

– Define the local install path– Accept the EULA and enter PID– Define default install state for Applications and

Features (local, network…)– Hide and Lock features– Add custom files and registry entries– Modify shortcuts– Define server locations– Specify other products to install or programs to run post

setup on PC– Configure Outlook– Remove previous versions

When to Use Transforms

• To make extensive customizations• To make changes not readily made

by using the Setup command line or Setup settings file

• To deliver varying configurations to groups of users using multiple transforms

Office Profile Settings (OPS)

• The Profile Wizard saves and restores user-defined settings in Office 2003 applications

• Some settings like user name and MRU are excluded from a Profile scan

• Outlook 2003 is also not entirely captured

OPS Best Practice

1. Use Profile Wizard to create OPS that has default user settings

2. Use CIW to build transform that contains the OPS

3. Install Office 2003 on users PCs with transform

4. Open each Office application on a test PC and set options desired (Tools/ Options)

Office 2003 Downloads

• Office 2003 Resource Kit Toolshttp://tinyurl.com/novd

• Customisable Alertshttp://tinyurl.com/33tmv

• Package Definitions (For SMS)http://tinyurl.com/2rpq8

Creating The Administrative Share

Building A TransformWith the Custom Install Wizard

Editing Setup.ini

Capturing User Settings

Questions

5. Installing Office 2003 Applications

Documents