Software Deployment Question

Kace 1000 scripting Microsoft Lync 2013

12/21/2012 8971 views

I am new at scripting, so please give me as much detail as possible. I am trying to deploy Microsoft Lync 2013 to some test systems. I have one success and one failure. I am doing this through an online shell script using a bat file that I converted from Office 2010. The only difference between the 2 systems is one is on Windows 7 32bit and the other is on Windows 7 Enterprise 32bit. The log file shows "Setup ended with error code 216." From what I can tell is that the error code is stands for "The image file %1 is valid, but is for a machine type other than the current machine". I have tried using the msi installer vs. using bat installation but, could not get the msi to install on any machine. Has anyone had success deploying any of the Office 2013 products? If not I'll take suggestions on possible solutions!

0 Comments   [ + ] Show comments


All Answers


Which machine does it fail on?


Answered 12/25/2012 by: jdornan
Red Belt

  • It fails on the Windows 7 Enterprise.
  • Can you show us how you created the script?

Here is the script :



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=Lync


REM Set DeployServer to a network-accessible location containing the Office source files.

set DeployServer=\\server\share\Software\MicrosoftLync\Lync2013\x64


REM Set ConfigFile to the configuration file to be used for deployment (required)

set ConfigFile=\\server\share\Software\MicrosoftLync\Lync2013\x64\lync.WW\config.xml


REM Set LogLocation to a central directory to collect log files.

set LogLocation=\\server\share\Software\MicrosoftLync\Lync2013\x64\LogFiles


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


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) 


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.


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.




And the config.xml file that it is pointing to:

<Configuration Product="Lync">


<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />


<Logging Type="verbose" Path="%temp%" Template="LyncSetupVerbose(*).log" />


<USERNAME Value="Customer" />


<COMPANYNAME Value="MyCompany" />


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




<LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" />


<DistributionPoint Location="\\server\share\software\MicrosoftLync\Lync2013\x64\lync.ww" />


<OptionState Id="LOBiMain" State="absent" Children="force" />


<Setting Id="SETUP_REBOOT" Value="never" />


<Command Path="%windir%\system32\msiexec.exe" Args="/i \\server\share\software\MicrosoftLync\Lync2013\x64\lync.ww\lyncww.msi" QuietArg="/q" ChainPosition="after" Execute="install" />



Answered 12/27/2012 by: otisruxpin
Senior White Belt

  • So, it looks like this will work with multi-architecture? x86/x64...?

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