How to connect Lync 2013 client with OCS 2007 R2 Edge server

Hi,
We have OCS 2007 R2 Edge server for external & OCS 2007 R2 FE Server for internal access in our environment.
We able to access internally Lync2013 clients with OCS 2007R2 server, however from external we cannot access Lync2013 client with OCS2007 R2 server.
Is there any patch or registry key trick to access OCS from lync2013 client externally? We cannot immediately migrate to Lync2013 server from OCS.
Any help
MD

Hi,
I suggest you still use OCS 2007 R2 client to login OCS 2007 R2 Server untill finishing migration to Lync Server 2013, as using Lync client with OCS 2007 R2 Server will offer a pretty limited experience.
Here is a great blog about Lync 2010 Client unsupported with OCS, it is for Lync 2010 client but similar for Lync 2013 client:
http://blog.schertz.name/2010/09/lync-client-unsupported-ocs/
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

Similar Messages

Lync 2013 Clients in Child Domain Log "The server returned HTTP status code '403 (0x193)' with text 'Forbidden'."

Hey All, I am really stumped on this one.
Environment - Is using split DNS
Forest Root Domain - Contains new Lync 2013 Server Standard, ADDS, DNS, Enterprise CA, Workstations
Clients in this domain connect and work beautifully. No errors.
Child Domain - ADDS, DNS, Workstation, Lync 2013 client
Client autodiscovers, and then asks for a password. Enter the password and this comes up...
Can't sign in to Lync, You didnt get signed in, It might be your sign-in address or logon credentials.. blah blah blah"
Client log shows
Error:
There was an error communicating with the endpoint at 'https://domainlync13srv.Domain.net/WebTicket/WebTicketService.svc'.
The server returned HTTP status code '403 (0x193)' with text 'Forbidden'.
The server understood the request, but cannot fulfill it.
As far as i can tell certificates are correctly configured with all the SAN's possible in my forest. The user is correctly set up in Lync control panel. Autodiscovery seems to be working as it should. EWS is working correctly.
Repaired client, removed cached creds, has all lync 2013 updates no dice
Thank you all!

I am an IDIOT.
I did not prepare the child domain with the LYNC setup tool. Logged on to a file server in the child domain with domain admin rights and sure enough the setup said the domain was "partial". Ran the setup and bam it all started working.

Configuring Lync 2010 Mobility with Front end and Edge Server

I have been racking my brain the past week trying to figure out how to get the lync edge server working properly and how to get the mobility service working properly.
Currently I have 1 front end server that is configured and working. I have one edge server that has been configured according to nearly every online help I could find along with public CERT.
If I use microsoft's online connectivity test and I run the test for
Lync Server Remote Connectivity Test everything passes. I am also able to connect to lync using a windows lync client from outside of the internal network however I have to specify the server name as being sip.ourdomain.com I cannot get connected using
autodiscover.
When I run the Lync Autodiscover Web Service Remote Connectivity Test it fails due to SSL error to lyncdiscover.ourdomain.com which then lead me down the path that I needed to install
the Mobility service but it also tells me that I may need to update our SSL cert as well.
This is where I am getting confused and would like to be pointed in the correct direction.
When I installed mobility service on the front end server it created the autodiscover section in IIS. If I am inside our network I can browse to it without any issue. Where I am confused at this point is how to either setup DNS or how to configure
the edge server to use autodiscover.
Do I need to setup an additional public IP and point lyncdiscover.ourdomain.com to the IP of our front end server or to our edge server? If I have to point this to our front end server then that would mean that I use one public IP that goes to 443,
444 and 5061 for our edge server and then I would need one public IP that goes to ports 443 and 80 that get redirected to ports 4443 and 8080 on our front end server? If that is the case then do I have to get an external cert for the front end server
that contains lyncdiscover or can clients connect if it is just using the self signed cert from the domain?
This is where I am getting confused at and hopefully some nice folks out there can clarify this for me so I can get this resolved.
Thank you
KK

