Lync 2010 client and Office 2013

I have Office 2013 installed minus Lync 2013 and have Lync 2010 installed in its place, we have a Lync 2010 infrastructure and are planning on upgrading our customers’s workstations to office 2013 and maintaining the Lync 2010
clients.
Is it expected behavior in this scenario to get prompted with the “Join the meeting using your web browser”, “Download and install Lync Attendee” & “Use Communicator” page when attpempting to join a meeting?
Thanks….  

Thanks for the reply.
The reason that we though to stay with the Lync 2010 client is that we were told that the Lync 2013 client only communicates to the Lync 2010 back-end via the Lync Edge servers. In looking at the Lync 2013 client configuration
information I see that Inside User Status: True which looks like it might not be communicating via the Edge servers.
Is this a valid reason not to push forward with Lync 2013 client while still having Lync 2010 back-end?
Thanks…

Similar Messages

  • Getting the Lync 2010 client to use 2013 Persistent Chat

    We are migrating to Lync 2013 from 2010 and just testing the 2013 environment right now with a few users. Only thing left I need to configure is getting the Lync 2010 client to connect to the 2013 Persistent Chat server. Most of our users are Windows XP
    so they can only use the 2010 client.
    We did not have Group Chat prior to this so Persistent Chat is new to everyone. I created the Persistent Chat Endpoint in Lync 2013 per the article
    http://technet.microsoft.com/en-us/library/jj204901.aspx but now what.
    The article tells you how to create the endpoint but that's it. What else is needed. Does a Lync user in 2013 need to exist that matches the SIP addresses in the command? The icon for Persistent Chat is not showing up in the Lync 2010 client so something
    is missing.

    You still need this endpoint, as long you will Need Lync 2010 Chat clients. Without this endpoint, you will be able to login but could not find any chat rooms.
    For login you use your normal Lync credential. Lync Chat server has not deployed before.
    Have you  test to use the Pchat with this user on a Lync 2013 client?
    Here is a link with additional help
    http://lyncinsider.com/tag/group-chat/
    regards Holger Technical Specialist UC

  • Lync 2010 client connecting to 2013 persistent chat server

    Since we never had Group Chat in our 2010 environment, I have no idea how it works and now that we have 2013 Persistent Chat, I am struggling with getting the Lync 2010 connected. The 2013 client works just fine as it is integrated into the client. I found
    out Lync 2010 needs a separate Chat client to run along side the IM client.
    I installed this client but from there I have no idea how to connect it to the 2013 Chat server. I created the endpoint on the Lync 2013 server according to the article
    http://technet.microsoft.com/en-us/library/jj204901.aspx but something else needs to be done. I just don't know what. Not even sure where to start looking. Many of our Lync clients have
    to use 2010 because the OS is XP so I need to find out how to get these users to work with Persistent Chat.
    I am not sure what the point is of creating the End point according to the article. I am sure its necessary but not sure how it fits into the clients using it to connect. What does the article mean when it says "Next, configure Persistent Chat clients
    to use that SIP address as their contact object". Do you need Group Chat functioning in 2010 for this to even work?
    The problem is we never had Group Chat with 2010 so I am sure there are some settings missing like DNS records etc...

    If you have users running legacy clients (such as Microsoft Lync 2010 these users might find the default Persistent Chat URIs difficult to work with and difficult to use when pointing their legacy client towards the pool. Because of this,
    administrators need to use the New-CsPersistentChatEndpoint cmdlet to create an additional contact object for the pool, a contact object that provides a friendlier, easier-to-use URI.
    Lisa Zheng
    TechNet Community Support

  • Lync 2010 client and SRV record

    When Lync 2010 was originally set up in our environment, we included our login domain which is a .local as a SIP domain but everyone uses our additional SIP domain which is a .org.
    In our internal DNS, we have SRV records under both domains. Question is if a Lync 2010 client is doing autodiscover and their SIP domain is the .org, will the client look at the SRV record in the .local domain? I don't think this SRV record was ever used
    even though its the users login domain, its not their SIP domain.

    You're right, the SRV records that belongs to your .local domain are not used by the lync client for a user that hs a .org sip domain sign-in address, so as you are saying if all the users are configured with a .org sip domain that means these SRV records
    were never used, and you can safely remove them.
    Regards,
    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

  • Lync 2010 Compatibility with Office 2013

    Hi Team,
    We are planning to upgrade to Microsoft Office 2013 SP1. But we are planning to retain Lync 2010 in place. Would it cause any compatibility issues with the outlook add-in? Conversation history? on schedule Lync Meeting?
    Thanks,
    V
    Vas

    Those should work, are you upgrading the client to 2013 as well and keeping the 2010 back end server? If so, this is supported and very compatible with a caveat found in this article: http://technet.microsoft.com/en-us/library/jj204672.aspx If you're keeping
    the 2010 Lync client (you don't have to), then you should be fine as well. Nothing will reassure you like a quick test on one of your own machines though. :)
    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".
    SWC Unified Communications

  • App-V CRM 2013 Outlook Client and Office 2013 Click to Run

    Hi,
    I'm trying to get going with enbing the CRM 2013 for Outlook client with the VL version of Office Pro Plus 2013.  I have successfully published and use Office App-V package in a test environment.  App-V version 5.0 SP2 is installed on the client
    PC (Windows 7 64bit).  SCCM 2012 R2 is used to publish APP-V applications to user groups.
    I have sequenced the CRM 2013 Outlook client (offline mode disabled) with UR2 and published it using SCCM as a "Add-on or Plug-in.  I've also created a connection group so that the App-V version of Office 2013 is able to connect to the sequenced
    CRM client.  The client installs successfully, but the CRM tab doesn't appear in the Outlook Ribbon, and the Configuration Wizard crashes each time it is launched.  The App-V event log is blank (which I'm taking to be a good sign).  All CRM
    client prerequisites have been preinstalled on the target PC.
    I'm thinking that the CRM client can't see the Outlook application and therefore crashes and doesn't integrate with the Outlook application.  Problem Signature 09 (from the crash explanation) states "System.NullReference Exception".
    I can't seem to find much out there for sequencing the 2013 version of the client.  Has any else managed this yet or have any ideas where I'm going wrong?
    Thanks,
    Tim

    Hello,
    I would use Process Monitor to understand what happens and to see why Outlook isn't seeing the plugin, and why the wizard is crashing
    Nicke Källén | The Knack| Twitter:
    @Znackattack

  • Sql Server Native Client and Office 2013 Professional Plus template

    Does the Office 2013 Professional Plus template include sql server native client 10.0? 
    This is in response to an earlier question: https://social.msdn.microsoft.com/Forums/azure/en-US/70e91af7-586a-41ca-994e-b8378928847e/connecting-access-2013-using-preview-image-to-azure-sql-database?forum=AzureRemoteApp
    Using the Office 365 trial subscription image - the sql server native client 10.0 is not included in this image. 
    The reason for the question is that I'd like to link an MS Access database front end to SQL Azure and it is quite helpful to have the sql server native client 10.0. 
    Thanks, 
    Dave 

    Hi Dave,
    Unfortunately the Office 365 ProPlus (Subscription required) (Uploaded on 11/26/2014) image template
    does not include the SQL Server Native Client.
    As of now you would need to
    create a custom image template with the required software and upload it.
    I just created one a couple of days ago for a customer that had what you are requesting plus a few extras.  In their case they have a custom application that they needed to connect to SQL Server on an IaaS VM so I built the custom
    image to accommodate that plus other requirements.
    -TP

  • Lync 2010 client issues with Exchange 2007/13 coexisting

    Hi all,
    Does anyone know of any update regarding the following link ??
    http://silbers.net/blog/2013/12/19/lync-ews-broken-during-exchange-20132007-transition/
    many thanks

    Hi
    I have Lync 2010 clients with Exchange 2013 Server, i came from 2007 as well.

  • Uninstall Lync 2010 client, Install Lync 2013 using Group Policy/VB/MS Customisation Tool

    Hi, I am using Group Policy/vb/Lync customization tools to deploy 2013 and remove 2010. The machines have Office 2010. The vb script is as below:
    Dim objShell 'As Object
    Dim objFSO 'As FileSystemObject
    '-- SET OBJECTS
    Set objFSO = CreateObject("Scripting.FileSystemObject")
    Set objShell = CreateObject("WScript.Shell")
    strComputerName = objShell.ExpandEnvironmentStrings("%COMPUTERNAME%")
    Dim WshNetwork : Set WshNetwork = WScript.CreateObject("WScript.Network")
    objShell.Run """\\xxxxxxxxx - Do not Remove\Lync Install 2013 2010\Lync 2013 Outlook 2010\setup.exe"""
    I have amended the OCT with relevant settings, Lync 2013 installs but Lync 2010 does not uninstall. Here is how i have it set:
    In the Office Customization Tool - Set-up - Add Installation and Run Programs,
    In target - pointing to the Lync2010 exe file (on above share)
    In Arguments - /silent /uninstall
    Is this correct?
    Also, i would have thought that, Remove Previous Installations, it would have an option to remove Lync2010?
    Anyway..pulling my hair out here!
    Hope you can help.

    Hi,
    Based on your description, we can refer to the following threads for help.
    Slient Unninstall of Lync 2010 on client machines script required
    http://social.technet.microsoft.com/Forums/lync/en-US/69e32128-4581-4be5-9a44-b5d133e1f480/slient-unninstall-of-lync-2010-on-client-machines-script-required
    Scripting a Lync 2010 client Uninstall
    http://social.technet.microsoft.com/Forums/en-US/a65bd0d0-daa1-4616-8725-63f349fdde86/scripting-a-lync-2010-client-uninstall?forum=lyncconferencing
    For this issue is more related to Lync, in order to get better help, we can ask the question in the following TechNet dedicated Lync forum.
    Lync 2010 and OCS - Lync Clients and Devices
    http://social.technet.microsoft.com/Forums/lync/en-US/home?forum=ocsclients&filter=alltypes&sort=lastpostdesc
    In addition, for it also involves scripts, we can also ask for help in the following scripting forum.
    The Official Scripting Guys Forum
    https://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?forum=ITCG&filter=alltypes&sort=lastpostdesc
    Hope it helps.
    Best regards,
    Frank Shen

  • Lync 2013 Client pops up automatically while typing in Word , Excel in Windows 7 after upgrade from Lync 2010 client

    Hello All,
    Facing very much weird issue for only 4 users in my organization. This 4 users are migrated to Lync 2013 pool from Lync 2010 pool with Lync 2010 client migrated to Lync 2013 client.
    Now whenever this users are typing in (apps like word, excel) automatically pops up Lync 2013 client which is annoying.
    All my users are Windows 7 with latest updates & updates Lync 2013 with latest updates installed.
    Any help really appreciated.
    Regards
    Anand S
    Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

    Hi 
    The solution is to do a ‘repair’ install of Office 2013.  This will reregister the needed components and the popups will stop. 
    A repair install can be done from ‘Programs and Features’, highlight Office 2013 and click ‘Change’.  When the install wizard appears, choose the ‘repair’ option.
    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)

  • Uninstall Legacy Lync 2010 enterprise and install Lync 2013

    I have a customer who has Lync 2010 enterprise and decided to install Lync 2013 but don't want migration and instead want to uninstall Lync 2010 . I would like to know in this case how to clean the active directory schema from Lync 2010 ? 
    and If there's anything else to consider before uninstalling Lync 2010 ? I will have to disable/remove all currently Lync enabled users but is there anything else?
    I found this article, but would like to know what's the steps in sequence of removing Lync in this case? 
     https://social.technet.microsoft.com/wiki/contents/articles/9849.how-to-remove-lync-server-2010-from-active-directory.aspx
    for example, do I have to first 
    1- Disable LYnc users.
    2- Uninstall Lync server Application from Control panel
    3- Remove Lync from Active Directory? 
    Would appreciate your help. thanks
    thanks
    Mohammed JH

    Hi 
    Check this to Uninstall Lync 2010
    http://terenceluk.blogspot.nl/2011/01/step-by-step-instructions-for.html
    Check this to remove AD References 
    http://blog.ucmadeeasy.com/2010/11/09/lync-server-2010-active-directory-references-and-how-to-remove-them/
    http://digitalbamboo.wordpress.com/2014/01/28/how-to-clean-your-server-of-old-active-directory-lync-ad-references-in-the-rtc-service-when-removing-the-last-2010-pool-fails-to-publish-in-the-lync/
    Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

  • 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.

  • Managing "Access Levels" on a domain level from Lync 2010 client

    Hello,
    Our company moved from Office Communicator 2007 R2 clients to Lync 2010 clients.
    Previously in Office Communicator 2007 R2 client, it was possible to set default Access Levels for complete domains (instead of individual users only), using the Access Level Management view.
    In the Lync 2010 this options seems to be missing. The management options per user are still there (by right-clicking a user), but the access to manage it for a domain is no longer visible.
    Is there any way to manage Access Levels for domains, in a similar way we had in Communicator 2007? It appears that Lync 2010 stilluses the Access Levels set previously for domains, but users do no longer have any possibility to make further updates,
    and are stuck (from their perspective at least) with the settings made in 2007 before.
    Thanks.

    Lync 2010 doesn’t have the feature natively.
    With Lync Server 2010, by default, the contacts from federated domains are added as External Contacts.
    Lisa Zheng
    TechNet Community Support

  • Start Lync 2010 client on remote machine

    I have a couple of users who like to logout of their Lync 2010 client. They apparently think that they are being watched through this program.  This is a bit of a hassle since we use this program to see if users are sitting at their desk.
    I am trying to write a .bat file to automatically kill the communicator process and then restart the program on the remote machine.  I am having nothing but success with killing the communicator process using pskill.  When attempting to start the
    client using psexec, however, it will not work.  
    It will start a new communicator.exe process on the remote computer just fine.  It doesn't seem to actually start the program though.  There is no icon in the taskbar showing the program is running and communication with the user does not work
    as it still shows them offline.
    On the local machine (the one I am running from), I just use a bat file that calls another .bat file on the remote machine.  The .bat file on the remote machine kills all communicator.exe processes using pskill -t.  It then attempts to start a
    new communicator session using "start communicator /fromrunkey"  This will start a new communicator.exe process on the remote computer without any problems. That's all it will do though.
    Anybody have any suggestions on what I can do to make it actually launch the client on the remote computer?  I have exhausted all options I can come up with.  I would like to get this working so the users in question finally figure out that if
    they logout of Lync it is going to just start back up on them.  Hopefully after time they will catch on and stop logging out of the program.

    Have we tried giving the complete location of the communicator.exe
    "start c:/.../communicator.exe /fromrunkey
    Using the same script are you able to open Notepad.exe on the remote machine just for testing 
    for more info look at http://blogs.technet.com/b/rischwen/archive/2013/06/20/lync-2013-client-auto-start-registry-key.aspx
    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" Regards Edwin Anthony Joseph

  • Problem activating Lync 2010 client

    I am running Windows 7 (64) and have installed MS Office Pro Plus (HUP).  Then my company switched from Communicator to Lync and I installed the Lync 2010 demo version.  When the trial use expired, I obtained a HUP activation key for Lync 2010
    client, but am unable to enter it.  Whenever Lync is activated, I get the error:
    Microsoft Lync 2010 cannot start. The product license may be expired because you are using a pre-release or evaluation copy of the program, or the product key information may have been modified in your Windows registry.  Please uninstall and then reinstall
    Lync.
    I have uninstalled and reinstalled Lync 2010 client several times as well as uninstalling and reinstalling both  MS Office Pro Plus and Lync together.  Also I have received an email from the HUP support (ESD support) that only the 32 bit version is
    supported by HUP and it should work on both 32 and 64 bit versions (X17-30021),  but of course when I try to run the .exe, I get the error message:
    This installer is not supported on your computer. Please use the 64-bit installer to complete the Microsoft Lync 2010 installation. 
    A final note the product key that I was sent for the Lync 2010 client activation by ESD support is the same as my Office Pro Plus 2010 activation key, and the office products are all activated correctly, but the Lync 2010 client does not recognize the activation.

    Hi,
    Looks like the following article has the same issue:
    http://social.technet.microsoft.com/Forums/en-US/ocsclients/thread/fabb5651-a04e-45fa-870e-01d2807e1cea
    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.

Maybe you are looking for

  • What is domain and dataelement.....diff b/w domain and data element

    dear all what is domain? what is data element? In one domain how many data elements are possible to used? with out data element how can u create a table? explain briefly.

  • Aaaaggghhh!!!! Stop cropping my DVD!!! Urgent help please!*

    Hi, would really really appreciate some help with this one. So, i shot my footage on an HD camera and have worked and edited the film in Final Cut Pro X (in 1280 x 720). It looks great, really happy with it! Now i need to put this onto DVD (just a no

  • How to use external libraries jar files in the composite application?

    Hi, I have some external jars files (which consists of java classes) that I would like to use in my composite application.  I have created a DC with type as external library for the jars.  However, I don't know how to specify the DC to be used in my

  • Dynamic Class

    With Dynamic Classes you can add properties at run time. But the same can be done with Non Dynamic classes using their prototype property. For e.g. I've a Person Class for which the code is as follows: class Person { private var id:Number; function P

  • FTP Adapter staging_dir

    Anyone know exactly how the staging directory works? I've added a directory as per directions in user docs but nothing ever seems to appear in the directory I specify. file.sender.staging_dir=c:/dfmsftp/stage