Few administrators would turn down a security update that helps protect the company network from the latest computer virus. It's the process of applying updates to each and every user's computer that gives them pause. Particularly when not every user has reliable, high-speed access to the network at any given moment. With a little foresight, however, you can deploy Microsoft Office 2003 in a way that makes the patching process a whole lot simpler and more straightforward.

When you install Office 2003 from a CD image on the network — rather than from an administrative installation point — Setup caches the compressed cabinet files on the local computer and performs the installation from there. After the installation is complete, users can keep the local installation source where it is — hidden and available. The local installation source (LIS) is compressed, so it takes up relatively little hard disk space.

What does this mean for patching? With a local source always available, users do not need the original network source or the CD to install features on demand, add new features, or apply updates. Because users always have access to the source on their own computer, they can apply client patches directly to the local installation of Office. And because the original network image stays the same, clients never become out of sync with an updated image.

Of course, these benefits hinge on users having the LIS on their computers. As an administrator, you can help ensure that a complete LIS is installed. A new version of the Office Setup Program allows you to set properties that force the creation of the LIS when Office is installed. The enhanced Setup.exe also lets you deploy the LIS separately, before you deploy Office.

Another new tool, the new Local Installation Source Tool (LISTool.exe), gives administrators more flexibility in managing the LIS after Office is installed. You can find this downloadable file on the Office 2003 Resource Kit Downloads page.

Using the LISTool, they can:

• Create a local installation source from the original source after Office is installed.
• Move the local installation source to a different drive on users’ computers.
• Disable the local installation source for users who are running short of hard disk space.

Related links

If you want to install Office with a local installation source, do not run Setup /a to create an administrative installation point. Instead, deploy Office from a compressed image of the CD. For more information, see Taking Advantage of a Local Installation Source.

Having a local installation source on their computer frees users from their dependence on the original source for many maintenance tasks, including patching. For information about distributing client updates to users, see Distributing Office 2003 Product Updates.

You can customize the way Setup handles local caching by setting properties in the [Cache] section of the Setup settings file (Setup.ini). For more information see Setup Settings File in the Office 2003 Resource Kit Reference.