You need an additional public IP to point to a reverse proxy, which will listen on port 443 and proxy requests to your front end server on port 4443 (notice the extra 4). You can use IIS ARR, Web Application Proxy, or whatever else you may have for
this purpose, but you need to ensure you redirect port 443 to port 4443. This reverse proxy cannot be collocated on your front end server or edge, you'll need a separate box or appliance.
Beyond Lyncdiscover, you'll want to do this for your external web services FQDN as defined in the topology builder and your meet and dialin URLs too. You'll want a third part cert for all of this (though it doesn't need to be installed on the front
end, just the reverse proxy) so that you don't need to install any internally signed root certs on anyone's smartphone.
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.

Lync 2013 client is deployed but user accounts are not migrated from OCS to Lync 2013 Server - how to open Lync meetings automatically in the Lync Web Plug-in

We have in our enterprise the following scenario:
1 - Lync 2013 client is installed
2 - User accounts are not migrated to Lync 2013 Server, users are using Office Communicator as their main tool
3 - Users receive Lync 2013 meeting requests but when try to access them, Lync 2013 client launches and shows error. Users will need to open the browser and paste the URL to the address bar but this still open
4 - We cannot use the workaround of adding "?SL=1" to the Lync 2013 meeting URL as the user base is large and manual workaround is not accepted
5 - Question: is there any automated way, via egistry key or GPO setting, so that users temporarily (until their accounts are migrated to Lync 2013 server) can bypass Lync 2013 client completely and automatically open all Lync 2013 meetings
on the browser, using Lync Web Plug-in?

Thanks for the response,
First, I should have mentioned clearly that users have Office Communicator 2007 client and Lync 2013 client installed in their machines. Their accounts are not migrated yet to Lync 2013 server.
Second, we are using IE9 and IE10. The issue is that users CAN join Lync 2013 meetings with their browsers but have to paste the URL manually to browser and add "?SL=1" otherwise, if they just click at the "Join Online Meeting" or "Join
Lync Meeting" URL it launches Lync 2013 client which shows error because is not configured yet, as they are using OCS client and migrating slowly to Lync 2013 server.
Is there a Group Policy setting or a registry key from Microsoft that can be turned on to these users machines and make will all Lync meeting requests to be opened in IE browser instead of Lync 2013 client. We need a way to ignore
Lync 2013 client until user accounts are migrated to Lync 2013 Server. Manually typing URLs is not an option in a big organization, can't explain thousands of users of different levels what to do.
We are regretting the decision not to separate Lync 2013 from Office 2013 package we deployed recently. If Lync 2013 is uninstalled then all Lync meeting requests are opened in browser without an issue.

Lync 2013 client deployment via SCCM with silent uninstall of Communicator / Live Meeting / Plugin

Hi
We are rolling out Lync 2013 across our org to many remote sites and are wondering the best approach for this.
We hope to leverage our SCCM, but so far we've only been installing Lync manually in our local test group.
I noticed that when installing Lync, it doesn't remove Communicator, Live Meeting, or the Live Meeting plugin for Outlook though.
Ideally, we would want to be able to push Lync 2013 client (standalone version, not Office 2013 Suite) via SCCM as well as uninstall Communicator 2007 R2, Live Meeting 2007 and Conferencing Add-in for Microsoft Office Outlook, all silently. Whether this
can be done while the user is logged in and using Outlook/Communicator, I am unsure (probably not), so doing this overnight with users logged off but machines on would probably work best.
Is there any documentation / guides from MS or other blog sites that have gone through this same process? From the searching I've done, it doesn't seem to be too common for a large deployment / jump from OCS 2007 to Lync 2013 on-premise.

Hi,
refer to this article it might help
http://social.technet.microsoft.com/Forums/lync/en-US/cf9ca58c-b9e8-465c-afb4-ed3992092f81/lync-2013-client-silent-installation
also did you try using Group Policy?
http://blogs.technet.com/b/mir/archive/2011/06/04/how-to-automate-lync-client-2010-deployment-in-multi-architect-environment-using-active-directory-group-policy.aspx
hope this help
If you find this helpful
please click "Vote as Helpful" if it answered your question please click "Mark as Answer"
Mostafa Eltohamy
Blog: http://Lyncdude.com Twitter:
LinkedIn:
XING:

How to configure Lync 2013 with Citrix xendesktop,

when we publish the Lync clinet in the Citrix XenApp 6.5, the mic is not working. we install the Lync VDI plug-in but still is not working.

