Make sure all Office 2000 features are completely installed. Apparently it is trying to install a feature that wasn't installed when the user runs the program.
Main Topics
Browse All TopicsSkip to the last line if you don't want to read what I've tried already...
This is for a public room booking venue, I want all the applications to be as easy to use as possible - a lot of "Windows/Office for dummies" classes are run here.
I'm upgrading one of the computer labs from NOT w/NT4 DC, configured with the old policy editor, to Win2kP clients, Win2kAS DC/fileserver.
I've configured user profile customisations via group policies, and the only issue I'm having now is when office applications are run, the "Install Program As Other User" dialog pops up, presenting the user with the options:
--------------------------
* Run the program as MMLAB\<user>
* Run the program as the following user:
? User name: |Administrator|
? Password: |<blank>|
? Domain: |<blank>|
[ ] Always run install programs as MMLAB\<user>
--------------------------
Running as the current user is sufficient for the installer to do... whatever it is that it wants to do, so no elevation of privileges is needed.
Ticking the box "Always run install..." sets the registry value:
--------------------------
[HKEY_CURRENT_USER\Softwar
"WarnOnNonAdminInstall"="n
--------------------------
But this is, of course, on a user-by-user basis. I want to stop this dialog from popping up altogether.
I've written plenty of ADM's for the old-school policy editor, and never had any issues setting any values, anywhere in the registry... but writing up an ADM for the new GPEditor /seems/ to only allow writing values to:
--------------------------
CU\Software\Policies
CU\Software\Microsoft\Wind
LM\Software\Policies
LM\Software\Microsoft\Wind
--------------------------
I might be wrong in this (but it's what the MS doc says - http://www.microsoft.com/w
When I create a ADM to manipulate the specific key, the policy doesn't show up in the editor, but writing to:
--------------------------
CU\Software\Policies\Explo
CU\Software\Policies\Windo
CU\Software\Policies\Micro
CU\Software\Microsoft\Wind
CU\Software\Microsoft\Wind
CU\Software\Microsoft\Wind
--------------------------
Don't prevent the dialog from popping up.
---------- [Example ADM] --------------------------
#if version >= 3
;;;;;;;;;;;;;;;;;;;;;;;;;;
CLASS USER ;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;
CATEGORY !!WindowsComponents
CATEGORY !!WindowsInstaller
POLICY !!WINA
KEYNAME "Software\Microsoft\Window
EXPLAIN !!WINA_Help
VALUENAME "WarnOnNonAdminInstall"
VALUEON "no" VALUEOFF "yes"
END POLICY
END CATEGORY ; WindowsInstaller
END CATEGORY ; WindowsComponents
#endif
[strings]
WindowsComponents="Windows
WindowsInstaller="Windows Installer"
WINA="Warn if not Administrator"
WINA_Help="If ticked, and not logged in as a local system administrator the user will not be prompted with RunAs authentication dialog, by the Office 2000 installer.\nInstead, the program will automaticaly run under their credentials"
--------------------------
So here's my question:
How do I stop the "Install Program As Other User" dialog from popping up?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Check out this link too. It is for xp but should work for 2000 also.
http://support.microsoft.c
You can still use your old adm files in the GP editor, and you can still set registry keys outside the "Policiies" keys using GPOs. Microsoft calls this (registry settings outside the policies key) now "branding" or "preferred settings" (not policies), as these will behave like the NT4 system policies: they will *NOT* be reset when the policy is set to "Unconfigured".
Anyway, all you have to do is highlight the "Administrative Templates" node in the group policy editor, go into the "View" menu and uncheck the "Show policies only" entry. The "preferred settings" will be displayed in red, not in blue as the "real" policies.
So simply change your adm template back to the original position and reimport it.
[HKEY_CURRENT_USER\Softwar
Soulja>
1. Office 2000 was completely installed.
2. While this is sort of related to the RunAs service, I'm not sure if the MSKB item will resolve this issue and won't have a chance to test it.
oBdA> Great answer, that's just what I wanted.
Post a comment in http://www.experts-exchang
Business Accounts
Answer for Membership
by: ASCII_ManPosted on 2004-01-28 at 23:51:05ID: 10225403
[Note] ge.com/Net working/Wi nNT_Networ king/ Q_208 66569.html ] - I will award the points from both postings (1000 points) to whoever gets me the answer.
Also posted in WinNT Networking [http://www.experts-exchan
I need this for tomorrow if possible.