Lync 2013 Test Server Deployment

Hi All,
I have been asked to look at using Lync 2013 in our organisation.
As this is a test deployment to start with, I have the following restrictions:
Access to only 1 public IP Address
Mobility is a requirment
No budget for Reverse Proxy
I have been looking at various ways to test this, but have been unable to successfully get this working. I have started again, with a blank canvis. I am now at the stage where I need to install Lync 2013 on our test domain and am not sure where to go.
I have read about external DNS (A Record for sip.domain.co.uk to point to public IP & SVR Record for _sipfederationtls._tcp.domain.co.uk points to sip.domain.co.uk on port 5061).
Could anyone give me any pointers?
Thanks in advance

Hi Daymondeo,
As thamaraw said, the Reverse Proxy is required for functioning mobility.
With one public IP, you have to deploy TMG . Using TMG as a reverse proxy, then you can have all the Lync features.
Have a look at this article,
http://social.technet.microsoft.com/wiki/contents/articles/9807.how-to-configure-forefront-tmg-2010-as-reverse-proxy-for-lync-server-2010.aspx
Best regards,
Eric

Similar Messages

Lync 2013 Edge Server Deployment

We have already deployed 5 Frontend Server (1 Standard Server and 1 Pool with 4 FE Servers) and one Edge Server some Days ago. Now we are trying to Setup another Lync 2013 Edge Server and get stucked.
When we try to Import the Configuration File, which we had exported from a Frontend Server (export-Csconfiguration..) we get the following error:
Cannot open database "xds" requested by the loging
We can publish the topology on the Frontend Server without Errors.
We have already deinstalled all the lync and SQL componentes and tried again - no success
Best regards
Bueschu
Bueschu

On reviewing the error and confirming the backup service was started, in order to resolve the issue the following actions were performed.
1. In the Lync Topology Builder remove the front end resiliency settings that were previously applied and publish the topology.
2. Connect to each front end server that comprises the pool pairing and run step two of the deployment wizard, by performing this the replicator and backup services will be removed and essentially the pairing will be broken.
3. In the topology Builder re-apply the resiliency settings and publish the topology in order to recreate the pairing.
4. Connect to each front end server that comprises the pool pairing and run step two of the deployment wizard, by performing this the replicator and backup services will be added again. Once the deployment wizard is completed, ensure the
backup services are started on each front end and ensure the Invoke-CSBackupServiceSync PowerShell commands are run as per the "What to do next" information.
5. In the Lync Server Mangement Shell run the "Get-CsBackupServiceStatus -PoolFqdn yourpool.domain.local" and ensure the services is operating in a normal state for both front end servers.
That's it, the deployment wizard and associated xds database access error should now be cleared.
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"

Single LYNC 2013 Edge Server Deployment

Hi,
I intend to deploy single site edge deployment for two physical lync sites.
So the scenario would be…
Redmond LYNC Pool-----Redmond & its remote sites LYNC users connect to it
Portland LYNC Pool-------Portland & its remote sites LYNC users connect to it
But the Edge Server deployment is only at Redmond site, so any internet lync users(Redmond or Portland) will hit the Redmond Edge and then will be serviced out of either Redmond pool or Portland pool.
If this is workable scenario ???
If so, then I need to understand the network consideration for this specific type of deployment and where/how exactly the redirection will happen to ensure Portland users access lync services from their specific pool and Redmond users access from theirs.
Regards, Pushkal MishrA, This posting is provided “AS IS” with no warranties and confers no rights. I request you to test the solution in lab and post successful outcome you should try this on production.

Hi,
It is possible to use single Edge Server for both Pools.
You can use a single SRV record. The user from the other site has to connect to the only edge and then route though the WAN link to go to its own pool. Access Edge is responsible for proxying SIP traffic for remote clients to the next hop, which
can be a Director or a Lync pool. For details:
http://blogs.technet.com/b/nexthop/archive/2012/05/15/lync-server-2010-geographically-dispersed-edge-topology-part-1.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 edge server deployment manger