The better place to ask is the Lync Forums. But make sure you are using the latest Cumulative Updates for your Lync 2013 clients. Also have a look at these threads:
http://social.technet.microsoft.com/Forums/lync/en-US/96c421a3-5dbf-4a7c-b760-09d21e35617a/lync-2013-support-on-citrix-xenapp-65?forum=ocsclients
http://support.citrix.com/article/CTX138408
http://support.microsoft.com/kb/2812461
Lync Forums:
http://social.technet.microsoft.com/Forums/lync/en-us/home?category=OCS
http://mariusene.wordpress.com/

Lync 2013 client connectivity to Lync Edge Pool

Hi all,
I have a question regarding Lync 2013 topology deployment
I have read somewhere that
The external interfaces of the Edge Server must not be routable by either clients or servers on the internal corporate network. The internal interface of the Edge Server must not be routable from the Internet. These routing principles must be enforced by deploying
firewalls between the Edge Servers (an internal and an external firewall) or by enforcing strict routing at the network layer.
Is the statement true? If it is, then there is no way for the internal client to talk directly to Edge server: its internal network interface doesn't have default route, so this interface can't talk to any client/server that is located on different subnet.
(unless I have to manually add-route in command line for all the subnets in the internal network, which is not preferable)
Any advise is greatly appreciated. Thanks

The mentioned statement is true. You need to manually add static routes in to the Edge server. Only the external interface must have a Gateway configured.
http://thamaraw.com

Lync 2013 client - Set people to "Blocked Contacts" relationship by default?

We are in the process of implementing Lync Server 2013 (on-premises). We have already implemented one front end pool and one edge pool and successfully tested the basic functionality. Now we are moving on to configuring the various policies based
on our requirements. One requirement that has come late in the planning is to prevent people from receiving IMs unless they explicitly allow people to IM them and to have the ability to whitelist IMs from people on an individual basis. This is a feature
that was submitted as a requirement by way of our IT HelpDesk manager.
From what I gather, this could be accomplished if someone had the ability to set the default to the "Blocked Contacts" relationship for everyone instead of "Colleagues". In my research on how to set that as the default, I found
a setting "ShowManagePrivacyRelationship" in Set-CsClientPolicy. I created a new per-user client policy called "TEST" and applied it to myself. Then I set ShowManagePrivacyRelationShip to $true via PowerShell on the TEST policy.
However, even hours after making the change and signing out and back into the Lync 2013 client, I still don't see any change in functionality or new options.
Now, if I instead sign in with the Lync 2010 client, I can indeed see a "Manage Privacy Relationships" option in a drop-down near the right side of the client which takes me to a view where I can see and move "People in my company" and
"People in domains connected to my company" pseudo-contacts from the "Colleagues" relationship to "Blocked Contacts" and this accomplishes exactly what we want to do.
Where can I find the "Manage Privacy Relationship" setting in Lync 2013 client? If there is no setting called that, how can I accomplish what I am trying to do using Lync 2013?
I would rather not use the Lync 2010 client, as our HelpDesk technicians all use Windows 8.1 and Office 2013.

David:
Yes, I have all of those relationships categories in Lync 2013. What I am missing is the ability to set the rest of the organization to
Blocked Contacts by default. I can do this with the Lync 2010 client using the same user login and the same Lync Server 2013 environment.
The following image demonstrates the location of the Manage Privacy Relationships option I would like to leverage in Lync 2013. The image is of the Lync 2010 client.
https://www.dropbox.com/s/i0g83i9su9e5zox/Manage_Privacy_Relationships.png
If I click that Manage Privacy Relationships option, I end up on the following screen. Note that there is a
People in my company object under Colleagues.
https://www.dropbox.com/s/kkatgtoexea7evt/Default_Privacy_Relationships.png
I am able to move that People in my company object to another relationship option. I moved it to
Blocked Contacts, as you can see below.
https://www.dropbox.com/s/956kw0ih15uksgr/People_In_Company_Blocked.png
As you can see in the following image, after making this change if I do not have a person on my Contacts list, they are unable to IM me. As you can see in my Lync 2013 client relationships list, no one is in my
Blocked Contacts list yet the Lync Test Account is being blocked due to the fact that I put People in my company there and haven't added them to my Contacts list.
https://www.dropbox.com/s/cue09wjj8tidbau/Blocked.png
After adding the Lync Test Account to my Contacts list, the Lync Test Account is able to IM me.
https://www.dropbox.com/s/nalju5ia980lc30/Unblocked.png
I hope these images help make clear that there seems to be a capability present in the Lync 2010 client that I am unable to locate in the Lync 2013 client. I can't find this
Manage Private Relationships option anywhere in the Lync 2013 client or any other option that lets me see those People in my company and People in domains connected with my company objects.
With regards to the EnablePrivacyMode option, I am already aware of it and that is not what we are looking for.

