Hey
I like to get understand one thing. Lync KHI Excel is stating the followings :
Performance counter: \LS:Usrv - DBStore\Usrv - Queue Latency (msec)
Description: The average time a request is held in the request queue to RTCDyn database
Performance counter: \LS:Usrv - REGDBStore\Usrv - Queue Latency (msec)
Description: The average time a request is held in the request queue to RTC database
Performance counter: \LS:Usrv - SharedDBStore\Usrv - Queue Latency (msec)
Description: The average time a request is held in the request queue to RTCShared database

But e.g. the Lync virtualization whitepaper stating about the counter: \LS:Usrv - DBStore\Usrv - Queue Latency (msec):
Queue latency is the amount of time (in milliseconds) that it takes for a request to leave the Front End Server’s queue toward the back-end database.

So what are the actual differences between DBStore, REGDBStore and SharedDBStore. And what they are measuring?

We all know the RTCDyn is on the Front End, RTC is on the Front End and RTCShared is on the Back End.

To which information I can trust?

Petri

Hello All..............How are HA and DR achieved of following components of the Lync 2013

1.  Edge

     My understanding so far is that for HA you would have one-1 external record for each of the services with each record pointing to a minimum oftwo-2 nodes in the Edge Pool such as:

Record                      Node                 Priority

accessedge1             Node1 of Pool     10

accessedge1             Node2 of Pool      20

webconferencing1     Node1 of Pool      10

webconferencing1     Node2 of Pool       20

audiovideo1              Node1 of Pool       10

audiovideo1              Node2 of Pool        20

This way if either server is down we would get HA at the Primary Site.  For DR, what could be required? could this work:

Record                      Node                 Priority

accessedge2             Node1 of Pool     10

accessedge2             Node2 of Pool      20

webconferencing2     Node1 of Pool      10

webconferencing2     Node2 of Pool       20

audiovideo2              Node1 of Pool       10

audiovideo2              Node2 of Pool        20

2.  Reverse Proxy

I am aware of how HA can be managed, but not sure how DR is managed for Reverse Proxy.

Thanks in advance.

Hello All........When migrating from 2010 to 2013, what is migrated by default once you introduce 2013 Pool into 2010 and what is to be migrated:

Kindly, Add the comment in front of each item such as Required/Manual, By Default, Not Required, etc.

Users

               User Search

Topology

               Status

               Server Application

               Simple URL

               Trusted Application

IM and Presence

               File Filter

               URL Filter

Voice Routing

               Dial Plan

               Voice Policy

               Route

               PSTN Usage

               Trunk Configuration

               Test Voice Routing

Voice Features

               Call Park

               Unassigned Numer

Response Group

               Workflow

               Queue

               Group

Conferencing

               Conferencing Policy

               Meeting Configuration

               Dial-in Access Number

               PIN Policy

Clients

               Client Version Policy

               Client Version Configuration

               Device Update

               Test Device

               Device Log Configuration

               Device Configuration

External User Access

               External Access Policy

               Access Edge Configuration

               Federated Domins

               Provider

Monitoring and Archiving

               Call Detail Recording

               Quality of Experience Data

               Archiving Policy

               Archiving Configuration

Security

               Registrar

               Web Service

               PIN Policy

Network Configuration

               Global

               Location Policy

               Policy Profile

               Region

               Site

               Subnet

               Region Link

               Region Route

Hello All...........If architecture of the Lync 2013 Organization is based on Primary Site and DR Site then how would following be handled:

1.  CMS - Would it be just placed on Primary Site or Active Copy on Primary Site and Passive Copy on DR Site? Any pointers?

2.  Backup Service - is it automatically configured when we make pool pair?

Hello All.............If following situation is true:

Primary Site:

Lync 2010 FE Pool (Pointing to Lync 2010 Edge Pool, still holds CMS)

Lync 2010 DR Pool (Pointing to Lync 2010 DR Edge Pool)

Lync 2010 Edge Pool

Lync 2010 DR Edge Pool

Lync 2010 FE Pool and DR Pool are paired

Lync 2013 FE Pool introduced (Pointing to Lync 2013 Edge Pool)

Lync 2013 Edge Pool Introduced

Users moved from 2010 to 2013 Pool and tested (Half of them)

Can it be said that Edge has been cut over to 2013 Edge Pool?

DR Site:

Lync 2013 DR FE Pool Introduced (Pointing to Lync 2013 DR Edge Pool)

Lync 2013 DR Edge Pool Introduced

Then:

1.  Would it be okay to test pool pairing in this scenario? What would be required? Just configure pair and use cmdlet to test failover and failback?

