Office 2007 Std Group Policy Deployment Failing

I'm trying to deploy Office 2007 Std using group policy. I used the OCT to
create an (MSP file) and stored it in the Updates folder.

The current office installation directory is the following

\\orion\technology\software\application\office12\s tandard.ww

When attempting to deploy the installation package via group policy, nothing
happens during the group policy update. I check the event logs and see that I
received 2 errors.

Event Id 102: The install of application Microsoft Office Standard 2007 from
policy Office 2007 Deployment failed. The error was : The installation source
for this product is not available. Verify that the source exists and that you
can access it.

Event Id 108: Failed to apply changes to software installation settings.
Software changes could not be applied.

Do I need to have a config.xml file for deployment? From my understanding
that the OCT was sufficient.

Any help would be appreciated.

Bruce

Hi Bruce,

Office 2007 setup basically gives you the choice of using GPO or using the
MSP files and the Office Custmization Tool for deployment. MS Installer
(MSI) doesn't deploy .MSP (patch files) via GPO.

You may want to review the information in the MS Office 2007 Resource Kit on
GPO deployment at
http://microsoft.com/office/ork
You can use scripting and the config.xml (which doesn't support all of the
details on its own of MS Office 2007 Setup.exe (with built in OCT) on its
own.

==========
"Kerevek" wrote in message
...
I'm trying to deploy Office 2007 Std using group policy. I used the OCT to
create an (MSP file) and stored it in the Updates folder.

The current office installation directory is the following

\\orion\technology\software\application\office12\s tandard.ww

When attempting to deploy the installation package via group policy, nothing
happens during the group policy update. I check the event logs and see that
I
received 2 errors.

Event Id 102: The install of application Microsoft Office Standard 2007 from
policy Office 2007 Deployment failed. The error was : The installation
source
for this product is not available. Verify that the source exists and that
you
can access it.

Event Id 108: Failed to apply changes to software installation settings.
Software changes could not be applied.

Do I need to have a config.xml file for deployment? From my understanding
that the OCT was sufficient.

Any help would be appreciated.

Bruce
--
Bob Buckland ?:-)
MS Office System Products MVP

"Bob Buckland ?:-)" wrote in message
...
| Hi Bruce,
|
| Office 2007 setup basically gives you the choice of using GPO or using the
| MSP files and the Office Custmization Tool for deployment. MS Installer
| (MSI) doesn't deploy .MSP (patch files) via GPO.
|
| You may want to review the information in the MS Office 2007 Resource Kit
on
| GPO deployment at
| http://microsoft.com/office/ork
| You can use scripting and the config.xml (which doesn't support all of the
| details on its own of MS Office 2007 Setup.exe (with built in OCT) on its
| own.

Having just started to plan deployment of Off2007, I feel that the changes
to the deployment are an extremely retrograde step, and could prevent me
from using this product - Off2003 still works, and in some areas,
particularly Outlook, works better - having to tell everyone to run it
minimised to prevent it taking up all available memory is not going to be
fun (no exchange, one POP connection, one IMAP connection = 390MB memory in
use - not good) - and one aspect of Off2003 that was better was the
configuration for deployment via Group policy. This allowed very fine
customisations of the installs, and even non-technical users could generate
their own transforms. Now, to get the same degree of control is impossible.

Having broken their own Installer technology by not allowing MST files is
not good, and not allowing all the customisation options in the hideous
config.xml file is even worse, and not providing a simple tool to construct
valid XML files is just silly.

Open office and Google Docs are looking more palatable by the day.

All the best,

pOB

Hi Bob,

So I took your advice and removed the OCT file and created an config.xml
file. Here is the config.xml script

Configuration Product="Standard"

Display Level="full" CompletionNotice="yes" SuppressModal="no"
AcceptEula="yes" /

Logging Type="Off" /

PIDKEY Value="enterkeyhere" /

USERNAME Value="username" /

COMPANYNAME Value="companyname" /

INSTALLLOCATION Value="%programfiles%\Microsoft Office" /

DistributionPoint
Location="\\orion\technology\software\application\ office12" /

Setting Id="Reboot" Value="IfNeeded" /

/Configuration

When just running the following command from the command line I can get the
config.xml to run properly

\\orion\technology\software\application\office12\s etup.exe /config
\\orion\technology\software\application\office12\S tandard.WW\config.xml

After verifying that my config.xml is correct when ran manually, I tried to
apply it to the GPO and used the following start.txt script in the startup
script

setlocal

REM ************************************************** *******************
REM Environment customization begins here. Modify variables below.
REM ************************************************** *******************

REM Get ProductName from the Office product's core Setup.xml file.
set ProductName=Standard

REM Set DeployServer to a network-accessible location containing the Office
source files.
set DeployServer=\\orion\technology\software\applicati on\Office12

REM Set ConfigFile to the configuration file to be used for deployment REM
(required)
set
ConfigFile=\\orion\technology\software\application \Office12\Standard.WW\config.xml

REM Set LogLocation to a central directory to collect log files.
Set LogLocation=\\orion\technology\software\applicatio n\Office12\Office12Logs

REM ************************************************** *******************
REM Deployment code begins here. Do not modify anything below this line.
REM ************************************************** *******************

IF NOT "%ProgramFiles(x86)%"=="" SET WOW6432NODE=WOW6432NODE\

reg query
HKEY_LOCAL_MACHINE\SOFTWARE\%WOW6432NODE%Microsoft \Windows\CurrentVersion\Uninstall\%ProductName%
if %errorlevel%==1 (goto DeployOffice) else (goto End)

REM If 1 returned, the product was not found. Run setup here.
eployOffice
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% Setup ended with error code %errorlevel%.
%LogLocation%\%computername%.txt

REM If 0 or other was returned, the product was found or another error
occurred. Do nothing.
:End

Endlocal

I then try to run the gpo by performing a gpupdate /force on the client
machine and I still receive the same event errors.

Any suggestions?

Bruce

"Bob Buckland ?:-)" wrote:

Hi Bruce,

Office 2007 setup basically gives you the choice of using GPO or using the
MSP files and the Office Custmization Tool for deployment. MS Installer
(MSI) doesn't deploy .MSP (patch files) via GPO.

You may want to review the information in the MS Office 2007 Resource Kit on
GPO deployment at
http://microsoft.com/office/ork
You can use scripting and the config.xml (which doesn't support all of the
details on its own of MS Office 2007 Setup.exe (with built in OCT) on its
own.

==========
"Kerevek" wrote in message
...
I'm trying to deploy Office 2007 Std using group policy. I used the OCT to
create an (MSP file) and stored it in the Updates folder.

The current office installation directory is the following

\\orion\technology\software\application\office12\s tandard.ww

When attempting to deploy the installation package via group policy, nothing
happens during the group policy update. I check the event logs and see that
I
received 2 errors.

Event Id 102: The install of application Microsoft Office Standard 2007 from
policy Office 2007 Deployment failed. The error was : The installation
source
for this product is not available. Verify that the source exists and that
you
can access it.

Event Id 108: Failed to apply changes to software installation settings.
Software changes could not be applied.

Do I need to have a config.xml file for deployment? From my understanding
that the OCT was sufficient.

Any help would be appreciated.

Bruce
--
Bob Buckland ?:-)
MS Office System Products MVP