Q. How can I extract a Microsoft Office service pack for enterprise deployment?

A. When you download an Office service pack, you typically get one big file. When we run this file on a client, it's extracted locally on the client then executed. This process can take a lot of disk space and slow down your installation. It's also very annoying if you're virtualizing applications and the service pack application generates a large cache of patches.

You can extract a service pack to a folder using the /extract switch. For example:

<pre>"D:\Software\Office 2007\en_2007_microsoft_office_suite_service_pack_2_x86.exe" /extract:"d:\software\office 2007\sp2"

Discuss this Article 1

ebraiter
on Mar 8, 2010
Seems you have to be in IE8 compatibility view to scroll across to see the box. Without compat mode you get a bix box with the text cut off.

It's too bad that the Office 2007 installer doesn't correctly show the completion bar. If you add one or more updates [for me SP1, SP2 and the help updates only], it's sits at the end saying it's applying updates. Sort of like the Win XP SP3 where it's sitting at the end finalizing things and that could take forever on a slower system.

Please or Register to post comments.

Upcoming Training

Mastering System Center 2012

During over 6 hours of training you can join John Savill from your computer as he will walk you through the key components and capabilities of System Center 2012, what’s involved in using the components, and the benefit they can bring to your environment.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.