All machines get Lync 2013, but not all machines get the full Office 2013. So the Lync application gets deployed to all machiens, but the full Office 2013 application only gets installed to certain machines that are certified for Office 2013. Otherwise, clients get Office 2010. It's fine to run Office 2010 and Lync 2013 on the same computer.
On Mon, May 11, 2015 at 9:47 PM, Corkill, Daniel < [email protected]> wrote: > Thanks for your feedback, much appreciated. I'll be using all your > suggestions. > > > > My understanding is that Office updates for all products are applicable > and installed regardless of which of those products you actually have. For > instance, we install Office 2013 without Lync, OneDrive for Business, > InfoPath or Publisher and yet if I create a software update group with the > latest updates for those four products and deploy it to all machines they'd > install all four updates. > > > > Not that it really concerns me, but I'm curious why you're deploying Lync > separately if all machines get it anyway. > > > > Daniel. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *ccollins9 > *Sent:* Tuesday, 12 May 2015 11:32 AM > *To:* mssms > *Subject:* Re: [mssms] How are you installing Lync 2013 via ConfigMgr? > > > > If Lync is "not available", then how is a Lync update hitting the > machine? It shouldn't be registered as installed and thus the update won't > install, right? > > > > We are installing Lync with an MSP made with the OCT and using the line: > > setup.exe /adminfile Lync2013_ConfigFile.MSP > > > > We push Lync 2013 in a separate SCCM application than Office 2013 but use > the same source files. All of our clients get Lync, but not everyone gets > full Office 2013. Remember, you deploy Applications, not Deployment Types. > In your case (as in mine), I would consider Lync 2013 as its own > Application from Office 2013 and treat it accordingly. It's a lot easier > to create a collection based on AD groups and deploy an app to that than it > is to adjust requirements on a deployment type to only install to certain > AD groups. I don't believe AD group filtering is available by default in > the requirements of an deployment type, so you would need to create a > custom global condition. Not worth it IMO. Just create two apps. > > > > Just my thoughts. > > > > On Mon, May 11, 2015 at 8:35 PM, Corkill, Daniel < > [email protected]> wrote: > > We currently deploy Office 2013 without Lync as a ConfigMgr application > in a task sequence. On a side note, despite Lync being configured as not > available via the OCT as soon as a Lync update touches a machine Lync > becomes available, so if anyone has any thoughts on that I'd love to hear > them. > > > > Anyway, there's a few things I want to clarify: > > > > · Do I create an msp via the OCT to enable the Lync feature or > just write a config.xml? > > · Should the install happen via setup.exe or using msiexec? > > · Should I create a separate application for Lync? > > o If so, should I use the Office 2013 data source or a separate source? > > · Rather than creating a separate application, is a separate > deployment type in the existing Office 2013 application more appropriate? > > > > The idea is that Lync will not be installed on all machines, rather users > will be added to a group which then deploys Lync to the user's primary > machine. > > > > Daniel. > > > > > > > > ********************************************************************* > > This email, including any attachment, is confidential to the intended > recipient. It may also be privileged and may be subject to copyright. If > you have received this email in error, please notify the sender immediately > and delete all copies of the email. Any confidentiality or privilege is not > waived. Neither the Council nor the sender warrant that this email does not > contain any viruses or other unsolicited items. > > > > This email is an informal Council communication. The Council only accepts > responsibility for information sent under official letterhead and duly signed > by, or on behalf of, the Chief Executive Officer. > > > > Privacy Collection Notice > > Logan City Council may collect your personal information, e.g. name, > residential address, phone number etc, in order to conduct its business > and/or meet its statutory obligations. The information will only be accessed > by employees and/or Councillors of Logan City Council for Council business > related activities only. If your personal information will be passed onto a > third party, Council will advise you of this disclosure, the purpose of the > disclosure and reason why. Your information will not be given to any other > person or agency unless you have given us permission or we are required by > law. > > > > > > > > > > > > > ********************************************************************* > This email, including any attachment, is confidential to the intended > recipient. It may also be privileged and may be subject to copyright. If > you have received this email in error, please notify the sender immediately > and delete all copies of the email. Any confidentiality or privilege is not > waived. Neither the Council nor the sender warrant that this email does not > contain any viruses or other unsolicited items. > > This email is an informal Council communication. The Council only accepts > responsibility for information sent under official letterhead and duly signed > by, or on behalf of, the Chief Executive Officer. > > Privacy Collection Notice > Logan City Council may collect your personal information, e.g. name, > residential address, phone number etc, in order to conduct its business > and/or meet its statutory obligations. The information will only be accessed > by employees and/or Councillors of Logan City Council for Council business > related activities only. If your personal information will be passed onto a > third party, Council will advise you of this disclosure, the purpose of the > disclosure and reason why. Your information will not be given to any other > person or agency unless you have given us permission or we are required by > law. > > > > >
