728x90

Introduction

Managing address book in Lync\SFB environment, in itself, is a task. Lync\SFB admins keep on getting address book related issues in the environment.

  • Users may notice duplicate contacts in address book search
  • User may notice old contact details (name, phone number, title etc).
  • Users see contacts deleted in Active Directory (resigned cases)
  • Users may not be able to search address book.
  • Users may experience “Cannot Synchronize Address Book” error as below.

"This article focusses on steps to resolve address book issues."


Re-Create the Address Book (Server)

This section of the article explains the process to re-create address book files at server end. Navigate following folder and delete the contents (existing address book files).

Lync_File_Share\1-WebServices-1\ABfiles\000000000\000000000



Forces the back-end user database to clear its replication status with Active Directory. This causes the database to re-read all the user-related information stored in Active Directory Domain Services.


Now, run following command on the Front End server;

Update-CsAddressBook

Forces the specified Address Book servers to synchronize their contents with the User database.


Wait for some time (5-10 mins, may be longer), and navigate to following location. You should see the files being recreated.

Lync_File_Share\1-WebServices-1\ABfiles\000000000\000000000

Check Address Book URLs

As a next step, make sure that you can browse to the following URLs.

As an internal client;

https://<internal web services url>/abs/handler 
https://<internal web services url>/abs/handler/GroupExpansion/Service.svc

As an external client;

https://<external web services url>/abs/handler 
https://<external web services url>/abs/handler/GroupExpansion/Service.svc

Test Address Book Service

Run following commands to check errors. You should be fine if it doesn’t return configuration related erros.

Test-CsAddressBookService

Test-CsAddressBookWebQuery

AddressBookAvailability Setting in Client Policy

You have option to select how a user should search a contact. There is a setting, AddressBookAvailability, in Lync\SFB client policy for this. By default, the policy is set to allow address book download and web search (by typing SIP URI of a contact).

Run following command to check address book setting.

Get-CsClientPolicy | Select-Object Identity,AddressBookAvailability | ft

There are currently three available settings for this parameter; WebSearchAndFileDownload,WebSearchOnly, and FileDownloadOnly. Define it as per your organization’s requirement.

  • WebSearchOnly is realtime and address book file content could be 24 hrs old.
  • You need to type full SIP URI for web search. Contact searching is user friendly if address book file downloaded.


Re-Create the Address Book (Client)

Now, re-create address book file, after performing above steps. First, delete local SIP profile of the users.

If user is running Skype For Business 2016

  • Log off of the Lync client and delete the profile from:
  • %userprofile%\appdata\Local\Microsoft\Office\15.0\Lync
  • Delete following registry key.
  • HKCU\Software\Microsoft\Office\16.0\Lync\sip@Domain.com

If user is running Lync 2013\Skype For Business 2015

  • Log off of the Lync client and delete the profile from:
  • %userprofile%\appdata\Local\Microsoft\Office\15.0\Lync
  • Delete following registry key.
  • HKCU\Software\Microsoft\Office\15.0\Lync\sip@Domain.com

If user is running Lync 2010

  • Log off of the Lync client and delete the profile from:
  • %userprofile%\AppData\Local\Microsoft\Communicator
  • Delete following registry key.
  • HKLM\Software\Policies\Microsoft\Communicator\sip@Domain.com

Download Address Book Immediately

In some cases, Lync\SFB users may face delay (upto 60 minutes) in address book download. Create this registry key to download address book immediately.

Run following command if user is running Skype For Business 2016

  • reg add HKLM\Software\Policies\Microsoft\Office\16.0\Lync /v GalDownloadInitialDelay /t REG_DWORD /d 0 /f

Run following command if user is running Lync 2013\Skype For Business 2015

  • reg add HKLM\Software\Policies\Microsoft\Office\15.0\Lync /v GalDownloadInitialDelay /t REG_DWORD /d 0 /f

Run following command if user is running Lync 2010

  • reg add HKLM\Software\Policies\Microsoft\Communicator /v GalDownloadInitialDelay /t REG_DWORD /d 0 /f


