M
Mikko Paavola
Hello,
I have little trouble to understand deployment guides and need little help.
We are going to deploy Office 2007 Pro Plus product + some extra proofing
tools.
Deployment method is GPO with startup script.
Installing en-us customized base version of the Office is no brainer, but
problem is proofing tools.
We currently have several language packs, but we only need to install
proofing tools from those packs.
So question is how do we achive this and can we incorporate proofing tools
installation to the same procedure as base installation.
And how about .msp and config.xml file scenario. If we have customized both
files how can we get both run. I make script to config.xml does it run
automaticly also .msp file and vice versa or do I need to make script to
point both files ex. "/adminfile office.msp /config config.xml"?
Cheers,
Mikko
I have little trouble to understand deployment guides and need little help.
We are going to deploy Office 2007 Pro Plus product + some extra proofing
tools.
Deployment method is GPO with startup script.
Installing en-us customized base version of the Office is no brainer, but
problem is proofing tools.
We currently have several language packs, but we only need to install
proofing tools from those packs.
So question is how do we achive this and can we incorporate proofing tools
installation to the same procedure as base installation.
And how about .msp and config.xml file scenario. If we have customized both
files how can we get both run. I make script to config.xml does it run
automaticly also .msp file and vice versa or do I need to make script to
point both files ex. "/adminfile office.msp /config config.xml"?
Cheers,
Mikko