Lync Server 2013

  1. Authentication failed during an attempt to connect to server. Authentication failure during an attempt to connect to server ...
  2. Authentication of incoming MTLS connection from Web Conferencing Server failed. Serial number of cert provided by Web Conferencing ...
  3. Authentication parameter is required. Supported values are "LiveId", "Negotiate" and "TrustedServer". E.g. Authentication=TrustedServer ...
  4. Authorization cannot be delayed because Allow or Deny has been called, or the method is not being called from the event handler. ...
  5. Autodiscover failed to find a users hosting provider User Uri: %1 Hosting Provider Fqdn: %2 Cause: Possible configuration ...
  6. Autodiscover failed to lookup user information. User Uri: %1 Cause: Possible configuration problem. Resolution: Please look ...
  7. Autodiscover failed to retrieve OAuth configuration for OAuth request. Cause: Possible configuration problem. Resolution: ...
  8. Automatic import of flushed file into Storage Service encountered file error. Automatic import of flushed data encountered ...
  9. Automatic import of flushed file into Storage Service encountered file error. The following automatic flushed data import ...
  10. Automatic Problem Reports Upload to Microsoft is currently disabled for this phone. To enable this setting, press Enable. ...
  11. Automatic Problem Reports Upload to Microsoft is currently disabled for this phone. To enable this setting, press OK. For ...
  12. Automatic Problem Reports Upload to Microsoft is currently disabled for this phone. To enable this setting, tap Enable. For ...
  13. Automatic Problem Reports Upload to Microsoft is currently enabled for this phone. To disable this setting, press Disable. ...
  14. Automatic Problem Reports Upload to Microsoft is currently enabled for this phone. To disable this setting, press OK. For ...
  15. Automatic Problem Reports Upload to Microsoft is currently enabled for this phone. To disable this setting, tap Disable. ...
  16. Average background noise level for audio received from the gateway. High values can be caused by configuration or setup issues ...
  17. Average background noise level of audio sent. High values can be caused by capture device, capture device setup issues, or ...
  18. Average bandwidth allocated for video. Low values can indicate low picture quality or low frame rate and can be caused by ...
  19. Average difference between the OverallAvgNetworkMOS and the maximum possible OverallAvgNetworkMOS for the codec used. High ...
  20. Average duration in milliseconds of periods of high packet loss. High values can be caused by congestion, exceeding available ...
  21. Average duration in milliseconds of periods of low packet loss. Low values can be caused by congestion, exceeding available ...
  22. Average estimation of the available bandwidth between the endpoints. Low values can be caused by congestion or access bandwidth ...
  23. Average gain applied to audio received from the gateway. High values indicate significant level adjustments were required, ...
  24. Average jitter in the arrival time between RTP packets. High jitter values can be caused by congestion or an overloaded media ...
  25. Average jitter in the arrival time between RTP packets. High jitter values can be caused by congestion or an overloaded media ...
  26. Average level of echo sent to the other endpoint. High values can be caused by capture/render device, capture/render device ...
  27. Average listening quality mean opinion score (MOS) of the audio received based on the packet loss, jitter, and codec used. ...
  28. Average listening quality mean opinion score (MOS) of the audio received based on the speech level, noise level, and glitches ...
  29. Average listening quality mean opinion score (MOS) of the audio sent based on the speech level, noise level, device characteristics, ...
  30. Average number of capture timestamp glitches per 5 min. High values here can be caused due to high CPU usage or device/driver ...
  31. Average number of render timestamp glitches per 5 min. High values here can be caused due to high CPU usage or device/driver ...
  32. Average rate of net video frames lost due to network quality. High values indicate frozen or choppy video and can be caused ...
  33. Average rate of video frames lost due to network quality. High values indicate frozen or choppy video and can be caused by ...
  34. Average ratio of capture device sampling rate deviation to nominal sampling rate. High value here can be caused due to mismatch ...
  35. Average ratio of compressed audio samples to the total number of samples. High values indicate significant levels of sample ...
  36. Average ratio of concealed audio samples to the total number of samples. High values indicate significant levels of loss ...
  37. Average ratio of render device sampling rate deviation to nominal sampling rate. High value here can be caused due to mismatch ...
  38. Average ratio of stretched audio samples to the total number of samples. High values indicate significant levels sample stretching ...
  39. Average received speech level for audio received from the gateway. Low values can be caused by configuration or setup issues ...
  40. Average RTP packet loss rate during periods of high packet loss. High values can be caused by congestion, exceeding available ...
  41. Average RTP packet loss rate for video packets. High values indicate frozen or choppy video and can be caused by network ...
  42. Average RTP packet loss rate. High loss values can be caused by congestion, exceeding available bandwidth, wireless congestion/interference, ...
  43. Average RTP round-trip time between the endpoints. High round-trip time values can be caused by international call routing, ...
  44. Average speech level of audio sent. Low values can be caused by capture device, capture device setup issues, or environmental ...
  45. Average video bit rate. Low values may indicate low picture quality or low frame rate and can be caused by insufficient bandwidth ...
  46. Average video frame rate. Low values indicate choppy or jerky video and can be caused by high network packet loss, low lighting, ...
  47. Back-end Database: %1 Connection string of: %2 Cause: Database marked as offline. Resolution: Mark the database as online ...
  48. Backend state does not match expected state. Backend {0} is passed as backup SQL Server, but the state of this server is ...
  49. Backup module "{0}" current exported batch details: NumOfChanges={1}, NumOfExportedChanges={2}, NumOfChangesFromTheOtherPool={3}, ...
  50. Backup module "{0}" detailed status: ImportStatus={1}, ExportStatus={2}, HasChangesFromTheOtherPool={3}, HasChangesSince={4}. ...
  51. Backup module "{0}" pre-fetched exported batch details: NumOfChanges={1}, NumOfExportedChanges={2}, NumOfChangesFromTheOtherPool={3}, ...
  52. Backup service on computer "{0}" is active. Its overall export operation status is "{1}" and overall import operation status ...
  53. Backup task is currently assigned to this Front End. Backup task assignment stays on this Front End as long as Microsoft ...
  54. Backup task is no longer assigned to this Front End. Backup task assignment is no longer assigned to this Front End. This ...
  55. Bandwidth limit applied to this stream in bits/second. Low values can cause poor quality if it forces a low quality codec ...
  56. Based on the capacity calculations for your topology, we recommend deploying Collocated Mediation Servers on the Front End ...
  57. Based on the features you want enabled on this site, we recommend that you use a DNS load balancer. Do you still want to ...
  58. Because both RemoveExportedConfiguration and Force are specified, this operation will remove all response groups and associated ...
  59. Because Force is selected and the initial failover attempt failed, database failover will be forced for database "{0}". CAUTION: ...
  60. Because of an internal error, Topology Builder cannot create the Central Management store. Please save your work and try ...
  61. Because the external IP address of this Edge pool is translated by NAT, please specify the public IP address that is used ...
  62. Because this is a scaled edge deployment, the same certificate must be assigned to all Edge Servers in this pool. You need ...
  63. Because you are disabling privacy mode, we recommend that you also disable client version check in order to allow communications ...
  64. Because you are enabling privacy mode, we recommend that you also enable client version check in order to block communications ...
  65. Because you used the Force option, the user's contact list will not be exported from Exchange before roll back. As a result, ...
  66. Before using the -Force parameter, ensure that you have exported the conference directory data using DBImpExp.exe and imported ...
  67. Before you can share your screen, you must uninstall the {0} plug-in. When you begin sharing, you will be prompted to reinstall ...
  68. Before you can use this phone, you will be guided through a short setup process. Do you have a computer available to simplify ...
  69. Before you install Microsoft Lync Server 2013, you must install an update for Windows Server 2008 R2. For details about the ...
  70. Before you install Microsoft Lync Server 2013, you must install Microsoft ASP.NET 4.5 by using the Add Roles and Features ...
  71. Before you install Microsoft Lync Server 2013, you must install Microsoft Windows Communication Foundation Activation by ...
  72. bit dual processor, hex-core, 2.26 gigahertz (GHz) or higher Intel Itanium processors are not supported for Lync Server server ...
  73. bit dual processor, quad-core, 2.0 gigahertz (GHz) or higher, or, 64-bit 4-way processor, dual-core, 2.0 GHz or higher Intel ...
  74. bit Dual processor, quad-core, or 4-way processor, dual-core 2.0 GHz+ 2x72 GB, 10K RPM HDD, High Performance SSD 16GB Memory ...
  75. Block with URL: Blocks the client from logging on and presents the user with a message indicating that the user is using ...