Lync 2010 for HP slate 8 pro tablet

My play store makes lync 2010 unavailable for my tablet. What is the problem? I have an HP slate 8 pro tablet and my company enables us to connect to lync using android OS

The Lync 210 client is only supported on an Android phone: http://technet.microsoft.com/en-us/library/hh690980(v=ocs.14).aspx
more
info: http://social.technet.microsoft.com/Forums/lync/en-US/604617f5-1d42-4ab6-a6d4-39b378617fc1/lync-mobile-client-for-android-not-compatible-with-your-device-for-tablets
Microsoft only recently announced that support for Lync 2013 mobile client on Android tablets should be available end of June 2014: http://blog.lync2013.org/tag/lync-adroid-tablet/
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Similar Messages

How to block file transfer and desktop sharing in Lync 2010 for Fedrated and Guest Users

Dear,
Can anybody guide me how to restrict desktop sharing and file transfer for federated and Anonymous logins in Lync 2010.
I have tried to apply this policy through “Conferencing Policy”, but this gets applied to all users including corporate users.
Please help in this.

Hi,
As my knowledge, the CsFileTransferFilterConfiguration and setting in confercing policy are used to block transfer file between users. So if the policy is applied to user, the user would not transfer file with anybody. Since all Federation and Guest
Users access thought the Access Edge service, here is a update that helps to enable the control of the file transfer through the Access Edge service.
http://support.microsoft.com/kb/2621840
The update helps to define the file transfer policy between users on the local area network and users that connect through the Access Edge server in a Microsoft Lync Server 2010 environment. It helps protect Microsoft Lync Server 2010 deployment against
the spread of the most common forms of viruses with minimal degradation to the user experience.
Regards,
Kent Huang
TechNet Community Support ************************************************************************************************************************ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a
marked post does not actually answer your question.

HP, please respond! 4.4 Kitkat for Slate 21 Pro?

Is there anyone from HP reading this who can respond as to when we might see a 4.4 Kitkat update for the Slate 21 Pro
What about 5.0 Lollipop?
Is there an official plan to keep this platform current with the Android development roadmap? Or is this going to be a "one and done" platform?
Thanks.

Thanks, Wyrenut. Would still like an "official" response from HP.
I've been an HP user in both personal and professional roles (IT Manager) since mid-90s and have authorized purchase of multiple HP servers for enterprise environment. Their enterprise support is excellent. Their consumer support, quite frankly, leaves a lot to be desired. Communication - or complete lack of it - is their #1 shortcoming, in my opinion.
Hey HP, if you're out there and reading this, what's the story? Are you supporting ongoing development of Android on the Slate 21 Pro platform? Or is this a one-off?

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

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

Lync 2010 with Exchange 2010-2013 Migration?

We are installing Lync 2010 for the purpose of internal LAN and Internet/Federated instant messaging, video chat and desktop sharing.
There is no telephone integration and there is no Unified Messaging used in Exchange 2010.
Within a few months after rolling out Lync 2010, Exchange 2010 is going to be migrated to Exchange 2013. Outlook will remain at Office 2010 and Lync client will be 2010. We will continue to not use Exchange Unified Messaging after Exchange is
upgraded to 2013.
Are there any steps required to keep Lync 2010 working normally after the Exchange environment is upgraded from 2010 to 2013 in this scenario?

Hi
During the migration and post migration to EWS URL for the user i reachable by the Lync 2010 Client
And the outlook client is able to establish a Mapi session with the mailbox all should be fine
as best practice please have the Lync 2010 and outlook 2010 client update to the latest CU update
There is known issue when migrating from Exchange 2007 to 2013 good to know information
http://silbers.net/blog/2013/12/19/lync-ews-broken-during-exchange-20132007-transition/
Please remember, if you see a post that helped you please click ;Vote As Helpful" and if it answered your question please click "Mark As Answer" Regards Edwin Anthony Joseph

Lync 2010 won't download - error says it requires Windows 7

Lync 2010 won't download - error says it requires Windows 7 BUT I HAVE WINDOWS 7 !!
Very frustrating. After using Lync 2010 for the last year it did an auto-update and at first said it was missing a file. So I uninstalled and reinstalled and now am told that "Only windows XP3, Windows Vista and Windows 7 are supported. Please upgrade
your PC" But I DO have Windows 7.
Yes I know it's old. My new PC is sitting here waiting for me to change over but that can't happen for another month or so as I need more memory in it. In the meantime, I need to get my Lync 2010 working again.
Any help is greatly appreciated!

