RE: Upgrading elements of Office 2003 to 2007 using AD / GPO
- From: TimStokeUK <TimStokeUK@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 17 Aug 2009 07:19:02 -0700
Thanks for the info TXGuy.
I presume that you mean to create a .cmd file that runs at computer startup
to install the software with the relevant .msp file as a modifier? Won't
that run the script, and therefore re-install the software, everytime the
computer is started though? Or is there another way to define a script in a
GPO that means it only executes once?
"TXGuy" wrote:
If you want to initially upgrade only Outlook and then later upgrade the
remaining apps, you can configure the Feature Installation States and Removal
Behavior in the OCT for initial and future configurations, just as you did in
the old CIW, and then use "Setup /adminfile <path>\<file>.msp" commands to
use the appropriate .MSP to customize the installation. Office 2007 is not
designed to be deployed directly via GPO but the alternate method is to use a
GPO startup script to "emulate" the process:
Office Customization Tool in the 2007 Office system
http://technet.microsoft.com/en-us/library/cc179097.aspx
Use Group Policy to assign computer startup scripts for 2007 Office deployment
http://technet.microsoft.com/en-us/library/cc179134.aspx
Hopefully this helps clarify things a bit!
--
TXGuy [MSFT]
.
- References:
- Upgrading elements of Office 2003 to 2007 using AD / GPO
- From: TimStokeUK
- RE: Upgrading elements of Office 2003 to 2007 using AD / GPO
- From: TXGuy
- Upgrading elements of Office 2003 to 2007 using AD / GPO
- Prev by Date: Re: Office Home & Student 2007 Product Key(Trial Version)
- Next by Date: Re: install Office on a work computer
- Previous by thread: RE: Upgrading elements of Office 2003 to 2007 using AD / GPO
- Next by thread: RE: "Please wait while Windows Configures Microsoft Office 2007" Messa
- Index(es):
Relevant Pages
|