Recipient cache в линке что значит
Recipient cache в линке что значит
Question
How to remove the recipient cache which shows while searching for the users in Lync 2010. Tried to delete the SIP folder which creates on the local system but there was no luck.
Each time the user logoff from VDI, this folder gets clear automatically. is there any other location we need to clear or any idea?
Answers
I was able to exclude the Recipient Cache search results by just excluding that folder from search via client policy.
Created a Client policy for contact and excluded the Recipient Cache folder, currently the results while searching lync is not showing from recipient cache.
Thanks all for your support.
If this is the case, you are on the right way. 🙂
I wrote a related article a few months ago.
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 tnmff@microsoft.com.
All replies
If you are talking about the ABS file, delete the Sip folder should also remove the local abs cache.
In addition, Lync client will use Outlook OAB file if it exists when searching contacts in Lync. If you have trouble in searching contacts, you may consider to delete it.
%userprofile%\AppData\Local\Microsoft\Outlook\Offline Address Books \
Recipient cache в линке что значит
Вопрос
How to remove the recipient cache which shows while searching for the users in Lync 2010. Tried to delete the SIP folder which creates on the local system but there was no luck.
Each time the user logoff from VDI, this folder gets clear automatically. is there any other location we need to clear or any idea?
Ответы
I was able to exclude the Recipient Cache search results by just excluding that folder from search via client policy.
Created a Client policy for contact and excluded the Recipient Cache folder, currently the results while searching lync is not showing from recipient cache.
Thanks all for your support.
If this is the case, you are on the right way. 🙂
I wrote a related article a few months ago.
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 tnmff@microsoft.com.
Все ответы
If you are talking about the ABS file, delete the Sip folder should also remove the local abs cache.
In addition, Lync client will use Outlook OAB file if it exists when searching contacts in Lync. If you have trouble in searching contacts, you may consider to delete it.
%userprofile%\AppData\Local\Microsoft\Outlook\Offline Address Books \
Recipient cache в линке что значит
Вопрос
How to remove the recipient cache which shows while searching for the users in Lync 2010. Tried to delete the SIP folder which creates on the local system but there was no luck.
Each time the user logoff from VDI, this folder gets clear automatically. is there any other location we need to clear or any idea?
Ответы
I was able to exclude the Recipient Cache search results by just excluding that folder from search via client policy.
Created a Client policy for contact and excluded the Recipient Cache folder, currently the results while searching lync is not showing from recipient cache.
Thanks all for your support.
If this is the case, you are on the right way. 🙂
I wrote a related article a few months ago.
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 tnmff@microsoft.com.
Все ответы
If you are talking about the ABS file, delete the Sip folder should also remove the local abs cache.
In addition, Lync client will use Outlook OAB file if it exists when searching contacts in Lync. If you have trouble in searching contacts, you may consider to delete it.
%userprofile%\AppData\Local\Microsoft\Outlook\Offline Address Books \
Clearing AutoComplete and other Recipient Caches
Posted on July 16, 2014
Anyone who has participated in migrations or transitions to Exchange has most likely encountered or has had to work around potential issues caused by the nickname cache. A “cache,” also known by its file extension, NK2 in older Outlook clients, is a convenience feature in Outlook and Outlook WebApp (OWA) which lets users pick recipients from a list of frequently-used recipients. This list is displayed when the end user types in the first few letters.
The potential issue revolves around end users using those lists to send messages, as the list contains cached recipient information. Because this information is static, it may become invalid at some point. Thus, when users pick recipients when sending messages, they may be sending messages to non-existent recipients or invalid e-mail addresses, which create issues like non-delivery of e-mail.
For the storage of static recipient information, some migration scenarios organizations might wish to zap all or parts of that cached information at some point in the process. For that purpose I have written a script. Depending on your scenario, this may prevent NDR issues or users being instructed to clean those entries themselves at the cost of having them re-enter frequently used e-mail addresses once.
Before I get into details on script usage, I will first elaborate a bit on the various caching mechanisms.
AutoComplete Stream
The autocomplete stream contains information from previously used recipients when using Outlook. The list contains address information such as SMTP or LegacyDN addresses and is limited to 1,000 most-recently used entries. The information is stored in a so-called folder-associated information (FAI) table in your Inbox, which is a hidden folder. FAI entries can be inspected using utilities like MFCMAPI or EWS Editor, like in the example below where I opened the associated contents of an inbox using MFCMAPI.
The autocomplete stream is stored in the item of message class IPM.Configuration.Autocomplete. The entries themselves are stored in the property PR_ROAMING_BINARYSTREAM (pidTagRoamingBinary, tag 0x7C09000A) which, as the name implies, is in binary format. However, you can inspect the information in a more comprehensible format using MFCMAPI. In MFCMAPI, open up the PR_ROAMING_BINARYSTREAM property of the IPM.Configuration.Autocomplete item using the Smart View structure definition Nickname Cache.
Be advised that Outlook will only retrieve the autocomplete stream when addressing functionality, like when entering a recipient in the To section when composing an e-mail. Any updates to the autocomplete stream will not be written back to the FAI item immediately, but will be saved when Outlook is closed. Because of this, Outlook has to be closed when making changes to the autocomplete stream otherwise Outlook may overwrite it with its version of the autocomplete stream.
End users can reset the nickname cache from Outlook via File > Options > Mail > Send Messages using the button Empty Auto-Complete List, or through starting Outlook using the switch /CleanAutoCompleteCache.
Outlook WebApp AutoComplete
Like Outlook, Outlook WebApp (OWA) caches recently used recipient information. Unfortunately, it does not share this information with Outlook. OWA stores its autocomplete stream information in the FAI table of your mailbox root folder, in a User Configuration object of message class IPM.Configuration.OWA.AutocompleteCache. In the example below, I opened the associated contents of the root container of a mailbox using MFCMAPI.
The autocomplete stream is stored in the item of message class IPM.Configuration.OWA.AutocompleteCache, but when accessing User Configuration information through Exchange Web Services, you need to remove the IPM.Configuration prefix. The entries themselves are stored in the property PR_ROAMING_XMLSTREAM (pidTagRoamingXmlStream, tag 0x7c080102) which, as the name implies, is stored in XML format (in the example the stream does not contain any entries).
In OWA Light (not Premium), end users can reset the OWA nickname cache via Options > Messaging > Clear Most Recent Recipients List.
Suggested Contacts
The Suggested Contacts folder is created by Outlook. It is an Address Book to which contact objects will be added for each recipient used to send messages to, but that are not present in your Contacts folder. Like ordinary address books, Suggested Contacts can be used as an additional address book for picking or searching recipients.
Note that unlike autocomplete, Suggested Contacts entries cannot be searched when typing the first few characters of a recipient.
Recipient Cache
The Recipient Cache folder was introduced with Exchange 2013. It is a non-visible, well-known folder that sits below the Contacts folder.
Unfortunately, the specific purpose of the Recipient Cache folder is not documented. It does however, contain cached recipient information.
Clean-AutoComplete Script
The script is really straightforward. It requires Exchange 2010 or later and Exchange Web Services Managed API 1.2 (or later). Alternatively, you can copy the Microsoft.Exchange.WebServices.DLL with the script as it will also look for it in the current folder.
The script Clean-AutoComplete.ps1 has the following syntax:
Clear-AutoComplete.ps1 [-Mailbox] [-Server ] [-Impersonation] [-Credentials
So for example, suppose you want to clear the Autocomplete stream used by Outlook on a mailbox, you can use:
To remove the Autocomplete stream used by OWA on your Office 365 account, you can use:
Exchange Hybrid and Office 365 Monitoring and Reporting
On-premises components, such as AD FS, PTA, and Exchange Hybrid are critical for Office 365 end user experience. In addition, something as trivial as expiring Exchange or AD FS certificates can certainly lead to unexpected outages. By proactively monitoring hybrid components, ENow gives you early warnings where hybrid components are reaching a critical state, or even for an upcoming expiring certificate. Knowing immediately when a problem happens, where the fault lies, and why the issue has occurred, ensures that any outages are detected and solved as quickly as possible.
Recipient cache в линке что значит
Вопрос
Глюки заключаются в том, что при поиске контактов по имени появляются клоны. У кого 2, у кого три. Причем информация в карточках контакта клонов может различаться, в частности форматами номеров телефонов.
На клиентах Lync 2013 ничего похожего не наблюдается. Ошибок служб формирования адресной книги на сервере нет.
Да и не у все пользователей, у кого установлен MS Lync 2010 такая вот проблема. Никто не сталкивался с подобным поведением клиента?
Do not multiply entities beyond what is necessary
Все ответы
Попробуйте вот так:
Если вам помог чей-либо ответ, пожалуйста, не забывайте жать на кнопку «Предложить как ответ» или «Проголосовать за полезное сообщение»
К сожалению указанные действия никак не помогли. Я подозреваю, что проблемные клиенты при выполнении поиска подтягивают контакты одного и того же пользователя из различных источников, из тех же, из которых формируется адресная книга Lync. То есть из локального профиля outlook, из Exchange и из AD. Соответственно, между получаемыми контактами наблюдается определенная разница, поскольку, например, контакты outlook могут быть заведены пользователем самостоятельно, и, соответственно, могут отличаться какими-то деталями, кроме адреса электронной почты, например номерами телефонов. Клиент 2010 по какой то причине воспринимает это как три разных контакта. В клиенте 2013 подобного не происходит.
Буду копать дальше.
Do not multiply entities beyond what is necessary