[font="trebuchet ms"]Dear all,
[font="trebuchet ms"]I'm in the process of deploying Office 2007 Professional Plus to Vista SP1 32bit clients using GPO (Startup Script).
[font="trebuchet ms"]
[font="trebuchet ms"][font="trebuchet ms"]@echo off[font="trebuchet ms"]
if exist "C:\program files\microsoft office\Office12\winword.exe" goto eof
[font="trebuchet ms"]start /wait [font="trebuchet ms"]\\ro-adminftp\swdist$\Office2007\setup.exe [font="trebuchet ms"]

[font="trebuchet ms"]
[font="trebuchet ms"]Setup.exe uses an .MSP file in [font="trebuchet ms"]\\server\share\office12\updates[font="trebuchet ms"] and a very simple config.xml (which basically only logs - or should -- I've never been able to find "Microsoft Office Professional Plus Setup(*).txt") to configure Office 2007.
[font="trebuchet ms"]
[font="trebuchet ms"][font="trebuchet ms"]<Configuration Product="ProPlus">
[font="trebuchet ms"] <!-- <Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" /> -->
<Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" />
<!-- <PIDKEY Value="BCDFGHJKMPQRTVWXY2346789B" /> -->
[font="trebuchet ms"] <!-- <USERNAME Value="Customer" /> -->
<!-- <COMPANYNAME Value="MyCompany" /> -->
<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->
<!-- <LIS CACHEACTION="CacheOnly" /> -->
<!-- <SOURCELIST Value="\\server1\share\Office12;\\server2\share\Office12" /> -->
<!-- <DistributionPoint Location="\\server\share\Office12" /> -->
<!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->
<!-- <Setting Id="Reboot" Value="IfNeeded" /> -->
<!-- <Command Path="msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->
[font="trebuchet ms"]</Configuration>

[font="trebuchet ms"]
[font="trebuchet ms"]In essence, this works. However, users don't have to await the installation process - they can log right in. This causes funny situations where the individual applications aren't (fully) installed yet. Some 20 minutes after initiation (well after the user has logged on) the setup.exe, msiexec.exe and ose00000.exe processes disappear and Office 2007 is fully functional.

[font="trebuchet ms"]Most dicussions I've come across debate deployment strategies but don't go into any detail regarding the actual installation.
[font="trebuchet ms"]
[font="trebuchet ms"]I was hoping the /wait switch would cause Vista to wait for the Office 2007 deployment to finish before showing the Logon screen, but evidently this simple hold up is insufficient.
[font="trebuchet ms"]Deployment directly through an MSI tied to a GPO worked intially, but only seems to installed the Shared applications, reboots, allows the user to login then only continues when you start "New Office Document.lnk" from the start menu. Then reboots again. No go.
[font="trebuchet ms"]
[font="trebuchet ms"]Please advise, discuss and hopefully we'll all learn something today.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


[font="trebuchet ms"]SitRep -- Status Update


[font="trebuchet ms"]Dear all,
[font="trebuchet ms"]Another issue I was having were extremely long installation times (about 40 minutes -- on certified gbit). I then proceeded and first copied the Distribution Point's contents to C:\Install before running the batch file. This resulted in installation times in the 5-10 minutes range.
[font="trebuchet ms"]
[font="trebuchet ms"]At the moment we're leaning towards a solution where we distribute the needed source files to the client through WDS, then initiate the installation with a Startup Script through GPO.
[font="trebuchet ms"]
[font="trebuchet ms"]Climb onto your keyboards and dive into the discussion!
Answered 12/12/2008 by: MajorMalfunction
Yellow Belt

Please log in to comment
Here is my two cents:

I have also come across long installation times so I decided to create a logoff script that upgrades the Office Suite at logoff (shutdown) rather than logon. It usually takes around 20 minutes to complete but the user is less impacted.
Answered 12/19/2008 by: ScriptGuy
Yellow Belt

Please log in to comment