Lync 2013 Standard, publishing externally via edge/TMG

Hi
I am looking into implementing lync into our environment and have been considering using lync standard in the following setup
total users will be 3000 so thinking of placing 1500 on each server at primary site A and then pairing them with the servers at site B we will only really be using this for IM and Presence. The Primary site will be where all the users are located and only
in DR will we failover to the DR site.
Site A (Primary)
1x FEA1 1xBEA1
1x FEA2 1xBEA2
1x FEedgeA1
Site B (DR)
1xFEB1 1xBEB1
1xFEB2 1xBEB2
1xFEedgeB1
my questions are this
1. If we have two servers in site A each with a separate pool because they are standard, how many external URLS will I have to have if I am connecting using a Iphone using the lync client?
2. If a server goes down in site A and we fail the users over to site B what will happen to the Iphone users how will they connect back onto lync does this require the users to enter a new URL?
3. does Lync edge server require a public IP address and should its internal address be an IP on the DMZ or the internal LAN?
4. do you need TMG/ARR/WAP to reverse proxy lync or can Lync edge do this on its own for Iphone devices wanting to use IM?
5. In the standard lync model is the backend server a role or a separate server or can it be both, above I have listed as separate servers but was not sure if this could be a role on the FE?
thanks in advance
J

Hello,
Please find the answers below;
Each Lync pool need to publish external web service URL. Simple URLs can be shared between pools. So you need to publish meet ; dialin , lyncdiscover and webextA1 and webextA2. I assume , your sip domain remains the same for all pools.
In a DR scenario , you will have to make external DNS changes and repoint Lyncdiscover record to site B reverse proxy server.
Yes, edge server require public IP address. Internal edge IP address should be reachable from user VLAN. So internal IP should be fine.
Reverse proxy is required for mobility connectivity.
Lync standard edition backend database will be installed on the same box.
Thanks
Saleesh
If answer is helpful, please hit the green arrow on the left, or mark as answer.
Technet Blog

Similar Messages

Lync 2013 standard number of Backends required and pool paring setup?

Hi
I am in the process of putting together a lync 2013 implementation. The plan is to use lync 2013 standard as IM and Presence are the only requirement we have approx. 3000 users
we have two sites
Site A (Primary)
x 2 FE-A1 FE-A2 Lync 2013
x1 BE-A1 Lync 2013
Site B (D.R)
X 2 FE-B1 FE-B2 Lync 2013
X1 BE-B1 Lync 2013
what I want to know is
1. If Site A has two FE servers each will require there own pool if I pair FE-A1 with FE-A2 can I also pair FE-A1 with FE-B1 and the same for 2?
2. Can the servers FE-A1 and FE-A2 use the same BE server or should I be using a separate server for each?
3. In this design I was thinking of using two edge servers 1 at each site that would be published using TMG, would this be correct, this would be for IPhone mobile users to use.
thanks in advance
J

1) If site A has to FE servers, and you go with Standard edition, they would be their own pools. If you wanted HA you could put three enterprise servers together into a single pool and load balance them. If you pair FE-A1 with FE-A2, those
two pools cannot be paired with any other pool. You also can't Pair FE-A1 to FE-A2, then FE-A2 to FE-B1.
2) Your diagram looks like Lync 2013 for the back end, it would actually be SQL, and this would specifically apply if you're using Lync enterprise. If the Lync front end servers are in the same pool, they can use the same backend, if they're not they
need separate back ends.
3) Edge servers would be published with a standard firewall, if TMG is your firewall that would work. If TMG is only being used as a reverse proxy, you would use it to publish your web services on your front end servers. Either way, you'll need
to also publish the web services on your front end servers to the Internet for mobile clients to function.
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.

Certificate Requirement for Lync 2013 Standard Edition

I have successfully run the setup of lync 2013 standard edition now I am stuck due to certificates required for lync 2013. when I generate a csr. it show the subjected urls for that.
hostname.domain.com
sip.domain.com
diali.domain.com
meet.domain.com
admin.domain.com
lyncdiscover.domain.com
lyncdiscoverinternal.domain.com
im.domain.com (External URL)
so if I go for 3 party CA then I need 8 certicate only for internal lync. As I also need to connected federated partner and external user so I need Edge for again I need 3 more certificates
web.domain.com
a/v.domain.com
sip.domain.com
now when I go for these certificate it quit costly and I didn't understand why such certifcates required. can anyone help me to fix such requirement.
Or, what are the necessary url to which I buy 3 party CA rest leave as it is.
I also want to deploy Edge with single adopter as we have only one network so can anyone assist me to proceed it further.
Talha Faraz Malik

To save on the cost of your third party certificates, I would deploy an internal certificate authority to sign certificates for your internal front end. For your third party certificate, you would only need the SANs for the edge and for your
reverse proxy and as Edwin said, this can be a single cert with multiple SANs.
For example, for your edge you would need:
sip.domain.com
web.domain.com
You would not need A/V as this role does not require a SAN on your certificate. On the same certificate, which you could also use on your reverse proxy, you'd likely want the following FQDNs.
lyncdiscover.domain.com
im.domain.com (your external web services FQDN)
meet.domain.com
dialin.domain.com
You may also want to consider your internal web services FQDN and include the following so third party mobile devices can connect without needing a certificate installed:
im_internal.domain.com (your internal web services FQDN)
lyncdiscoverinternal.domain.com
I'm sure that's not entirely clear yet, so feel free to ask more questions or what the purpose of each is.
When you say Edge with a single adapter, you mean a single adapter in a DMZ or internal? You definably want two NICS, both in separate DMZs, but I've managed to get the edge working with a single adapter in a DMZ before. What you don't want is
the edge in your internal network.
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 Std and Ent Edition Edge co-existence