2.  Would I be needing to point Edge or Proxy at the Primary Site to the DR Site?

Hi Experts,

One of our customer has the below query:

We understand that dual homing is no longer supported by SfB, however we have been unable to locate any written documentation specifically stating this – are you able to point me in the right direction?

We have a specific situation where I have a Lync Server 2013 enterprise edition deployment that has Front End servers with collocated mediation role and dual homed NICs (one for internal network and one for the SBC/PSTN network).  Does this mean that in-place upgrade is unsupported in this scenario?

If so, what are our options for upgrading to SfB?  Would dual-homing of standalone Mediation servers be supported as an alternative?  We have a requirement to dual home in this way because customers bring their own IP address ranges for internal addressing, so we must have an alternative addressing scheme in place on the PSTN leg to prevent overlapping customer IP addresses on our SBCs.

Any advise would be much appreciated.

Error: An error occurred: "Microsoft.Rtc.Management.ADConnect.ADOperationException" "Active Directory operation failed on "veedeeoskypelab.veedeeoforest.com". You cannot retry this operation: "Access is denied 
00000005: SecErr: DSID-03152612, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

Im trying publish skype for bussiness topology, why i can fix this error.??

Thanks

Hello,

I migrated from lync 2010 to lync 2013 ,I moved all users and endpoints to lync 2013

I did all the below  steps,and showed 0 entries
bit still unable to publish topoply due to the existence  of users,contacts,..
Is there any tool which shows what r the users contacts they still in the pool

Ghassan

Hello,

I am trying to setup integration between Microsoft Lync 2013 Server and Exchange 2013 Server so that in OWA you can see presence information and also use Instant Messaging.

I am able to complete all the steps except for the following line on the Lync server:

New-CsPartnerApplication -Identity Exchange -ApplicationTrustLevel Full -MetadataUrl "https://autodiscover.domain.com/autodiscover/metadata/json/1"

I am getting an error that its not found:

New-CsPartnerApplication : Cannot bind parameter 'MetadataUrl' to the target. Exception setting "MetadataUrl": "The
metadata document could not be downloaded from the URL in the MetadataUrl parameter or downloaded data is not a valid
metadata document, error: The remote server returned an error: (404) Not Found."

Now I've already followed THIS thread: http://blogs.technet.com/b/jenstr/archive/2012/11/22/getting-internal-server-error-500-when-creating-new-cspartnerapplication-for-exchange-2013.aspx  But that did not help me at all.  Nor should it because that particular thread is a procedure to remedy an error 500.  Remember I am getting an error 404.

I can validate that the path to /autodiscover/metadata/json/1 does not exist because I get a 404 in any web browser that I attempt to access this path.  Also in IIS Manager on Exchange I do not even see a metadata folder.  IIS has been reset and also the server has been rebooted as of 7:40 AM EST today and the issue persists.

I am not sure what goes in that location but I would be willing to accept if someone else would upload their metadata/json/1 file on SkyDrive and I could put it at this location.

Otherwise Autodiscover service appears to be working as Outlook and Lync clients do not pose an error.  Testing e-mail autodiscover returns correct values and the paths /autodiscover/Autodiscover.svc and also autodiscover/autodiscover.xml are both reachable in a web browser.

I've removed a user from Skype for Business, yet this user is still searchable from the Skype For Business Client, displayed with an 'unknown' presence.   This user's account needs to remain active in Active Directory, and searchable within Exchange 2013,  which is what is complicating this issue, I suspect.    We've recently upgraded from Lync Server 2013, and I don't see an equivalent to the ABSConfig.exe utility,  which can be used to modify user attributes.   I also do not see the msRTCSIP-GroupingID attribute, which would allow segregation of the user into a new Skype for Business Address book (essentially hiding them),  for any user object in AD.   

I've removed the account using the Skype for Business control panel,  updated the address book on the Skype for Business server,  and also removed the local SIP profile from my client.   Unfortunately, the user account remains searchable.

any assistance welcomed.

Hi,

In our AD domain the group CSUserAdministrator is a member of the default group Account Operators.

This causes some issues since Account Operators is a 'protected group' and the users I add to CSUserAdministrator will be protected.

It was a long time since Lync was installed and I am not sure if CSUserAdministrator gets added to Account Operators during the Lync installation or if this is a change that was made by hand later on.

Could anyone help me check if it is Lync that placed CSUserAdministrator in Account Operators?

If that is the case I guess it have to be there for a reason.

Would it then make sense to create a new Admin Role based on CSUserAdministrator and add my users to that role instead?

Regards Erik

Our mobile clients that were previously working fine are no longer able to sign in to Lync 2013 with "Can't connect to the server messages"