728x90
728x90

Microsoft Teams: A Beginner's Guide to Teams in Office 365

www.chorus.co%2Fresources%2Fnews%2Fmicrosoft-teams-a-beginners-guide-to-teams-in-office-365&edit-text=

 

 

Office 365 E3 trial

https://portal.office.com/partner/partnersignup.aspx?type=Trial&id=fcc729ff-9a24-4906-8167-4385e8c518f2&msppid=525300

728x90
728x90

Lync 오디오 품질 메트릭 입문서

The topic of audio quality can be vast and complex. 음질의 주제는 방대하고 복잡 할 수 있습니다. The purpose of this post is to provide some practical and easy to read guidance on the key metrics used in several Lync Server monitoring reports. 이 게시물의 목적은 여러 Lync Server 모니터링 보고서에 사용되는 주요 메트릭에 대한 실용적이고 읽기 쉬운 지침을 제공하는 것입니다. This will enable IT professionals to quickly gain insight into the audio quality of a particular Lync call or conference and troubleshoot poor audio quality if need be. 이를 통해 IT 전문가는 특정 Lync 전화 또는 회의의 오디오 품질에 대한 통찰력을 얻고 필요한 경우 열악한 오디오 품질 문제를 해결할 수 있습니다.

Note : this post is focused on audio metrics for Lync Audio – not enterprise voice audio – although some of the same metrics apply. 참고 :이 게시물은 동일한 측정 항목 중 일부가 적용되지만 Lync Audio 용 오디오 메트릭 (엔터프라이즈 음성이 아님)에 중점을 둡니다.

See my previous blog post Key Tips to Get Started with Lync Monitoring & Reporting to get started with the Lync Monitoring role and reports. Lync Monitoring 역할 및 보고서를 시작하려면 Lync Monitoring & Reporting 을 시작하는 데 필요한 이전 블로그 팁 주요 팁을 참조하십시오. Microsoft has a set of 4 documents to get you started and interpret the reports: Microsoft Lync Server 2010: Work Smart Guide for Monitoring Server Reports . Microsoft는 보고서를 시작하고 해석 할 수있는 4 가지 문서 세트를 제공합니다. Microsoft Lync Server 2010 : 서버 보고서 모니터링을위한 업무용 스마트 가이드 . Lastly, fellow Lync MVP Stale Hansen recently posted a good article regarding “ Lync Server 2010 Monitoring reports and why you always should deploy them ” which covers how and why you should deploy the Lync monitoring reports, and some of the metrics covered in this post. 마지막으로 동료 Lync MVP Stale Hansen은 최근에 " Lync Server 2010 모니터링 보고서 및이 보고서를 배포해야하는 이유 "와 관련된 좋은 기사를 게시했습니다.이 보고서 에는 Lync 모니터링 보고서를 배포해야하는 방법과 이유 및이 게시물에서 다루는 측정 항목 중 일부가 나와 있습니다.

 

728x90
728x90

Skype For Business 2019 Server 평가판 다운로드 링크

http://download.microsoft.com/download/2/0/9/209372AB-F64F-4F04-8BDA-FBAB1C685BA3/W17_2044.76_Eval.iso

 

Skype for Business Server 2019 is available as a 1.7GB ISO

728x90
728x90

1. 특정 Front-End 서버의 사용자만 찾고자 하는경우

Get-CsUser | Get-CsUserPoolInfo | Where-Object {$_.PrimaryPoolPrimaryRegistrar -eq "fe01.mani4u.com"} | ft identity, PrimaryPoolPrimaryRegistrar

 

 

2. 특정 Front-End 서버의 특정 사용자만 찾고자 하는경우

Get-CsUser -Filter {DisplayName -Like "*TEST*"} | Get-CsUserPoolInfo | Where-Object {$_.PrimaryPoolPrimaryRegistrar -eq "fe01.mani4u.com"} | ft identity, PrimaryPoolPrimaryRegistrar

 

결과값