Hi all,
I'm seeing an odd issue with our current migration. We have the following:
Site1: Lync 2013 Standard with Edge server.
Site 2: Lync 2013 EE with 3 FEs, mirrored DBs and no Edge server deployed
All users live on Site1 and all is ok. Site 1 contains the CMS & PChat DB's
I'm re-using the current Edge server in Site1 as I need to retain the same URLs at the moment - the long term plan will be to build up a new Edge pool in Site2 once Site1 has been decommed.
I'm planning to move a bunch of pilot users onto Site 2 in the next week, but I see the following issues when I move a couple of test accounts into the pool:
Can't start a "meet now" conference
Can't expand Disti Lists
Can't search for contacts - addressbook never seems to download
Can't see federated contacts
P2P IM & AV works fine.
Client logging from a user in the new EE pool shows the following errors when try to communicate with a federated partner:
ms-diagnostics: 1038;reason="Failed to connect to a peer server";fqdn="standardserver.corp.domain.local:5062";ip-address="172.20.130.32";peer-type="InternalServer";winsock-code="10061";winsock-info="The
peer actively refused the connection attempt";source="FEPool.corp.domain.local"
My initial thoughts that its something to do with firewalling but I can ping & telnet from the old Front End and Edge over to the new FE pool (which are geographically separated and on different subnets) so I would have thought media should be able to
flow between the 2 sites without a problem. The FE pool has a HLB sitting in front of it.
I can also see our Exchange server ok from the new FE pool too.
Looking for any suggestions on what else I can look at.

Hi,
From your description, did you mean you don’t move anything from Standard pool to Enterprise pool (just move test users to Enterprise pool to test the function)?
Did you test internal or external of your corporation?
Please create a new Lync account on Lync 2013 Enterprise pool to check if the issue also happen.
Please check if CMS replication has update to the latest status with the help of following cmdlet:
Get-CsManagementStoreReplicationStatus.
If the status not to the latest status, you can invoke by the following cmdlet:
Invoke-CsManagementStoreReplication
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support
Hi Eason,
I have 2 laptops I'm testing with 2 different accounts that were initally provisioned on the new pool, one is connected to our corp LAN, the other is on our guest wifi to simulate an external connection.
CMS replication looks ok (servernames changed for obvious reasons!):
UpToDate           : True
ReplicaFqdn        : StdFrontEnd.corp.domain.local
LastStatusReport   : 20/08/2014 08:16:49
LastUpdateCreation : 20/08/2014 08:16:46
ProductVersion     : 5.0.8308.556
UpToDate           : True
ReplicaFqdn        : StdEdge.corp.domain.local
LastStatusReport   : 20/08/2014 08:16:48
LastUpdateCreation : 20/08/2014 08:16:46
ProductVersion     : 5.0.8308.556
UpToDate           : True
ReplicaFqdn        : StdTrustedAppServer.corp.domain.local
LastStatusReport   : 20/08/2014 08:16:48
LastUpdateCreation : 20/08/2014 08:16:46
ProductVersion     : 5.0.8308.0
UpToDate           : True
ReplicaFqdn        : EntFE1.corp.domain.local
LastStatusReport   : 20/08/2014 08:16:51
LastUpdateCreation : 20/08/2014 08:16:46
ProductVersion     : 5.0.8308.556
UpToDate           : True
ReplicaFqdn        : EntFE2.corp.domain.local
LastStatusReport   : 20/08/2014 08:16:51
LastUpdateCreation : 20/08/2014 08:16:46
ProductVersion     : 5.0.8308.556
UpToDate           : True
ReplicaFqdn        : EntFE3.corp.domain.local
LastStatusReport   : 20/08/2014 08:16:51
LastUpdateCreation : 20/08/2014 08:16:46
ProductVersion     : 5.0.8308.556
UpToDate           : True
ReplicaFqdn        : EntPChat1.corp.domain.local
LastStatusReport   : 20/08/2014 08:16:51
LastUpdateCreation : 20/08/2014 08:16:46
ProductVersion     : 5.0.8308.556

Lync 2013 standard edition server disadvantages

I have 3000 users, client is so cost effective , wanna insisting on Lync 2013 standard edition server. no enterprise voice
Feature required :- IM.presence, A/V conf, persistence chat, external access.
planned servers :- 1 Standard server in DC, 1 in DR. 1 edge server in DC and 1 in DR
1. if i make a pool of standard servers, then will it serve as HA, if yes how much time wil take for failover and what would be the impact on users?
2. If complete DC is down how mch time would take for fail-over and what is the procedure, impact on users?
3. can i collocate persistence chat role on standard edition? any limitation? how backend sizing would be for persistence chat as sql express would be there
4. can i suggest any better solution with standard servers where HA in DC .

For 3000 users Standard Edition will be fine. Use the capacity planner to size out your environment. http://www.microsoft.com/en-us/download/details.aspx?id=36828
1. It won't really serve as HA, as pool pairing is the only option it's more of a DR solution. The RTO for a pool failover is 30mins. So it could take anywhere up to 30mins. http://technet.microsoft.com/en-us/library/jj205079.aspx
2. Same as above. Here is how you failover http://technet.microsoft.com/en-us/library/jj204678.aspx
3. Yes, you can co-locate Persistent Chat on the Front End with Standard Edition. If sized correctly, there should be no performance issues.
4. The only option with Standard is Pool Pairing, so no better suggestions.
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)
This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Lync 2013 standard server for 3000

Planning to deploy Lync 2013 standard server for 3000 users, IM/presence, Audio/video, persistence chat, monitoring/archive. external access required so 1 edge server in DC and 1 in DR. No enterprise voice. DC and DR are corrected with dark fiber
one lync 2013 standard server in DC and 1 in DR. 1 edge server in DC and 1 Edge server in D R.have couple of queries.
1. can i get HA while doing server pairing in DC and DR?
2. how much time will it take for frontend failover if my frontend server is down in DC.
3. how much time will take for external access failover in DC and DR?
4. are there any potential risks if using standard version instead of enterprise?
Basically client need cost effective solution as lync is not critical for him, does not want to use 3 FE servers in DC and 3 FE in DR to achive HA. want to achieve the solution with standard servers.