Relevant factors I think are:

- This issue seems to have come up immediately after the latest round of windows updates

- Another symptom is a lot of Webhost errors on the front end server which also appeared just after updates

Any help with diagnosing this error would be greatly appreciated!!

regards,

Rob.

I'm at a bit of a loss here on what to do with my Branch Sites. AND I'm really hoping this isn't a "dumb" question.

I have 12 remote sites with PSTN Gateways. I've got User Dialplans, Voice Policies and routes etc. configured for all these locations.

Now I want to migrate the sites to Lync 2013.

Simple steps were advised from MS PFE:

1. Move users to CMS
2. Remove SBS from 2010 Branch Site Topology
3. Remove components from Server
4. Add SBS to 2013 Branch Site Topology
5. Install 2013 components
6. Move users back

Sounded simple enough - so no further discussion was had.

Only it's a lot more complicated than that.

I can't find anything out there that documents this at all.

When you "delete" a SBS from a site - if the gateway is associated it won't let you. If you remove the gateway and then delete the SBS - you get errors on the gateway being associated to all the routes.

Do I have to remove everything in Control Panel for these sites and start over when I install the 2013 components? I'm really hoping I don't have to do this. I wanted this to be as seamless as I could get it. I feel like I'm missing something.

Anyone have any advice?

Sandra

helo guys,

 I have an environment. There is 2 pool On DC is Lync 2013 and DRC is skype for bussines 2015,

and it has back end server on DC nor DRC

as details: DC have 3 front end Lync 2013 and DRC have 3 front end Skype for bussiness

Can it test failover ? 

I was read some of blog, it just same of an environment to the test failover DC and DRC is like Lync 2013 or skype for bussines 2015 are both.

pls, I need advice and give me some articel to reference 

Some of the users are experiencing their conversation history saved in a different mail account on their Outlook.

We are on Lync 2013 CU3 and Exchange 2013 CU3.

These users have Lync 2013 client and have their Exchange 2013 email account configured on Outlook 2013.

They also have other exchange accounts configured on their Outlook 2013 which is configured on other users Outlook as well in the team. 

When one of the user has a conversation with any user , his conversation is saved to this another account which is visible to all.

This issue is observed only with some users in the environment.

Please suggest if someone has faced similar issue.

Good Morning,

Our SCOM Administrator recently installed the Management packs for Lync Server 2013.  When he did this we received multiple warning messages and a couple of critical messages in SCOM.

I have been working through them, but having issue finding good information. More or less just trying to understand the alerts and  if they are relavant to functionality or can be overridden in SCOM

LS Acccess Edge Component

1. Connection attempt to at least one service in a pool failed.

Connection attempts to the following services have failed. Another attempt will be made for each service every 10 minutes.
Service Address: 23.253.178.224:5061; Pool FQDN: sip.rackspace.com; Down Time: 7:44
Service Address: 23.253.178.227:5061; Pool FQDN: sip.rackspace.com; Down Time: 7:15

Cause: The specified service(s) are unavailable.
Resolution:
Check the servers in the pool(s) on which the service(s) are installed.

2. TLS outgoing connection failures.

Over the past 3 minutes, Lync Server has experienced TLS outgoing connection failures 31 time(s). The error code of the last failure is 0x80092010(CRYPT_E_REVOKED) while trying to connect to the server "sip.domain.com" at address [148.159.162.184:5061], and the display name in the peer certificate is "Unavailable".
Cause: Most often a problem with the peer certificate or perhaps the host name (DNS) record used to reach the peer server. Target principal name is incorrect means that the peer certificate does not contain the name that the local server used to connect. Certificate root not trusted error means that the peer certificate was issued by a remote CA that is not trusted by the local machine.
Resolution:
Check that the address and port matches the FQDN used to connect, and that the peer certificate contains this FQDN somewhere in its subject or SAN fields. If the FQDN refers to a DNS load balanced pool then check that all addresses returned by DNS refer to a server in the same pool. For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the local machine.

3. The following discovered partners are sending frequent invalid SIP requests to the Access Edge Server.

Traffic from these partners is restricted to 1 message per second as a security measure.
Certificate Subject: "US, Michigan, Grand Rapids, "BDO USA, LLP", sip.bdo.com"; Issuer: "BE, GlobalSign nv-sa, GlobalSign Organization Validation CA - G2"; Serial Number: 1121939BFCDED892C02B4E0F3E281A570806; Common Failures: OTHER(430)=1 OTHER(4xx)=1

Cause: Federated partners that were discovered through DNS SRV are sending frequent SIP requests that cause an error response from the local Lync Server deployment.
Resolution:
It is recommended that connections from these partners be blocked at the firewall.
***NOTE - Think our Senior Lync engineer is working on this one...we have an open Federation

