Re: The system administrator has set policies to prevent this inst



Weird. Your description in that it now is applying to all computers in the
domain would seem to indicate a Group Policy setting for Windows Installer
as does the registry key being used though that registry key can also be
configured manually, possibly by malware. Did running rsop.msc on an
affected domain computer show any settings configured for Windows Installer
under either computer OR user configuration /administrative
templates/Windows components/Windows Installer? Does it show and Group
Policy logon or startup scripts under Windows settings/scripts? Have you
scanned at least one of the affected computers for malware?

Steve


"Travis" <Travis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0A230F80-48DA-4612-8F8E-6CBE336FA5EB@xxxxxxxxxxxxxxxx
Ok, tried it. No change.

I've also checked every GPO for a Software Restriction Policy and none are
present.

Travis

"Steven L Umbach" wrote:

Did you run rsop.msc on a couple of the domain workstations to see if it
shows that a Group Policy setting for Windows Installer is disabled??
Unless
this is happening via a direct registry mod such as a Group Policy
startup
script using a .reg file it would seem that this would be happening via a
GPO. What you might try is to create a new Group Policy, link it to the
domain container, enable enforcement/do not override for that GPO, put it
at
the top of the list, and go to computer configuration/administrative
templates/Windows components/Windows installer and set disable Windows
Installer to disabled or enabled for "never". Then run gpupdate /force on
the domain controller and do the same on the domain workstation or reboot
it.

Steve


"Travis" <Travis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8BF2ECE8-B2C1-4517-BB97-97DB3BC66C2C@xxxxxxxxxxxxxxxx
It now appears that it is affecting every computer in this Domain. So
far
I
have been unable to install Office 2003, Group Policy Management
Console,
MS
Installer Cleanup Utility, Financial Edge, and Raiser's Edge. On the
workstations it seems that the following registry key has been
modified.

HKLM\Software\Policies\Microsoft\Windows\Installer\disableMSI

The value on the workstations is set to 2. This value is not present on
my
servers. When I change the value on the workstations from 2 to 0 I am
then
able to install whatever I like. I have added the desableMSI key to a
server
and made the value 0 but I am still unable to install anything.

I have also created a new GPO, set it to block policy inheritance, and
move
the DC to this GPO. I then ran "gpupdate /force". I was then able to
install
the Group Policy Management Console but I still recieve the same error
when I
attempt to Upgrade my Accounting package.

Is it possible that a recent Windows Update may have caused this?

Travis

"Roger Abell [MVP]" wrote:

The last time that I searched the KB with the exact string you quoted
there were a number of hits for different apps with installs that gave
that
result and their various workarounds.

"Travis" <Travis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BC9BC2B1-8B69-4A51-B667-C4CC5B9076A8@xxxxxxxxxxxxxxxx
I am unable to run certain MSI and EXE files. I receive the following
error..

"The system administrator has set policies to prevent this
installation"

Windows Server 2003 SP1
Domain Contoller

I am logged in as a Domain Admin with local Admin rights. I
installed
this
server 2 years ago and have been the only Admin to touch it. The
only
modifications to any GPO is for logon scripts, folder redirection,
and
WSUS.

I have updated Windows Installer to version 3.1 v2

I have added the DisableMSI reg key and set the value to 0

I attemepted to run the Windows Installer Cleanup utility to remove
the
application that will not install but I receive the same error when
I
try
to
install it.

Any help would be much appreciated.

Travis








.



Relevant Pages

  • RE: Windows installer on SBS server 2003 SP2
    ... "The Windows Installer Service could not be accessed. ... Windows Installer Service cannot be started correctly. ... Verify that the SYSTEM/administrators account has been added and that it has Full control. ...
    (microsoft.public.windows.server.sbs)
  • Re: New Imformation on System Restore & Windows Installer Registry Corruption
    ... html bar click in and think since I'm not using any html selection (bold, ... 2003 Updates and other Office version updates, ... After running the Installer Clean utility to remove remnants of OfficeXP, ... > Windows Installer version 1.0 to Windows Installer version 1.1. ...
    (microsoft.public.windowsxp.customize)
  • Re: UNABLE TO CHECK FOR UPDATES ON THIS COMPUTER
    ... Running the Windows Installer Cleanup Utility should take care of the patch ... i did download the windows installer cleanup utility w/o ... >There are some known issues with the Office Update site. ...
    (microsoft.public.officeupdate)
  • Re: New Imformation on System Restore & Windows Installer Registry Corruption
    ... html bar click in and think since I'm not using any html selection (bold, ... 2003 Updates and other Office version updates, ... After running the Installer Clean utility to remove remnants of OfficeXP, ... > Windows Installer version 1.0 to Windows Installer version 1.1. ...
    (microsoft.public.windowsxp.basics)
  • Re: Removal/Install Office 2000
    ... You might try the Windows Installer Cleanup Utility, ... >> This problem may occur if the registry contains Microsoft Windows ...
    (microsoft.public.office.setup)