Hi,
I am getting error while importing the local configuration file on edge server.
Error returned while installing ocscore.msi(feature_localmgmtstore), code 1603
failed to create network share (---- -xds-replica)
failed to drop network share (--- -xds-replica)
I am able to telnet from CMS server to Edge server over port 4443.

Hi PawanDeepSingh,
Is there any update ?
In my opinion, the issue might be caused by one of the followings.
1. Permissions issue. Please make sure that you logged in as a local administrator.
2.
Windows service issue. During the installation process, some system services might be used.
(e.g. Task Scheduler Service)
http://blogs.technet.com/b/ariel/archive/2014/09/09/1603-error-when-installing-lync-server-2013-standard-edition-or-enterprise-front-end-server.aspx
If the issue is hard to troubleshoot, I suggest reinstall the operation system and then retry.
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 Edge Server Issues

Forgive me if this question sounds rather "entry level", I have never worked with Lync and this project was handed to me by my boss, who hasn't worked with Lync either.
I have been reading various posts and forum messages until I went cross eyed about setting up Lync 2013 Edge server correctly. I am still running into some questions and issues with the Access, Web, and A/V services starting. Here is my main
question, and below is my setup.
Question:
Is there a need for both an external and internal nic card IF all three external IP's for the external services are programmed at the firewall and router to go directly to 1 internal IP address?
Setup:
Currently I have 1 FE-Standard server that also acts as the Mediation Server, and 1 Edge Server both of which are virtual and running Server 2012. Originally I did have 2 network cards setup, as all other documentation suggested, 1 external and 1 internal.
However my boss, who setup the DNS/Firewall entries stated to remove the External Card since the external address that was setup for the 3 services was routed to 1 internal address. The Access Services, Web Services, and A/V services are all running on three
separate ports with their own unique FQDN- 443, 444, and 445. The cert that was deployed is a wild card cert from GoDaddy, this has been used by other servers that point inside and outside without issues.
Issues and Errors Messages:
I have run into a few different issues and error messages from the Event Viewer:
System
Provider
[ Name]
LS Protocol Stack
EventID
14352
[ Qualifiers]
50153
Level
2
Task
1001
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2013-09-09T15:44:51.000000000Z
EventRecordID
2885
Channel
Lync Server
Computer
edgesvr01
Security
EventData
0xC3E93C0A
SIP_E_STACK_TRANSPORT_FAILED
System
Provider
[ Name]
LS Server
EventID
12303
[ Qualifiers]
50152
Level
2
Task
1000
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2013-09-09T15:44:51.000000000Z
EventRecordID
2884
Channel
Lync Server
Computer
edgesvr01
Security
EventData
80072741
The requested address is not valid in its context.
System
Provider
[ Name]
LS Protocol Stack
EventID
14336
[ Qualifiers]
50153
Level
2
Task
1001
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2013-09-09T15:44:51.000000000Z
EventRecordID
2883
Channel
Lync Server
Computer
edgesvr01
Security
EventData
TLS
external IP address that is now used now
5061
Please help, I am at a loss as to where to go from here.

Thanks for the quick responses.
I have re-enabled the external NIC. All services are running now. When I ran the Remote Connectivity tester this was the outcome.
Testing remote connectivity for user: username@domain... to the Microsoft Lync server.
Specified remote connectivity test(s) to Microsoft Lync server failed. See details below for specific failure reasons.
Test Steps
Attempting to resolve the host name lync.metisconnect.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: xxx.xxx.xxx.xxx (external address)
Testing TCP port 443 on host: host fqdn to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server host fqdn on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=*.ourdomain.com, OU=Domain Control Validated, Issuer: SERIALNUMBER=######, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona,
C=US.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
The host name that was found, lync.metisconnect.com, is a wildcard certificate match for common name *.ourdomain.com.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=*.ourdomain.com, OU=Domain Control Validated.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 7/31/2013 4:02:03 PM, NotAfter = 7/31/2014 4:02:03 PM
Testing remote connectivity for user username@domain to the Microsoft Lync server.
Specified remote connectivity test(s) to Microsoft Lync server failed. See details below for specific failure reasons.
Tell me more about this issue and how to resolve it
Additional Details
Couldn't sign in. Error: Error Message: Operation failed because the network connection was not available..
Error Type: ConnectionFailureException.
External calls from a 3g/4g data connection are not connecting when using the Lync call feature to an internal users Lync Client. Outcome is: Connecting Call and No Audio. Then call ends.

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 Edge Server Migration

