Lync 2010 hybrid deployment

I am wondering if it is possible to have on premise mediation server deployed for Enterprise voice and use Office 365 for rest of the features. Is this type of installation possible? If so, please point me to some relevant documentation.

Hi,
Splitting workload between office 365 Lync online and Lync 2010 on-prem isn't supported. You can enable federation between Lync on-premise and online by using different sip domains.
However , hybrid deployment is supported on Lync 2013. Following link may help you ;http://technet.microsoft.com/en-us/library/jj204805(v=ocs.15).aspx
Thanks
Saleesh
If answer is helpful, please hit the green arrow on the left, or mark as answer.

Similar Messages

LYNC 2010 hybrid deployment support

Hi,
We are currently using Microsoft LYNC 2010 on premise. Which is working fine.
We are thinking of moving to office 365 for exchange etc. As we a partners we receive licenses also for LYNC online. I was wondering we have some users in the UK Maylasia etc, we would like them to use the LYNC online features as we here in Australia are
on the LYNC on premise. We would eventually all be under the same domain.
ie users [email protected] would be the username for office 365 login,
If user A was in Au he would connect to the on premise link
If user is in Uk or not setup to au LYNC server he can login to the online LYNC??
spafco

Hi,
Lync server 2010 is not support hybrid deployment. Hybrid deployment will be supported by Lync server 2013.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Is ADFS mandatory for Lync 2013 Hybrid Deployment?

We alreadys have Lync 2013 Onpremise.
We now wish to do a Lync Hybrid setup with O365 Lync Online but wish to know the following.
While doing a Lync Hybrid setup, is deploying ADFS mandatory? We ask this because the new DirSync tool has the ability to Sync users password and thus we can avoid deploying ADFS/ADFs proxy/ADFS farm etc, thus reducing Onpremise
complextities. We dont care about SSO as far as users can Logon Onpremise or Online using their same AD password.
If we can do a Lync2013 hybrid setup without ADFS, then can we later have our Lync 2013 Hybrid setup to federate with our partners domain?

yes, read it too quick. it happens.
check these two resources:
http://immencloud.wordpress.com/2013/06/03/office-365-dirsync-with-password-sync/
http://blogs.technet.com/b/educloud/archive/2013/06/03/new-azure-active-directory-sync-tool-with-password-sync-is-now-available.aspx
in short, if you are happy without a true SSO experience and other limitations described in the blogs, then you should need no AD federation.

Lync 2013 Hybrid deployment with resource forest scenario on-premise

Hi there,
Im starting to deploy this scenario of Lync on-premise in resource forest with Lync Online:
I´am not finding any documentation about this specific scenario. I wish to know how the flow between forests will be to have users in lync online and users on premise.
Thank you very much in advance for your help.
Joaquin Gonzalez

Hi Joaquin,
You need to deploy Microsoft Forefront Identity Manager (FIM) 2010 to manage the life cycle of user accounts.
In a resource forest topology, one forest is dedicated to running server applications, such as Microsoft Exchange Server and Lync Server. The resource forest hosts the server applications and a synchronized representation of the active user object, but it
does not contain logon-enabled user accounts. The resource forest acts as a shared services environment for the other forests where user objects reside. The user forests have a forest-level trust relationship with the resource forest. When you deploy Lync
Server in this type of topology, you create one disabled user object in the resource forest for every user account in the user forests. If Microsoft Exchange is already deployed in the resource forest, the disabled user accounts might already exist. A directory
synchronization product, such as MIIS, Microsoft Forefront Identity Manager (FIM) 2010, or Microsoft Identity Lifecycle Manager (ILM) 2007 Feature Pack 1 (FP1), manages the life cycle of user accounts. When a new user account is created in one of the user
forests or a user account is deleted from a forest, the directory synchronization product synchronizes the corresponding user representation in the resource forest.
Click the links below for more information.
Supported Active Directory topologies in Lync Server 2013
http://technet.microsoft.com/en-us/library/gg398173.aspx
Windows Azure Active Directory Connector for FIM 2010 R2 Quick Start Guide
http://technet.microsoft.com/en-us/library/dn511002(v=ws.10).aspx
Hope it can be helpful.
Best regards,
Eric

Migration From Exchange 2010 Hybrid to Exchange 2013 Hybrid Deployment