1) HA typically refers to automatic failover, so not with Standard edition, but you can get manual failover with this with nearly full functionality.
2) Again, this is manual, but once invoked less than 20 minutes I'd think, possibly faster, only testing invoke-failover will tell you for sure but it won't be too bad.
3) This involves a topology change to change the federation route, possibly next hop for the edge, and possibly media path for a front end pool. That can be completed and replicated in under a minute. You may want to point your external simple
URLs and such (lyncdiscover) at the remaining server, this may be a DNS change to point to a separate reverse proxy. Your _sipfederationtls._tcp SRV record can have a lower matching partner as well, but I typically prefer to keep low TTLs on the external
DNS records so they can be changed quickly.
4) Sure, no automatic failover, your scalability is limited without building out new pools later, no SQL backend that can be mirrored for a bit more resiliency. But again, you can manually failover without issue, you just have to be able to tolerate
a short outage.
Technically, you'd only need 1 FE in the DR site. You have to match Ent/Ent or Std/Std in a pool pair, but the number of servers don't need to match. Still, the HLB and SQL requirements can be costly so I understand this.
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 2013 Standard Edition on Cisco UCS E-Series

Hello,
We have a working Lync 2013 deployment:
- Front-End Enterprise Pool consisting of 3 FE servers
- one Edge Server
- one Back-End server
- one Mediation Server
- one IP PBX gateway, where ITSP's SIP trunks end.
Because we have geographically distributed offices, we are considering deploying of branch offices deployments.
Technet recommends to use SBA for branch offices where there are less than 1000 users. But in case of WAN outage, no conferencing will be available for branch users.
Lync 2013 Standard edition branch deployment would offer all Lync features in case of WAN outage.
In every branch, we consider deploying a Cisco ISR G2 router for terminating branch SIP trunks. This equipment have option to add Cisco UCS E-Series blade that supports CPU with hardware virtualization and supports decent amount of RAM (up to 16GB and up
to 48GB).
Have anyone experience with deploying Lync Standard Edition on this equipment - Cisco UCS E-Series blades? In every branch office there are up to 50 - 500 users that will use Lync.
Thanks,
Andrei Moraru Endava

Hi,
I don’t think you can deploy Lync server 2013 on Cisco UCS E-Series blades.
Here is a link below of “System Requirements for Servers Running Lync Server 2013” may help you:
http://technet.microsoft.com/en-us/library/gg398588.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013- Standard Edition - Persistent Chat

What is the capacity of the Persistent Chat if it is collocated on Lync 2013 Standard edition front end ?
ie, number of chat rooms /usage?
In a Lync 2013 standard edition deployment if Persistent Chat is on separate server, can the SQL be offloaded to central SQL cluster enviornment or it will be held on the local server?

I haven't seen a chart that really defines the capacity, and it's difficult to measure because it's difficult to say how active the rooms will be or how much content you'll generate. That much is different from organization to organization.
There are some guidelines in general here:
https://technet.microsoft.com/en-us/library/gg615006(v=ocs.15).aspx but they don't really touch the standard model.
The pChat database can be offloaded to a central SQL cluster if you'd prefer, there are no requirements to collocate it with the local Lync databases.
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 Standard backup questions

Hello
I need to backup our Lync 2013 Standard Edition setup.
We have Only one server atm.
Looking at this post for inspiration:
http://blogs.technet.com/b/heyscriptingguy/archive/2014/06/28/weekend-scripter-basic-lync-server-2013-backup-and-restore-part-1.aspx
As far as i can understand, i don't need to do SQL backup at all? Or am i missing the point?
Would I be able to restore my Lync from these 3 commands:
Export-CSConfiguratiom, Export-CSLisConfiguration and Export-CsUserData - Is that enough for a disasterrecovery?
And a bonus question:
When i run Export-CSLisConfiguration . The export only contains the following:
<?xml version="1.0"?>
<LisDatabase xmlns="urn:schema:Microsoft.Rtc.Lis.Database.2008"/>
Is that not incomplete somehow?

That much would get you back up and running, yes. But it may not be a "full" restore.
For example, if you have persistent chat data, it wouldn't necessarily be included in there. If you have an archiving database where all IMs are sent, that information wouldn't be in the PowerShell exports above. If you don't have a copy of the
certificate and private key, that's lost.
Typically, I run my own custom version of Lasse's backup script https://gallery.technet.microsoft.com/Backup-script-for-Lync-2013-aacbb9b9
That pulls all the data, including your file stores, SQL exports, certificates, and everything into a single folder and zips it for you. If you back those zips up, you'll have most everything.
Restoring directly back into SQL isn't the recommended method, if you did need to get back up you'd want to follow standard restore procedures by using the supported PowerShell, but you'll have other avenues to restore if needed and a more complete copy
of your data.
The LIS export may be complete if you don't have any Lync locations defined. You'd typically enter these for 911 purposes.
Check out Lasse's Channel 9 video as well:
http://channel9.msdn.com/Events/TechEd/Europe/2014/OFC-B331
Check out his backup series docs here as well:
http://tech.rundtomrundt.com/search/label/Backup-Lync2013
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 mobility and external access not working

