Deploy Office 2010 as an application - user needs admin rights?

[Aerobaticrug]

Followed this guide for deploying office 2012 as an application - http://blogs.technet.com/b/mniehaus/archive/2011/08/13/deploying-office-2010-with-configuration-manager-2012-beta-2.aspx

 

Works fine if your an admin, however if you are a normal user it states you need admin rights to install this application. How can I get this to work for users?

[Iroqouiz]

How have you deployed the application?

[Aerobaticrug]

Followed the guide above and then deployed to all users group

[Iroqouiz]

Yeah, I figured you HAD deployed it. Was curious as to what settings you chose

 

Edit: You deployed it to the All Users collection and then people install it from the App Catalog?

[Iroqouiz]

Did you check this by mistake?

 

[Aerobaticrug]

Hi, yeah, deployed to all users collection and then users are supposed to be able to install it from the app catalog.

 

It gets as far downloads the app then goes to run it and fails with the "you need admin rights to install this application".

 

I'm pulling my hair out as obviously if I did it as a package you can tell it to run with admin rights, but can't figure out how as an application.

 

Other applications such as Firefox, 7 zip all install fine. Obviously they are native MSI files though.

[Aerobaticrug]

No, no approval on this one. I also have Visio which has require approval ticked and same result even after giving approval

[Aerobaticrug]

It's also ignoring the msp admin file when you attampt the install with an admin account, don't know if that's part of the problem?

[Tay]

Under administration, site configuration, sites, right click your site and select Configure Site Components then select Software Distribution. On the Network Access Account tab it will show the user that will be used to install apps from the catalog. If that user is not in the local admin group for the client then it will not work.

[Tay]

Also make sure the MSP file is in the Updates folder and the config.xml file is in the root with setup.exe. Your config.xml should look something like this.

 

<Configuration Product="SingleImage">

<Display Level="basic" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes" />

 

<!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Single Image Setup(*).txt" /> -->

 

<!-- <USERNAME Value="Customer" /> -->

 

<!-- <COMPANYNAME Value="MyCompany" /> -->

 

<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->

 

<!-- <LIS CACHEACTION="CacheOnly" /> -->

 

<!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> -->

 

<!-- <DistributionPoint Location="\\server\share\Office" /> -->

 

<!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->

 

<!-- <Setting Id="Reboot" Value="IfNeeded" /> -->

 

<!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->

</Configuration>

[Aerobaticrug]

Changed that to an account that is a member of the local admin, but it still won't work?

[Coenie]

I honestly don't remember exactly where the setting is (during package creation, or deployment), you can try "Run as Administrator" or something similar, and see what this does for you.

Also, can the users physically access the software share?

[ratsour256]

Any success ??
I have same issue

[Peter van der Woude]

Did you configure the client settings with Computer Agent > Install permissions to either All Users or Only administrators and primary users.