Identity                                PrimaryPoolPrimaryRegistrar
--------                                ---------------------------
1000002@mani4u.com                     fe01.mani4u.com
1000010@mani4u.com                     fe01.mani4u.com
1000013@mani4u.com                     fe01.mani4u.com
1000014@mani4u.com                     fe01.mani4u.com
1000016@mani4u.com                     fe01.mani4u.com
1000019@mani4u.com                     fe01.mani4u.com
1000021@mani4u.com                     fe01.mani4u.com
1000024@mani4u.com                     fe01.mani4u.com

728x90
728x90

Phone Number Normalization Rule Regular Expressions

The pattern-matching notation of regular expressions makes it possible to quickly parse large amounts of text to find specific character patterns; to extract, edit, replace, or delete text substrings; or, to add the extracted strings to a collection in order to generate a report. You use .NET regular expressions to specify the phone pattern and the translation pattern as follows:

  • Phone pattern regular expression. This consists of designators and variables that represent specific sets of numbers. For example, the phone pattern regular expression of ^9(\d{7})$ describes phone numbers that consist of the number 9 followed by any seven digits.

  • Translation pattern regular expression. This consists of the + symbol, numbers, and the $ symbol. The $ symbol captures the items of the phone pattern regular expression that are included inside the parenthesis. The number following the $ symbol must be less than or equal to the total number of captures specified by the phone pattern regular expression.

    For example, the translation pattern regular expression of +1425$1 describes a translation that adds a prefix of +1425 to the captures (the phone pattern items in parenthesis). If the phone pattern regular express is ^9(\d{3})(\d{4})$ (containing two captures), the number following the $ sign can only be 1 or 2.

The following table shows sample normalization rules and the corresponding values for the rule name, description, phone pattern, and translation pattern.

Rule Name

Description

Phone Pattern

Translation Pattern

Example

4digitExtension

Translates 4-digit extensions

^(\d{4})$

+1425555$1

1234 is translated to +14255551234

5digitExtension

Translates 5-digit extensions

^8(\d{4})$

+1425558$1

81234 is translated to +14255581234

7digitcallingRedmond

Translates 7-digit numbers to Redmond local number

^(\d{7})$

+1425$1

5551212 is translated to +14255551212

7digitcallingDallas

Translates 7-digit numbers to Dallas local number

^(\d{7})$

+1972$1

5551212 is translated to +19725551212

10digitcallingUS

Translates 10-digit numbers in US

^(\d{10})$

+1$1

2065551212 is translated to +12065551212

LDCallingUS

Translates numbers with LD prefix in US

^1(\d{10})$

+1$1

12145551212 is translated to +12145551212

IntlCallingUS

Translates numbers with international prefix in US

^011(\d*)$

+$1

011914412345678 is translated to +914412345678

RedmondOperator

Translates 0 to Redmond Operator

^0$

+14255551212

0 is translated to +14255551212

RedmondSitePrefix

Translates numbers with on-net prefix (6) and Redmond site code (222)

^6222(\d{4})$

+1425555$1

62221234 is translated to +14255551234

NYSitePrefix

Translates numbers with on-net prefix (6) and NY site code (333)

^6333(\d{4})$

+1202555$1

63331234 is translated to +12025551234

DallasSitePrefix

Translates numbers with on-net prefix (6) and Dallas site code (444)

^6444(\d{4})$

+1972555$1

64441234 is translated to +19725551234

 

출처

https://support.office.com/en-us/article/phone-number-normalization-rule-regular-expressions-6ea76427-0892-4237-b024-10b418dcb05e

 

추가 참고

Lync Dial Plans and Normalization Rules :

http://designinglync.blogspot.com/2011/05/lync-dial-plans-and-normalization-rules.html

728x90
728x90

Phone Number Normalization Rule Regular Expressions