Hi all.
I installed and configured Lync Server 2013 Front End and Lync Server 2013 Edge on Windows Server 2012 R2.
Internal lync clients (not mobile) can successfully connect to server and everything works fine for them. External users can connect only with manual configuration of address of external lync server in lync client, autodiscovery doesn't work.
I also installed and configured IIS ARR Reverse Proxy on Windows Server 2012 R2 using this article -
http://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.aspx. But it doesn't work too. When I try to connect I get 'Unable to connect to the server. Check your network connection or the server address and
try again'.
I configured dns records in the external dns zone.
For Edge:
sip.extdomain.ru – IP1
lyncwebconf.extdomain.ru – IP2
lyncav.extdomain.ru – IP3
For Reverse Proxy:
lyncdialin.extdomain.ru - IP4
lyncmeet.extdomain.ru - IP4
lyncextweb.extdomain.ru - IP4
lyncdiscover.extdomain.ru - IP4
I issued all needed certificates by the internal CA and added following alternative names.
For FE certificate:
sip.cherry.loc
lync.cherry.loc
dialin.cherry.loc
meet.cherry.loc
admin.cherry.loc
lyncdiscoverinternal.cherry.loc
lyncdiscover.cherry.loc
lyncdialin.extdomain.ru
lyncmeet.extdomain.ru
lyncextweb.extdomain.ru
lyncdiscover.extdomain.ru
For Edge external and Reverse Proxy:
lyncav.extdomain.ru
sip.extdomain.ru
lyncwebconf.extdomain.ru
lyncdialin.extdomain.ru
lyncmeet.extdomain.ru
lyncextweb.extdomain.ru
lyncdiscover.extdomain.ru
cherry.loc
The root certificate of internal CA installed on all servers and client devices.
Using Wireshark I see that Reverse Proxy communicating with FE on port 4443.
Here is an excerpt from mobile client log.
GET https://lyncdiscover.extdomain.ru/?sipuri=sip:[email protected]
Request Id: 0x6f54648
HttpHeader:Cache-Control no-cache
HttpHeader:Content-Length 1006
HttpHeader:Content-Type application/vnd.microsoft.rtc.autodiscover+xml; v=1
HttpHeader:Date Mon, 22 Sep 2014 11:17:45 GMT
HttpHeader:Expires -1
HttpHeader:Pragma no-cache
HttpHeader:Server Microsoft-IIS/8.5
HttpHeader:StatusCode 200
HttpHeader:X-AspNet-Version 4.0.30319
HttpHeader:X-Content-Type-Options nosniff
HttpHeader:X-MS-Server-Fqdn lync.cherry.loc
HttpHeader:X-Powered-By ASP.NET, ARR/2.5
Ôªø<?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance" AccessLocation="External"><Root><Link token="Domain" href="https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/domain?originalDomain=extdomain.ru" /><Link token="User" href="https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru"
/><Link token="Self" href="https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root?originalDomain=extdomain.ru" /><Link token="OAuth"
href="https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/oauth/user?originalDomain=extdomain.ru" /><Link token="External/XFrame" href="https://lync.cherry.loc/Autodiscover/XFrame/XFrame.html" /><Link
token="Internal/XFrame" href="https://lync.cherry.loc/Autodiscover/XFrame/XFrame.html"
/><Link token="XFrame" href="https://lync.cherry.loc/Autodiscover/XFrame/XFrame.html" /></Root></AutodiscoverResponse>
</ReceivedResponse>
2014-09-22 15:17:53.041 Lync[299:715a000] INFO TRANSPORT CUcwaAutoDiscoveryResponse.cpp/119:location value is external
2014-09-22 15:17:53.042 Lync[299:715a000] INFO TRANSPORT CUcwaAutoDiscoveryResponse.cpp/195:User url is
https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru
2014-09-22 15:17:53.042 Lync[299:715a000] INFO TRANSPORT CHttpRequestProcessor.cpp/266:Sending event to main thread for request(0x6f54648)
2014-09-22 15:17:53.042 Lync[299:3c2a218c] INFO APPLICATION CTransportRequestRetrialQueue.cpp/822:Req. completed, Stopping timer.
2014-09-22 15:17:53.043 Lync[299:3c2a218c] INFO APPLICATION CUcwaAutoDiscoveryGetUserUrlOperation.cpp/290:Received a root response
2014-09-22 15:17:53.043 Lync[299:3c2a218c] INFO APPLICATION CUcwaAutoDiscoveryGetUserUrlOperation.cpp/224:UcwaAutoDiscoveryGetUserUrlOperation completed with
url = https://lyncdiscover.extdomain.ru/?sipuri=sip:[email protected], userUrl = https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru, status = S_OK (S0-0-0)
2014-09-22 15:17:53.043 Lync[299:3c2a218c] INFO APPLICATION CTransportRequestRetrialQueue.cpp/725:Response received for req. GET-UnAuthenticatedGet(0x6f54648): S_OK (S0-0-0) (Success); Done with req.; Stopping resend timer
2014-09-22 15:17:53.044 Lync[299:3c2a218c] INFO TRANSPORT CCredentialManager.cpp/176:getSpecificCredential for serviceId(1) returning: credType (1) signInName ([email protected]) domain (cherry) username (user) password.empty() (0) certificate.isValid() (0)
privateKey.empty() (1) compatibleServiceIds(1)
2014-09-22 15:17:53.044 Lync[299:3c2a218c] INFO TRANSPORT CMetaDataManager.cpp/403:Received a request to get the meta data of type 0 for url
https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru
2014-09-22 15:17:53.044 Lync[299:3c2a218c] INFO TRANSPORT CMetaDataManager.cpp/458:Sending Unauthenticated get to get the web-ticket url
2014-09-22 15:17:53.044 Lync[299:3c2a218c] INFO TRANSPORT CTransportThread.cpp/135:Added Request() to Request Processor queue
2014-09-22 15:17:53.045 Lync[299:3c2a218c] INFO TRANSPORT CAuthenticationResolver.cpp/109:Waiting on Meta Data from https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru
2014-09-22 15:17:53.045 Lync[299:659a000] INFO TRANSPORT CTransportThread.cpp/347:Sent Request() to Request Processor
2014-09-22 15:17:53.045 Lync[299:3c2a218c] INFO APPLICATION CTransportRequestRetrialQueue.cpp/385:Submitting new req. GET-AuthenticatedUserGetRequest(0x6e83da8)
2014-09-22 15:17:53.045 Lync[299:659a000] WARNING TRANSPORT CCredentialManager.cpp/317:CCredentialManager::getSpecificCredential returning NULL credential
for serviceId (4) type (1)!
2014-09-22 15:17:53.046 Lync[299:3c2a218c] INFO APPLICATION CUcwaAutoDiscoveryService.cpp/1263:Submitting Authenticated AutoDiscovery request to
https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru
2014-09-22 15:17:53.046 Lync[299:659a000] INFO TRANSPORT TransportUtilityFunctions.cpp/689:<SentRequest>
GET https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru
Request Id: 0x133b6a8
HttpHeader:Accept
</SentRequest>
2014-09-22 15:17:53.046 Lync[299:659a000] INFO UTILITIES CHttpStreamPool.cpp/399:Allocating stream 0x6e73850 for url - https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user with persistent id as 16
2014-09-22 15:17:53.047 Lync[299:659a000] VERBOSE TRANSPORT CHttpProxyHelper.cpp/435:CHttpProxyHelper::discoverProxy : No proxy found for url
https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru. Sending over direct connection.
2014-09-22 15:17:53.050 Lync[299:659a000] ERROR TRANSPORT CHttpConnection.cpp/1029:Request Type = 0x%u0x6e743a0 Error domain = kCFErrorDomainCFNetwork code = 0x2 ErrorDescription = The operation couldn‚Äôt be completed. (kCFErrorDomainCFNetwork error 2.) ErrorFailureReason
= ErrorRecoverySuggestion =
2014-09-22 15:17:53.050 Lync[299:659a000] ERROR UTILITIES CHttpConnection.cpp/958:GetAddrInfo returned error 0x8
2014-09-22 15:17:53.050 Lync[299:659a000] INFO UTILITIES CHttpStreamPool.cpp/467:Releasing stream 0x6e73850.
2014-09-22 15:17:53.050 Lync[299:659a000] INFO UTILITIES CHttpStreamPool.cpp/599:Releasing stream 0x6e73850.
2014-09-22 15:17:53.051 Lync[299:659a000] INFO TRANSPORT CHttpRequestProcessor.cpp/173:Received response of request() with status = 0x22020001
2014-09-22 15:17:53.051 Lync[299:659a000] INFO TRANSPORT CHttpRequestProcessor.cpp/201:Request resulted in E_ConnectionError (E2-2-1). The retry counter is: 0
2014-09-22 15:17:53.051 Lync[299:659a000] WARNING TRANSPORT CCredentialManager.cpp/317:CCredentialManager::getSpecificCredential returning NULL credential
for serviceId (4) type (1)!
2014-09-22 15:17:53.052 Lync[299:659a000] INFO TRANSPORT TransportUtilityFunctions.cpp/689:<SentRequest>
GET https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru
Request Id: 0x133b6a8
HttpHeader:Accept
</SentRequest>
2014-09-22 15:17:53.052 Lync[299:659a000] INFO UTILITIES CHttpStreamPool.cpp/399:Allocating stream 0x14102a0 for url - https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user with persistent id as 16
2014-09-22 15:17:53.053 Lync[299:659a000] VERBOSE TRANSPORT CHttpProxyHelper.cpp/435:CHttpProxyHelper::discoverProxy : No proxy found for url
https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru. Sending over direct connection.
2014-09-22 15:17:53.056 Lync[299:659a000] ERROR TRANSPORT CHttpConnection.cpp/1029:Request Type = 0x%u0x14080f0 Error domain = kCFErrorDomainCFNetwork code =
0x2 ErrorDescription = The operation couldn‚Äôt be completed. (kCFErrorDomainCFNetwork error 2.) ErrorFailureReason = ErrorRecoverySuggestion =
2014-09-22 15:17:53.056 Lync[299:659a000] ERROR UTILITIES CHttpConnection.cpp/958:GetAddrInfo returned error 0x8
2014-09-22 15:17:53.056 Lync[299:659a000] INFO UTILITIES CHttpStreamPool.cpp/467:Releasing stream 0x14102a0.
2014-09-22 15:17:53.056 Lync[299:659a000] INFO UTILITIES CHttpStreamPool.cpp/599:Releasing stream 0x14102a0.
2014-09-22 15:17:53.057 Lync[299:659a000] INFO TRANSPORT CHttpRequestProcessor.cpp/173:Received response of request() with status = 0x22020001
2014-09-22 15:17:53.057 Lync[299:659a000] INFO TRANSPORT CHttpRequestProcessor.cpp/201:Request resulted in E_ConnectionError (E2-2-1). The retry counter is: 1
2014-09-22 15:17:53.057 Lync[299:659a000] INFO TRANSPORT CHttpRequestProcessor.cpp/266:Sending event to main thread for request(0x133b6a8)
2014-09-22 15:17:53.058 Lync[299:3c2a218c] INFO TRANSPORT CMetaDataManager.cpp/572:Received response for meta data request of type 60 with status 570556417
2014-09-22 15:17:53.058 Lync[299:3c2a218c] ERROR TRANSPORT CMetaDataManager.cpp/588:Unable to get a response to an unauthenticated get to url
https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru
2014-09-22 15:17:53.059 Lync[299:3c2a218c] INFO TRANSPORT CAuthenticationResolver.cpp/208:MetaData retrieval for url https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru completed with status 570556417
2014-09-22 15:17:53.059 Lync[299:3c2a218c] INFO TRANSPORT CAuthenticationResolver.cpp/238:Deleting 1 pended Meta data requests for url
https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru
2014-09-22 15:17:53.059 Lync[299:3c2a218c] ERROR TRANSPORT CAuthenticationResolver.cpp/334:Unable to get the meta data for server url
https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=extdomain.ru
2014-09-22 15:17:53.059 Lync[299:3c2a218c] INFO TRANSPORT CAuthenticationResolver.cpp/337:Failing request to the request manager
2014-09-22 15:17:53.060 Lync[299:3c2a218c] INFO TRANSPORT CRequestManager.cpp/284:Failing secure request UcwaAutoDiscoveryRequest with status E_ConnectionError (E2-2-1)
2014-09-22 15:17:53.060 Lync[299:3c2a218c] INFO APPLICATION CTransportRequestRetrialQueue.cpp/822:Req. completed, Stopping timer.
2014-09-22 15:17:53.060 Lync[299:3c2a218c] INFO APPLICATION CUcwaAutoDiscoveryService.cpp/1358:Received autodiscovery response with status E_ConnectionError (E2-2-1)
2014-09-22 15:17:53.060 Lync[299:3c2a218c] INFO APPLICATION CUcwaAutoDiscoveryService.cpp/1316:Raising Autodiscovery event with status E_ConnectionError (E2-2-1) for eventType 0
2014-09-22 15:17:53.061 Lync[299:3c2a218c] INFO APPLICATION CUcwaAutoDiscoveryServiceRetrialWrapper.cpp/417:Received event for type 0 with status E_ConnectionError (E2-2-1)
2014-09-22 15:17:53.061 Lync[299:3c2a218c] INFO APPLICATION CUcwaAutoDiscoveryServiceRetrialWrapper.cpp/539:Autodiscovery scheduled retrial timer. Timer 0.000000 seconds
2014-09-22 15:17:53.061 Lync[299:3c2a218c] INFO APPLICATION CAlertReporter.cpp/64:Alert received! Category 1, Type 201, level 0, error E_ConnectionError (E2-2-1), context '', hasAction=false
2014-09-22 15:17:53.061 Lync[299:3c2a218c] INFO APPLICATION CAlertReporter.cpp/117:Alert cleared of Category 1, Type 201, cleared 0 alerts
2014-09-22 15:17:53.062 Lync[299:3c2a218c] INFO APPLICATION CTransportRequestRetrialQueue.cpp/725:Response received for req. GET-AuthenticatedUserGetRequest (0x6e83da8): E_ConnectionError (E2-2-1) (RemoteNetworkTemporaryError); Done with req.; Stopping resend
timer
2014-09-22 15:17:53.062 Lync[299:3c2a218c] INFO UI CMAlertViewController.mm/87:ObservableListItem Added event received
2014-09-22 15:17:53.062 Lync[299:3c2a218c] INFO UI CMAlertViewController.mm/97:showalert is 1
2014-09-22 15:17:53.063 Lync[299:3c2a218c] INFO UI CMConversationCommon.mm/43:not signed in
2014-09-22 15:17:53.063 Lync[299:3c2a218c] INFO UI CMConversationCommon.mm/43:not signed in
2014-09-22 15:17:53.063 Lync[299:3c2a218c] INFO UI CMConversationCommon.mm/43:not signed in
2014-09-22 15:17:53.063 Lync[299:3c2a218c] INFO UI CMConversationCommon.mm/43:not signed in
2014-09-22 15:17:53.063 Lync[299:3c2a218c] INFO UI CMConversationCommon.mm/43:not signed in
2014-09-22 15:17:53.064 Lync[299:3c2a218c] INFO UI CMNotificationManager.mm/697:desired view is alert, size 1
2014-09-22 15:17:53.064 Lync[299:3c2a218c] INFO UI CMNotificationManager.mm/737:adding the desired view
2014-09-22 15:17:53.065 Lync[299:3c2a218c] INFO UI CMNotificationManager.mm/472:reposition floating views
2014-09-22 15:17:53.065 Lync[299:3c2a218c] INFO UI CMAlertViewController.mm/104:showalert is 1
2014-09-22 15:17:53.065 Lync[299:3c2a218c] INFO UI CMAlertViewController.mm/108:showalert is 0
2014-09-22 15:17:53.066 Lync[299:3c2a218c] INFO UI CMUIUtil.mm/410:Mapping error code = 0x22020001, context = , type = 201
2014-09-22 15:17:53.066 Lync[299:3c2a218c] INFO UI CMUIUtil.mm/1708:Mapped error message is 'Unable to connect to the server. Check your network connection or the server address and try again.

