none
Lync Archiving External Communications Even When Policy Is Disabled

    Question

  • Hello!

    I've got an interesting scenario here. We have enabled a Global Archiving Policy (which I have verified is applied to ALL users... no accidental per user/site/server policy enabled) in which I have chosen to archive INTERNAL conversations only and exclude EXTERNAL. It is my understanding that this configuration should result in a scenario in which Employee A and B of my organization can chat, and it will save their history, but Employee A of my company and Employee 1 of a federated company can chat and expect that it will NOT archive the conversation.

    However, in the current conditions, Archiving is saving ALL conversations regardless of this preference. So the question is-- is there something wrong with my implementation, am I misunderstanding how this is supposed to work, or is the game afoot that something is wrong unexpectedly?

    Any advice would be greatly appreciated, and I'll be happy to provide any further information and perform diagnostics as needed. It is imperative that I resolve this quickly, otherwise, I will have to disable the functionality to prevent any issues with one of my business's customers.

    Thanks,
    Aaron


    PS-- I just noticed that this was incorrectly put into the Lync 2010 queue instead of Lync 2013. Not sure how much difference it makes, but if a moderator could move it, that might be more helpful in getting eyes on it.
    jeudi 16 février 2017 19:13

Toutes les réponses

  • Interesting.

    Can you post the output of Get-CsArchivingPolicy here?

    Also, try running logging on the archiving component on Edge and Front End servers while reproducing the issue and see if it points to something.


    My Blog : http://www.theskypeguy.com

    Note: If you find a post informative, please mark it so using the arrow to the left. If it answers a question you have asked, please mark the thread as answered to aid others when they are looking for solutions to similar problems or queries.

    jeudi 16 février 2017 23:44
  • PS C:\Users\AHALLADMIN> Get-CsArchivingPolicy

    Identity        : Global
    Description     :
    ArchiveInternal : True
    ArchiveExternal : False

    PS C:\Users\AHALLADMIN>

    As you can see, there's only the one policy, so I don't think there's any confusion on which is being used.

    Here's the values for Get-CsClientPolicy as well...

    PS C:\Users\AHALLADMIN> Get-CsClientPolicy

    Identity                                    : Global
    PolicyEntry                                 : {}
    Description                                 :
    AddressBookAvailability                     : WebSearchAndFileDownload
    AttendantSafeTransfer                       :
    AutoDiscoveryRetryInterval                  :
    BlockConversationFromFederatedContacts      :
    CalendarStatePublicationInterval            :
    ConferenceIMIdleTimeout                     :
    CustomizedHelpUrl                           :
    CustomLinkInErrorMessages                   :
    CustomStateUrl                              :
    DGRefreshInterval                           :
    DisableCalendarPresence                     :
    DisableContactCardOrganizationTab           :
    DisableEmailComparisonCheck                 :
    DisableEmoticons                            :
    DisableFeedsTab                             :
    DisableFederatedPromptDisplayName           :
    DisableFreeBusyInfo                         :
    DisableHandsetOnLockedMachine               :
    DisableMeetingSubjectAndLocation            :
    DisableHtmlIm                               :
    DisableInkIM                                :
    DisableOneNote12Integration                 :
    DisableOnlineContextualSearch               :
    DisablePhonePresence                        :
    DisablePICPromptDisplayName                 :
    DisablePoorDeviceWarnings                   :
    DisablePoorNetworkWarnings                  :
    DisablePresenceNote                         :
    DisableRTFIM                                :
    DisableSavingIM                             : False
    DisplayPhoto                                : AllPhotos
    EnableAppearOffline                         :
    EnableCallLogAutoArchiving                  : True
    EnableClientMusicOnHold                     : False
    EnableConversationWindowTabs                :
    EnableEnterpriseCustomizedHelp              :
    EnableEventLogging                          :
    EnableExchangeContactSync                   : True
    EnableExchangeDelegateSync                  :
    EnableFullScreenVideo                       :
    EnableHighPerformanceConferencingAppSharing : False
    EnableHotdesking                            :
    EnableIMAutoArchiving                       : True
    EnableMediaRedirection                      :
    EnableNotificationForNewSubscribers         :
    EnableSkypeUI                               : True
    EnableSQMData                               :
    EnableTracing                               :
    EnableURL                                   :
    EnableUnencryptedFileTransfer               :
    EnableVOIPCallDefault                       : True
    ExcludedContactFolders                      :
    HotdeskingTimeout                           : 00:05:00
    IMWarning                                   :
    MAPIPollInterval                            :
    MaximumDGsAllowedInContactList              : 10
    MaximumNumberOfContacts                     :
    MaxPhotoSizeKB                              : 30
    MusicOnHoldAudioFile                        :
    P2PAppSharingEncryption                     : Supported
    EnableHighPerformanceP2PAppSharing          : False
    PlayAbbreviatedDialTone                     :
    SearchPrefixFlags                           :
    ShowRecentContacts                          : True
    ShowManagePrivacyRelationships              : False
    ShowSharepointPhotoEditLink                 : False
    SPSearchInternalURL                         :
    SPSearchExternalURL                         :
    SPSearchCenterInternalURL                   :
    SPSearchCenterExternalURL                   :
    TabURL                                      :
    TracingLevel                                : Light
    WebServicePollInterval                      :
    HelpEnvironment                             :

    PS C:\Users\AHALLADMIN>

    And one more bit of info, here's what I have for Get-CsUser details...

    PS C:\Users\AHALLADMIN> Get-CsUser ahall | fl

    Identity                : CN=AHall,*confidential*
    VoicePolicy             : Warren Long Distance
    VoiceRoutingPolicy      :
    ConferencingPolicy      :
    PresencePolicy          :
    DialPlan                : Warren.*confidential*
    LocationPolicy          :
    ClientPolicy            :
    ClientVersionPolicy     :
    ArchivingPolicy         :
    ExchangeArchivingPolicy : Uninitialized
    PinPolicy               :
    ExternalAccessPolicy    : Allow Federation+Public+Outside Access
    MobilityPolicy          :
    PersistentChatPolicy    :
    UserServicesPolicy      :
    HostedVoiceMail         :
    HostedVoicemailPolicy   :
    HostingProvider         : SRV:
    RegistrarPool           : *confidential*
    Enabled                 : True
    SipAddress              : sip:aaron.hall@*confidential*
    LineURI                 : tel:+*confidential*
    EnterpriseVoiceEnabled  : True
    ExUmEnabled             : True
    HomeServer              : CN=*confidential*
    DisplayName             : Hall, Aaron
    SamAccountName          : AHall

    PS C:\Users\AHALLADMIN>

    vendredi 17 février 2017 12:57
  • This looks pretty straightforward and should work as configured. Your only option now is to collect logs and see if you can find something.

    My Blog : http://www.theskypeguy.com

    Note: If you find a post informative, please mark it so using the arrow to the left. If it answers a question you have asked, please mark the thread as answered to aid others when they are looking for solutions to similar problems or queries.

    vendredi 17 février 2017 19:17
  • That was my thought as well.

    Any advice on how I can collect and review these logs? I'm still fairly new at learning Lync Server.

    Thanks,

    Aaron

    vendredi 17 février 2017 19:49
  • http://blog.schertz.name/2011/06/using-the-lync-logging-tool/

    https://technet.microsoft.com/en-us/library/gg558599%28v=ocs.14%29.aspx?f=255&MSPPError=-2147217396

    Check these out. Under components select Archiving.


    My Blog : http://www.theskypeguy.com

    Note: If you find a post informative, please mark it so using the arrow to the left. If it answers a question you have asked, please mark the thread as answered to aid others when they are looking for solutions to similar problems or queries.

    vendredi 17 février 2017 21:57
  • Unfortunately, I'm not seeing anything overly useful in the logs for the issue.

    mardi 21 février 2017 13:21
  • It would seem as though I've figured out my own issue. In fact, it's not an issue of the Archive Policy not working at all. It is working EXACTLY as expected. The issue is actually the client policy doesn't adhere to the archive policy with conversation history saving. The desktop client is simply archiving ALL conversations into Outlook's Conversation History folder regardless of Internal/External. This is NOT the desired result, obviously, and was a definite misunderstanding of the way Lync works on my part.

    A little more explanation here... the desire is to have INTERNAL conversations be saved and EXTERNAL not be saved. Conversation history is extremely valuable internally because it guarantees we never "miss" a window or lose information because of closing the chat window. It's crucial to making the mobile clients work, because if the window isn't active, IMs are pointless without the history being saved. It seems, however, that I can disable autoarchiving on desktop and enable it on Mobile, which is great... but it still leaves the condition that external conversations are saved which can violate the policy we have.

    So now the question becomes-- can conversation history be configured in a way that it blocks a per-domain basis or block external universally, etc.?



    mardi 28 février 2017 14:28