Lync 2010

How can I federate or connect Microsoft Lync 2010 with skype?

Hello fthillet,
How about a very detailed document on how to get Microsoft Lync and Skype connected via an Asterisk product? I have a link to a (Skype un-supported) web page that will answer all of your questions about Lync, Asterisk, and Skype. It's called "Step-by-step Microsoft Lync 2010, Asterisk and Skype installation/integration guide". It will even have more detail than you really need, with lots of questions and answers, but is everything you always wanted to know. It's written by a very respected author, and Microsoft "Most Valuable Professional", ADAM "I'm a UC Blog".
His Link to Lync is: http://imaucblog.com/archive/2010/10/09/step-by-step-microsoft-lync-2010-asterisk-and-skype-installa...
Please visit that link and let us know what you think. If you need any more information, there are many professionals here that should be able to answer your questions.
Thank You for using Skype and the Skype Community Forums.
Regards,
Victor S.
Regards,
Victor S.
Skype Enterprise Support

Similar Messages

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

LYNC 2010 on Supportability on Windows 2012 R2

Is it possible to run Lync server 2010 on Windows server 2012 R2?
Is there any known issues running LYNC 2010 Enterprise pool with Enterprise Voice on Windows 2012 R2 OS?
Any special requirements or issues installing LYNC 2010 on Windows 2012 R2?
We have one pool on Windows 2008 R2, would like to add additional pool with Windows 2012 R2.
Thanks in Advnace
Tek-Nerd

Per the following URL:
http://technet.microsoft.com/en-us/library/gg412883(v=ocs.14).aspx
Microsoft does not support this on operating systems that are not listed on this page for Lync 2010. Windows Server 2012 (and R2) are not listed as supported.
There are several new features in Server2012 that are not used in Lync 2010. I would not install 4 year old enterprise software on a platform such as Server 2012 R2. There are enough hoops to jump through with Lync 2013.
if my post is helpful - please click on the green arrow. (please excuse, in advance, any perceived sarcasm/humor - as I often forget it does not translate through text) :)

User profile sync Sharepoint 2010 photos thumbnail with AD and Lync 2010 - error on Full Synchronization- get events 8311, 6110, 6803 FIMSynchronization Service

User profile sync Sharepoint 2010 photos thumbnail with AD and Lync 2010 - error on Full Synchronization- get events 8311, 6110, 6803 FIMSynchronization Service
We're trying to set up sync between Sharepoint and AD so photos are displayed in Lync.
The certificate referenced in 8311 is not the sharepoint root cert, its the UCC cert with our FQDN of the site. sharepoint.domain.com
Is this causing the problem with the sync and holding up the photos?
I have tried several proposed fixes, it hasn't helped.
tried this as well:
http://blogs.technet.com/b/praveenh/archive/2011/05/11/event-id-8311-certificate-validation-errors-in-mss-2010.aspx
Josh

Try this fix and see if its sync the photos:
http://blogs.technet.com/b/steve_chen/archive/2010/09/20/user-profile-sync-sharepoint-2010.aspx#Profile Picture Property
http://blogs.technet.com/b/steve_chen/archive/2010/09/20/user-profile-sync-sharepoint-2010.aspx#SyncPicAD2SPS
Update-SPProfilePhotoStore -CreateThumbnailsForImportedPhotos 1 -MySiteHostLocation <mySiteHostURL>
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Questions on Lync 2010 to 2013 Addressbook Migration

Hi Team,
We are in the process of migrating the users from Lync 2010 to Lync 2013 pilot pool.
https://technet.microsoft.com/en-us/library/jj205160.aspx
According to the above article, basically the Lync Server 2010 Address Book is migrated along with the rest of your topology and don’t have to worry about the post migration steps if we don’t have customized settings such as GAL partition (By setting
up an attribute ‘msRTCSIP-GroupingID’), customized AB normalization rules and customized phone normalization rules.
Questions:
1. How do we confirm that there is no customized settings of phone normalization, AB normalization and GAL partition in the existing Lync 2010 environment?
2. Is there any powershell command to validate the current Lync 2010 settings?
Please advise.
Many Thanks.

