/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


Installing Lync2013

01/04/2013 16217 views

Im trying to deploy the Microsoft Lync 2013 client silently, and for the life of me cant get it to work...  I have tried setting it up under Distribution > Managed Installation,wraped it in a zip, played with the config.xml, tried a .MSP file.  Neither of those worked. 

 

So my thinking was to just do a script that runs the exe from a \\server\share\etc... with the config changed(also didnt work) and tried the /adminfile whatever.msp (nope)

 

Anyone know what im missing?

0 Comments   [ + ] Show comments

Comments


All Answers

0

I have done this just the way I have done all the office 2007 and 2010 installs...

Create an MSP & a copy of the config.xml next to the setup.exe
Then a batch file to run this:
"%~dp0setup.exe" /adminfile "%~dp0Yourfile.msp" /config "%~dp0Lyncinstall.xml"

 

I dont put the MSP in the updates folder, I keep it separate and tell the setup.exe where it is.

 

Answered 04/27/2014 by: Badger
Red Belt

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.
0

I would make sure that you are using the options shown here: http://technet.microsoft.com/en-us/library/jj204651.aspx

Also make sure that your config.xml file is in the root of the folder structure where the setup.exe file is. 

Answered 01/08/2013 by: WhitzEnd
7th Degree Black Belt

0

I am trying to do the exact same thing and have taken your approach as well. I have had success running a script to a Windows 7 machine. Unfortunatly for me most of my clients are Windows 7 enterprise and have not been able to get the same script to work on them. I did what WhitzEnd stated as well as I created a folder named logfiles and droped that in the x64 folder. I used the online shell script and be sure you save it as a .bat instead of the default .sh. Let me know if this works for you and if it does please let me know if you had to modify it. Here is a copy of the script I used:

 

 

 

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

 

 

 

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

 

set DeployServer=\\server\shared\MicrosoftLync\Lync2013\x64

 

 

 

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

 

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

 

 

 

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

 

set LogLocation=\\server\shared\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

 

: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

 

 

 

Endlocal

 

Answered 01/09/2013 by: otisruxpin
Senior White Belt

  • If Exist %systemroot%\%computername%.txt goto END

    If Exist "C:\Program Files (x86)\" goto X64

    Set ARCHITECTURE=x86

    REM Creating Lync and office suite Client folder on %USERPROFILE%

    IF NOT EXIST "%USERPROFILE%\Lync_Client\X86" MKDIR "%USERPROFILE%\Lync_Client\X86"

    REM Copying Lync software to Lync Software folder on %USERPROFILE%

    pushd "\\it\installationer\apps\CLIENT_APPS\Lync2010\x86"

    XCOPY "*.exe" "%USERPROFILE%\Lync_Client\X86" /I /Y /Q

    "%UserProfile%\Lync_Client\%ARCHITECTURE%\LyncSetup.exe" /install /silent

    Echo "Lync Successfully installed" on %COMPUTERNAME% > %systemroot%\%Computername%.txt

    Echo "Lync Successfully installed" on %COMPUTERNAME% >\\it\installationer\apps\CLIENT_APPS\Lync2010\x86\%computername%.txt

    :X64

    If NOT EXIST "C:\Program Files (x86)\" goto END

    Set ARCHITECTURE=x64

    REM Creating Lync Client folder on %USERPROFILE%

    IF NOT EXIST "%USERPROFILE%\Lync_Client\X64" MKDIR "%USERPROFILE%\Lync_Client\X64"

    REM Copying Lync software to Lync Software folder on %USERPROFILE%

    pushd "\\it\installationer\apps\CLIENT_APPS\Lync2010\x64"

    XCOPY "*.exe" "%USERPROFILE%\Lync_Client\X64" /I /Y /Q

    "%UserProfile%\Lync_Client\%ARCHITECTURE%\LyncSetup.exe" /install /silent

    Echo "Lync Successfully installed" on %COMPUTERNAME% > %systemroot%\%Computername%.txt

    Echo "Lync Successfully installed" on %COMPUTERNAME% >\\it\installationer\apps\CLIENT_APPS\Lync2010\x64\%Computername%.txt

    :END

    EXIT
0

I'm looking to do this as well... I would like to deploy to multi-architecture.

Answered 02/13/2013 by: akilpatrick
Brown Belt

 
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