Hi,
This was finally figured out by someone internal to my company, a Lync specialist. This is what the solution was (in I.T. speak - sorry, I'm not I.T.):
Resolution: Checked and found COE was configured to run on XP SP3 where the minimum requirement is SP3
He definitely was opening files and checking boxes way beyond my simple "uninstall" and "reinstall".
Thanks!

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

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 client asks for credentials when outside of corporate network.

Hello,
We are running Lync 2010 Enterprise. Everytime our Lync users are outside of our network and they log in to their Lync client, they get a pop-up window asking for credentials. When they log into Lync inside our network the Lync client connects automatically
without asking for credentials. Is this normal behavior? I assumed that the Lync client would behave exactly no matter where they were connecting from. They are using Lync 2010 client on domain joined laptops, I would assume the Lync client would just use
the same credentials they used to log in to their computers and not ask for anything. Please let me know if there is a way to stop the pop-up from showing up when people try to connect to Lync from outside our network.
Thanks for any help!

Outside of the network the credential popup is for Exchange web services on the back end to check calendar info, contact lookup, etc. If Lync is already logged in when they see the popup, this is normal behavior.
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.

Best way to go for Cisco UC with Lync 2010 Integration

I have requirements to integrate Cisco UC 9.1 (single cluster) with Lync 2010. The decision is to use Lync for IM/presence and use Cisco phone for VOICE features.
Now I have two options which are Microsoft RCC and CUCI-Lync in my mind.My questions are:
Are CUCI-Lync and MS. RCC conflicting features? If not, can we enable both of these features and what could be the strong points to do this way?
Cisco Application dial rule and directory lookup features will allow Lync client to see the calling name displayed when making calls to the other Lync users. However, the inter site calls are sent through PSTN which does not accept the calling name IE in ISDN so the called party will NOT see the calling name displayed on the Cisco IP phone. In this scenario, would the Lync client still be able to see the name displayed on this call?
Can we have presence status updated to Lync clients when Cisco handset if offhook/ busy?
Appreciate for any feedbacks on the above. Thanks

Hi
Firstly, Lync + Cisco often isn't the best solution - yes, Lync is good, and yes, Cisco voice is good. That doesn't mean that by having two systems you are getting the best solution.
CUCI-Lync works when implemented properly but it's not perfect.
Anyway.... I'm sure you'll properly pilot the solution!
1. Yes, they conflict. CUCI-Lync performs more advanced call control than RCC and there's no real reason to implement RCC with it. The only case I can think of for that is maybe for Macs, as there is no CUCI-Lync for MAC. As I recall there's nothing to stop both being configured....
2. As long as each endpoint has it's own DDI presented when dialing over the PSTN, the reverse lookup rules should still allow a correct lookup against AD (so if each AD account has both the 'internal' extension number and the DDI in attributes that CUCI-Lync uses for reverse lookup then it should display the name).
3. Yes - you need to carry out the steps in the documentation that describe setting up 'custom presence states' for this to work though. People miss that a lot...
Regards
Aaron

Looking for documentation for CSM and the Lync 2010

hi experts,
Does anybody knows have Cisco any good documentation for the Lync 2010?
We have to setup the CSM for the load balancing as we are not able to use DNS load balanbing method. Or we have done so, but we need to very if things are correct.
Pepi

Hello Dunc_F,
Is this what you were looking for?
http://a248.e.akamai.net/pix.crutchfield.com/Manuals/472/472RADIO2.PDF
B-rock

Article ID: 2809243 Need Readme for Lync 2010.

Tried to find the new CU for Lync 2010 and found Article ID: 2809243, but this only contains readme for Lync 2013. Does anyone know where to find the right one for Lync 2010?

Check here for a current list including the April 2014 update:
http://support.microsoft.com/kb/2493736
Direct link to the April update:
http://support.microsoft.com/kb/2957044
I'd stick with the first link, and run the LyncServerUpdateInstaller and back end database updates when you're aware of new releases. It just makes life easy.
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

Lync 2010 & 2013 Co-existence, After Moving fileshare clients are prompting for Credentials for RGS

Hello,
I am in middle of migration from lync 2010 to 2013. At the moment both enviroments are in Co-existense state, Got pools on both enviroments, however all users are moved to 2013 pool already. Also edge has been migrated already to 2013, and it seems to work
fine (except mobility).
Last Friday I decided to move the lyncshare from old server to new one (both servers were using same lyncshare on old server). I was using this guide: http://technet.microsoft.com/en-us/library/gg195742%28v=ocs.14%29.aspx and all were working pretty fine.
When about hour was passed after last steps, problems started to occur. All clients are asking for credentials to RGS, nowhere else. Entering credentials won't help, prompt appears again. If i cancel the prompt, lync works, but shows error in lower right corner:
Cannot synchronize addressbook (or something similar). Checking connection configuration from client shows that EWS is not deployed, which has been deployed.
I have also checked twice that the permissions are right on lyncshare.
Where should i start to look a solution for the problem ? Seems bit odd that moving a share kinda breaks whole system.

Hello,
Apparently the problem this time is not the Lync, but Exchange. As we are having Exchange migration on the same domain at the same time, I were troubleshooting the problem more, and found out that Lync Client is configured to use EWS Internal & External
url in "https://server005.domain.local/ews/exchange.asmx" , but when opening the url i receive the followin page:
and syntax is: svcutil.exe "https://server014.domain.local:444/EWS/Services.wsdl" , so If i understood right, the problem is in exchange, not in Lync at the moment.
About errors in FE Event Viewer, There is one error repeating often, have not found a solution yet.
Best Regards
Jaakko

Microsoft Lync 2010 continuously asks for credentials after signing in

Hi,
we have lync 2010 frontend server at our office, it is working fine for the all the users, but one user who will connect our network through VPN it will continuously prompts for credentials eventhough if we are providing right credentials, because of this
user will be not able to recieve emails from his outlook. all other VPN users working fine. how to troubleshoot this issue, please any help?
Regards
Asha

Hi,
The issue may occur if the Outlook integration is not correctly on this client after connecting through VPN. What is the
difference for the location or sign in type between this user and other working users?
Lync generally only prompts you for credentials after you are logged in when it must connect Lync to a linked service such as the Microsoft Exchange Free/Busy service or the Calendar service.
If Lync continues to ask for credentials after three separate dialog prompts, there is likely an issue with Outlook integration or with the Exchange services themselves. I suggest referring to the following information to check the issue.
http://support.microsoft.com/kb/2298541
http://support.microsoft.com/kb/2436962
Regards,
Kent

Lync 2010 for HP slate 8 pro tablet

Similar Messages

Maybe you are looking for