Re: sus office updates
From: David Randall [MSFT] (davidra_at_online.microsoft.com)
Date: 07/13/04
- Next message: ajewell_at_purdue.edu: "Re: MS02-006/MS02-008"
- Previous message: Evan [MSFT]: "Re: sms info? where? thanks"
- In reply to: Charles Muscat: "sus office updates"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 13 Jul 2004 09:22:33 -0700
Charles,
There are two ways to accomplish this task. You can modify the registry
entries on the client computers, or you can script a change for MSI to add
the source list entries for you. Most Office installations are per-machine
installations (installed for all users of the computer). If this is the
case for your users, you can modify the source list registry key that lists
any valid sources of the original installation files of Office. Of course,
all the usual disclaimers apply about modifying the registry, and how it's
not officially supported.
That said, if you look in \HKCR\Installer you will find a subkey called
"products". Under that, you'll see a bunch of strings of numbers as keys.
These are the "encrypted" product keys. They are formed by reversing some
groups from the original product code.
For example, my "encrypted" product code for Office 2003 Professional is:
9040110900063D11C8EF10054038389C
The original product code for Office 2003 Professional is:
{90110409-6000-11D3-8CFE-0150048383C9}
First, determine which product code's registry entry you need to modify.
Then, open the regkey Sourcelist, then open the regkey Net.
Add a new expandable string value below the current entry, numbered with the
next sequential number (probably 2). In that value, put the path of the
share you have your office components in.
If you are good with scripting, you can use the function
MSISourceListAddSource() to do the work properly for you in a script that
you send to your client computers.
UINT MsiSourceListAddSource(
LPCTSTR szProduct,
LPCTSTR szUserName,
DWORD dwFlags,
LPCTSTR szSource
);
You're on your own for writing the script, as I don't have any samples
available for you.
Background information on Source Resiliency:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/source_resiliency.asp
Hope that helps, let me know how it goes.
Dave
"Charles Muscat" <anonymous@discussions.microsoft.com> wrote in message
news:2b0a001c468a0$fda68020$a601280a@phx.gbl...
> Is there any way that I can share a directory and
> automatically tell the package to find and install what
> ever MS office components it needs in sms 2 When I am
> sending the patches.
>
- Next message: ajewell_at_purdue.edu: "Re: MS02-006/MS02-008"
- Previous message: Evan [MSFT]: "Re: sms info? where? thanks"
- In reply to: Charles Muscat: "sus office updates"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|