Something that might come handy:
The package can be also deployed as a per machine installation, and after
that it will be out of the scope of the users to tamper with the installed
state of the software, but they'll still be able to launch it.
2007/11/30, Huseyin Tufekcilerli <[EMAIL PROTECTED]>:
>
> Hello,
>
> I am trying to deploy a sample MSI package which simply installs a
> text file to Program Files folder. The setup runs just fine if you run
> it through double-clicking or via msiexec /i package.msi command line
> interface (with the current user is being an administrator on that
> computer). Then I have created a GPO for the domain that the computer
> resides and added the MSI package as an Assignment to that user. So
> when that user, who is a local admin on that computer, logins the
> computer; the installation is deployed to that computer just fine. But
> whenever I have removed that user's local admin privileges the MSI
> package can not be deployed with these event log error records:
>
> 1)
> Source : Userenv
> Event ID : 1085
> User : NT AUTHORITY\SYSTEM
> Description : The Group Policy client-side extension Software
> Installation failed to execute. Please look for any errors reported
> earlier by that extension.
> 2)
> Source : Application Management
> Event ID : 108
> User : DOMAIN\user.name
> Description : Failed to apply changes to software installation
> settings. Software changes could not be applied. A previous log
> entry with details should exist. The error was : Access is denied.
> 3)
> Source : Application Management
> Event ID : 103
> User : DOMAIN \user.name
> Description : The removal of the assignment of application
> {OurProductName} from policy {OurGroupPolicyName} failed. The error
> was : The system cannot find the file specified.
>
> 4)
> Source : Application Management
> Event ID : 101
> User : DOMAIN \user.name
> Description : The assignment of application {OurProductName}
> from policy {OurGroupPolicyName} failed. The error was : Access is
> denied.
>
>
> In a nutshell, both (manual and GPO-deployed) installations fail if
> the running user is not an admin. Since a GPO-deployed installation is
> granted by a domain administrator, I think there must be an option to
> run that installation as a privileged user during a non-privileged
> user's login.
>
> Any help/pointer would be greately appreciated.
>
> Hüseyin.
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell. From the desktop to the data center, Linux is going
> mainstream. Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
