none
Lync/Skype 2016 GPO to disable chat logging

    Question

  • Support,<o:p></o:p>

    We
    are deploying Office 2016 to our end users and would like to make sure that
    conversation/chat logging is disabled through Lync/Skype. We have already
    installed the Administrative Templates for 2016 on our Domain Controller. Is
    there a policy we can create through AD that will disable that feature?<o:p></o:p>

    Thanks.<o:p></o:p>


    Thursday, October 29, 2015 5:00 PM

Answers

  • We are deploying Office 2016 to our end users and would like to make sure that
    conversation/chat logging is disabled through Lync/Skype. We have already
    installed the Administrative Templates for 2016 on our Domain Controller. Is
    there a policy we can create through AD that will disable that feature?


    No. Not many settings for Lync/S4B can be controlled via AD GP. This changed some versions ago.

    There are some settings which can be controlled via AD GP, but not this one.
    There are some client settings which can be controlled by registry settings but no templates for those, it seems:

    https://technet.microsoft.com/en-us/library/dn954919(v=ocs.15).aspx



    You will need to use the Lync Server Management Shell, to configure client policy for most settings, on the Lync Server (if you have on-premises Lync/S4B server), otherwise, if you use O365, follow the suggestions from @Jedi_Administrator.

    https://technet.microsoft.com/en-us/library/gg398300(v=ocs.15).aspx

    In Lync Server, client policies replace the Group Policy settings used in previous versions of the product. In Microsoft Office Communicator 2007 and Microsoft Office Communicator 2007 R2, Group Policy helped determine what users could do with Communicator and other clients; for example, there were Group Policy settings that determined whether or not users could save a transcript of their instant messaging sessions; whether information from Microsoft Outlook was incorporated into their presence information; and whether or not users could include emoticons or formatted text in instant messages.

    Lync Server uses client policies instead of Group Policy. Client policies are applied each time a user accesses the system, regardless of where the user logs on from and regardless of the type of device the user logs on with. In addition, client policies, like other Lync Server policies, can readily be targeted toward selected groups of users. You can even create a custom policy that gets assigned to a single user.

    Client policies can be configured at the global, site, and per-user scopes. The Set-CsClientPolicy cmdlet enables you to modify any (or all) of the client policies that have been configured for use in your organization.


    As @Jedi_Administrator suggests, the settings you seem interested in, are these:

    EnableCallLogAutoArchiving
    When set to True, information about your incoming and outgoing phone calls is automatically saved to the Conversation History folder in Microsoft Outlook. (The actual call itself is not recorded. What is recorded is information such as who took part in the call; the length of the call; and whether this was an incoming or an outgoing call.)
    When set to False, this information is not saved to Outlook.
    This setting is equivalent to the Office Communications Server 2007 R2 Group Policy setting "Enable/disable automatic archiving of call logs to Outlook mailbox."

    EnableIMAutoArchiving
    When set to True, a transcript of every instant message session that a user takes part in will be saved to the Conversation History folder in Microsoft Outlook.
    When set to False, these transcripts will not be saved automatically. (However, users will have the option to manually save instant message transcripts.)
    This setting is equivalent to the Office Communications Server 2007 R2 Group Policy setting "Enable/disable automatic archiving of IM conversations to Outlook mailbox."


    Don [doesn't work for MSFT, and they're probably glad about that ;]


    Saturday, October 31, 2015 11:08 AM