The pattern-matching notation of regular expressions makes it possible to quickly parse large amounts of text to find specific character patterns; to extract, edit, replace, or delete text substrings; or, to add the extracted strings to a collection in order to generate a report. You use .NET regular expressions to specify the phone pattern and the translation pattern as follows:

  • Phone pattern regular expression. This consists of designators and variables that represent specific sets of numbers. For example, the phone pattern regular expression of ^9(\d{7})$ describes phone numbers that consist of the number 9 followed by any seven digits.

  • Translation pattern regular expression. This consists of the + symbol, numbers, and the $ symbol. The $ symbol captures the items of the phone pattern regular expression that are included inside the parenthesis. The number following the $ symbol must be less than or equal to the total number of captures specified by the phone pattern regular expression.

    For example, the translation pattern regular expression of +1425$1 describes a translation that adds a prefix of +1425 to the captures (the phone pattern items in parenthesis). If the phone pattern regular express is ^9(\d{3})(\d{4})$ (containing two captures), the number following the $ sign can only be 1 or 2.

The following table shows sample normalization rules and the corresponding values for the rule name, description, phone pattern, and translation pattern.

Rule Name

Description

Phone Pattern

Translation Pattern

Example

4digitExtension

Translates 4-digit extensions

^(\d{4})$

+1425555$1

1234 is translated to +14255551234

5digitExtension

Translates 5-digit extensions

^8(\d{4})$

+1425558$1

81234 is translated to +14255581234

7digitcallingRedmond

Translates 7-digit numbers to Redmond local number

^(\d{7})$

+1425$1

5551212 is translated to +14255551212

7digitcallingDallas

Translates 7-digit numbers to Dallas local number

^(\d{7})$

+1972$1

5551212 is translated to +19725551212

10digitcallingUS

Translates 10-digit numbers in US

^(\d{10})$

+1$1

2065551212 is translated to +12065551212

LDCallingUS

Translates numbers with LD prefix in US

^1(\d{10})$

+1$1

12145551212 is translated to +12145551212

IntlCallingUS

Translates numbers with international prefix in US

^011(\d*)$

+$1

011914412345678 is translated to +914412345678

RedmondOperator

Translates 0 to Redmond Operator

^0$

+14255551212

0 is translated to +14255551212

RedmondSitePrefix

Translates numbers with on-net prefix (6) and Redmond site code (222)

^6222(\d{4})$

+1425555$1

62221234 is translated to +14255551234

NYSitePrefix

Translates numbers with on-net prefix (6) and NY site code (333)

^6333(\d{4})$

+1202555$1

63331234 is translated to +12025551234

DallasSitePrefix

Translates numbers with on-net prefix (6) and Dallas site code (444)

^6444(\d{4})$

+1972555$1

64441234 is translated to +19725551234

 

출처

https://support.office.com/en-us/article/phone-number-normalization-rule-regular-expressions-6ea76427-0892-4237-b024-10b418dcb05e

 

추가 참고

Lync Dial Plans and Normalization Rules :

http://designinglync.blogspot.com/2011/05/lync-dial-plans-and-normalization-rules.html

728x90
728x90

use rtc

SELECT FE.Fqdn as 'FE서버', count(*) as '할당유저수' FROM Resource R with(nolock)
INNER JOIN ResourceDirectory RD ON RD.ResourceId = R.ResourceId
INNER JOIN RoutingGroupAssignment RGA ON RGA.RoutingGroupId = RD.RoutingGroupId
INNER JOIN FrontEnd FE ON FE.FrontEndId = RGA.FrontEndId
GROUP BY FE.Fqdn

 

각 프론트엔드 서버별 사용자 수가 적절하게 분배 되었는지 확인

728x90

'IT이야기 > S4B&Lync' 카테고리의 다른 글

Phone Number Normalization Rule Regular Expressions  (0) 2018.10.25
Normalization Rule  (0) 2018.10.24
복제 상태 확인  (0) 2018.10.08
SIP 응답코드  (0) 2018.10.04
Lync 2013 Microsoft Innovation Day 발표 자료 1 (스크랩)  (0) 2016.09.02
728x90

출처 : https://docs.microsoft.com/ko-kr/powershell/module/skype/get-csmanagementstorereplicationstatus?view=skype-ps