Result of Lync Connectivity Analyzer.
External Auto discover service : https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root
Starting Lync server autodiscovery
Please wait; this test may take several minutes to complete...
Starting automatic discovery for secure (HTTPS) internal channel
lyncdiscoverinternal.extdomain.ru can't be resolved by the DNS server. Skipping internal discovery.
Starting automatic discovery for secure (HTTPS) external channel
Server discovery has completed for https://lyncdiscover.extdomain.ru/.
Automatic discovery results for https://lyncdiscover.extdomain.ru/
Access Location : Internal
SIP Server Internal Access : lync.cherry.loc
SIP Server External Access : sip.extdomain.ru
SIP Client Internal Access : lync.cherry.loc
SIP Client External Access : sip.extdomain.ru
Internal Auth broker service : https://lync.cherry.loc/Reach/sip.svc
External Auth broker service : https://lync.cherry.loc/Reach/sip.svc
Internal Auto discover service : https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root
External Auto discover service : https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root
Internal MCX service : https://lync.cherry.loc/Mcx/McxService.svc
External MCX service : https://lync.cherry.loc/Mcx/McxService.svc
Internal UCWA service : https://lync.cherry.loc/ucwa/v1/applications
External UCWA service : https://lync.cherry.loc/ucwa/v1/applications
Internal Webscheduler service : https://lync.cherry.loc/Scheduler
External Webscheduler service : https://lync.cherry.loc/Scheduler
Total server discovery time: 5,0 seconds
Server discovery succeeded for secure (HTTPS) external channel against URL https://lyncdiscover.extdomain.ru/
Starting automatic discovery for unsecure (HTTP) external channel
Couldn't connect to URL http://lyncdiscover.extdomain.ru/[email protected] (HTTP status code NotAcceptable)
Server discovery failed for unsecured external channel against http://lyncdiscover.extdomain.ru/
Starting the requirement tests for Lync Mobile 2013 App
Please wait; this test may take several minutes to complete...
Testing the app requirements using the following discovery response:
Access Location : Internal
SIP Server Internal Access : lync.cherry.loc
SIP Server External Access : sip.extdomain.ru
SIP Client Internal Access : lync.cherry.loc
SIP Client External Access : sip.extdomain.ru
Internal Auth broker service : https://lync.cherry.loc/Reach/sip.svc
External Auth broker service : https://lync.cherry.loc/Reach/sip.svc
Internal Auto discover service : https://lync.cherry.loc/Autodiscover/AutodiscoverService.svc/root
Internal MCX service : https://lync.cherry.loc/Mcx/McxService.svc
External MCX service : https://lync.cherry.loc/Mcx/McxService.svc
Internal UCWA service : https://lync.cherry.loc/ucwa/v1/applications
External UCWA service : https://lync.cherry.loc/ucwa/v1/applications
Internal Webscheduler service : https://lync.cherry.loc/Scheduler
External Webscheduler service : https://lync.cherry.loc/Scheduler
Starting tests for Mobility (UCWA) service
Verifying internal Ucwa service: https://lync.cherry.loc/ucwa/v1/applications
Successfully created the UCWA service
Completed tests for Mobility (UCWA) service
Verification failed for Mobility (UCWA) service. The service could not be reached from an external network.
Select All results above for more information about the failures. Detailed information can also be found in the log file.
Your deployment meets the minimum requirements for Lync Mobile 2013 App.

