microsoft deployment workshop deploying office 2003 editions

Microsoft Deployment WorkshopDeploying Office 2003 EditionsJoe Liptrot

Linkpad Limited

Introduction

Presenter background & experience

About the Deployment Workshops

Logistics

–Breaks

–Restrooms

–Emergency Exits

–Evaluations

Questions

Agenda

1. Office installation options

2. Office compatibility

3. Migrating applications - Application Compatibility Toolkit

4. Access / Word / Excel migration issues

5. Project Management

6. XP - the road to Longhorn

Office Installation Options

Some Basics

Resources

New installation features

Customisation

Maintenance

Putting it all together

Some Basics

Some Basics

–Office 2003 Editions Versions, licensing and product activation

–How Setup works

–Windows Installer Fundamentals

Office 2003 Editions Versions

Office Retail vs. Enterprise

Retail requires mandatory activation

Enterprise SKUs only available through volume licensing

Enterprise SKUs enable use of:

– Office Resource Kit (ORK)

– Custom Installation Wizard (CIW)

– Custom Maintenance Wizard (CMW)

– Administrative Installation


Where Product Activation Applies

All boxed x86 versions and languages

Sales Channels

–Retail/System Builder OEMs

–Direct OEM: System Locked Preinstall. (SLP)

…But not Enterprise Version


Volume Licensing Overview

All volume channels

–Enterprise Agreements

–Select

–Open

–Etc.

Single licence Key

VL media - No activation

Some Basics

Some Basics


–How Setup works


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.

Setup.exe

Setup.ini

Office 2003 package (MSI)

OPC files used to clean up previous versions

Root of Administrative image

Files\Setup

Root of Administrative image

Files\Program Files\MSOffice\Office11

How Setup Works

Some Basics

Some Basics


–How Setup works


Windows Installer Fundamentals

File Versioning

Reference counting for ALL resources

Products (applications) are:

– Resources

– Files, registry keys etc

– Components

– The atomic units of the installation

– Features

– Correspond to custom install.


Products have one or more features

Features have one or more components

Components have one or more resources

Resources are single files, registry keys etc

Each product has a unique ID (GUID)

– Windows Installer tracks components usage by product ID

– Components can be shared between features or products.


Features can have 4 states following installation:

– Installed locally

– Installed to Run From Source (e.g. across the network)

– Advertised

– “On demand”, installed on first use

– Not installed.


Package Format:

Custom Database format

– Created by setup developer

– One per product

– Described in relational tables

Products have

– Features

– Components

– Installable resources

– Entry points

.MSI file extension

Features

Components

Shortcuts

Action

Files

Optional Internal CAB

Summary Information Other Tables...

Pointers to source files


Windows Installer Transforms:

Generic way to customise an installation

A Transform describes the delta between the original MSI package and the customised version

– Saved to an .MST file

– Is applied on the fly

Transforms can only be associated with app during initial install.

How Setup Works

Demo•SETUP.EXE, SETUP.EXE, PRO11.MSI

•MSI structure using ORCA


Some basics

Resources


Customisation

Maintenance


Resources

Office 2003 Editions Resource Kit

Windows Desktop Deployment Resource Kit

Solution Accelerator for Business Desktop Deployment

Resources

Microsoft QuickStart for Business Desktop

Microsoft QuickPlan for Business Desktop


Some basics

Resources


Customisation

Maintenance


New Installation Features

Locally Installed Source (LIS)

–From compressed CD image only

–Saves disk space (compared with admin install)

–Use to support mobile users

–Can:

– Use .MST to customise

– Set Install on Demand

– Chain packages in SETUP.INI

– Use SMS to deploy

–Can’t:

– Set to run over the network

– Enter licence key & accept agreement on behalf of users (as Admin install)

New Installation Features

Locally Installed Source (LIS) - continued

–Use Custom Installation Wizard to Set Licence key (and accept agreement)

– [Cache] section in SETUP.INI applies

New version of SETUP.EXE in RK Toolbox

–Ensures every install gets and keeps a complete LIS

