Installing Office 2007 via GPO
Hi,
I've been searching and testing ways to send Office 2007 via Group Policy and this really confused me.
I read a Microsoft document about Deploying Office 2007 through GP but it does not work. Actually it's even more confusing that in the doc they say to use the EnterpriseWW.msi and on another Technet page, they say that you cannot use EnterpriseWW.msi directly, you have to use Setup.exe. When I use EnterpriseWW.msi or StandardWW.msi I immediatly get Error 1713.
I also tried having a snapshot for Office 2007 installation to convert Setup.exe to MSI but also didn't work.
I read all the threads related to this problem and couldn't find any solution for that.
Has anyone figured out a way to deploy Office via Group Policy?
Thank you
I've been searching and testing ways to send Office 2007 via Group Policy and this really confused me.
I read a Microsoft document about Deploying Office 2007 through GP but it does not work. Actually it's even more confusing that in the doc they say to use the EnterpriseWW.msi and on another Technet page, they say that you cannot use EnterpriseWW.msi directly, you have to use Setup.exe. When I use EnterpriseWW.msi or StandardWW.msi I immediatly get Error 1713.
I also tried having a snapshot for Office 2007 installation to convert Setup.exe to MSI but also didn't work.
I read all the threads related to this problem and couldn't find any solution for that.
Has anyone figured out a way to deploy Office via Group Policy?
Thank you
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
spartacus
14 years ago
Hello,
As you have probably read, there are a number of caveats to deploying Office 2007 via GPO using the EnterpriseWW.msi directly.
Although it doesn't directly address the issue of why you cannot get the documented method working (Error 1713 is a generic error code and doesn't tell us a great deal), you might instead want to consider a startup script method documented here - the advantages of this method is that it allows you to use an OCT generated MSP to perform any customizations rather than going down the (somewhat restrictive) changes to config.xml route.
Regards,
Spartacus
As you have probably read, there are a number of caveats to deploying Office 2007 via GPO using the EnterpriseWW.msi directly.
Although it doesn't directly address the issue of why you cannot get the documented method working (Error 1713 is a generic error code and doesn't tell us a great deal), you might instead want to consider a startup script method documented here - the advantages of this method is that it allows you to use an OCT generated MSP to perform any customizations rather than going down the (somewhat restrictive) changes to config.xml route.
Regards,
Spartacus
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
