When I installed OO.o 2.3 on my sister’s computer, I was disturbed that it kept offering her admin account as the single account it would install under, even though we were not running the installer under that account.
At my XP SP2 system at home, I installed the same version and I did not have that problem. This time it did name the account I was using, even though it was not my normal administrator account. It was, however, the first account that had been set up on my machine, as was the case for admin on my sister’s machine.
So I tried again, this time on my Tablet PC and Windows Vista Ultimate. For variety, I also used the OO.o 2.1 Novell edition, installing from CD-ROM. There, I ran into exactly the same problem. I was presented with this dilemma:
Once again, me is not admin. I am doing this install from my standard-user account (SUA). But just to see what would happen, I took that option anyhow. Guess what: This dialog is lying. It will install only for the account being used. The bug is that it doesn’t present the correct account name. The behavior is actually correct.
So if you are attempting to install OpenOffice.org 2.3 (or the 2.1 Novell Edition) only under the account you are running in, you can ignore the incorrect account name. It will do the right thing.
The next time I assist my sister in adding an OpenOffice.org update, I’ll be sure to uninstall the current version and then install the new one only for her standard account.
Now, you might wonder what the fuss is all about. If you are as obsessive as I am about computer security, you might want to omit all but pure administrative applications from the administrative account, and only ever use the administrative account for essential administrative operations.
This means that to have ordinary applications install properly in the ordinary accounts where it is safest to run them I elevate my standard-user account to an administrator account just long enough to install the software and run it the first time under the standard account. This gyration is required because many programs expect to perform final administrative setup operations on the first execution. Setting of registry entries and creation of application data, plus other details, may be specific to the account that is used for the install. I will usually discover the firewall conditioning that is required upon the first execution. From then on, I can use the program as a standard user.
When certain programs (e.g., Second Life) install for all users with no other option, I will remove the shortcuts and links placed on the "All Users" desktop and startup menu and place them in the profile information of my standard user account. This is just a little preventative against my foolishly using recreational software from my administrative account.