–Allows Admins to deploy LIS first, then launch installer

New Installation features

Demo•LIS location and contents

•Installation using LIS


Some basics

Resources


Customisation

Maintenance


Customisation

pro11.msi

YourTransform.mst

Custom Installation Wizard

Profile Wizard

Setup /aor CD image

Customise Office

*.ops

Templates

Add-ins

Logos

CustomisationCustomisation MSI Cmd

LineINI File MST File OPS

FileRemoval Wizard

Setup Process

PRO11 X X X

LIS (CD image only)

PRO11 X x

Office Features

PRO11 X

Security PRO11 X X

Outlook* PRO11 X X X

Other user PRO11 X X

Removal PRO11 X X

Language MUI X

Chained chain X

Customisation

Group Policy

.ADM files are installed as part of ORK

Also available as separate download

Import into Group Policy and modify as required

Note that GPO settings managed settings. Settings from Profile Wizard or CIW just set defaults

Customisation

Precedence:

Command Line Options override .INI settings which override .MST settings

Except – “Company Name in CIW (.MST) takes precedence over both command line and .INI settings

Customisation

Conflict Resolution:

Settings applied later override settings applied by previous methods

Order of application of settings:

1. .OPS inside .MST

2. .MST

3. Registry values in .MST

4. Profile Wizard when run during setup

5. Settings migrated from previous Office version

6. Settings from Profile Wizard or CMW post installation

7. Settings from Group Policies

Customisation

Best Practices:

Separate managed from unmanaged settings and document

Configure volatile settings late in the process (i.e. via command line, .INI file or .OPS file to be applied after setup

Put corporate templates on shared network location rather than on each PC. Use CIW to configure paths.

Configure security settings using GPOs


Some basics

Resources


Customisation

Maintenance


Maintenance

To change default settings

–Use Profile Wizard to produce .OPS file or Custom Maintenance Wizard to produce .CMW file

–<path>\proflwiz.exe /r MyConfig.ops /q

–<path>\maintwiz.exe /c MyConfig.cmw

To prevent users changing options you set

–Use Group Policy with Office.ADM files

Implementing Service Releases:

–On distribution share use full file version ( e.g. Office2003SP1-kb842532-fullfile-enu.exe)

–On client machines use the client update version (e.g. Office2003SP1-kb842532-client-enu.exe)

Maintenance

Windows Server Update Services

Helps automate the update management process

Reduces time, effort, cost, and risk

Update Services helps you to:

– Increase efficiency and control over the update management process

–Minimise network bandwidth usage and impact of network issues on the update process

–Easily determine key system health and update deployment metrics

–Optimize the end user experience by minimising disruption to productivity

Maintenance

Windows Server Update Services

Initial release delivers updates for:

–Windows

–Office

–Exchange

–SQL / MSDE

Support for updating other Microsoft products will be enabled on an ongoing basis without requiring an upgrade or redeployment of the existing Update Services infrastructure.


Some basics

Resources


Customisation

Maintenance


Putting it all Together

DemoOffice Profile Wizard

Custom Installation Wizard

Editing SETUP.INI (cache options & chained install)

Using Group Policy to set options

Using Group Policy to Assign software and apply Transform

Custom Maintenance Wizard

Using Group Policy to update software

Welcome to this TechNet Event

FREE bi-weekly technical newsletter

FREE regular technical events hosted across the UK

FREE weekly UK & US led technical webcasts

FREE comprehensive technical web site

Monthly CD / DVD subscription with the latest technical tools & resources

FREE quarterly technical magazine

We would like to bring your attention to the key elements of the TechNet programme; the central information and community resource for IT professionals in the UK:

To subscribe to the newsletter or just to find out more, please visit www.microsoft.com/uk/technet or speak to a Microsoft representative during the break

http://www.microsoft.com/uk/technet



Microsoft Deployment Workshop – Office 2003

microsoft deployment workshop deploying office 2003 editions

Documents

setup developerone

product idcomponents

editions versionsoffice

registry keys etceach

boxed x86 versions

resources files

single files

installed locallyinstalled