No audio device detected - Lync 2013 Client

I have a brand new Dell Latitude E6430 laptop running Windows 7 x64 SP1. I installed Office 2013, including the Lync 2013 client. We are running Lync 2013 server as well. I have connected three different audio devices.
Polycom CX600 phone.
Plantronics Bluetooth headset.
Logitech Video Camera (The video on this works with Lync but no audio)
I cannot get Lync to recognize either of them. I can see them as devices in Windows but within Lync I only get a screen that says "We didn't find an audio device, which you need for calling". Does anyone have any idea on how to resolve this issue?
It is driving me crazy. Especially since it worked perfectly on my old laptop that had the same OS and patches, etc...
Thanks for your help in advance.
Jamie

Had the same issue. For me it required uninstalling the Intel Widi device from device manager. I think it was titled "wiusb" or something similar. It was in its own group in device manager. After uninstalling that, Lync would then
recognize my mic/speakers again.
I had the exact same problem as everyone else. I purchased two Dell Latitude E6530 laptops with Windows 7 Pro 64-bit. Both laptops had the issue. I uninstalled the WIUSB devices, restarted Lync, and Lync suddenly is able to detect devices...
I refreshed device manager to see if the devices would auto-install again... but there weren't detected again.
William Christenson
This worked for me as well. Uninstalled the WIUSB and WIUSB Host Controller which was present under its own group, Exit Lync process and started again, it detected the Sound Devices again. Definitely a driver conflict but it was quick resolution to uninstall
and get it working. No other issues with user as far as another device stopped working due to uninstallation of the devices.
It does not look like any driver conflicts, all other software detects audio device perfectly (Skype, Recorder,softphone, Lync 2010 etc.), but only Lync 2013 client keeps saying ""we didn't find an audio device". it appears the faulty in Lync 2013 client

Disable Lync 2013 Client and Exchange 2010 Integration

Is it possible to disable integration to Exchange 2010 from a Lync 2013 client? I found a key that works for Lync 2010 by setting HKLM\Software\Policies\Microsoft\Communicator\PersonalContactStoreOverride to 1. That does not seem to do anything
to a Lync 2013 client, nor have I been able to find a solution to disable it via Registry/GPO. Some things I have found seem to indicate that key does is not used by a Lync 2013 client but that is somewhat speculation. Can someone tell me if there
is a key to disable this connectivity and disable it like what the key above does for 2010? Thank you!

Create a new-csclientpolicyentry -name "PersonalContactStoreOverride" -value "1" and assign it to a Client Policy
see Raffaele's post at: http://social.technet.microsoft.com/Forums/lync/en-US/0762e036-1f9f-43a6-bb81-686864260c9d/how-to-install-the-lync-client-through-sms-with-personal-information-manager-set-to-none?forum=ocsplanningdeployment
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Lync 2013 client installation using SCCM

Hi everyone,
I have been performed Office 2013 installation in my domain. For this puprpose, I used SCCM 2007 R3.
At the beginning I customized this installation using OCT. I have excluded Lync from my Office 2013 distribution package, because we use Communicator Server 2007. Afterwards, I found that it is possible to use Lync 2013 with OCS 2007: http://www.technipages.com/lync-2013-fix-cannot-sign-in-because-the-server-version-is-incompatible-with-microsoft-lync-error.html
How can I silently deploy Lync on workstations, which already have received Office 2013 without Lync? If I simply try to add Lync feature in my package using OCT, silent installation stops on "Add/remove/repair components..." (which,
we, of course, cannot see during a silent setup).