All replies

  • In your office 2016 GPO go to the administrative templates section look for Microsoft lync 2016 template... There should be one for machine and user Do you see the gpo setting in any of these locations?
    Thursday, October 29, 2015 8:56 PM
  • Disable IM Auto Archiving for single user in Lync Online using Lync Online PowerShell

    Pre-requisites to run Lync Online PowerShell commands:
    1.Windows PowerShell v 3.0
    2.Lync Online PowerShell Module

    To disable IM Auto archiving for a single user, run below commands in Windows PowerShell. You must use Office 365 Global Administrator credentials to run below commands.
    1.Import-Module LyncOnlineConnector
    2.$cred = Get-Credential 
    3.$CSSession = New-CsOnlineSession -Credential $cred
    4.Import-PSSession $CSSession -AllowClobber
    5.Get-CsClientPolicy | Where-Object {$_.EnableIMAutoArchiving -eq $False -and $_.EnableCallLogArchiving -eq $false}
    6.get-csonlineuser | Grant-CsClientPolicy -PolicyName Tag:ClientPolicyNoSaveIMNoArchivingNoIMURL
    7.Grant-CsClientPolicy -PolicyName Tag:ClientPolicyNoSaveIMNoArchivingNoIMURL -Identity user@domain.com

    o Import-Module LyncOnlineConnector

    o $cred = Get-Credential

    o $CSSession = New-CsOnlineSession -Credential $cred

    o Import-PSSession $CSSession -AllowClobber

    o Get-CsClientPolicy | Where-Object {$_.EnableIMAutoArchiving -eq $False -and $_.EnableCallLogArchiving -eq $false}

    o Grant-CsClientPolicy -policyname tag:ClientPolicyNoSaveIMNoArchivingNoIMURL –Tenant xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

    (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx is a tenant GUID)


    Once you run the command, it takes about 4-6 hours to apply the policy. The last command will disable IM archiving history for whole tenant, so all the domains in the tenant and all users under all domains would get this policy applied.


    Once the policy is applied, in Lync client, IM archiving option would be grayed out.

    Friday, October 30, 2015 3:58 PM
  • We are deploying Office 2016 to our end users and would like to make sure that
    conversation/chat logging is disabled through Lync/Skype. We have already
    installed the Administrative Templates for 2016 on our Domain Controller. Is
    there a policy we can create through AD that will disable that feature?


    No. Not many settings for Lync/S4B can be controlled via AD GP. This changed some versions ago.

    There are some settings which can be controlled via AD GP, but not this one.
    There are some client settings which can be controlled by registry settings but no templates for those, it seems:

    https://technet.microsoft.com/en-us/library/dn954919(v=ocs.15).aspx



    You will need to use the Lync Server Management Shell, to configure client policy for most settings, on the Lync Server (if you have on-premises Lync/S4B server), otherwise, if you use O365, follow the suggestions from @Jedi_Administrator.

    https://technet.microsoft.com/en-us/library/gg398300(v=ocs.15).aspx

    In Lync Server, client policies replace the Group Policy settings used in previous versions of the product. In Microsoft Office Communicator 2007 and Microsoft Office Communicator 2007 R2, Group Policy helped determine what users could do with Communicator and other clients; for example, there were Group Policy settings that determined whether or not users could save a transcript of their instant messaging sessions; whether information from Microsoft Outlook was incorporated into their presence information; and whether or not users could include emoticons or formatted text in instant messages.

    Lync Server uses client policies instead of Group Policy. Client policies are applied each time a user accesses the system, regardless of where the user logs on from and regardless of the type of device the user logs on with. In addition, client policies, like other Lync Server policies, can readily be targeted toward selected groups of users. You can even create a custom policy that gets assigned to a single user.

    Client policies can be configured at the global, site, and per-user scopes. The Set-CsClientPolicy cmdlet enables you to modify any (or all) of the client policies that have been configured for use in your organization.


    As @Jedi_Administrator suggests, the settings you seem interested in, are these:

    EnableCallLogAutoArchiving
    When set to True, information about your incoming and outgoing phone calls is automatically saved to the Conversation History folder in Microsoft Outlook. (The actual call itself is not recorded. What is recorded is information such as who took part in the call; the length of the call; and whether this was an incoming or an outgoing call.)
    When set to False, this information is not saved to Outlook.
    This setting is equivalent to the Office Communications Server 2007 R2 Group Policy setting "Enable/disable automatic archiving of call logs to Outlook mailbox."

    EnableIMAutoArchiving
    When set to True, a transcript of every instant message session that a user takes part in will be saved to the Conversation History folder in Microsoft Outlook.
    When set to False, these transcripts will not be saved automatically. (However, users will have the option to manually save instant message transcripts.)
    This setting is equivalent to the Office Communications Server 2007 R2 Group Policy setting "Enable/disable automatic archiving of IM conversations to Outlook mailbox."


    Don [doesn't work for MSFT, and they're probably glad about that ;]


    Saturday, October 31, 2015 11:08 AM
  • When you say it takes about 4-6 hours to apply the policy. . are you referring to how long it takes for the Powershell cmdlets to run? Or are you referring to the S4B policy actually hitting the client.


    I believe you're referring to the latter, but I wanted to confirm before I pushed this out to my enterprise.
    Thursday, August 4, 2016 4:40 PM