User installations are disabled via policy on the machine как исправить

Hi,
  • Remove From My Forums

  • Question

  • Hi,

    I’ve been using this Vista computer for a few years now and I wanted to upgrade my version of VNC.  I unistalled VNC and ran the installer for the newer version I want to use.  At the end of the installation a message pops up which says;

    «User installations are disabled via policy on the machine.»

    I am on a Domain and I do restrict installations for standard users, however, I’m logged in as the domain administrator and I do not apply policies to that account.  I even tried installing from the local administrator account with the same results.

    I’ve disabled my virus suite and double-checked that UAC is turned off.  I tried right-click and there’s no «run as…» option and I even tried shift-right-click.

    The only thing that is unusual about this computer is that I have installed the full version of SQL server 2008 R2.

    Any thoughts as to why I would have this trouble with a VNC installation and how to correct it?

    Thanks in advance,

    Linn

    • Moved by

      Thursday, January 10, 2013 8:34 PM
      Moved to more appropriate forum category (From:Windows Vista Setup)

Answers

  • Hi,

    Thanks for the tip, although the image seems to be broken so I can’t see it. 

    But I did figure out my issue here.  I realized that I am setting the «Prohibit User Installs» policy at the computer level.  So even though the policy isn’t applied to the Administrator account it is applied to all computers.  I changed the
    «User Install Behavior» to «Allow User Installs». 

    I’m not sure I want to leave it like this but it will have to do for now.  I did notice that «Prohibit User Installs» doesn’t exist for the user configuration, otherwise I’d move it there.

    Thanks,

    Linn

    • Marked as answer by
      lkubler
      Thursday, January 31, 2013 2:56 PM

Источник
*Bulletin ID* A2E_163
*Last Review* 05/11/2007
*Revision* 1.0
*Previous IDs* None
*Obsoletes* None

Summary

Group policies may be set to prevent per-user installation of applications (as opposed to installation for all users on the machine). This especially applies to servers running Terminal Services, which disables per-user installations by default. Add2Exchange should not be installed on Terminal Servers.

Symptom

The installation fails with the error:

User installations are disabled via policy on the machine.

Description

Terminal Services or manual editing of the group policies of the server on which Add2Exchange is being installed may be set to prevent the installation of applications that do not make themselves available to all users. Because of Add2Exchange’s special role on the server, the installation process will only install and make itself available under the Add2Exchange Service Account. The process does not give the option to install for all users because no other user has the privileges necessary for the Add2Exchange Console to function properly.

The Group Policy Object editor (gpedit.msc) may have been used to edit the policy for user installations. You should consult with any other administrators in your organization to determine why this policy has been set and what impact it will have to unset the policy if you should so choose.

Resolution

If Terminal Services is the cause for having disabled per-user installations, the ideal resolution is to separate Terminal Services from the Synchronization Server (the server on which Add2Exchange is installed). It is up to your organization to determine the best deployment of services on your available hardware.

If you determine that you cannot install on any other server, you may attempt to temporarily enable per-user installations on the server in question.

THE FOLLOWING PROCEDURE IS NOT WARRANTIED BY DIDITBETTER SOFTWARE AS BEING FIT FOR ANY PARTICULAR PURPOSE AND IS PROVIDED AS-IS. DIDITBETTER SOFTWARE IS NOT RESPONSIBLE FOR ANY INCIDENTAL OR CONSEQUENTIAL ADVERSE IMPACT RESULTING FROM ITS USE.

  1. From the Start menu, click Run…
  2. In the Run… command dialog, enter gpedit.msc
  3. In the Group Policy Editor, select Computer Configuration > Administrative Templates > Windows Components > Windows Installer
  4. In the Extended Properties pane, double-click Prohibit User Installs
  5. Click Disabled
  6. Click OK and close the Group Policy Editor

If you have a reason to have this setting on Enabled in your normal course of administration, do not forget to revisit this setting after you have completed the Add2Exchange installation.

Applies To

  • Add2Exchange Standard
  • Add2Exchange Enterprise

Keywords: Installation, Group Policy

Источник

  • Hi Paolo,

    According to the log you provided, you encountered an issue during your Service Pack 1 installation.

    Based on your log:

    MSI (s) (D4:20) [12:16:47:106]: Executing op: ProductInfo(ProductKey={ED780CA9-0687-3C12-B4393369F224941F},ProductName=Microsoft Visual Studio
    2010 Service Pack 1,PackageName=VS10sp1_x86.msi,Language=0,Version=167812379,Assignment=0,ObsoleteArg=0,,,PackageCode={E36D1CC4-511B-4631-8482-BDBFFCC23F04},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)

    MSI (s) (D4:20) [12:16:47:471]: Prodotto: Microsoft Visual Studio 2010 Service Pack 1 — Errore 1934. Nel computer sono attivi criteri che impediscono
    le installazioni da parte di utenti.

    We can learn that the installation program encountered an error during the installation process. The error number is 1934. This error means that user
    installations are disabled through policy on the machine. This error indicates that user Installation have been disabled via the
    DisableUserInstalls policy. Error 1934 is a
    critical problem that is commonly caused by an unstable system registry or corrupt system files that are required to run Windows smoothly.

    Here is my suggestion:

    ·        
    Open the Registry, find this key:
    HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsInstaller.

    ·        
    Check that if this key not to be at fault value.

    ·        
    If this key is not to be at
    default value, I recommend you modify it manually. The “
    Default “ is normal value. Before you set it, please do backup so that if you have any problems after the change, you can restore the registry.

    o  
    If this policy is not set, the installer searches the registry for applications in the following order: managed applications registered as per-user, unmanaged
    applications registered as per-user, and finally applications registered as per-machine.

    o  
    If this policy is set to 1, the installer ignores all applications registered as per-user and only searches for applications registered as per-machine. Calls
    to the Windows Installer application programming interface or system ignore per-user applications. An attempt to perform an installation in the per-user
    installation context causes the installer to display an error message and stops the installation.
    In this case, the Windows Installer also prevents per-user installations from a terminal server.

    I am looking forward to hearing from you soon.

    If I have misunderstood anything, please feel free to let me know.

    Best Regards,

    Alexander Sun [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Помечено в качестве ответа
      Andrew.Wu
      23 мая 2011 г. 2:47

    • Источник

    Понравилась статья? Поделить с друзьями:
  • User information is error please input again error mt pon at 4
  • User has no active profile как исправить kingdom come deliverance
  • User canceled как исправить
  • User authentication failed как исправить
  • User authentication failed or your session may be expired please try again error code ev01