Milly Staples said:
[snip]
As for the Office installation, you need to runas admin on the users
accounts and install the program for each user. Also, be sure to accept the
license. You can also bump up the priviledges that the users have to allow
them to install programs.
Is the same true for Office 2000 on W2K? If so, I have a couple questions.
1) I installed from a CD that predates most of the upgrades and so spent
half a day after installing it to apply all the upgrades. What will hapen
now if for the secound user ID I created I install it again to make the
installer messages I get, just like the OP, go away? Will I have to apply
the patches all over again, or is it smart enough to know that the code is
already there and it just needs to provide entries into the registry, or
whatever it is that the install program does other than copy files; just as
the registry only install does for Borland's C++ Builder -i.e. to make
builder available to anyone who logs on to a given machine, you install once
as an administrator, which puts all the files in the right place, and then,
for each user, do a registry only install which takes care of registry
settings for each user)?
2) I had assumed that the fix for this problem was simple, so, when I saw
the programs seemed to work once I cancelled the installer, I set up my
email in Outlook. Am I going to have to do that all over again?
I take it that when you talk about bumping up the priviledges for a given
user, you can do that by a) giving the user administration rights while you
install the program under the user's account, and then b) remove
administrative rights once installation is complete. This isn't too bad in
a small shop with only one or two people who might use a given computer, but
I can see it being a royal pain in a large operation. I can't imagine
anyone doing this for hundreds or thousands of machines. There are few
circumstances in which I would allow anyone other than an autorized
administrator install programs. Or have I misunderstood what you meant by
running as admin on the users' accounts? (I am not a system administrator,
as you can probably tell - I know just enough to be dangerous even on my own
system. ;-)
I am curious, though, as to why this is necessary. When I installed MS
Visual Studio Enterprise on my workstations, as the system administrator,
and then logged on as a mere mortal, all of the VS applications seemed to
behave properly. I didn't see a need to install it while logged on as each
user. I thought the whole purpose of installing software as an
administrator was to make it available to all users.
Cheers,
Ted