LS Mediation Server Component

1. There was no response from a Trunk to an OPTIONS request sent by the Mediation Server.

The Trunk, 10.16.210.1;trunk=10.16.210.1, is not responding to an OPTIONS request sent by the Mediation Server service.
DNS Resolution Failure: False
Exception: Microsoft.Rtc.Signaling.ConnectionFailureException:Unable to establish a connection. ---> System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

--- End of inner exception stack trace ---
at Microsoft.Rtc.Signaling.SipAsyncResult2`1.ThrowIfFailed()
at Microsoft.Rtc.Signaling.SipAsyncResultBase2.EndAsyncOperation[TResult](Object owner, IAsyncResult result)
at Microsoft.RTC.MediationServerCore.PeriodicOptionsSender.FinishSendOptionMessage(IAsyncResult ar)
Detected at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at Microsoft.Rtc.Signaling.RealTimeException..ctor(String message, Exception innerException)
at Microsoft.Rtc.Signaling.ExceptionUtilities.TryMapS4Exception(Exception s4Exception, SecurityAssociationContext securityContext, Boolean isSipEndpoint, String traceId, Object parentObject, Object childObject, RealTimeException& ex)
at Microsoft.Rtc.Signaling.SipTransactionAsyncResult`1.ConnectionConnectCompleted(IAsyncResult result)
at Microsoft.Rtc.Signaling.SipAsyncResult2`1.MakeCallback()
at Microsoft.Rtc.Signaling.SipAsyncResult2`1.Complete(TEx ex, Boolean synchronousCompletion)
at Microsoft.Rtc.Signaling.RealTimeConnection.CompletePendingConnects(IEnumerable`1 results, RealTimeException exception)
at Microsoft.Rtc.Signaling.RealTimeConnection.<.ctor>b__1(SipConnection sender, Object reason)
at Microsoft.Rtc.Internal.Sip.SipConnection.FireDisconnectedEvent(Object reason)
at Microsoft.Rtc.Internal.Sip.SingleThreadedDispatcherQueue.DispatcherCallback(Object queue)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Cause: The Mediation Server service cannot communicate with the Trunk Service over SIP due to network connectivity issues.
Resolution:
Please ensure network connectivity and availability of the Trunk for the Mediation Server service to be able to function correctly.

2. The Mediation Server service has received a call that does not support comfort noise. This event is throttled after 5 calls from a single Trunk peer.

The Mediation Server service has received a call that does not support comfort noise from the Trunk, 10.16.210.1;trunk=10.16.210.1
Cause: The Trunk does not support comfort noise.
Resolution:
Please ensure the comfort noise option on the Trunk has been enabled.

I appreciate and feedback and apologize in advance since this is alot of information.

Thank You

Hi,

I just saw that my Skype for Business server is not able to insert any data into QoE database.

I see the following in event log: (This log appeared right after upgrading to Skype4B)

Failed to insert QoE to back-end due to unexpected error.

Component: QoE Adaptor 
Error: System.IO.InvalidDataException: Invalid input. MediaLine is null.
   at Microsoft.Rtc.Server.UdcAdapters.QoE.PackReport.Pack(VQReportEventType report, LyncMessageDetails msgDetails, DBQoEReport dbReport)
   at Microsoft.Rtc.Server.UdcAdapters.QoE.QoEProcessor.ProcessQoEReport(ContentChunk content, LyncMessageDetails msgDetails)
   at Microsoft.Rtc.Server.UdcAdapters.QoE.QoEProcessor.ChooseMessageProcessor(LyncMessageDetails msgDetails)
   at Microsoft.Rtc.Server.UdcAdapters.QoE.QoEProcessor.ProcessQueueItems(LyssQueueItem queueItem)
Cause: an unexpected condition has resulted in the error.
Resolution:
Verify the back-end is up and this Skype for Business Server has connectivity to it. If the problem persists, notify your organization's support team with the relevant details.

Any idea what would be causing this?

Also, does anyone know which service is responsible for insertion of data into QoE databases? perhaps a restart of that service might work.

Update: The error has been appearing in Lync event logs for 6 days, only today the server actually failed to update the database. 

After a reboot of the front end, it is able to insert the records again, but I still see the errors popping up. I guess it will be a matter of time before it actually fails to insert the records.

Hi

I've just updated our Lync FE server to V5.0.8308.872   and in the management console set the EnableSkypeUI to $true.

The client still launches as Lync 2013 and does not signal to change to Skype for Business, if I amend manually in the registry is then still asks to swap back to Lync interface?

Any ideas?