Migration to Lync 2013 - Unable to remove 2010 Edge Server

Hi
We did a migration from Lync 2010 to Lync 2013. Everything worked without any problems. But now we are unable to remove the Lync 2010 Edge Pool. Everything has been done according to
https://technet.microsoft.com/en-us/library/jj205369.aspx “Migration from Lync Server 2010 to Lync Server 2013”.
I am able to remove the 2010 Edge pool, but by trying to publish the topology, I receive the following error: “Error: An error occurred: "System.InvalidOperationException" "Cannot publish topology changes. Call orbit still
exists on one or more deleted application servers."
How can I resolve this error?
Regards
Peter

Hi Peter,
You have to change the Call Park Destination FQDN to the Lync 2013 Pool.
Please check out the following article.
Migrate Call Park application settings
Best regards,
Eric
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Lync 2013 not working externally

Hi,
Recently I have installed Lync 2013 in my organization and everything is working fine internally but when I tried from outside nothing is working. Please assist me in order to sort out this issue as I'm facing
this issue since last so many days and I tried so many things from my end but it didn't work.
Below is configuration on my edge.
Internal Interface--
192.215.x.x
Mask: 255.255.255.0
External Interface:
Public IP: 62.215.x.x
Mask: 255.255.255.x
Default: x.x.x.x
DNS: x.x.x.x
I have created the edge pool by using a option
use a single FQDN & IP Address, I'm using singe host name for access edge service, web conferencing & A/V edge server i.e. Pool1.domain.com.
Below is external setting for edge pool
Access Edge Service
FQDN: pool1.xyz.com
IP Address: 62.215.x.x
Port: 5061
Protocol: TLS
Web Conferencing edge service
FQDN: pool1.xyz.com
IP Address: 62.215.x.x
Port: 444
Protocol: TLS
AV Edge Service
FQDN: pool1.xyz.com
IP Address: 62.215.x.x
Port: 443
Protocol: TLS
I'm using same External IP for all three services.
Please let me know if I did anything wrong and assist me to resolve this issue as early as possible.
Regards,
Hakim. B
Hakim.B Sr.System Administrator