Skype for Business Server 복제 프로세스에 대한 정보를 반환합니다. 여기에는 Skype for Business Server 컴퓨터의 복제본이 최신 상태인지 여부에 대한 정보가 포함됩니다. 이 cmdlet은 Lync Server 2010에 도입되었습니다.

통사론

PowerShell
Get-CsManagementStoreReplicationStatus   [[-ReplicaFqdn] <String>]   [-CentralManagementStoreStatus]   [<CommonParameters>]

기술

관리자가 Skype for Business Server로 변경 한 경우 (예 : 관리자가 새 음성 정책을 만들거나 주소록 서버 구성 설정을 변경 한 경우) 변경 사항은 중앙 관리 저장소에 기록됩니다. 그런 다음 Skype for Business Server 서비스 또는 서버 역할을 실행하는 모든 컴퓨터에 변경 내용을 복제해야합니다.

데이터를 복제하기 위해 Master Replicator (중앙 관리 서버에서 실행)는 수정 된 구성 데이터의 스냅 샷을 생성합니다. 이 스냅 샷의 사본이 Skype for Business Server 서비스 또는 서버 역할을 실행하는 각 컴퓨터로 전송됩니다. 이러한 컴퓨터에서 복제 에이전트는 스냅 샷을 수신하고 수정 된 데이터를 업로드합니다. 에이전트는 최신 복제 상태를보고하는 메시지를 Master Replicator에 전송합니다.

Get-CsManagementStoreReplicationStatus cmdlet를 사용하면 조직의 모든 Skype for Business Server 컴퓨터에 대한 복제 상태를 확인할 수 있습니다.

예제들

-------------------------- 예제 1 ---------------------- ----

PowerShell
Get-CsManagementStoreReplicationStatus

예 1에서 Get-CsManagementStoreReplicationStatus cmdlet은 매개 변수없이 호출됩니다. 모든 Skype for Business Server 컴퓨터의 복제 상태 (최신 상태 또는 최신 상태가 아님)를 반환합니다.

-------------------------- 예제 2 ---------------------- ----

PowerShell
Get-CsManagementStoreReplicationStatus | Where-Object {$_.UpToDate -eq $False}

예제 2는 복제가 최신이 아닌 모든 컴퓨터의 컬렉션을 반환합니다. 이 작업은 먼저 Get-CsManagementStoreReplicationStatus cmdlet를 사용하여 모든 서버의 복제 상태가 포함 된 컬렉션을 검색하여 수행됩니다. 그런 다음이 컬렉션을 Where-Object cmdlet으로 파이프합니다.이 cmdlet은 반환 된 데이터를 UpToDate 속성이 False 인 컴퓨터로 제한하는 필터를 적용합니다.

-------------------------- 예제 3 ---------------------- ----

PowerShell
Get-CsManagementStoreReplicationStatus -ReplicaFqdn atl-cs-001.litwareinc.com

예제 3에서 반환 된 데이터는 한 대의 컴퓨터로 제한됩니다. atl-cs-001.litwareinc.com/

-------------------------- 예제 4 ---------------------- ----

PowerShell
Get-CsManagementStoreReplicationStatus | Where-Object {$_.LastUpdateCreation -lt "8/11/2018 8:00 PM"}

예 4는 2018 년 8 월 11 일 오후 8시 이전에 마지막으로 복제 된 컴퓨터에 대한 정보를 반환합니다. 이렇게하려면 Get-CsManagementStoreReplicationStatus cmdlet가 먼저 호출되어 모든 Skype Business Server 컴퓨터에 대한 복제 정보를 반환합니다. 이 정보는 2018 년 8 월 11 일 (8/11/2018 오후 8:00) LastUpdateCreation 속성이 오후 8:00보다 작은 컴퓨터 만 선택하는 Where-Object cmdlet으로 파이프됩니다. 2018 년 8 월 11 일 8:00 PM 이후에 마지막으로 복제 된 컴퓨터에 대한 정보를 반환하려면 -gt (보다 큼 연산자)를 사용하십시오.

