Lync 2013 deployment via SCCM 2007

Hi All,
We are trying to deploy Lync 2013 to Windows 7 workstations that currently have Office 2013 professional installed on.
Unfortunately we arent have much luck at the moment..
It seems to push Office 2013 tools out but not Lync itself..
The package was created using the Office customisation tool
the sccm command is set to setup.exe /adminfile updates \name.msp and also tried msiexec command line but no joy
Please can someone advise me how to achieve this Lync rollout?
Kind Regards, Enjoy the weekend!
James
J R Vose

Are you using Office2013Professional (the Retail edition), or are you using Office2013ProfessionalPlus (the Volume Licensing edition)?
Or are you using Office365ProPlus (the Subscription edition of 2013, which comes in a Click-to-Run format)?
The steps may vary for you, depending upon the above.
Also, which Lync are you using for the install? (there are various ways to deploy Lync, depending upon what you have)
e.g. if you have previously deployed Office2013ProfessionalPlus, and at that time, you customised the installation such that Lync would not be enabled, and now, you wish to enable Lync, you would use the tip from Daniel, via something like this:
setup.exe /modify ProPlus /config AddLyncConfig.xml
[the AddLyncConfig.xml would be a file you create, containing the content like Daniel has suggested]
refer: https://technet.microsoft.com/en-us/library/cc178956.aspx
These steps are valid for Office2013ProfessionalPlus, but aren't valid for Office2013Professional nor for Office365ProPlus.
Ultimately, it depends whether your are "adding a new product" or  are "modifying an existing product".
ConfigMgr is merely automating your instructions, it doesn't "know" if what you are telling it is "valid".
Have you tried to install/enable Lync using manual steps first as a test?
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

  • Deploying Lync 2013 client and SCCM Detection method

    So I am deploying the stand alone Lync 2013 client via SCCM 2012 R2, I have used OCT to create a .MSP, and I am trying to import it into SCCM.  However, I am curious as to what others are using for the Detection method?  Normally I would just
    use the MSI code, but since there is no single MSI, that is not possible with this particular version?  I'm not sure what the best method would be, Option 1 is to find a registry key that is installed by Lync, or Option 2, use a file, maybe Lync.exe under
    the Program Files?

    From the testing I've done Lync creates this reg location...
    HKLM>Software>Microsoft>Office>15.0>Lync
    Try using one of the keys in there, or you could use the file version but not sure if this would change with updates.

  • Lync 2013 client deployment via SCCM with silent uninstall of Communicator / Live Meeting / Plugin

    Hi
    We are rolling out Lync 2013 across our org to many remote sites and are wondering the best approach for this.
    We hope to leverage our SCCM, but so far we've only been installing Lync manually in our local test group.
    I noticed that when installing Lync, it doesn't remove Communicator, Live Meeting, or the Live Meeting plugin for Outlook though.
    Ideally, we would want to be able to push Lync 2013 client (standalone version, not Office 2013 Suite) via SCCM as well as uninstall Communicator 2007 R2, Live Meeting 2007 and Conferencing Add-in for Microsoft Office Outlook, all silently. Whether this
    can be done while the user is logged in and using Outlook/Communicator, I am unsure (probably not), so doing this overnight with users logged off but machines on would probably work best.
    Is there any documentation / guides from MS or other blog sites that have gone through this same process? From the searching I've done, it doesn't seem to be too common for a large deployment / jump from OCS 2007 to Lync 2013 on-premise.

    Hi,
    refer to this article it might help
    http://social.technet.microsoft.com/Forums/lync/en-US/cf9ca58c-b9e8-465c-afb4-ed3992092f81/lync-2013-client-silent-installation
    also did you try using Group Policy?
    http://blogs.technet.com/b/mir/archive/2011/06/04/how-to-automate-lync-client-2010-deployment-in-multi-architect-environment-using-active-directory-group-policy.aspx
    hope this help
    If you find this helpful
    please click "Vote as Helpful" if it answered your question please click "Mark as Answer"
    Mostafa Eltohamy
    Blog: http://Lyncdude.com  Twitter:
      LinkedIn:
      XING:

  • Lync 2013 x64 silent client deployment via SCCM 2012 SP1

    Greetings everyone!
    I ran into a problem with Lync 2013 x64 silent deployment.
    I need to provide every workstation with Lync 2013 client, so i decided to use deployment via SCCM 2012 sp1.
    I created 2 msp files with OCT, one based on x86 Office 2013 Proplus, and other based on x64 Office 2013 Proplus.
    Added them as applications to sccm software library.
    Deployment of Lync 2013 x86 application was a success with over than 80% compliance. 
    But all Lync 2013 x64 automatic installations finish with different errors.
    I created special device collection for workstations with office 2010 x64 and 2013 x64, because i can't install other architecture products once it has x64 product installed.
    My membership query-rules for this collection:
    Office 2013 x64
    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
    = SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90150000-0011-0000-1000-0000000FF1CE}"
    Office 2010 x64
    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
    = SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90140000-0011-0000-1000-0000000FF1CE}"
    My application deployment type points to setup.exe in office 2013 x64 installation folder, where i created msp file in updates folder via OCT and edited config.xml file in proplus.ww folder.
    So my installation program looks like this setup.exe /adminfile updates\1lync.msp /config proplus.ww\config.xml
    The same configuration works with Lync 2013 x86 deployment, except other setup folders.
    When i try running installation program setup.exe with /adminfile and /config parameters locally, it installs successfully without errors or warnings.
    I'm trying to find out problem source, does anyone have ideas what I am doing wrong?
    Also i'm trying to reduce office 2013 installation folder size, what subfolders are necessary for Office 2013 proplus installation (still installing only lync with common files and tools)? Because now 3.5 GB package is quite hard to distribute to sccm secondary
    sites with deployment point.
    Thanks in advance.

    Hi,
    Here are some tips and tricks for your reference.
    Tips and Tricks: Deploying Lync 2013 client using SCCM 2012 | Lync 2013 Client Customization for SCCM 2012 Deployment Package
    http://zahirshahblog.com/2014/01/08/tips-and-tricks-deploying-lync-2013-client-using-sccm-2012-lync-2013-client-customization-for-sccm-2012-deployment-package/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Problem deploying Office 2010 via SCCM 2007

    Hello, 
    I have a problem with deploying Office 2010 to Workstations. 
    I did exactly as instructed settings: http://technet.microsoft.com/en-us/library/ff404178(v=office.14).aspx
    When you release it manually (I tested it) everything went fine but when I let you install via SCCM 2007 workstation, just run setup.exe and processes stuck there and nothing happens.I have no idea why setup.exe. What is wrong any ideas?
    (It does not matter who's office: 013,010,07)
    Thanks

    Are you using any silent key like setup.exe/s S  or setup/quite etc.. ??
    Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights
    No, should i? Microsoft does not say anything like that...  Name field,
    which in this example is named Office 2010 silent installation.
    In the Command line field,
    in this example type setup.exe.
    Of course I'll try but I do not suppose this helped ...

  • Windows 8.1 Pro OS Deployment Using SCCM 2007 SP2 R3 - Possible? Supported?

    I have been able to successfully capture and deploy a Windows 8.1 Pro image to a desktop, however the Apply Device Drivers action consistently fails with the following error in the smsts.log:
    Driver-signing policy cannot be configured on this operating system
    After that point no suitable drivers are able to be found and the task sequence is unable to proceed due to the lack of drivers. I'm using the same task sequence I used for Windows 8 OS deployment within SCCM 2007 SP2 R3. I'm just looking for confirmation
    on whether or not driver deployment is now broken in Windows 8.1.

    The toolset has been updated significantly to support Win 8.1. Exact technical details of the changes aren't published anywhere beyond the fact that it simply isn't supported.  It's insufficient simply because it is known not to work -- beyond that,
    does it really matter?
    Note that even Win8 deployment within ConfigMgr is unsupported so basically you're off into uncharted territory and assuming a lot of risk in doing so.
    Jason | http://blog.configmgrftw.com

  • Windows 7 deployment using SCCM 2007 SP2

    Hi,
    We planning to do Windows 7 deployment using SCCM 2007 SP2 so we have some queries regarding same.
    Is it possible to take entire HDD backup & restore using SCCM 2007 SP2? Also is it recommended to do so?
    What will be the effective method to deploy OS at remote branches?
    If we want to save the network bandwidth then what will way to send image to distribution point and client as well.
    Is it mandatory to have PXE boot enable in bios & set as first boot preference on each client machine for PXE initiated windows 7 deployment? If so then is there any option to enable PXE boot & set as first preference on client machine
    remotely?
    Is it possible to deploy OS in other than C drive i.e D or E to have dual boot option?
    Which we will be best method to have zero touch deployment without any end user intervention and why?
    Please help to clarify.

    As Jason said, these are the configurations that requires some high level skills to configure it, the answers are the same as said by Arnav... below links would give you a good heads up for the OSD in SCCM if you still want to try it on your own...
    http://download.microsoft.com/download/7/C/9/7C9A54AC-9661-48CA-9A7C-E3D2B5B23CF2/SystemCenterConfigurationManager2007OperatingSystemDeploymentGuide.pdf 
    http://blogs.technet.com/b/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx
    https://blogs.technet.com/b/birojitn/archive/2010/01/20/windows-7-deployment-using-sccm-2007-sp2.aspx
    bluerail

  • Lync 2013 client deployment via SCCM 2012 forcing restart

    All, 
    I am attempting to deploy the Lync 2013 x86 client via SCCM 2012 to 158 machines running the Office 2010 suite. My package runs, and the installs complete but they are forcing a restart after the install even though I have gone in to everything that I can
    think of to tell the install not to force a restart. I am a newb in the ways of SCCM so I have been self teaching, and I may have missed something. 
    I have gone into the config.xml and changed the value SETUP_REBOOT to NEVER. 
    In the program properties I have RUN set as HIDDEN, and AFTER RUNNING set to NO ACTION REQUIRED. 
    Is there something that I am missing to stop the users machine from restarting after the install completes?

    Great, unfortunately it will be because files (usually shared DLLs) are in use as Office is opened, despite it being an older version. 
    Agree it's not optimal, I usually just tell clients that they will need to reboot, or that it will push out overnight (when I schedule it) and their computer will restart, so make sure they save everything.
    If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
    Georg Thomas | Lync MVP
    Blog www.lynced.com.au | Twitter
    @georgathomas
    Lync Edge Port Check (Beta)

  • Deploying Lync 2010 client via SCCM

    I am trying to distribute the new Lync client via SCCM (SCCM is not the problem here, this related to any software distribution product).
    I am getting frustrated at the way the new client has been packaged - LyncSetupEval.exe in particular. Why can't Microsoft provide a simple MSI file?
    I can run the LyncSetupEval.exe file with /Install /Silent, but this managed to crash OUTLOOK.exe when it runs. Also when it completes, it automatically starts communicator.exe in the SYSTEM context, meaning that unless you restart your machine, you
    cannot run the Lync client in the user context. 
    Is anyone else having the same frustrations? I've played around with the files in the OCSetup directory, but there are of no use.

    Hi Ryan,
    Happy to share. I do a simple messy batch file / VB Script combination like this:
    @echo off
    ECHO Set wshShell = CreateObject( "WScript.Shell" ) >> usermessages.vbs
    echo wshShell.Popup "The Microsoft Lync 2010 client is about to be installed.  Please close Microsoft Outlook and Internet Explorer before clicking OK to continue.", 300, "Microsoft Lync 2010 installation" >> usermessages.vbs
    ECHO WScript.Sleep(5000) >> usermessages.vbs
    WSCRIPT.EXE usermessages.vbs
    DEL usermessages.vbs /q
    ECHO Installing Microsoft Lync 2010...
    taskkill /F /IM communicator.exe
    taskkill /F /IM outlook.exe
    taskkill /F /IM iexplore.exe
    LyncSetup.exe /Install /Silent
    taskkill /F /IM communicator.exe
    msiexec.exe /p OUTLOOK.msp /qb-!
    office2007-kb936864-fullfile-x86-en-us.exe /passive /norestart
    msiexec.exe /update Lync.msp /qb-!
    ECHO Set wshShell = CreateObject( "WScript.Shell" ) >> usermessages.vbs
    echo wshShell.Popup "The Microsoft Lync 2010 client installation was successful and can now be run from the Start Menu.", 300, "Microsoft Lync 2010 installation" >> usermessages.vbs
    WSCRIPT.EXE usermessages.vbs
    DEL usermessages.vbs /q
    I'm sure it could be a lot nicer, there is no error passing or anything but it has served me well.
    blog.danovich.com.au

  • How to remove OCS and install lync 2013 on MS Office 2007 and 2010

    Hi,
    We need to install lync 2013 on our systems having office 2007 and 2010 via SCCM 2012.
    Please suggest.
    Regards, Syed Fahad Ali

    Lync 2013 no longer has its own installer, but instead uses the Office installer.  You can create a customized installation and deploy it just like you do with Office:
    http://technet.microsoft.com/en-us/library/jj204827.aspx
    I hope that helps,
    Nash
    Nash Pherson, Senior Systems Consultant
    Now Micro -
    My Blog Posts
    If you've found a bug or want the product worked differently,
    share your feedback.
    <-- If this post was helpful, please click "Vote as Helpful".

  • IE11 prereqs deploy via SCCM 2012

    Hi,
    To deploy IE 11 on Windows 7, apparently you need to install 9 prereqs (see http://www.itninja.com/blog/view/how-to-package-internet-explorer-11-x64-for-windows-7-x64): 
    These prereqs are: KB2834140
    KB2670838 KB2639308 KB2533623 KB2731771
    KB2729094 KB2786081 KB2888049 KB2882822
    I don't find the prereqs in red within sccm 2012. Did check the classifications (checked them all in software update point) and did a full sync.
    Please advise howto find/deploy them (I hoped to do this via windows updates and not via seperate packages).
    J.
    Jan Hoedt

    Hi,
    I just checked the first Patch:
    http://support.microsoft.com/kb/2670838
    And there you can find the section: How to obtain this update.
    Is there is Windows Update not noted, you can't receive this Patch through Windows Updates. Consider to deploy the Patch as prerequisite as an application. Here you can find an example of installing hotfixes as prerequisite for the App-V client:
    http://scug.be/sccm/category/detection-methods/
    Detection method is VBScript. Ar you want to create a Detection method with Powershell, refer to this blog post:
    https://sccmfaq.wordpress.com/2013/03/19/sccm-2012-application-detection-with-powershell-and-code-signing/
    Hope this helps.
    www.sccmfaq.ch

  • Skype for Business not updating icons on start menu - Using OCT for Lync 2013 deployment

    We're currently deploying Lync 2013 to out fleet using the OCT to customize where the shortcuts are created.
    What we are finding is that the Skype for Business Patch does not update these icons.  It only updates the icons if they are in the default location (no OCT).
    Is there a standalone Installer for Skype for Business we could apply a TRANSFORM to? Or some other method of updating all icons startmenu, taskbar etc.
    Thanks

    Hi Alan Dooley,
    Have you tried to create a new desktop shortcut ?
    In addition, you can try to follow the FAQ below to rebuild the icon cache.
    https://social.technet.microsoft.com/Forums/windows/en-US/bea47202-d869-4155-8c8f-2a5b8bd7be1d/forum-faqhow-to-rebuild-icon-cache
    Best regards,
    Eric
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Migrating Clients from SCCM 2007 to SCCM 2012 R2 via SCCM 2007 PACKAGE

    I can migrate sccm clients from sccm 2007 to sccm 2012 using sccm 2007 package with sccm 2012 client?
    Thanks!
    Atenciosamente Julio Araujo

    Thanks for help me Peter and Torsten but this documentation says:
    "You cannot upgrade Configuration Manager 2007 clients to System Center 2012 Configuration Manager by using this method.
    In this scenario, use automatic client upgrade, which automatically creates and deploys a package that contains the latest version of the client."
    I Need migrate clients from sccm 2007 to sccm 2012 r2 and
    I thought ofcreate a package in sccm 2007 with a sccm 2012 client.
    Atenciosamente Julio Araujo

  • How to connect Lync 2013 client with OCS 2007 R2 Edge server

    Hi,
    We have OCS 2007 R2 Edge server for external & OCS 2007 R2 FE Server for internal access in our environment.
    We able to access internally Lync2013 clients with OCS 2007R2 server, however from external we cannot access Lync2013 client with OCS2007 R2 server.
    Is there any patch or registry key trick to access OCS from lync2013 client externally? We cannot immediately migrate to Lync2013 server from OCS.
    Any help
    MD

    Hi,
    I suggest you still use OCS 2007 R2 client to login OCS 2007 R2 Server untill finishing migration to Lync Server 2013, as using Lync client with OCS 2007 R2 Server will offer a pretty limited experience.
    Here is a great blog about Lync 2010 Client unsupported with OCS, it is for Lync 2010 client but similar for Lync 2013 client:
    http://blog.schertz.name/2010/09/lync-client-unsupported-ocs/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
    Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • PXE Boot a client to connect to a Remote Desktop Session Host/Terminal Server Farm via SCCM 2007

    Hi all,
    we've got a bunch of old desktops which are destined for disposal but i was wondering if we couldn't use them as disk-free clients to connect to our Remote Desktop farm. I did some digging and have managed to put together an iso which will boot
    the machine into WinPE and then connect to our farm. However, since it's an iso i have to use either a cd or usb for this to work. (This is pretty much what i did: http://www.iammacgyver.com/2011/02/easy-rdp-60-from-winpe-30-simple-boot.html) 
    What i want to do is to advertise the boot.wim to the client via SCCM so that it boots via PXE and then picks up the WinPE image and connect to the RD farm. I've imported the boot.wim file into SCCM under Boot Images and created an empty Task Sequence
    with the boot.wim as its Boot Image. I then advertised this Task Sequence to a collection which contains the old desktop clients. The machine PXE boots ok and loads up WinPE but rather than launch a remote desktop connection, it trundles through the normal
    WinPE stages and once it's finished 'Preparing Network Connections' it simply ends and the client reboots.
    Is what i'm trying actually possible?
    Can anyone tell me why the ISO works yet pushing the boot.wim out as a Boot Image doesn't? I know the boot.wim file (which is the same one present in the ISO) is ok since the client boots into WinPE fine when PXE booted so why doesn't the remote
    desktop session conenction launch? How is booting from the ISO different from booting from the PXE boot.wim file?
    Slightly long winded problem so many thanks in advance to anyone who can pass some info my way!

    It doesn't work because importing it into ConfigMgr injects binaries and the task sequence engine along with the process to launch the engine thus suppressing whatever you've got configured.
    Perhaps you could use a pre start command (pre-execution hook in 2007 parlance) to launch your RDP process though.
    Jason | http://blog.configmgrftw.com | @jasonsandys

Maybe you are looking for