Lync 2010 Stranded Edition Limitations

Can Lync 2010 Stranded Edition provide same features as Enterprise Edition other than failover options?
Kris

Hi,
With Enterprise Edition you can choose to collocate or define a stand-alone Mediation Server. The Monitoring Server and Archiving Server can use a stand-alone server running SQL Server. Or, they can have instances of SQL Server running on the database server
for the Front End Servers and pools.
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

Similar Messages

  • Lync 2010 Standard Edition Front-End and Edge Cerificate Renewal issue

    Hi Experts,
    I have a client with Single Standard Edition FE server and 1 Edge server and both are using PUBLIC certificates. It also has a reverse-proxy server (F5 HLB) with wildcard certificate installed. The FE and Edge certificates are about to expire and the client
    now wants the ff.
    1. Internal Certificate from Internal CA server for FE
    2. External Certificate from Public CA for Edge
    What I did was,
    A. For Internal Cert - I generated a CSR from MMC cert manager using custom request from the FE server and have it signed by the Internal CA. Reason I did that was, everytime I requested the CSR from Lync Certificate Wizard, it is getting the certificate
    template not supported by the Internal CA.
    B. For External Cert - I requested the Edge external CSR thru Lync Certicate Wizard and submitted to the client for public CA renewal.
    When I installed both certificates, internal lync works fine but anything external (i.e. external lync access, mobile, federation) do not work anymore.
    So I decided to roll back the certificates and everything went back to normal?
    Question is, what steps or process did i miss or gone wrong? Hope for your response. Thank you in advance.

    Hi DaxZilla,
    You also need to request a certificate to internal interface of Edge Server from internal enterprise certificate authority.
    The certificate for the external edge interface should contain SANs as below:
    SAN=Access Edge service FQDN
    SAN=Web conference service FQDN
    SAN=SIP domain FQDN
    Mobile client goes through reverse proxy server to sign in. It is not related with Edge Server. Check the certificate on reverse proxy is not expired.
    Best Regards,
    Lisa Zheng
    Lisa Zheng
    TechNet Community Support

  • Lync 2013 Cloud Service Limitations

    Can anyone point me to some references on the limitations with Lync 2013 in the
    cloud? What are some pros and cons about cloud services with voice and video?

    How much of this list is still true to the limitations of Lync Online?
    The features not available are:
    Searching for employees by their skillset in an on-premise SharePoint Server and SharePoint Online
    Persistent group chat
    Connect (federate) to IBM Sametime unified communications platform
    IM/presence federation with XMPP networks such as Jabber  and Google Talk
    IM/presence with AOL and Yahoo
    Authenticated experience in Lync Web App
    Outlook delegation for scheduling online meetings
    Generate a link to schedule a meeting via web page
    Schedule an online meeting in Outlook Web App
    Dial-in audio conferencing on Lync Server
    Multimedia content upload
    Screen shot capture (including annotation)
    Interoperability with on-premise video conferencing systems
    Make incoming/outgoing calls over the phone network (PSTN dialling)
    Call hold/retrieve
    Dial-out over the phone network (PSTN) for meetings
    Advanced call controls including transfer, forward and simultaneous ring
    Access to Exchange Online voice mail
    Team calling
    Delegation for voice, for example, boss delegates to secretary
    Call park
    Outgoing Direct Inward Dialing (DID) manipulation
    Enhanced 9-1-1 for location by emergency services
    Dial plans and policies
    IP desk phone support
    Survivable Branch Appliances for branch office resiliency
    Call admissions control
    Support for analog devices such as a fax
    Response groups
    Private line (secondary DID for executives)
    Interoperation with third-party private branch exchange (PBX)
    Presence interoperation with third-party PBX
    Remote call control (RCC) (also known as “click-to-call”) with on-premises PBX
    Malicious call trace
    Unassigned number
    Network Quality of Service (QoS) and Differentiated Services Code Point (DSCP)
    Media path optimisation
    Phone number management
    Call detail recording (CDR) and billing reporting
    Integration with call centre solutions (Aspect)
    Connect to IP phones (Lync 2010 Phone Edition)
    Advanced interface for receptionists (Lync 2010 Attendant client)
    Legacy clients (eg. Office Communication for Mac, 2007 R2, Mobile for Windows Mobile 6.x)
    Anti-malware scanning for meeting content and file transfers
    Instant message archiving (server-side only)
    Exchange Unified Messaging (UM) interoperation with Exchange Online
    Exchange UM interoperation with Exchange on-premise
    Use the same domain for Lync on-premise and Lync Online users
    Splitting workloads (for example, running IM/presence/voice on-premises, and conferencing in the cloud)
    Attendee/user reporting
    Reporting (using call recording and Quality of Experience)
    Server side APIs to connect to other programs

  • FQDN Query when publishing the Lync 2010 Topology

    Hello All
    While am Defining  the Topology for Lync 2010 Enterprise Edition , in which the define of  SQL store , i forgot to mention the FQDN of SQL server name, instead i was mentioned only server name. my sql server FDQN is SQL.doitnow.com
    Define a new sql Store 
    SQL Server FQDN : SQL
    instead of SQL.doitnow.com
    SQL instance : RTC
    Topology published successfully .
    is there any issue will come in future without mentioning of FQDN during the initialization of lync 2010?
    After published the topology, all the data stored in central management Store and so, how can i modify any of the  data's after it saved to CMS (after Published topology)
    can i delete / remove - CMS and re-publish the topology ? is there any harm ?

    Thanks Holger 
    So i  need to do the below
    1. open an existing topology file , by downloading topology from existing deployment from the server  LYNCFE01n.doitnow.com
    2.Expand Enterprise Edition Front End Pools
    3. Right Click the POOL --> New Server -- FQDN of Second Server  abd Primary IP address
    4. Loging to the second FE server and install the Prequesties
    4.Run the Deployment wizzard on your new Server.
    5.Install the certificate
    6.Start the service
    if i need load balance then need the below ,
    Configure the load balancer for th web services 
    Configure the required DNS entries.
    Could you please correct me if am i missing anything 

  • SIMPLE QUESTION: LYNC 2010 -- AVAYA CS1000 DIRECT SIP: IS THAT POSSIBLE? PLEASE HELP!

    Hello,
    I would like to ask really simple question here: is that possible to establish (configure, setup, create, make etc.) a direct SIP connection between LYNC 2010 and AVAYA CS1000 PBX. On one side I have Lync 2010 Standard Edition acting as Front-End Server
    with co-located Mediation Server. On another side I have AVAYA CS1000 IP PBX Version 7.0. We are trying to make this happen for 1 full year with no luck. The issue is that we do not manage our PBX (external company does).
    Here is what we are basically trying to achieve:
    All I want is that basically LYNC user (phone # 5678) can dial PBX user (phone # 1234) and talk. Also PBX user can call LYNC user and they can talk. I'm pretty sure that all I'm asking is very simple thing. I don't expect magic to happen (e.g. when one user
    calls another user the world will change). All I want is to be able to call between LYNC and PBX users so they can talk.
    Sorry for repeating again but here is my simple question: can direct SIP (or call it SIP trunk if this is the right word) be established so LYNC and PBX users can call each other and talk. Whatever protocol is (G.711, G.722 etc.) I will be happy.
    If you can let me know I would very much appreciate this. I'm sure I'm not alone in this world and many companies out there using AVAYA CS1000 and deployed LYNC and probably have the same question so it may be helpful to other people as well.
    Thanks!

    Hi Thamara for reply. I can see where you are going, but the challenge here is that I have found many threads including in this forums from people who successfully connected CS1000 PBX to Lync 2010 for two-way calling, and even dual-forking (which I cannot
    even dream about at this time).
    If you go to AVAYA WEB site, you can find official AVAYA compatibility MATRIX that is available here:
    http://www.google.ca/url?sa=t&rct=j&q=avaya%20compatibility%20matrix%20lync&source=web&cd=1&ved=0CBwQFjAA&url=http%3A%2F%2Fsupport.avaya.com%2Fcss%2FP8%2Fdocuments%2F100135385&ei=v3-5TsXVKMLX0QGHpdSkCA&usg=AFQjCNG6cmW5izdOASMuW34b8iK0vWnwuw
    According to this document, only CS1000 version 7.5 supports Lync 2010 and only via ACE - starting first quarter of 2011 (which is done deal by now) - see below for details. The problem is that I have a hard time to understand the meaning of the word "Supported".
    I do not really need full support, all I want is to be able to call in both directions using 2 distinct numbers (e.g. 4 digits extensions) that are configured in both systems.
    Another thing is this ACE. Apparently it is a big monster software that you need to buy and pay big bucks and lots of configuration just to make it working. But I'm not even sure what will work. We do have one-way calling (from Lync to PBX) - it just does
    not work other way, and I have no idea why. I'm not sure if this cannot be working, or because it was not setup right. As I mentioned before we have no access and clue about IP PBX - this is one of my issue here. Withoul knowledge how it works on PBX side
    I cannot be sure what is causing this.
    So I was wondering if anybody in this world was able to connect CS1000 PBX to Lync and perform two-way calling using two systems.
    Thanks!
    Microsoft OCS 2010 Lync
    Supported (via ACE) - 1Q11

  • Co-Existence Lync 2010 and Lync 2013

    Hi,
    How do we check that CMS is moved from lync 2010 to Lync 2013 in Co-Existance environment lync standard edition.
    I know that users are moved form Lync 2010 to Lync 2013 but i don't if CMS is moved? And in the existing co-existence we have two edge servers Lync 2010 and Lync 2013. How can i check if traffic is  routing through Lync 2010 or lync 2013. 
    Because we want to Decommission the Lync 2010 STD Edition before doing this i want to make sure every thing go smooth.
    Please help me on this.
    Thanks
    Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

    To find out if the CMS is moved:
    Get-CsConfigurationStoreLocation, if it's a standard server it will tell you the pool name.  If it's an Enterprise server, it will tell you the SQL server name associated with the pool. 
    http://technet.microsoft.com/en-us/library/gg412814.aspx
    Otherwise it's at the top of the topology builder (the top top part that says Lync Server in the left pane, under the Central Management Server spot in the right pane. 
    For a full decommission article, here's a decent one with screenshots.  As Ben said, if you can advise about the other places we could be more specific.
    http://www.oiboran.com/?p=1073
    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

  • Phone edition Aries Polycom CX600 coexistence - Lync 2010 and 2013

    Hi all,
    Currently busy with a Lync 2010 > 2013 migration where Aries Lync phones like Polycom CX 600 (using a blend of USB tethering, PIN authentication as well as common area phones) are involved. Phones have a blend of different CU releases ranging from .4066
    (CU5) to .4451 (CU14)
    User migration must be done in stages. That’s presenting a challenge in that Lync 2010 and 2013 must coexist for some time, yet providing seamless support for Lync phones.
    The normal migration scenario will be based on a site-by-site migration: users are moved from 2010 to 2013, DHCP options for that site are changed to provide relevant Lync phones  the new Lync 2013 pool parameters. HOWEVER, there is a considerable number
    of users travelling across sites, and it’s likely occurrence that a user still on 2010 would travel to a site migrated to 2013 (including phones). And the other way round can also occur.
    Based on this, my questions are:
    1) Can a Lync 2010 user sign-in (USB tethering) on a phone if DHCP is providing options for Lync 2013?
    2) Can a Lync 2010 user sign-in (PIN auth) on a phone if DHCP is providing options for Lync 2013?
    3) Can a Lync 2013 user sign-in (USB tethering) on a phone if DHCP is providing options for Lync 2010?
    4) Can a Lync 2013 user sign-in (PIN auth) on a phone if DHCP is providing options for Lync 2010?
    Also, is there any dependancy on a specific CU version for the sign-in process to succeed? Note all discovery records are strict domain matching compliant. 
    I was hoping LPE would feature a redirect mechanism like with desktop client but based on the very little specific literature available, that does not seem the case. Any advice would be very welcome.
    thanks all.
    Alessio Giombini | Microsoft Solutions Architect | Twitter: @AlessioGiombini
    Lync 2013 Detailed Design Calculator: try it at http://goo.gl/jU1hZR

    Hi,
    You can refer to the following link of “Lync 2010 – 2013 Migration: Lync phone edition devices”:
    http://unifiedme.co.uk/2013/09/lync-2010-2013-migration-lync-phone-edition-devices/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
    Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Lync Phone Edition coexistance with lync 2010 and 2013

    Hi Everyone
    I am currently planning a coexistent network between Lync 2010 and 2013 as I need to get 2013 out urgently. My question is around the Lync phone edition and how to get the phone to find the front end to register the phone to depending on which lync
    pool the user is configured to use. Right now all phones are configured with DHCP and are configured to use the 2010 front end server to get its cert provisioned. I also use the HP 4110 and 4120 phones in the office.
    How should I configure DHCP so that I do not cut my user off if they are moved the 2013 pool?
    Many Thanks
    Joe
    Joe

    Hi,
    Check this old Thread
    https://social.technet.microsoft.com/Forums/office/en-US/fca0b7be-124e-4480-ba2f-19ca4eebbd53/phone-edition-aries-polycom-cx600-coexistence-lync-2010-and-2013?forum=lyncvoice
    http://unifiedme.co.uk/2013/09/lync-2010-2013-migration-lync-phone-edition-devices/
    Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

  • Lync 2010 Voice & Video Support on Windows 2012 R2 SP1 RDSH & RDVH

    Hello - We have successfully demonstrated RDSH & RDVH using Windows 2012 R2, Windows 8 virtual desktops and Dell T10 Zero clients. RemoteFX has been successfully tested as well for Printing across RDSH & RDVH environments.
    Problem at hand is that we are unable to showcase Lync 2010 Voice & Video calling across both these environments (RDSH & RDVH).
    RDSH Environment
    In an RDSH environment, we observe that a Platronics headset connected to the Dell T10 thin client is able to get redirected to the RDSH Server using RemoteFX and in-turn the RDSH Server is able to detect the connected hardware. However, the Lync 2010 client,
    published using RDSH, is UNABLE to detect the connected audio device.
    As for Logitech Webcam connected to the Dell T10 thin client, we have no issues with device detection and the Lync 2010 client is able to see the connected Webcam device.
    RDVH Environment (Pooled Desktop)
    As for the RDVH environment, we observe that both the Platronics headset & Logitec Webcam connected to the the Dell T10 thin client are UNABLE to get redirected to the RDVH Server using RemoteFX. We have enabled RemoteFX via Group policy in this environment.
    Queries:
    A. Could you help providing some direction into troubleshooting/isolating the audio-device detection issue on Lync clients in an RDSH environment.
    B. Could you help providing some direction into troubleshooting/isolating the audio & webcam re-direction issue in an RDVH environment. FYI, our test bed server does NOT support GPU and wanted to check if that would be a limitation towards detection
    of these devices?
    Thanks
    Srinath
    sgopalkr

    Hi Dharmesh,
    Thank you for a response.
    We had already enabled Audio and Video playback option.
    But when we have tested with windows 7 desktop machine, the audio devices are detecting in Lync client in both RDVH and RDSH
    environment and we are able to make audio calls. So we are planning to test with the different thin clients. Post we will update the same.
    Thanks.
    Manikandan

  • 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 Enterprise Pool Front End Servers

    Can we mix Windows 2008 R2 Enterprise Edition and Standard Edition virtual servers in same LYNC 2010 Front End Pool?
    Tek-Nerd

    Agree with Lisa,Lync Server virtualization supports a mix of operating systems. For example, a host server running Windows Server 2012 R2 that runs virtual servers that run Windows Server 2008 R2 is supported.
    You cannot mix different types of servers within the same pool. All servers within the same pool must either be physical or virtual
    Also you can refer below link
    http://technet.microsoft.com/en-us/library/gg399035.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"

  • Photo Uploaded in AD but not showing/visible in Lync 2010 client

    Photo Uploaded in AD but not showing/visible in Lync 2010 client
    bala

    Hi,
    Please also double check the size of the photograph in AD, make sure the size not overtake 48 pixels by 48 pixels, as it has a serious limitation on the size and resolution of the photos: the thumbnailPhoto attribute can only hold a photograph with
    a maximum size of 48 pixels by 48 pixels.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Users still able to sign into Lync 2010 even though their Lync accounts are disabled

    I have 2 users who are still able to sign into Lync 2010 even though I disabled their Lync accounts. They no longer show up in the Lync console or when you use get-csuser. Their Lync account were associated somehow with their AD accounts in an old domain
    that we just decommissioned. I wanted to delete Lync accounts and recreate to see if that fixed their issue. After deleting the Lync account, they are still able to login. So, I guess I need to edit the Lync database to get rid of them and start fresh?.
    HDL

    Hi Winterthur,
    Agree with Tek-Nerd,
    this user certificate is valid for a period of 180 days, and is automatically renewed one month prior to expiration regardless of whether the user is connected internally or externally.
    Jeff Guillet’s article Disabling a User in AD Does Not Disable the User in Lync provides
    a good background about revoking this certificate and properly disabling the user from accessing Lync services when their Active Directory user account is disabled.
    For more details,
    http://blogs.technet.com/b/nexthop/archive/2012/11/28/lync-2010-client-authentication.aspx
    Best regards,
    Eric

  • Lync 2010 client does not offer any NON-direct UDP Candidates in its SIP Invite' SDP - why?

    Hello.
    We have a customer, experiencing the following issue.
    They have big multi-continental Lync Server 2010 Enterprise Edition deployment, with non-NAT'ted Edge Pool.
    The call scenario is simple: peer-to-peer video (A/V) call between external Lync client and Video system, Cisco VCS
    in this case but does not matter, which (video system) only supports media over UDP (which is nothing strange). The VCS has a lot of video endpoints all over the Globe, Lync clients are also everywhere, so call can be any "distance", not predictable.
    All video endpoints are registered on this single VCS.
    The video call, as I suspect, only succeeds IF direct peer-to-peer UDP connection works and fails otherwise.
    I skip the overall design, keeping here only what is relevant.
    Video system offers only its own local IP as UDP candidate (type = host), which in this particular
    case is expected, let's assume there is no TURN etc expected on video system' side, it is directly Internet-facing.
    Now the main bit. Lync client offers ALL proper TCP candidates: both local AND non-local, using external
    public IP addresses of both A/V Edge Hardware LoadBalancer VIP and public IP address of one of Edge servers.
    Those candidates are enlisted perfectly fine (I checked carefully), so SIP INVITE has them all offered.
    Now: the Lync 2010 client ONLY offers direct/local UDP candidate (type = host) with its own IP address,
    but does NOT offer any NON-local UDP Candidates at all (while, again, for TCP candidates the full set of non-local (A/V Edge) ones is offered).
    WHY this can happen?
    Again my guess on where to dig is: TCP candidates (which are completely useless for such video call)
    are all offered fine with A/V Edge's public IPs, both VIP and particular node ones. Does this fact make sense?
    WHAT can be the reason why the same or similar remote/Edge Candidates are not being
    offered/enlisted for UDP while for TCP they are offered?
    What I already found, to be excluded easily: the whole client sign-in and in-band provisioning is OK, all about
    certificates is Ok, and all about MRAS URI and MRAS Credentials (looking sign-in traces) is also fine. Client gets proper MRAS username/password and ALL about signaling before SDP is also fine (no TLS or MRAS related errors).
    I cannot rule-out potential DNS issues at the moment, however unlikely: otherwise how it would get proper list
    of NON-local TCP candidates and all SIP signalling with the Edge working Ok if it would be DNS-specific issue?
    What, however, I have not confirmed is: UDP port 3478 is most likely NOT opened on/between all of the involved parties (Edge's private and public interfaces, Hardware LoadBalancer's interfaces and client),
    and/or UDP 3478 communication is most likely getting blocked completely (when the client is external), however for instance TCP 443 is everywhere opened.
    Can THIS be somehow related to why it properly allocates non-local TCP but none of
    non-local UDP Candidates?
    What traces show on call negotiation is ICE Connectivity Failed and/or ICE Warning - I have real it carefully, did WireShark'ing, what I suspect is: simply ICE Connectivity Checks fails on direct P2P UDP which is of course expected, and because no non-local
    UDP candidates are offered and TCP is not allowed on video system' side - it fails. WireShark shows the following: millions of outgoing UDP from the client to Cisco VCS and not even one INcoming UDP back from VCS.
    Sometimes, depending on the external client's location, call, however, succeeds. I guess (guess)
    this is because SOMETIMES direct UDP flows Ok, while in vast majority of the cases it expectedly does not.
    Big thanks.
    /roubchi

    Hi,
    VideoendpointsonlysupportUDPmedia.ICEusuallyoffers3candidates: Host(privateIP), ServerReflexive(outsideIPaddressoffirewalllocaltothemediasupplyingagent–B2BUAorLyncClient),
     TURNserver(typicallytheEdgeServer/VCSExpressway)
    You can refer to the link of “Cisco
    VCS and Microsoft Lync Deployment Guide (X8.1)” to check the configuration of Lync integrated with Cisco VCS.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

Maybe you are looking for