You could utilize Config.xml to deploy Lync client. This will make installation silently.
http://technet.microsoft.com/en-us/library/jj204651.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Hi Juke,
Thanks for you answer. But actually not all is clear for me. In this article, I can see this:
"By default, the Config.xml file that is stored in the core product folder (for example, \product.WW) directs Setup to install that product. For example, the Config.xml file in the following folder installs Lync 2013:
\\server\share\Lync15\Lync.WW \Config.xml"
But in my Office 2013 installation folder, the Lync.WW folder does not exist.
Should I create it (and Config.xml too) manually? Can I remove other folders like Excel, Word from Office2013 installation folder?

App V 5.0 Sequence - Lync 2013 Client

Hello,
Could you please help me find sequencing steps to virtualize Lync 2013 Client (Basic/Enterprise) using App-V 5.0 SP2?
Regards,
Srinivasa Prasad

Follow that link for advice on how to download Office click-to-run and convert it to an App-V package...
When I did this, I set the Product ID in the CustomConfig.xml file as ProPlusVolume and used ExcludeApp tags to exclude all apps except for Lync:
Access
Excel
Groove
InfoPath
OneNote
Outlook
PowerPoint
Project
Publisher
SharePointDesigner
Visio
Word
Here is the info on how to configure this file:
http://technet.microsoft.com/library/jj219426(v=office.15).aspx
I believe it is also possible to set the Product ID to Lync, but not sure of the exact value to set and I have not tried this myself. Bonus tip - when you deploy Lync 2013 virtually, the plugins automatically integrate with the locally installed copy of
Outlook!
Dan Gough
UK App-V MVP
packageology.com
@packageologist
LinkedIn

Outlook 2010 contacts not showing phone number in Lync 2013 client

Hi,
We have Lync 2013 with Exchange 2010. Recently we started upgrading Lync clients from 2010 to 2013.
A few users started reporting that their local Outlook contacts does not show phone numbers in Lync 2013 (working with 2010)
I have installed the august patch which should solve this issue
981751 - Lync 2013 does not display telephone number of an Outlook 2010 contact in the contact card
Any idea where to look next?

Hi Tobias Borgen Nielsen,
Lync expects all the phone numbers to be in the E.164 format, meaning they should be +1-111-11111111 etc. If they’re not like this, you will have to normalize them if you want Lync
to publish them.
The related article for your reference.
Lync not populating contact cards phone numbers from Active Directory (Or: How to normalize AD phone numbers for Lync Server 2010 and 2013)
http://y0av.me/2012/02/23/normalize_ad_numbers/
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.
Hope it can be helpful.
Best regards,
Eric

Lync 2013 Client Not Display Numbers in Contact Card

Hi
I have a problem where Lync 2013 client connecting to Lync 2010 backend appears not download the contact list completely. Lync 2010 clients are all operating normally. On Lync 2010 client, you can view all contact details including Enterprise Voice
numbers and cell numbers for all users. However on Lync 2013 clients, Lync contact details for some users do not populate completely. In most cases, Enterprise numbers/Work Numbers/Mobile Numbers are missing. If the contact is pinned then the details
are retrieved.
In cases where Work/Voice/Cell numbers are not displayed, affected users is limited to making lync to lync calls only. The user can still dial the number and get through without any issues.
I have deleted and contacts cache on Lync 2013 but this has not helped.
Regards

Hi,
How about check the contact of “Outlook Test” user from the Lync 2010 client?
According to the second screenshot, since it’s an external account, the information will be limited.
Thanks,
Simon Wu
TechNet Community Support

Schedule a meeting via Lync 2013 client

Hi All,
quick run down of my set up,
Exchange 2013 SP1 (no UM) and new installation of Lync 2013 FE with Feb 2015 cumulative updates (no Ent voice )
haven't integrated Exchange with Lync.
my problem is when i try to schedule a meeting with a colleague via Lync 2013 client it says "no free/busy information could be retrieved and if i let it stay open for 5 min it will come up or unless I unselect and reselect the user the information
comes up.
any idea what's causing thus and how to fix it?
Thanks in advance

Not sure of a fix, but Michael LaMontange posted a workaround for it:
http://realtimeuc.com/2013/04/no-free-busy-when-scheduling-meeting-from-lync/
Some other thoughts here:
http://www.doitfixit.com/index.php?option=com_content&view=article&id=82:no-freebusy-information&catid=34:exchange-2010&Itemid=53
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.

How to connect Lync 2013 client with OCS 2007 R2 Edge server

Similar Messages

Maybe you are looking for