Hey SCCMers
I could use some of your valued insight!
We are getting ready to move our organization's mailboxes to Office 365 which requires that we upgrade our Outlook 2010 users to Outlook 2013 (technically Exchange Online mailboxes can be accessed from Outlook 2010 clients with specific updates installed, but we are using this as an opportunity to standardize everyone to Office 2013). All of our Office 2010 users have a Lync 2013 standalone client installed which serves as our UC platform. Our Office 2013 ProPlus OCT .msp specifies that previous version of Office be removed. This doesn't affect the existing Lync 2013 standalone client, presumably it is recognized as a current version; however, after the Office 2013 installation completes Lync crashes upon launching. Repairing the Office 2013 installation does not resolve the crash.
Next I tried to use supersedence to replace Lync 2013 standalone clients with Office 2013 ProPlus (with OCT also calling for the removal of Office 2010). Lync 2013 standalone is removed, Office 2010 is removed (mostly, SharePoint Workspace 2010 and Office 2010 Tools are left behind... grrr) and Office 2013 ProPlus is installed successfully, except... Lync 2013 contained in the ProPlus suite isn't reinstalled as expected. Supersedence of Lync 2013 standalone seems to also preclude the subsequent installation of Lync 2013 as part of ProPlus in the same SCCM application.
The goal is to make this available as a single Software Center item for users to install at their convenience. Am I left with the absurd prospect at this point of having to create a separate Office 2013 application customized to only install Lync with a dependency to the install "full" Office 2013 ProPlus deployment which itself is superseding Lync 2013 standalone?
Also, despite the uninstall config file specifying the display level is "none", the Lync uninstall throws a prompt warning that proceeding with the uninstall might require other Office components to need repair.