Hi,
Our organisation is in the process of changing gateway providers, so we have to move our currently deployed Lync 2013 Edge Server and TMG (Lync related sites) to the new provider datacentre. We have new public and DMZ IP addresses allocated for these services
and we can't use the current addresses.
Has someone been through this and is there a best practice to follow to transition these services with minimal outages to the users?
Any help would be appreciated.

the steps that you mentioned would work. I need to add some bits in to it,
1. Take a copy of the current Edge Server (VM) and place into the new datacentre
2. changed the IP addressing (of services) for the Edge Pool in the Topology builder and publish/sync
3. Change the IP address of the edge server and run the deployment wizard with "Add remove Lync server component step"
3. Start services
4. Publish the Lync services on the new TMG reverse proxy
5. Test connectivity
http://thamaraw.com

Lync 2013 edge server request certificates

I am deploying Lync 2013 edge server, how to get the certificate request file[certificate
signing request (CSR)] on setp 3: Reques,install or Assign Certficates.
i need your help!
Thanks!

Agree with Jason.
On the Certificate Request File page, type the full path and file name to which the request is to be saved.
After you get Certificate Request File, you need to submit this file to your CA (by email or other method supported by your organization for your enterprise CA) and, when you receive the response file, copy the new certificate to this computer so that it
is available for import.
Check how to set up certificates for the internal edge interface at
http://technet.microsoft.com/en-us/library/gg412750.aspx.
Check how to set up certificates for the external edge interface
http://technet.microsoft.com/en-us/library/gg398409.aspx.
Lisa Zheng
TechNet Community Support

Do we need License for Lync 2013 Edge server?

Hello Team,
We are currently running Lync 2013 Standard Edition Server. We are planning to enable users for External access and planning to deploly Lync 2013 edge server.
1. Do we need License for Lync 2013 Edge server?
2. Any other client licenses needed?
Please advise.

Hi,
No you don't required any additional License in order to install Lync Edge server. the only license required at OS level i mean windows server licence in terms of Lync concern you don't require any additional License
check this
https://products.office.com/en-us/lync/microsoft-lync-licensing-overview-lync-for-multiple-users
http://lyncuc.blogspot.in/2013/02/lync-2013-licensing-guide-how-to.html
And for client also you don't require any additional license with your existing client license will work for externally as well
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

OU For Lync 2013 Central Forest deployment when using GAL Sync

Hello,
We are attempting to set up Lync 2013 in a Central Forest configuration. We have a 2 way forest trust in place. The primary forest being A.com, the secondary forest being B.com. Exchange 2010 is deployed in both forests. Lync 2013 is deployed in forest A.com.
We currently have FIM 2010 installed, using GAL Sync between both forests. For GAL Sync, we have an OU in Forest A.com active directory called GALSync. There are currently contacts in that OU that correspond with the user accounts in forest b.com. Here's
my question:
When configuring FIM MA's for Lync 2013 Central Forest deployment, can I point the LCSCFG.xml file to the SAME GALSync OU we use for GAL Sync? Will it see the contacts already exist and just update with the necessary attributes needed to provision
the forest B.com users for Lync? Do I need to create a separate OU for the Lync MA to use? Or, am I going about this in the wrong way?
Any help you can provide will be greatly appreciated.
Thank you

