Scott_Gardner
asked on
Installing Custom Office 2003 Addin via GPO or SCCM
Hi
We have recently been asked to delpoy 3 components via GPO or SCCM to ensure all computers get them and also to save IT staff from having to walk to each computer and install manually.
We are doing this with a simple batch file that runs each setup in turn silently and this works fine with manual installs as an Admin account. If we do the same script in a GPO or SCCM, the software all appears to install correctly with success entries in the Windows event log, but the Addin will not appear in Office. Also if the script is run manually this addin works for all users.
"\\servername\vstoseruntim e\vstor.ex e" /q
msiexec.exe /i "\\servername\office2003pi a\o2003pia .msi" /q /l* "C:\windows\PIA_Setup.log"
msiexec.exe /i "\\servername\protective markingsetup.msi" /q /l* "C:\windows\PM_Setup.log"
One other thing is that with SCCM there is an error in the log about not being able to elevate privellages for the o2003pia.msi file, even thought it is set to run with elevated privellages.
I have been trying to work out why this will not install as the System account as it does for a user account and an coming up with nothing after searching through many sites.
NB: We have many other GPOs and SCCM installations that work fine with batch files, msi and setup.exe and this is not 'how to use GPO or SCCM issue'.
All help is much appreciated.
Thanks,
Neil
We have recently been asked to delpoy 3 components via GPO or SCCM to ensure all computers get them and also to save IT staff from having to walk to each computer and install manually.
We are doing this with a simple batch file that runs each setup in turn silently and this works fine with manual installs as an Admin account. If we do the same script in a GPO or SCCM, the software all appears to install correctly with success entries in the Windows event log, but the Addin will not appear in Office. Also if the script is run manually this addin works for all users.
"\\servername\vstoseruntim
msiexec.exe /i "\\servername\office2003pi
msiexec.exe /i "\\servername\protective markingsetup.msi" /q /l* "C:\windows\PM_Setup.log"
One other thing is that with SCCM there is an error in the log about not being able to elevate privellages for the o2003pia.msi file, even thought it is set to run with elevated privellages.
I have been trying to work out why this will not install as the System account as it does for a user account and an coming up with nothing after searching through many sites.
NB: We have many other GPOs and SCCM installations that work fine with batch files, msi and setup.exe and this is not 'how to use GPO or SCCM issue'.
All help is much appreciated.
Thanks,
Neil
ASKER
All of the files install as they are running in the context of the SYSTEM user in the GPO, which has full permissions to the computers. The event log shows that the installs were successfull also and you can see the installed products in Add / Remove section on computer. The only difference is that the addin does not load. I have checked in the Disabled Addin section of Word and it is no listed, although it is in the registry HKEY_LOCAL_MACHINE\SOFTWAR E\Microsof t\Office\W ord\Addins \. I have even run the Microsoft PSS VSTO 2005 Client TroubleShooter and this shows that all is installed as required.
I think I know what the issue is.... we had a similiar problem deploying vsto addins for all users and we implemented a hotfix and added extra code to the addin in the registry for this to work. have a read of this site and it may assist you.
http://blogs.msdn.com/b/vsto/archive/2010/03/08/deploying-your-vsto-add-ins-to-all-users-saurabh-bhatia.aspx?PageIndex=2
http://blogs.msdn.com/b/vsto/archive/2010/03/08/deploying-your-vsto-add-ins-to-all-users-saurabh-bhatia.aspx?PageIndex=2
ASKER
Hi
The thing is that this works perfectly fine and applies to all users if we run the batch file once in an Admin account. The same can not be said if run it from GPO or SCCM. Is the VSTO or o2003pia.msi needing to do something when installing that the SYSTEM account can't perform. It would not be so bad if the install at least failed, but it says successfull in the event log for all 3 components.
Thanks,
Neil
The thing is that this works perfectly fine and applies to all users if we run the batch file once in an Admin account. The same can not be said if run it from GPO or SCCM. Is the VSTO or o2003pia.msi needing to do something when installing that the SYSTEM account can't perform. It would not be so bad if the install at least failed, but it says successfull in the event log for all 3 components.
Thanks,
Neil
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What about adding those files to your package distribution, and calling each command line from within a program and linking the programs?