J
jtrudeau
Are there advantages to exploit by copying the Office 2003 source t
client PCs using the "cacheonly=1" setting in a setup.ini file
I'm looking at all possible options/combinations for an Office 200
install, where the users are not admins (e.g. they're Power Users)
The Local Installation Source provides the ability for local sel
healing (vs an install using group policy and an admin installatio
share on the network), and, from what I've read, is much easier t
patch when future service releases are available. Also, Group polic
appears to have other complexities and risks that are not present i
a local install
Other potential benefits might include the ability to have the use
kick off the install when it suits them, and the ability to drop
new transform file on user PCs before they do the install. This migh
be of benefit in a staged rollout of Office 2003 where tweaking o
features is done
Do these sound like benefits that would make this approach reasonable
The only part I'm not sure of, is how to elevate the user's account s
they can do the actual install from their local cache, without givin
them full admin privs over their PC, and, ensuring applications ar
closed before the install. Are there risks to this approach
Comments are appreciated
J
client PCs using the "cacheonly=1" setting in a setup.ini file
I'm looking at all possible options/combinations for an Office 200
install, where the users are not admins (e.g. they're Power Users)
The Local Installation Source provides the ability for local sel
healing (vs an install using group policy and an admin installatio
share on the network), and, from what I've read, is much easier t
patch when future service releases are available. Also, Group polic
appears to have other complexities and risks that are not present i
a local install
Other potential benefits might include the ability to have the use
kick off the install when it suits them, and the ability to drop
new transform file on user PCs before they do the install. This migh
be of benefit in a staged rollout of Office 2003 where tweaking o
features is done
Do these sound like benefits that would make this approach reasonable
The only part I'm not sure of, is how to elevate the user's account s
they can do the actual install from their local cache, without givin
them full admin privs over their PC, and, ensuring applications ar
closed before the install. Are there risks to this approach
Comments are appreciated
J