Thanks for the reply Anthony
Almost right. The only difference is that the remote users will get the autodiscover url and the ews url from their local domain and dns.
Here is how it is setup:
Shared public namespace
mycompany.com (email address and sip address use this in both domains)
Central Forest (mycompany.com)
Lync 2013
Exchange 2013
Autodiscover url
autosdiscover.mycompany.com/autodiscover/autodiscover.xml
192.168.10.10
EWS Url
https://mail.mycompany.com/EWS/Exchange.asmx
192.168.10.11
Remote Forest (Fabrikam.com)
Lync 2010
Exchange 2010
Autodiscover url
autosdiscover.mycompany/autodiscover/autodiscover.xml
192.168.11.23
EWS Url
https://mail.mycompany.com/EWS/Exchange.asmx
192.168.11.24
User in Fabrikam login locally with their Fabrikam credentials. They have a Lync enabled contact in mycompany. There is a 2 way trust in place. They login to mycompany Lync fine.
When they do the autodiscover DNS lookup, they return the same autodiscover and EWS url, but they point to the local Exchange 2010 since their mailbox and user account still resides there and that is the system that the Fabrikam account has access to.
Autodiscover works fine for Outlook.
I will take a look at Fiddler

Lync 2013 Edge Server

I have a few questions on setting up a Lync 2013 Edge Server. Let me give a little background into what is going on. My comapny currently still has the old Communicator server(1 user left to migrate to Lync!) and a Lync 2013 that is all setup
and functional. Our current Lync environment is only internal, since we do not have a Edge Server setup. That is what I am task to work on now. I have read alot of guides on how to build this server, where it needs to be placed in the DMZ,
and what is needed for it.
First question - Is there a hardware spec needed for this server?
Second question - I read that 3 public ip are needed. What are they needed for? So I can explain to our network guys why I need this.
Third question - Does it matter if the Edge server is on the domain or not? I read it shouldnt be. I dont think it will be an issue either way for me, but its easier to manage if on the domain.
Fourth question - Should I finish my Communicator server decom before worrying about the Edge server?
Final question - is there a guide on how to get rid of the Communicator Server Connections to our Lync Server?
Thanks in advance.

First question - Is there a hardware spec needed for this server?
Second question - I read that 3 public ip are needed. What are they needed for? So I can explain to our network guys why I need this.
Third question - Does it matter if the Edge server is on the domain or not? I read it shouldnt be. I dont think it will be an issue either way for me, but its easier to manage if on the domain.
Fourth question - Should I finish my Communicator server decom before worrying about the Edge server?
Final question - is there a guide on how to get rid of the Communicator Server Connections to our Lync Server?
First question- HW spec https://technet.microsoft.com/en-us/library/gg398835.aspx
For your reference, my edge servers happen to have 40 GB ram and 2x'E5-2690 2.9GHz' ... they don't have to be physical ... can be virtual however.
Second - 3 IP's are recommended ... it makes it easier because you can use standard ports as opposed to straying from 443 etc. ... and it makes troubleshooting easier. All three of the edge services include a 443 requirement - and, with SSL you can't
just share that socket on a single IP - so, lucky service gets 443. Also, you can segregate the traffic and see exactly what is happening. If you only had 1 IP - many scenarios in Lync would not work (e.g., I'm at a hotel and yoru AV port is not
allowed through the firewall).
Here is a wonderful reference - https://blogs.perficient.com/microsoft/2012/12/lync-scaled-consolidated-edge-public-ip-addresses/
Third - it is recommened that it is NOT domain joined - however, it's ok that it is. Mine IS domain joined because I have a domain in my DMZ and it assists with management (etc.) and may be required for yoru security. Your call. IMO, if
you have a domain , join it. Why not?
RE: OCS - there is a migration path from OCS 2007 R2 to Lync 2013 as per https://technet.microsoft.com/en-us/library/gg425764.aspx and several documents on the Internet that show the process for those who need to do so. It's not trivial.
Another interesting link: http://blogs.technet.com/b/saleesh_nv/archive/2014/04/24/lync-2013-tri-co-existance.aspx

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 Edge server compatibility with Lyn 2010 Front end Pool