Hi,
Thanks for update,
I have enable the windows event logging and getting below error when I checked with manual setting in lync client 2013.
The description for Event ID 4 from source Lync cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Lync
pool1.domain .com
Below error when I checked with Automatic setting in lync 2013 client.
The description for Event ID 3 from source Lync cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Lync
sipexternal.kcs.com.kw
Regards,
Hakim. B
Hakim.B Sr.System Administrator

IISARR URLS for Lync 2013 not working externally

Hello All,
Currently facing issue of opening lyncdiscover.domain.com from external.
I have created the server farm uing IISARR for Lync2013 & added 5 rules under the server farm as shown below:
meet.domain.com
dialin.domain.com
lyncdiscover.domain.com
owebapp.domain.com
When I tried browse all the above URL's none of the URLs are opening & showing below errors as attached screen shot:
Also when I tried test by using Lync 2013 Connectivity Analyzer showing below errors
SIP Uri: [email protected]
Logging test parameters:
User Name:
Discovery Type: Automatic Discovery
Network access: NetworkAccessInternal
Selected client: ApplicationLMX
Starting Lync server autodiscovery
Please wait; this test may take several minutes to complete...
Starting automatic discovery for secure (HTTPS) internal channel
lyncdiscoverinternal.domain.com can't be resolved by the DNS server. Skipping internal discovery.
For more information on DNS requirements for automatic discovery, please refer to http://go.microsoft.com/fwlink/?LinkId=278998
Starting automatic discovery for secure (HTTPS) external channel
Sending HTTP request to https://lyncdiscover.domain.com/[email protected]
Cookie found in autodiscover response: StatusCode: 500, ReasonPhrase: 'URL Rewrite Module Error.', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
Cache-Control: private
Date: Mon, 08 Sep 2014 11:51:26 GMT
Server: Microsoft-IIS/8.5
Content-Length: 5694
Content-Type: text/html; charset=utf-8
Autodiscover: SendRequest(): the URL https://lyncdiscover.domain.com/[email protected] couldn't be connected. Complete HTTP headers:\r\n Cache-Control: private
Date: Mon, 08 Sep 2014 11:51:26 GMT
Server: Microsoft-IIS/8.5
Couldn't connect to URL https://lyncdiscover.domain.com/[email protected]
Reason: Internal server error (HTTP status code 500)
System.Exception: Exception of type 'System.Exception' was thrown.
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.TerminateAD(String mesg)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for secured external channel against https://lyncdiscover.domain.com/
Starting automatic discovery for unsecure (HTTP) external channel
Sending HTTP request to http://lyncdiscover.domain.com/[email protected]
Cookie found in autodiscover response: StatusCode: 500, ReasonPhrase: 'URL Rewrite Module Error.', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
Cache-Control: private
Date: Mon, 08 Sep 2014 11:51:44 GMT
Server: Microsoft-IIS/8.5
Content-Length: 5765
Content-Type: text/html; charset=utf-8
Autodiscover: SendRequest(): the URL http://lyncdiscover.domain.com/[email protected] couldn't be connected. Complete HTTP headers:\r\n Cache-Control: private
Date: Mon, 08 Sep 2014 11:51:44 GMT
Server: Microsoft-IIS/8.5
Couldn't connect to URL http://lyncdiscover.domain.com/[email protected]
Reason: Internal server error (HTTP status code 500)
System.Exception: Exception of type 'System.Exception' was thrown.
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.TerminateAD(String mesg)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for unsecured external channel against http://lyncdiscover.domain.com/
None, AutoInternalDNSFail, AutoInternalSecureD, AutoInternalUnsecureD, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST,
MobilityMCXInternalLMXCheckGET, MobilityMCXInternalLMXCheckPOST, MobilityMCXExternalLMXCheckGET, MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
Automatic discovery of the Lync server failed. Please verify the server requirements at http://go.microsoft.com/fwlink/?LinkId=278998
Microsoft Lync Connectivity Analyzer cannot analyze deployment readiness until a discovery test has completed successfully.
=============================================================================
NOTE : For my current Set Up for Lync 2013 please refer this link & kindly ignore the SQL archiving & monitoring issue for database mismatch version as it is resolved:
http://social.technet.microsoft.com/Forums/lync/en-US/032a8ef2-636d-40ae-a4f1-951e9a39999f/lync-2013-archiving-and-monitoring-sql-database-version-mismatch-issues?forum=lyncdeploy
Any help really appreciated
Regards
Anand S
Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

