Office Failing To Install After O/S Deployment [Via WDS]

[6Foot2]

We deploy Windows 7: Pro: 64 Bit: SP1 using WDS. Applications are deployed with a mix of MSI and .BAT files.

 

Office 2010 [32 Bit] is deployed using a .BAT file:

 

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=\\FS\Office2010SourceFiles

REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\FS\Office2010SourceFiles\ProPlus.WW\config.xml

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

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 /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

 

[Customised to our requirements]

 

This was working well enough but we had to change how Sophos was deployed. It was deployed from the Sophos Console but that wasn't working so we switched to a .BAT file:

 

@ECHO OFFREM – For 32 Bit Windows 
if exist “C:\Program Files\Sophos\Sophos Anti-Virus\SavService.exe” goto End
REM – For 64 Bit Windows 
if exist “C:\Program Files (x86)\Sophos\Sophos Anti-Virus\SavMain.exe” goto End
REM Deploy to Windows 7/2008 R2  
\\Verapps01\SophosUpdate\CIDs\S000\SAVSCFXP\Setup.exe -s \ -user "Domain\Installer" -pwd "password" -mng yes
:End

 

Now Sophos deploys successfully but we find that Office does not. The Office install error is:

 

08/06/2012 15:11:31.61 Setup ended with error code 1618.

 

Another install process is already running?

 

I am guessing that this is either the initial Sophos install or Sophos updating when Office is trying to install.

 

Has anyone else solved this one?

 

Many thanks.

[plexer]

Install office first?

 

Ben

[6Foot2]

Install office first?

 

Ben

 

OK. Had thought of that but could not think of how to make sure that happens.

 

The batch file that installs Sophos is at the top level OU for the workstations. For various operational reasons the batch file that installs Office is applied to OUs that are lower down in our AD structure.

 

How would I ensure that Office is installed before Sophos given these conditions?

 

Thanks.

[plexer]

With that structure you can't without changing where sophos is deployed from.

 

Can you identify the process that is still running?

 

The office install script checks to see if office is installed and if it doesn't find the markers specified it should run on next boot and install or do you have it only attempting to run once?

 

Ben

[6Foot2]

...Can you identify the process that is still running?...

 

I would like to as it is only a guess at the moment that Sophos is causing the problem.

 

...The office install script checks to see if office is installed and if it doesn't find the markers specified it should run on next boot and install or do you have it only attempting to run once?...

 

No. The Office install error logs show that Office is trying to install at each station boot:

 

29/05/2012 11:50:43.51 Setup ended with error code 1618.

29/05/2012 12:55:02.25 Setup ended with error code 1618.

30/05/2012 9:09:23.49 Setup ended with error code 1618.

30/05/2012 14:52:11.49 Setup ended with error code 1618.

30/05/2012 15:10:09.86 Setup ended with error code 1618.

31/05/2012 8:50:21.10 Setup ended with error code 1618.

31/05/2012 13:54:09.58 Setup ended with error code 1618.

31/05/2012 15:44:39.08 Setup ended with error code 1618.

01/06/2012 9:07:52.96 Setup ended with error code 1618.

01/06/2012 10:38:13.00 Setup ended with error code 1618.

01/06/2012 15:02:16.30 Setup ended with error code 1618.

01/06/2012 15:11:42.57 Setup ended with error code 1618.

I am now installing Office manually at rebuilt stations until I can find a satisfactory answer.

[sted]

Sophos does do that to office installs. Simple answer copy n paste your sophos.bat lines at the end of office.bat

[6Foot2]

Sophos does do that to office installs. Simple answer copy n paste your sophos.bat lines at the end of office.bat

 

That works I guess. I had hoped for a more 'sophisticated' solution.

 

I will give it a go next week.

[morganw]

Or try forcing a reboot straight after the Sophos installer has finished. I recently did that in an MDT sequence and it seems to give up on trying to immediately update itself after a reboot, you would just have to make sure you aren't interupting anything else. I would recommend MDT as a way to enforce the order of the applications that you are installing or look at something like WPKG that you can run in the style of a service or execute directly as a script.

[sted]

That works I guess. I had hoped for a more 'sophisticated' solution.

 

I will give it a go next week.

 

Why complicate things