Issue 46041 - Published Installation with Active Directory Group Policy fails with error message
Summary: Published Installation with Active Directory Group Policy fails with error me...
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 2.0 Beta
Hardware: PC Windows XP
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2005-03-26 01:18 UTC by jdmeijer
Modified: 2019-10-06 17:03 UTC (History)
4 users (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description jdmeijer 2005-03-26 01:18:17 UTC
The Windows Installer service allows for automated software deployment with
Active Directory Group Policy. In short: Software (MSI Packages) can be assigned
(installed on reboot of a computer) of published (a non-administrative user can
add the software him/herself via Add or Remove Programs from the Control Panel).
More details on this can be found a.o. in the Office Deployment Guide from the
Microsoft Office Resource Kit

If software is published to a user, and the user chooses to install the software
(from Control Panel -> Add or Remove Programs -> Add New Programs -> Add
Programs from your Network) the the user does not need administrative privileges
to install the software. The Windows Installer service will in this case install
the software with 'elevated privileges' (as if the user were an administrator).

However the OOo 2.0 beta installer checks if the user has administrator
permissions, and if not it will generate an error message: 1.9.79 Installerinformationen
The Installation Wizard cannot be run properly because you are logged in as a
user without sufficient administrator rights for this system.

So the installation, which should run without problems, fails. This seriously
hinders OOo deployment in our environment (and possibly a lot of others).

The check for administrator permissions is either not adequate or it shouldn't
be there in the first place.

To reproduce the error you need to have a working Active Directory environment:

1) In Active Directory Users and Computers, create a Organizational Unit (for
2) In this OU, create a test user
3) Unzip OOo and run msiexec /a openofficeorg1979.msi. Put the installation
(Administrative Installation Point) on a share where the test user has read
4) Right-click the OU created in step 1 and open the properties. Activate the
Group Policy tab.
5) Create a new group policy object and double click to modify the new policy object
6) Navigate to User Configuration -> Software Settings -> Software Installation,
right click and Choose New Package...
7) Browse to the share from step 3 and double click the OOo MSI.
8) Choose Published and check that OOo apears in the list.
9) Close the Group Policy Editor
10) Log on to a workstation in the domain as the user created in step 2.
11) Open the Control Panel -> Add or Remove Programs -> Add New Programs.
12) Select OOo from the list of available software from the network and click 'Add' 

If the user is not an administrator, the error will appear.

Please let me know if I can help any further.


Jeroen Meijer
Comment 1 Olaf Felka 2005-03-26 07:22:02 UTC
OOo works as designed. It's not a defect.
of @ is: Please have a look.
Comment 2 flaime 2005-10-15 09:31:42 UTC
This is the same that happens again in the RC2 version. This is not a defect? I
dont thinnk so, why provide an .msi file if it does not work correctly with
Active Directory Group Policy? It is not possible to deploy OO in large
organizations like mine, and this is a serious limitation.
Comment 3 2006-01-04 10:01:43 UTC
Shifting target to "OOo 2.0.3". 
Comment 4 pulsifer 2006-04-10 15:33:16 UTC
This might be easy to fix.

In the msi file, the table "LaunchCondition" contains the condition "AdminUser".
 This should probably be changed to "Privileged".  See
Comment 5 joerg.skottke 2006-04-11 08:41:10 UTC
Back to me, i now have a valid testing environment.
The application installs ok as AdminUser (verified w. w2k3 and w2kSP4 client)
Comment 6 2006-04-11 09:17:50 UTC
Thank you, Jörg. Nevertheless it sounds good to use in the table
"LaunchCondition" the condition "Privileged" instead of "AdminUser".
Comment 7 jdmeijer 2006-04-12 17:52:52 UTC
I guess LaunchCondition was set to AdminUser for a reason:

I just tested installing 2.0.2 (published in A.D.) as a non-administrator. With
LaunchCondition set to AdminUser it fails to start the installer. With the
LaunchCondition set to Privileged the installation finishes normally, but
OpenOffice then fails to start. The Windows Installer kicks in to 'configure', and after that nothing happens.

the application event log contains the following error 3 times (after starting
OOo Writer):

Type: Warning
Source: MsiInstaller
Category: None
Event ID: 1001
Detection of product '{08D2F839-A9FD-4F5A-A529-D45FF6E238A3}', feature
'gm_p_Wrt_Bin' failed during request for component
Comment 8 jdmeijer 2006-04-13 12:32:12 UTC
The event log warnings and failure to start OOo in my previous comment are
caused by invoking the Start Menu item (shortcut) in the Programs/
folder. Starting OOo manually from the command line (swriter.exe) works fine!
Comment 9 joerg.skottke 2006-05-22 09:15:37 UTC
Not for 2.0.3 anymore.
Comment 10 joerg.skottke 2006-08-09 14:39:18 UTC
Comment 11 mikkojarvinen 2007-09-28 16:23:11 UTC
2.3.0 installs fine with LaunchCondition "AdminUser" changed to "Privileged",
but uninstall fails (Error 1730). If user has administrative rights, Windows
Installer makes the uninstall but is not removed.
Comment 12 joerg.skottke 2009-08-20 07:58:27 UTC
Someone to help with this one? I need someone to confirm the issue since i do
not have such an environment available.
Comment 13 hans_werner67 2011-03-28 11:51:03 UTC
Assign to new default-assignee
Comment 14 Marcus 2017-05-20 10:55:56 UTC
Reset assigne to the default "".
Comment 15 oooforum (fr) 2019-10-06 16:11:46 UTC
All this configuration is old.
MS KB is not available.

Feel free to reopen if this problem still occurs on recent Windows system.