Re: Use Group Policy to assign computer startup scripts for 2007 Office deployment



The Office 2007 pro install takes nearly 40 minutes, to long for users to
wait at logon. I just edited the local machine policy to run this script on
startup and got the same results. The script appears to end without doing
anything.

"Darren Mar-Elia" <dmanonymous@xxxxxxxxxxxxx> wrote in message
news:73B2CC36-E75A-4C47-932B-5E2EC3EBEAAE@xxxxxxxxxxxxxxxx
I haven't tried this specifically (I was able to get Office 2007 to install
via Software Installation but it is kludgy) but is there a reason you are
using Shutdown as opposed to Startup scripts? It could be that the timing
of the shutdown script is preventing a long-running task like an office
install from running.

Darren

--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policy

Simplify Group Policy Troubleshooting with the NEW GPExpert
Troubleshooting Pak 1.0 at http://www.sdmsoftware.com/products.php

Visit the GPOGUY: http://www.gpoguy.com -- The Windows Group Policy
Information Hub:
FAQs, Training Videos, Whitepapers and Utilities for all things Group
Policy-related

"msnews" <Kirk.Patti@xxxxxxxxxxx> wrote in message
news:eeDBOjhyHHA.5964@xxxxxxxxxxxxxxxxxxxxxxx
I'm trying to deploy Microsoft Office 2007 using group policy. I found
this TechNet article to accomplish it using startup scripts, since the
ProPlusWW.msi doesn't work.

http://technet2.microsoft.com/Office/en-us/library/a57c8446-b959-4025-a866-b690ddcaa66d1033.mspx?pf=true

I set GPO in an OU I created for the deployment and placed several XP
machines under it. It is supposed to run the batch file listed in the
article from Computer Configuration Windows Settings Scripts Shutdown.
The batch file essentially runs the setup.exe with the xml modifier and
outputs a text log.

The batch file performs the install flawlessly when run interactively on
the XP machines. I'm using virtual machines so I can revert back at
will, from snapshots.

For some reason GP is not updating the machines local policy with the
setting I have set on the OU, even if I run gpupdate on them.

Why isn't GP being pushed down?

I decided to make the changes locally that GP is supposed to be pushing,
to test if the script would run at shutdown and perform the install.
During shutdown I know the batch file is being accessed but it ends in a
couple seconds without doing anything, again if I run it interactively it
works fine.

Has anybody been successful following this procedure to deploy Office
2007?

Does anyone have another method deploy Office 2007 using GP?





.



Relevant Pages

  • Re: Further Questions on Adding group to local administrators group via GPO
    ... There are multiple ways of achieving the result required, and it depends if you want to install it for all users on certain machines or for all machines for certain users. ... you need to create a policy and go to the Software section of the machine component and create the install package. ... you do not require Local Admin rights to get the installation of the Software to work.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2000 Pro will not process logon script
    ... newer machines run the script and some of the older ones do not. ... I am not familar with the "slow link" policy. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2000 Pro will not process logon script
    ... newer machines run the script and some of the older ones do not. ... I am not familar with the "slow link" policy. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2000 Pro will not process logon script
    ... newer machines run the script and some of the older ones do not. ... I am not familar with the "slow link" policy. ... Would there be a differnce in the slow link process between XP ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2000 Pro will not process logon script
    ... newer machines run the script and some of the older ones do not. ... I am not familar with the "slow link" policy. ... Would there be a differnce in the slow link process between XP ...
    (microsoft.public.windows.server.active_directory)