hi,
I have existing Exchange Server 2010 Hybrid Deployment. Planning to migrate to Exchange 2013. However, while schema update, i am facing some errors/warnings as can be seen in attached screenshot.
I have already checked and current functional level in DC is Windows Server 2003. What could be the best steps to troubleshoot the problems and proceed further with Exchange 2013 installation?
Thanks

Hi Muhammad
Can you please give few more information about your environment so that people around here can help you out
I have existing Exchange Server 2010 Hybrid Deployment - Do you have Exchange 2010 and Office 365 in a
hybrid setup now ?
Are you trying to upgrade your on premise Exchange 2010 servers to Exchange 2013 ?
Or Are you trying to migrate your on premise Exchange 2010 to a different forest to Exchange 2013 ?
You can try the below suggestions-
I would better suggest you to follow Microsoft Exchange Server Deployment Assistant - http://technet.microsoft.com/en-us/office/dn756393.aspx
Also i would recommend you to check the prerequisites for hybrid deployment with office 365
http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
Cheers !!!
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Project Pro 2013 client Deployment with Lync 2010 and Team Explorer Excel Issues Following

Current machines are Office 2010 SP1 or SP2 32-bit
Just deployed Project 2013 Pro and Std to the existing machines that had Project 2010 Pro or Std. We selected the full install since people use integration into different tools.
Results:
lync 2010 64-bit when attending a meeting prompted user to start using and download the Lync Web Component, which breaks features such as muting, etc.
A repair sent to the workstations for Lync 2010 64-bit fixed that.
Team Explorer 2012 Export to excel from queries gives error Unable to cast COM object of type 'Microsoft.Office.Interop.Excel.ApplicationClass' to interface type 'Microsoft.Office.Interop.Excel._Application'. This operation failed because
the QueryInterface call on the COM component for the interface with IID '{000208D5-0000-0000-C000-000000000046}' failed due to the following error: The interface is unknown. (Exception from HRESULT: 0x800706B5).
Repair of Team Explorer, Office, Test Manager 2012, etc did not assist. if we go into excel and connect to TFS, we can then retrieve the query data. Just not from TFS exporting to excel. Had to unload Project 2013, repair Office 2010
and rebooted with project off the machine and now it works. It seems maybe the setup with the shared features and Office tools are breaking something? We need the ability for VBA and .net functionality, but what could be breaking this?

Hi,
Your environment will support 32 bit of Project professional 2013 (x86) as you have Windows and Office of (X86).
You try to modify registry then you wont face issue.
The issue when you hit a "1653" is that Windows
Installer "DisableRollback" is set. Office 2013 requires that "rollback" be enabled. If you are getting a "1653"
error in your logs as Ken did then the solution is to delete the "DisableRollback" (or set to '0') at the following registry keys:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
these are the issues I've seen:
Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.
Environment variable "ComSpec" had been modified (semicolon added). Fix was to remove the added semicolon (there should be no semicolon).
The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603
If you want to enable verbose logging via the following key, rerun your failed install, and collect all the setup and MSI* logs that will give more information.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"logging"= "voicewarmup"
kirtesh

Lync Hybrid Deployment and Dial-in Conferencing

I know this question could fall under community.office365.com forum, but didn't get any response there...
I'm looking at a possible Lync Hybrid deployment. All users will be hosted in the cloud, but we're looking at hybrid on-prem Lync deployment so we can connect a trunk from our IP PBX and use the on-prem server for Lync dial-in conferencing. We have a separate
phone system and users will use those phones to simply dial in to the Lync dial-in conference bridge for audio conferencing meetings.
Is this even possible with Hybrid deployment?
Thanks in advance!
me

Lync online doesn't support Hybrid Voice, please check out: http://pei.com/2014/03/lync-hybrid-deployments-with-enterprise-voice/
Brian Riggs has a great post about Lync Online supporting voice posted today: http://www.nojitter.com/post/240167129/lync-online-enterprise-voice-out-pstn-calling-in
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Lync issues in hybrid deployment

Hi,
We are in the process of configuring hybrid deployment of exchange 2013. recently we have added send and receive connectors
for setting up mail flow (still in progress) in O365 ,after that few of the O365 users are not able to sign into Lync .
what could be the issue ? Did someone face this type of issue before ?
Thanks

