MSP's located in the Updates folder are applied during setup making it easy to add updates to the base installation as they become available. MSP file was saved in the Updates folder off the root of the installation directory. The custom installation can be invoked by running setup.exe with no commandline parameters if the custom. MSP file created with the OCT by doing the following: The Office 2007 setup routine can be ran against the. This will launch the OCT UI which is similar to the CIW in previous versions of Office and will guide you through the various installation options that will be saved in the. To launch the OCT run the following command: MSP file that is used to apply custom settings to an Office 2007 installation. Unlike previous versions of Office where the CIW created a transform (.MST), the OCT creates a. The OCT can be launched by running setup.exe with the /admin switch and it is no longer necessary to download the ORK to obtain this functionality as it is now built into the base setup routine.Ĭreating a Custom Installation with the OCT Similar to creating a transform in Office XP and 2003 using the Custom Installation Wizard (CIW) from the Office Resource Kit (ORK) you can customize Office 2007 installations by using the Office 2007 Customization Tool (OCT). Using the Office Customization Tool in the 2007 Office system If Office 2007 is not installed, then the plugins may not install correctly.Īs a rule of thumb, I guess it would be best to ensure Office 2007 is the first application to deployed and any applications that plug into Office 2007 are the last applications to be deployed to ensure Office 2007 exists correctly on the machine prior to the plugins being installed. Normally this shouldn't be a problem, except when plugins for Office (such as Symantec Antivirus or the SMSMSE Premium Antispam plugin) are deployed immediately after Office 2007 via GPO. All the MSI appears to do is generate the MSOCache (which is mandatory and cannot be removed) and installs "Office Source Engine" which then starts and does the actual Office 2007 installation. This is the actual installer for Office 2007, not the MSI file. In the background is a Windows service called "Office Source Engine".
When deploying via GPO, the MSI finishes running, and Windows continues on with the next new queued software installation (if there is any), but Office 2007 is not technically installed at this point. Then simply create a GPO software install as you normally would with previous Microsoft Office versions, but without a. To deploy Office 2007 via GPO, xcopy the source cd to shared folder on the server, edit the config.xml file (located in the version.WW folder in the shared folder location), and replace it's contents with the config.xml below.
Below is a very basic config.xml that is the same as doing a custom install, selecting all of Microsoft Office to install locally and then disabling just HTML Source Editing's Web Debugging.
0 kommentar(er)