Where-Object {$_.LastUpdateCreation -gt "8/11/2018 8:00 PM"}

이 예제에서 지정된 날짜는 날짜 - 시간 값에 대해 미국 영어 형식을 사용합니다. 날짜는 지역 및 언어 옵션과 호환되는 형식을 사용하여 지정해야합니다.

-------------------------- 예제 5 ---------------------- ----

PowerShell
Get-CsManagementStoreReplicationStatus -CentralManagementStoreStatus

예 5에 표시된 명령은 CentralManagementStoreStatus 매개 변수를 사용하여 중앙 관리 저장소의 현재 상태에 대한 자세한 정보를 반환합니다. 여기에는 Active Master 및 File Transfer Agent 서비스의 정규화 된 도메인 이름과 해당 서비스 각각에 대해 감지 된 마지막 하트 비트의 날짜 및 시간이 포함됩니다.

선택적 매개 변수

-CentralManagementStoreStatus

활성 마스터 및 파일 전송 에이전트 서비스의 위치뿐만 아니라 활성 복제본 및 삭제 된 복제본 목록을 포함하여 중앙 관리 저장소의 현재 상태에 대한 추가 정보를 반환합니다.

유형:SwitchParameter
위치:명명 된
기본값:없음
파이프 라인 입력 허용 :True (ByPropertyName)
와일드 카드 문자 적용 :그릇된
적용 대상 :Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
-ReplicaFqdn

복제 상태를 확인할 컴퓨터의 정규화 된 도메인 이름 (FQDN)입니다. 예 : -ReplicaFqdn "atl-cs-001.litwareinc.com".

이 매개 변수가 포함되어 있지 않으면 모든 Skype for Business Server 컴퓨터의 복제 상태 정보가 반환됩니다.

유형:
위치:2
기본값:없음
파이프 라인 입력 허용 :True (ByPropertyName)
와일드 카드 문자 적용 :그릇된
적용 대상 :Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

투입물

없음

출력

Microsoft.Rtc.Management.Xds.ReplicaState 또는 Microsoft.Rtc.Management.Xds.CentralManagementStoreStatusResult

기본적으로 Get-CsManagementStoreReplicationStatus cmdlet은 Microsoft.Rtc.Management.Xds.ReplicaState 개체의 인스턴스를 반환합니다. CentralManagementStoreStatus 매개 변수가 사용되면 cmdlet는 Microsoft.Rtc.Management.Xds.CentralManagementStoreStatusResult 개체의 인스턴스를 반환합니다.


728x90
728x90
Informational
100: Trying
180: Ringing
181: Call is being forwarded
182: Queued (temporarily unavailable, server has decided to queue the call)
183: Session Progress

Success
200: OK

Redirection
300: Multiple Choices
301: Moved Permanently
302: Moved Temporarily
303: See Other
305: Use Proxy
380: Alternative Service

Client Error
400: Bad Request
401: Unauthorized
402: Payment Required
403: Forbidden
404: Not Found
405: Method Not Allowed
406: Not Acceptable
407: Proxy Authentication Required
408: Request Timeout
409: Conflict
410: Gone
413: Request Entity Too Large
414: Request-URI Too Large
415: Unsupported Media Type
416: Unsupported URI Scheme
420: Bad Extension
421: Extension Required
423: Interval Too Brief
480: Temporarily not available
481: Call Leg/Transaction does not exist
482: Loop Detected
483: Too Many Hops
484: Address Incomplete
485: Ambiguous
486: Busy Here
487: Request Terminated
488: Not Acceptable Here
491: Request Pending
493: Undecipherable

Server Error
500: Internal Server Error
501: Not Implemented
502: Bad Gateway
503: Service Unavailable
504: Server Time-out
505: Version not supported
513: Message To Large

Global-Failure
600: Busy Everywhere
603: Decline
604: Does not exist anywhere
606: Not Acceptable


728x90

+ Recent posts