The grouping ID is not something you'd normally put in. If all users can search for and see all other users, you'd be fine.
For the AB normalization look for Company_Phone_Number_Normalization_Rules.txt in your Lync file share in
X-WebServices-X\ABFiles (replace the X with whatever you see). If you have one, you could copy it over to your new Lync 2013 file share. This file is for normalizing phone numbers found in AD. To validate current settings, you can run
the BPA http://www.microsoft.com/en-us/download/details.aspx?id=4750 but if you're moving away from it, I wouldn't kill myself resolving issues. From PowerShell, there
are many things you could validate, is there something specific you're worried about?
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
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

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.

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 2010 and Lync 2013 blinking icon in taskbar not working properly

Hi,
We're experiencing a strange behaviour. Lync IM notifications are supposed to work this way below:
1) Notification bubble on the right-bottom corner
2) After a few seconds, a blinking icon in the task bar
3) After a few seconds, a coloured icon remains in the task bar
Some of our users, both Lync 2010 and Lync 2013, go 1) and 2) but then icon won't remain in the task bar, so they don't realize they have a conversation waiting (Windows XP and Windows 7).
If they open the icon, the conversation is there and coloured, and they can answer.
In my computer, it has also happened but most of the time it works fine (testing it, maybe it works 15 times and fails 1). Nevertheless, a lot of people is suffering from this strange behaviour.
We have looked into the causes but haven't found anything.
Any clue?
Thanks!

How long have you seen the problem?
What version of your Lync client? Try to update your Lync client to the latest version.
Try to repair office 2013.
Uninstall and reinstall Lync 2010.
Please install Lync 2013 or Lync 2010 on a fresh installation of Window to check if you can still see this problem.
Lisa Zheng
TechNet Community Support

Lync 2013 domain discovery not working, but Lync 2010 works flawlessly

We are using Lync 2013 and Lync 2010 in our company. Upon installation Lync 2010 can connect absolutely fine with for example [email protected], but when we use Lync 2013 we receive a DNS error saying it cannot resolve the domain when using the same
method. I have to manually enter the internal and external servers on each deployment of Lync 2013 to sipdir.online.lync.com:443 in order for successfully login to Lync 2013. We are upgrading all users to Lync 2013 and I want to avoid having to do this
on every deployment. This has always been an issue and not something that recently became an issue.
I have double checked my CNAME and SRV from my host provider and everything is as it should be. Contacting MS support they made me change my preferred DNS to 8.8.8.8 on the network adapter for the PC, but that breaks everything you connect to internally and
is not a solution to this issue.
Any ideas?

Hi,
The forum you posted is for Lync Server On Premise only. The issue is more related to Lync online, you can also post a question on Office365 forum for assistance. Thank you for your understanding.
http://community.office365.com/en-us/f/166.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

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

Why can't I copy contacts' email address from their name card in lync 2010

so here is the issue I have, when I need to copy someone's email addresses or their phone numbers, normally I will find them on lync, move the cursor on them, and their name card will show up, then I move cursor to their email address or their phone numbers,
right click it, there will be an option to "copy", right? but sometimes, right clicking doesn't work. that copy option just won't pop up, this issue happens randomly, I need to restart lync, then it will work again. Also, there is one thing
that's weird, after I restart lync, whatever I have copied in the clipboard will disappear, like if I press ctrl+c to copy something from word, then this issue happened, I restart lync, I can copy information in lync name card again, but all that
content I copied does not exist in clipboard anymore, I press ctrl+v, there is nothing coming out.
this is not a big problem, but it's really annoying, does anyone know why this issue happen and how to permanently? I tried to reinstall, does not work.
this issues happens with both lync 2010 32 bit on 32 bit win7 and lync 2010 64 bit on win7 64 bit.

