Re: Software Installation

You are rather limited when the computer does not belong to a domain. You
would have to make the user a power user or an administrator even if just
temporarily. In an Active directory domain you can either publish or assign
software via Group Policy but that is not possible in a non domain
environment. You also can configure Windows Installer to always install
with elevated privileges via Group Policy [computer
configuration/administrative templates/Windows components/Windows installer
but then any user on the computer can install .msi packages. --- Steve


"Shingooooo" <Shingooooo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D158C5F0-0102-47F6-8647-06ABDF6B5931@xxxxxxxxxxxxxxxx
I want to allow USER right to install software[the pc is not belong to a
domain]
but i cant find those policy
where is it


.

Relevant Pages

  • Re: published software: Unabled to extract deployment information.
    ... being able to publish an .exe file directly using group policy. ... can not be installed properly by GP using msi! ... WIndows Installer, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Users and Groups
    ... You can use Windows Installer in conjunction with group policy to deploy ... Please do not send e-mail directly to this alias. ... > logon script would ...
    (microsoft.public.windowsxp.security_admin)
  • RE: Client Apps
    ... It is important to us that we provide you with the best support possible ... you may use group policy to assign ... Copy the Microsoft Windows Installer package for the program ...
    (microsoft.public.windows.server.sbs)
  • Re: published software: Unabled to extract deployment information.
    ... software with .exe extensions using group policy. ... can not be installed properly by GP using msi! ... File types that you use with Group Policy Software Installation ... WIndows Installer, ...
    (microsoft.public.windows.server.active_directory)
  • Re: The system administrator has set policies to prevent this inst
    ... domain would seem to indicate a Group Policy setting for Windows Installer ... affected domain computer show any settings configured for Windows Installer ...
    (microsoft.public.windows.server.security)