office 2010 deployment

[itgeek]

We have created a computer startup script for office 2010, the installation works but takes about 10 mins per machine!! Could I ask is it possible to display a message when running startup?

[FN-GM]

Can we look at the existing script please?

 

Does it have a /S /silent switch? Try changing that to /passive

[strawberry]

why not execute the script overnight using psexec? . It'll allow you to run a script remotely.

[Michael]

If it's running as a startup script (as above), and you run it with the passive switch users should see a progress bar.

 

You should also consider temporarily putting the deployment on hold, as Office 2010 SP1 is due next month. Creating an admin install point, you can include the service pack as part of the deployment.

[SYNACK]

If it's running as a startup script (as above), and you run it with the passive switch users should see a progress bar.

 

You should also consider temporarily putting the deployment on hold, as Office 2010 SP1 is due next month. Creating an admin install point, you can include the service pack as part of the deployment.

 

 

Oooh, have the finally changed it to allow that, 2007 just ran the initial install them methodicly installed all the updates one at a time afterwards making the install take way too long.

[itgeek]

Here is the script, I cant find the /s we set the oct tool to suppress modal??

 

setlocal

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

REM Get ProductName from the Office product's core Setup.xml file, and then add "office14." as a prefix. 
set ProductName=Office14.PROPLUS

REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\server

REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\server

REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\server

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

IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)

REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if NOT %errorlevel%==1 (goto End)

REM Check for 32 and 64 bit versions of Office 2010 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS) 
:ARP86
reg query HKEY_LOCAL_MACHINE\SOFTWARE\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.
:DeployOffice
start /wait %DeployServer%\setup.exe /adminfile %DeployServer%\Updates\Office2010ProPlus.msp
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

[Michael]

Oooh, have the finally changed it to allow that, 2007 just ran the initial install them methodicly installed all the updates one at a time afterwards making the install take way too long.

 

I believe Office 2010 updates just like Office 2007 from the Updates folder. You can't slipstream like Office 2003

 

The point I was making however, is deploying Office 2010 now would involve repeating the process to deploy Office 2010 with SP1.

[Michael]

I believe you need to add the passive switch to this line:

 

start /wait %DeployServer%\setup.exe /adminfile %DeployServer%\Updates\Office2010ProPlus.msp