Hi,
Please try to delete Lync user profile and information in registry.
The path of Lync user profile: <user profile>\AppData\Local\Microsoft\Communicator\
The path of Lync information in registry: HKCU\Software\Microsoft\Communicator\[email protected]
Please also make sure Lync client update to the latest version.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Issues with iPhone and Android connecting to Lync 2010?

Our environment currently consists of a single Lync 2010 instance, which is currently performing all roles. The current challenge I'm running into is connectivity to iOS and Android devices not wanting to cooperate. Currently, Lync is using a certificate
issued by a local CA. The CA root certificate has been imported to the devices that are having trouble connecting, and I've done this via email import without success, as well as using the iPhone Configuration Utility. In all tested instances, an error that
"the certificate can't be verified" is displayed that prohibits a user from establishing a connection. All domain workstations and remote users that import the root CA have no issues connecting.
I can't seem to figure out what's going on here. Has anyone run into this? This is a quasi-test environment in my lab that I'm testing with a few other people, and as much as we've tried, can't seem to figure out the issue. Any ideas?

To confirm that the certificate has been installed successful do you have a corporate website that is available externally that uses a certificate issued by the CA in question? If the answer is yes I would browse to that site on the phone and see if you
get an error. The Lync mobile clients don't give you a heck of a lot of information for troubleshooting. This will rule out a certificate issue.
Next thing would be your reverse proxy. Are you using ISA server? Test the reverse proxy rule by browsing to the Lync mobile auto discover URL - https://lyncwebexternal.domain.com/Autodiscover/AutodiscoverService.svc/root
Assuming ISA also make sure the rule is configure correctly -
http://technet.microsoft.com/en-us/library/hh690011.aspx
http://blogs.technet.com/b/nexthop/archive/2012/11/19/configuring-reverse-proxy-for-lync-server-2010-mobility.aspx
Let me know what the results are of those tests.
Andrew Morpeth
Lync Server Specialist - Auckland, NZ
Check out my blog

Lync 2010 Certificate Issue - "There was a problem verifying your certificate from the server"

Greetings.
My Issue:
Lync 2010 client does not connect to server;error displayed "Cannot sign into Lync. There was a problem verifying the certificate from the server."
Description:
The client is running on my Windows 7 box, and my CA server is a Windows Server 2003 box. I have installed the hotfix on the Server 2003 box to update the Web Enrollment portion of CA to allow for newer clients (Vista and 7) to receive certificates from
this server.
Lync server is running on Server 2008 R2 STD, installation was a success.
The Windows 7 box is a part of the domain.
I have manually exported the Root CA from my Enterprise CA server from
Trusted Root Certification Authorities -> Certificates and imported into the same location on my Windows 7 box.
If I look at the certification path on the Root CA, on my Windows 7 box, it says "The certificate is OK." The same goes for the servers involved.
Still nothing.
I have read the other forum posts on here about people having success once they manually import the Root CA from the Enterprise CA server, but this is not my case here.
All certificates are successfully assigned on the Lync server box; however, I did have to manually import the Root CA into Lync server's
Trusted Root Certification Authorities -> Certificates before I could successfully assign them. Had to do this on another deployment I completed, so I didn't think anything of it.
To recap: it seems that even with my Root CA imported into my Windows 7 box I can still not connect to my Lync server with the client, and I get the error message "There was a problem verifying the certificate from the server."

Solved
Solution : Export certificate from Lync Server Start > Administrative Tools > IIS > Server Certificate > Export > abc.pfx save it, Copy and place the certificate where Ms Lync 2010 client is installed or getting certificate
error. Follow these steps on client machine to install certificate
Run > mmc > add or remove snap in > certificates > computer account > local computer >finish > ok > expand Certificate > Trusted Root Certification Authorities > Certificate > All task > Import > copy abc.pfx certificate
and delete unnecessary certificate from there.
Restart Client machine and open microsoft Lync client 2010 and open option menu > Personal > Advanced > choose Auto Configuration > save ok

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

Similar Messages

Maybe you are looking for