Hi,
Since your question is related to Lync online, here is the forum for you:
http://community.office365.com/en-us/forums/166.aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

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

Is there any documentation to deploy federation between Cisco IM and presence and Lync 2010 sister companies?

Hello All,
Company A – Using Cisco IM and Presence
Company B – Using Microsoft Lync 2010
We would like to establish federation between Company A and Company B and also looking for the documentation which has the step by step instruction.
Please let us know overall steps or provide us the documentation. Thank you in advance.
Thanks

For Federation between Lync and Cisco IM, you can check below link and this
document
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/interdomain_federation/9_0_1/CUP0_BK_IAAE17D8_00_integration-guide-interdomain-federation-90/CUP0_BK_IAAE17D8_00_integration-guide-interdomain-federation-90_chapter_01.html
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Lync 2013 standard deployment: Exchange 2010 Sharepoint 2010 and outlook 2007 collaboration

HI
I have Exchange 2010 and sharepoint 2010 with all our user using outlook 2007. what options do I have for collaborations between these systems if I was to install Lync 2013. I have seen posts that mention that you cannot use outlook 2007 and lync 2013 and
that you would be better off installing the lync 2010 client?
1. would we be covered from a licensing point of view if we had bought lync 2013 cals but install the lync 2010 software on desktops?
2. what Cals do we require for presence to be available in SharePoint we currently have standard sharepoint cals?
3. what new features will we loose if we install 2010 lync software.
4. if our mobile users use the 2013 lync software will these be able to communicate with the 2010 users?
thanks
J

Hi,
If you use Lync 2013 client with Outlook, multiple functions will not be achieved, such as: customize Outlook meeting invitations (add logo, help URL, disclaimer, footer text), in Outlook, configure meeting option to mute attendee audio and video by default,
presence status in the Microsoft Outlook To and Cc fields, and so on. As Lync 2013 is the part of Office 2013, the best choice is using Outlook 2013.
More details:
https://technet.microsoft.com/en-us/library/gg412817.aspx
For the CAL requirement, you can refer to following link:
Lync Licensing Guide
You can refer to the link below of “What’s new for clients in Lync Server 2013” to understand the new features for Lync 2013:
https://technet.microsoft.com/en-us/library/jj204933.aspx
If you use Lync 2013 mobile clients, you can communicate with 2010 users with no possible.
Best Regards,
Eason Huang
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]
Eason Huang
TechNet Community Support

New Lync 2010 Deployment With OWA 2010 Integration Not Working

I just installed Lync 2010 and it works fine with the Lync 2010 client.
Our Exchange Server is Exchange 2010 SP3 and I can't get the OWA integration to work.
I found various blogs with instructions, but they are all so old that I'm not sure all the prerequisite software hotfixes downloads they are pointing to install are still valid for Exchange 2010 SP3 and the Lync 2010 with all the latest updates.
For a little while I got it partially working in OWA where some of the Lync integration was showing, but it was grayed out and the contacts lists would never load. Now that I have tried several solutions, it no longer even partially works.
I think I need to clear all the integration settings from both Exchange and Lync, so I can start over with valid instructions.
What are the current instructions and current download files needed with the most up to date versions of Lync 2010 and Exchange 2010?
I also need to make sure that the syntax of the all the server and certificate names the various commands and wizards ask for are exactly correct. Some of it is confusing on whether it is the actual DNS name, Exchange certificate SAN name or something
else.