Hi,
Please make sure there is no typos in the URL rewrite rule.
You can configure IIS ARR to display more information with the error with the following path:
Open IIS Manager –> Sites –> Default Web Site –> Error Pages –> Edit Feature Settings.
Select Detailed error
Then you can access simple URL again to check the full error message.
More details:
http://unifiedme.co.uk/2014/04/iis-arr-500-internal-server-error-get-meaning-full-info/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 standard deployment: Exchange 2010 Sharepoint 2010 and outlook 2007 collaboration

HI
I have Exchange 2010 and sharepoint 2010 with all our user using outlook 2007. what options do I have for collaborations between these systems if I was to install Lync 2013. I have seen posts that mention that you cannot use outlook 2007 and lync 2013 and
that you would be better off installing the lync 2010 client?
1. would we be covered from a licensing point of view if we had bought lync 2013 cals but install the lync 2010 software on desktops?
2. what Cals do we require for presence to be available in SharePoint we currently have standard sharepoint cals?
3. what new features will we loose if we install 2010 lync software.
4. if our mobile users use the 2013 lync software will these be able to communicate with the 2010 users?
thanks
J

Hi,
If you use Lync 2013 client with Outlook, multiple functions will not be achieved, such as: customize Outlook meeting invitations (add logo, help URL, disclaimer, footer text), in Outlook, configure meeting option to mute attendee audio and video by default,
presence status in the Microsoft Outlook To and Cc fields, and so on. As Lync 2013 is the part of Office 2013, the best choice is using Outlook 2013.
More details:
https://technet.microsoft.com/en-us/library/gg412817.aspx
For the CAL requirement, you can refer to following link:
Lync Licensing Guide
You can refer to the link below of “What’s new for clients in Lync Server 2013” to understand the new features for Lync 2013:
https://technet.microsoft.com/en-us/library/jj204933.aspx
If you use Lync 2013 mobile clients, you can communicate with 2010 users with no possible.
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Lync A/V not working via Edge except for Federation

I have an interesting problem.
Internal users can do audio/video/screen sharing just fine from the internal network.
I can do A/V and screen sharing with my federated contacts just fine from my internal network.
When I use Lync on an external network (from home, public wifi, or even 4G), I can see presence, IM back and forth with no issues, but I can not do Audio/Video or screen sharing. I can do the whiteboard/Q&A/etc. It connects the call but I don't see or
hear the other internal participant, and then it disconnects after exactly 10 seconds.
The 2013 Lync Mobile app has the same issue - I can IM, but cant use audio or video.
Does anyone know where I should start? I currently have a mixed topology with Lync 2010 and 2013 front-end servers, and a Single consolidated 2010 Edge server, with 3 external IP's addresses NAT'd to 3 public addresses. I remember that this used to work,
but since it is not a heavily used feature, I don't know when it stopped working. It may have stopped when I installed the 2013 FE servers but i'm not positive.

You can verify my earlier statement by looking at your ICE candidate list when your AV fails...
Look in snooper at the log, and search for 'candidate'... you should see a list of at least 6 entries similar to this:
a=candidate:1 1 UDP 2140706431 192.168.1.101 39052 typ host
a=candidate:1 2 UDP 2140705918 192.168.1.101 39053 typ host
a=candidate:2 1 TCP-PASS 6656159 x.x.x.x 56276 typ relay raddr 192.168.1.101 rport 39041
a=candidate:2 2 TCP-PASS 6656158 x.x.x.x 56276 typ relay raddr 192.168.1.101 rport 39041
a=candidate:3 1 UDP 16648713 x.x.x.x 55824 typ relay raddr 192.168.1.101 rport 39050
a=candidate:3 2 UDP 16648712 x.x.x.x 52421 typ relay raddr 192.168.1.101 rport 39051
a=candidate:4 1 TCP-ACT 7086863 x.x.x.x 56276 typ relay raddr 192.168.1.101 rport 39041
a=candidate:4 2 TCP-ACT 7086350 x.x.x.x 56276 typ relay raddr 192.168.1.101 rport 39041
a=candidate:5 1 TCP-ACT 1664797951 y.y.y.y 39041 typ srflx raddr 192.168.1.101 rport 39041
a=candidate:5 2 TCP-ACT 1664797438 y.y.y.y 39041 typ srflx raddr 192.168.1.101 rport 39041
missing typ relay or typ srflx raddr means you're not successfully talking to your edge, and getting ports allocated, which is my suspicion. The best troubleshooting step from there is a network capture to verify whether you are getting responses
to your TURN requests. I can't comment on the connectivity test website, as I haven't used it, but I have spent a lot of time troubleshooting edge issues in multiple environments...
Jon McClary
Using the lync logging tool, which components should I log to get this output?

Lync 2013 Standard, publishing externally via edge/TMG

Similar Messages

Maybe you are looking for