Hi All,
Technet article (http://technet.microsoft.com/en-us/library/jj688121.aspx) says the following:
If your legacy Lync Server 2010 Edge Server is configured to use the same FQDN for the Access Edge service, Web Conferencing Edge service, and the A/V Edge service, the procedures in this section are not supported. If the
legacy Edge services are configured to use the same FQDN, you must first migrate all your users from Lync Server 2010 to Lync Server 2013, then decommission the Lync Server 2010 Edge Server before enabling federation on the Lync Server 2013 Edge Server.
Can you tell me why it is you have to change the External Lync Web services URL during a migration to Lync 2013 from Lync 2010. What purpose does this serve?
Also can you clarify this and explain why this is required, why would you have to migrate all of your users, would a Lync 2013 Edge not talk to a Lync 2010 front-end?
Any help would be much appreciated. MANY THANKS.

Thank you very much for all your inputs.
We still have few questions:
Questions:
Can you tell me if Lync 2010 users will be able to login using mobility if we repoint the reverse proxy (TMG) web services publishing rule to the Lync 2013 server? Remember both systems Lync 2010 and 2013 are using the same web
services URL so they will both end up at the Lync 2013 server. Alternatively if not we will migrate all users to 2013, this is not a problem
In addition to this I cannot find anything that states how Exchange UM will operate when you are running from a backup pool and the exchange UM contacts are not available because they are homed on the server that is down. This
configuration is 2 x standard edition servers pool paired. How can we make sure Exchange voice mail works during a pool failover?
Call Park is not clear to me I read the following:
Lync Server 2013 provides new disaster recovery mechanisms in the form of failover and failback processes. These failover and failback processes support recovery of Call Park functionality by allowing
users who are homed in the primary pool to leverage the Call Park application of the backup pool when an outage occurs in the primary pool. Support for disaster recovery of the Call Park application is enabled as part of the configuration and deployment of
paired Front End pools.
Is this saying we need to deploy Call Park in the DR pool and use a different range of orbit numbers, or can we use the same range in the DR pool?
Further, I can see that Common Area Phones will be fine as they will log into the DR pool automatically. Response Groups need to be exported and imported to the DR pool. Incidentally these did not migrate well at all and have
caused us a big headache!
Any inputs will be greatly appreciated. Thanks again for all of your time.

Lync 2013 - EWS not deployed external

Greetings!
Is there a way how to track the reason why Lync2013 client connecting over EDGE has status of EWS not deployed?
Lync 2013 Standard FE
Lync 2013 Edge
TMG
Exchange 2010
Have followed this instructions:
http://www.b4z.co.uk/lync-2013-ews-with-forefront-tmg-2010-issues.html/comment-page-1
On the TMG rules: Outlook web access, Outlook anywhere, I have deleted /autodiscover/* and /ews/* path and created a new rule,
which is connecting to a public addresses: autodiscover.company.com and owa.company.com, and on firewall rule under authentication tab selected: No delegation but client may authenticate directly.
Created also a new listener which has: No authenticaton.
PROBLEMS:
Before doing that we had a problem that Lync2013 client connecting outside LAN got a pop-up credentials and no matter what you have typed, it didn't accept it.
Now credentials pop-up is not appearing anymore, but the status of EWS is not deployed.
And we are also having another problem because we had deleted EWS and AUTODISCOVER on Outlook Web access firewall rule and on Outlook anywhere, now Outlook clients
connecting outside LAN without VPN are unable to get OOF working.
Any hints?
bostjanc

Hi Lisa!
Thank you for your reply.
Output of the command: Get-AutodiscoverVirtualDirectory -Server FQDN | fl name,InternalURL,ExternalURL
Name : Autodiscover (Default Web Site)
InternalUrl :
https://owa2010.company.com/autodiscover/autodiscover.xml
ExternalUrl :
https://owa2010.company.com/autodiscover/autodiscover.xml
Domain username is: [email protected]
SIP address is: [email protected]
Output of the command Get-WebServicesVirtualDirectory -Server FQDN | fl name,InternalURL,ExternalURL
Name : EWS (Default Web Site)
InternalUrl : https://owa2010.company.com/EWS/exchange.asmx
ExternalUrl : https://owa2010.company.com/EWS/exchange.asmx
A record for autodiscover.company.com is created in EXTERNAL DNS and is pointing to a newly created Firewall rule on TMG, which has /autodiscover/* and /ews/* paths,
no authentication (it passes the authentication to Exchange 2010).
There is no SRV record in External DNS if that is important?
Lync2010 client connecting external is also having EWS shown as not deployed.
QUESTION:
QUESTION1:
I have a question regarding your statement: "Make sure you have configured the CAS Server Certificates including all SAN Names for all SMTP and SIP domains."
On TMG side I have two rules for LYNC and I want to clarify something about the certificates.
1 rule is for MEET NOW links and MOBILITY. This rule has /* path, no authentication and it leads to lyncFE ip address. This rule is for Lync reverse proxy which is
visible on external DNS as lyncproxy2010.company.com. Rule is using certificate with this SAN names:
DNS Name=lyncproxy2010.company.com
DNS Name=meet.company.com
DNS Name=lyncdiscover.company.com
DNS Name=autodiscover.company.com
DNS Name=dialin.domain.local
2nd rule on TMG is newly created Firewall rule
for solving EWS problem for Lync 2013. It has /autodiscover/* and /ews/* paths,no authentication (it passes the authentication to Exchange 2010).
This rule is pointing to public address: autodiscover.company.com and to public address owa2010.company.com. Rule is using the sam certificate as we use it in other firewall rules for Outlook web access, Outlook anywhere and ActiveSync. Certificate has this
SAN names:
DNS Name=owa2010.company.com
DNS Name=exchange.company.local
DNS Name=exchange.company.com
DNS Name=exchange
DNS Name=autodiscover.company.local
DNS Name=autodiscover.company.com
Ok, my newly rule does not have lyncproxy2010.company.com should it have? It also does
not have lyncdiscover.company.com should it have?
QUESTION2:
Is EWS internal/external url
case sensitive?
QUESTION3:
With creating a newly rule for LYNC where ews and autodiscover are not authenticated on TMG side I have also removed path's /EWS/* and /AUTODISCOVER/* on rules for Outlook anywhere on TMG. Now we have problem that free/busy status ain't working
external in Outlook clients.
Soo, fixing pop-up credentials for Lync 2013 is partly solved, because credential window ain't appearing anymore, but EWS is still shown as not deployed, on the other side we have "created" another problem with OOF Outlook external. Any hints?
with best regards,
bostjanc

Lync 2013 Monitoring Server - Database reporting

Hi there,
Im a business intelligence professional rather than a Lync professional so excuse me if my question may show niavete or a clear lack of experience, both would probably be correct.
The basic question is, how does Lync record the relationship between a call being received and the call that is transferred.
Effectively I am looking to see how the monitoring server applies a unique record to a call. This looks like the SessionIdTime field. I also deduce that the 'ReplacesDialogueId' field is used to record when a call effectively replaces another one, and I
have formed a self join on the SessionDetailsView to track a calls progress.
Im struggling though when this relationship is not there. So for example, when a call comes in and is answered by a receptionist, we have the initial call entering the queue, with the call being answered by Reception having a replacedialogId that replaces
the call coming into the queue. Lets say that the receptionist then calls a director to see if they are available, and then transfers the call. There is a relationship between the call being made to the director, and the caller speaking to the director with
the dialogId and replacedialogid fields, though there is no relationship between the receptionist taking the call, and the receptionist calling the director and putting the call through.
Again, please forgive my noobie questions. In summary, how does Lync record the relationship between a call being received and a transferred call.

They are sparse, many of us have written custom reports but I forget what I've done as soon as I've done it. The Lync 2013 CDR Database Schema is available here:
http://technet.microsoft.com/en-us/library/gg398570.aspx
Typically what I do is just dig in and make test case calls, export the query results to something easy to work with like Excel and reverse engineer what I need for my reports. Watch the CorrelationID and anything else you can line up.
I'm not aware of any great guides that walk you though this unfortunately.
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 Test Server Deployment

Similar Messages

Maybe you are looking for