TL_ERROR(TF_CONNECTION) [0]0878.0AC8::09/21/2014-19:27:55.515.000002d3 (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(160))$$begin_record
LogType: connection
Severity: error
Text: The peer is not a configured server on this network interface
Peer-IP: 192.168.1.61:23952
Transport: TLS
Result-Code: 0xc3e93d6a SIPPROXY_E_CONNECTION_UNKNOWN_SERVER
Data: fqdn="domain.local"
$$end_record
TL_INFO(TF_PROTOCOL) [0]0878.0AC8::09/21/2014-19:28:36.289.00004a73 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 592054086
Instance-Id: 0000005B
Direction: outgoing;source="local"
Peer: 192.168.1.101:50734
Message-Type: response
Start-Line: SIP/2.0 401 Unauthorized
From: <sip:[email protected]>;tag=2b027e1110;epid=a25bafc9cb
To: <sip:[email protected]>;tag=54ADDA87F5DF7E9514FA2FACDF01EBC1
CSeq: 1 REGISTER
Call-ID: ccb79e71bef84e2084502ffbd63115ad
Date: Sun, 21 Sep 2014 19:28:36 GMT
WWW-Authenticate: NTLM realm="SIP Communications Service", targetname="Lync2010.domain.local", version=4
WWW-Authenticate: Kerberos realm="SIP Communications Service", targetname="sip/Lync2010.domain.local", version=4
WWW-Authenticate: TLS-DSK realm="SIP Communications Service", targetname="Lync2010.domain.local", version=4, sts-uri="https://Lync2010.domain.local:443/CertProv/CertProvisioningService.svc"
Via: SIP/2.0/TLS 192.168.1.101:50734;ms-received-port=50734;ms-received-cid=B00
Server: RTC/4.0
Content-Length: 0
Message-Body: –
$$end_record
TL_INFO(TF_PROTOCOL) [0]0878.0AC8::09/21/2014-19:28:36.304.000051a6 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 592054086
Instance-Id: 0000005D
Direction: outgoing;source="local"
Peer: 192.168.1.101:50734
Message-Type: response
Start-Line: SIP/2.0 401 Unauthorized
From: <sip:[email protected]>;tag=2b027e1110;epid=a25bafc9cb
To: <sip:[email protected]>;tag=54ADDA87F5DF7E9514FA2FACDF01EBC1
CSeq: 2 REGISTER
Call-ID: ccb79e71bef84e2084502ffbd63115ad
Date: Sun, 21 Sep 2014 19:28:36 GMT
WWW-Authenticate: TLS-DSK opaque="2068882F", gssapi-data="FgMBCWUCAABNAwFUHybk5YL8BIG6/hEQ8Ho3vB2JmvRbl5XJKZwxAM+FWCDVMQAAt9DcOnkWE+JUcGJjlZfh78cGOcAxLv/yU9+cmQAvAAAF/wEAAQALAAXqAAXnAAXkMIIF4DCCBMigAwIBAgIKYUQCVgAAAAAABjANBgkqhkiG9w0BAQsFADBHMRUwEwYKCZImiZPyLGQBGRYFbG9jYWwxFjAUBgoJkiaJk
TL_INFO(TF_PROTOCOL) [0]0878.0AC8::09/21/2014-19:28:36.367.0000785c (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 2754735576
Instance-Id: 00000063
Direction: outgoing;source="local"
Peer: 192.168.1.101:50734
Message-Type: response
Start-Line: SIP/2.0 403 Location profile only available when UC enabled.
From: <sip:[email protected]>;tag=60cf26eaec;epid=a25bafc9cb
To: <sip:[email protected];gruu;opaque=app:locationprofile:get;default>;tag=54ADDA87F5DF7E9514FA2FACDF01EBC1
CSeq: 1 SERVICE
Call-ID: b01cbdd5693c4bbbb4c013d87a6a51eb
Authentication-Info: TLS-DSK qop="auth", opaque="2068882F", srand="2A6F42FF", snum="2", rspauth="aec4e7a2404bbb46a0d55c9b42d3631cc36df614", targetname="Lync2010.domain.local", realm="SIP Communications
Service", version=4
Via: SIP/2.0/TLS 192.168.1.101:50734;ms-received-port=50734;ms-received-cid=B00
ms-diagnostics: 2;reason="See response code and reason phrase";AppUri="http://www.microsoft.com/LCS/TranslationService";source="Lync2010.domain.local"
Server: RTC/4.0
Content-Length: 0
Message-Body: –
$$end_record

Sharepoint online presence with Lync 2010 On Prem

We have recently moved to Office 365 in an exchange hybrid deployment. We have Lync 2010 on-prem, and are not using
lync online. We are experiencing issues with IM presence in sharepoint online and one drive, but have presence indicator within outlook online. We do not see the options to sign into im at all, and the presence indicator is grey. I verified
that the SIP:username@domainname was added to the PROXY attribute in AD.
Any idea where we should start?

Hi,
Did you integration Lync Server with SharePoint successfully?
Please check if ActiveX control work normally. To display the presence indicator and its associated contact card (in Office 2010), SharePoint uses the Microsoft ActiveX control
name.dll. The ActiveX control makes calls directly to the Microsoft Lync 2010 API, and then Lync makes MAPI or Exchange calls to supply the requested information.
You can refer to the following link:
http://blogs.msdn.com/b/modonovan/archive/2005/05/11/416376.aspx
Please also update Lync Server and SharePoint Server to the latest version and then test again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Need assistance creating applications with superseedence to uninstall Office 2010, Lync 2010 and then install Office 365 click to run 2013

We are getting ready in a few months to uninstall our locally installed Office 2010 and head to the cloud with Office 365 2013. I have created applications to uninstall Office 2010 and Lync 2010 and then added them to the supersedence tab for Office 365
office 2013 click to run with appv5.
When deploying the office 365 2013 application it does not uninstall office 2010 or lync 2010 with the supersedence. I am able to manually uninstall Office 2010 and Lync 2010 with the command lines I am using in the applications.
The application uninstall for Office 2010 is:
The application uninstall is an exe so I created an application, created a deployment type with the location of our Office 2010 admin point, installation program and uninstall program are set with the same line as I have tried to deploy it separately and
also as a supersedence in the Office 365 application setup.exe /uninstall ProPlus /config "\\sccmserver\share\Office2010\ProPlus.ww\silentuninstallconfig.xml. The silentuninstallconfig.xml was created from the original config.xml file and edited
to these settings:<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="NO" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="Reboot" Value="Never" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
<OptionState Id="ProductFiles" State="Local" Children="force" />
</Configuration>
The detection method is the folder path to see that office 14 exists. When I deploy this the machines finish with success showing this exists, but does not uninstall Office 2010.
running the command line manually mapped to this location on a machine uninstalls office 2010 without issue.
Lync 2010 uninstall:
Lync is an exe so I am using the LyncSetup.exe /silent /uninstall. The application is in the supersedence tab for Office 365 2013. This never installs. If I create a softare distribution and deploy it on its own it uninstalls without issue.
We are going to use Lync 2013 with our office 365 2013 installation so we need to uninstall this. The detection method for lync is file system folder and the Microsoft lync folder for detection.
MS Office 15 (Office 365) was created with the click to run tool. I can install this with the application I created using the appv5 package created with the click to run tool. The issue is we need Office 2010 and Lync 2010 uninstalled first.
Having both versions of Office installed in test has caused issues where Office 15 365 will not list in add and remove programs and cannot be uninstalled even with the fix it article to remove office 2013.
I have looked at many articles and so far it is not working for us. Any help appreciated to get us to the cloud.
Thanks,
Brit

The applications I have for uninstall of office 2010 and Lync 2010 for some reason do not uninstall. Manually testing the command lines they do. The detection method seems to be hanging things up. On the lync uninstall detection method I have
the setting type of file system, type folder, path c:\program files\ folder name Microsoft Lync.
I highly recommend using something other than a file/folder "exists" detection method. Installers are constantly leaving things behind due to environmental inconsistencies. It may leave files/folders behind with a schedule to delete files on next reboot.
These things are unpredictable and very hard to use. I just use the "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" Registry location. There you can actually key off the "Product Version" DWORD as well which gives you an even more accurate method
to determine if the application you are trying to deploy (or expect to exist) is truly there. This, of course, being if you are not using an MSI. If you have MSI technology ALWAYS use the product code unless the person writing the MSI chooses to use the same
product code for every version release of their product. In which case, Use the registry method.
As far as getting the supersedence and everything working. You need to start from the basics. Create Applications for all of the apps you want to remove. Make sure they install and uninstall properly (seems like overkill but it isn't that hard). Once you
have working install/uninstall applications then you can easily apply supersedence to your new applications with a setting of Uninstall on the superseded apps you should have no problem getting rid of them. I have done this for numerous things.
For example, I did this with Cisco Jabber to replace older versions of jabber, older versions of cisco unified personal communicator and lync and OSC. All of these replaced versions had to have an Application but once it was in it took two seconds to apply
all the supersedence rules and now I know when I push that software out no matter version is running on any machine it will pull all the old apps off and put the new one on.
Dustin Estes - MCP | www.dustinestes.com

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

Lync 2010 hybrid deployment

Similar Messages

Maybe you are looking for