SOLVED

Office365 - Conversation History

%3CLINGO-SUB%20id%3D%22lingo-sub-159041%22%20slang%3D%22en-US%22%3EOffice365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159041%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20noticed%20when%20I%20move%20my%20account%20from%20our%20on%20premise%20Skype%20for%20Business%20server%20to%20be%20homed%20instead%20in%20our%20Office365%20tenant%202%20of%20the%20Skype%20for%20Business%20client%20settings%20getting%20turned%20from%20off%20to%20on.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThey%20are%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESave%20IM%20conversations%20in%20my%20email%20Conversation%20History%20folder%3C%2FP%3E%0A%3CP%3ESave%20call%20logs%20in%20my%20email%20Conversation%20History%20folder%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHow%20do%20I%20force%20our%20Skype%20for%20Business%20online%20policy's%20to%20set%20these%20options%26nbsp%3Bas%20disabled%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-159041%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EConversation%20History%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-161253%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-161253%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Craig%2C%20that's%20not%20strictly%20true%20no%20-%20it%20means%20that%20the%20default%20setting%20for%20that%20parameter%20will%20apply%20-%20this%20isn't%20always%20%24True%20(1).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160750%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160750%22%20slang%3D%22en-US%22%3E%3CP%3EOK%2C%20thanks%20Ben.%20Last%20question%2C%20hopefully!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20a%20setting%20doesn't%26nbsp%3Bhave%20True%20or%20False%20against%20it%20(blank%20value)%26nbsp%3Bdoes%20it%20mean%20that%20the%20option%20is%20enabled%20(set%20to%20true)%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160732%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160732%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20completion%20sake%20you%20can%20also%20disable%20that%20yes.%20Although%20that%20setting%20provides%20server-side%20conversation%20history%2C%20meaning%20your%20history%20is%20available%20across%20all%20devices%20rather%20than%20just%20the%20device%20you%20had%20he%20conversation%20on.%20As%20you're%20turning%20off%20conversation%20history%20anyway%20I%20would%20imagine%20that%20it%20renders%20this%20setting%20irrelevant%20regardless%20of%20what%20its%20set%20to%20-%20but%20yes%20turn%20it%20off%20for%20good%20measure%20in%20case%20I'm%20wrong%20-%20happens%20all%20the%20time!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EKind%20regards%3CBR%20%2F%3EBen%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160710%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160710%22%20slang%3D%22en-US%22%3ECheers%20Ben%2C%20I%20presume%20I%20will%20also%20need%20this%20option%20setting%20to%20false%20also%20-%20EnableServerConversationHistory%3F%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20do%20not%20want%20any%20server%20side%20logging%20of%20conversations%20at%20this%20moment.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160662%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160662%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Craig%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20global%20client%20policy%20can%20be%20considered%20the%20default%20policy.%20If%20you%20don't%20explicitly%20assign%20a%20client%20policy%20to%20a%20user%20then%20they%20will%20use%20the%20settings%20defined%20in%20the%20global%20one.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20answer%20your%20questions%3B%3C%2FP%3E%0A%3CP%3E1.)%20That%20command%20is%20intended%20to%20retrieve%20all%20client%20policies%20that%20currently%20have%20those%20archiving%20settings%20set%20to%20false%2C%20but%20is%20a%20bit%20pointless%20as%20the%20rest%20of%20the%20script%20doesn't%20use%20the%20results.%3C%2FP%3E%0A%3CP%3E2.)%20There%20are%20lots%20of%20predefined%20client%20policies%20that%20exist%20that%20are%20configured%20for%20common%20scenarios.%20The%20idea%20is%20that%20you%20can%20simply%20assign%20these%20rather%20than%20have%20to%20amend%20or%20create%20new%20policies.%20Once%20upon%20a%20time%20we%20didn't%20have%20the%20capability%20to%20create%20custom%20policies%20so%20these%20were%20all%20that%20existed.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20want%20to%20change%20the%20global%20(default)%20policy%20only%20then%20run%20this%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%24credential%20%3D%20Get-Credential%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3E%24Session%20%3D%20New-CsOnlineSession%20-Credential%20%24credential%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3EImport-PSSession%20%24CSSession%20-AllowClobber%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3Eset-csclientpolicy%20-identity%20global%20-EnableIMAutoArchiving%20%24False%20-EnableCAllLogAutoArchiving%20%24False%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20want%20to%20make%20sure%20that%20ALL%20policies%20have%20these%20settings%20disabled%20then%20run%20this%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%24credential%20%3D%20Get-Credential%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3E%24Session%20%3D%20New-CsOnlineSession%20-Credential%20%24credential%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3EImport-PSSession%20%24CSSession%20-AllowClobber%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3Eset-csclientpolicy%20-EnableIMAutoArchiving%20%24False%20-EnableCAllLogAutoArchiving%20%24False%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you're%20not%20using%20custom%20policies%20then%20you%20probably%20only%20need%20to%20modify%20the%20global%20policy.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHope%20that%20helps.%3C%2FP%3E%0A%3CP%3EBen%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160591%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160591%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Ben%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOK%2C%20so%20I%20have%20the%20following%20script%20ready.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%24credential%20%3D%20Get-Credential%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3E%24Session%20%3D%20New-CsOnlineSession%20-Credential%20%24credential%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3EImport-PSSession%20%24CSSession%20-AllowClobber%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3EGet-CsClientPolicy%20%7C%20Where-Object%20%7B%24_.EnableIMAutoArchiving%20-eq%20%24False%20-and%20%24_.EnableCallLogArchiving%20-eq%20%24false%7D%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3Eset-CsClientPolicy%20-Identity%20Global%20-EnableIMAutoArchiving%20%24false%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3Eset-CsClientPolicy%20-Identity%20Global%20-EnableIMAutoArchive%20%24false%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20picked%20up%20the%20script%20above%20from%20another%20thread%20that%20I%20have%20seen.%20A%20couple%20of%20questions%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1.%20Why%20is%20this%20part%20of%20the%20script%20needed%3F%20I%20have%20ran%20it%20on%20its%20own%20and%20it%20returns%20no%20results%20I%20have%20also%20ran%20it%20with%20the%20options%20set%20to%20%24True%20and%20the%20command%20also%20returns%20no%20results.%3C%2FP%3E%0A%3CP%3E%3CEM%3EGet-CsClientPolicy%20%7C%20Where-Object%20%7B%24_.EnableIMAutoArchiving%20-eq%20%24False%20-and%20%24_.EnableCallLogArchiving%20-eq%20%24false%7D%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2.%20If%20I%20run%26nbsp%3B%3CEM%3EGet-CsClientPolicy%3C%2FEM%3E%20the%20command%20returns%20severeal%20policy%20including%20the%20global%20policy.%20For%20example%2C%20policies%20named%20like%26nbsp%3B%3CEM%3ETag%3AClientPolicyNoSaveIMNoArchivingNoIMURL%20%3C%2FEM%3Eand%3CEM%3E%20ClientPolicyNoIMURL%3C%2FEM%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20presume%20by%20using%26nbsp%3B%3CEM%3E-Identity%20Global%3C%2FEM%3E%20this%20will%20apply%20the%20changes%20to%20all%20policies%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160039%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160039%22%20slang%3D%22en-US%22%3E%3CP%3ENo%20problem...%20sorry%20it's%20resulted%20in%20more%20work!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-159968%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159968%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20Ben%20and%20I%20made%20sure%20I%26nbsp%3Bgot%20your%20name%20right%20this%20time%20%3A%20)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-159893%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159893%22%20slang%3D%22en-US%22%3E%3CP%3EYou'll%20need%20to%20manage%20the%20policy%20directly%20in%20O365%20I'm%20afraid%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F111873%22%20target%3D%22_blank%22%3E%40craig%20taylor%3C%2FA%3E.%20Client%20policies%20are%20relative%20to%20where%20the%20user%20is%20homed%2C%20so%20on-premises%20client%20policies%20can't%20be%20applied%20to%20users%20that%20are%20homed%20in%20SfBO.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EKind%20regards%3CBR%20%2F%3EBen%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-159616%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159616%22%20slang%3D%22en-US%22%3EHi%20Chris%2C%20yes%20found%20that%20in%20my%20research%20thanks.%20Is%20there%20no%20way%20to%20sync%20our%20policies%20from%20our%20local%20server%20to%20O365%3F%20I%20would%20prefer%20the%20local%20deployment%20to%20be%20authoritive%20and%20any%20changes%20we%20make%20there%20to%20flow%20up%20to%20O365%2C%20or%20is%20the%20only%20way%20to%20change%20the%20policy%20directly%20in%20O365%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-159260%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159260%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Craig%2C%20you%20will%20need%20to%20modify%20the%20existing%20SfBO%20Client%20Policy%20that%20is%20assigned%20to%20that%20user%2C%20or%20create%20a%20new%20SfBO%20Client%20Policy%20and%20assign%20it%20to%20that%20user%20(performed%20through%20PowerShell).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20two%20settings%20you%20need%20to%20set%20within%20that%20client%26nbsp%3Bpolicy%20are%3B%3C%2FP%3E%0A%3CP%3E1.)%20EnableCallLogAutoArchive%20%24False%3C%2FP%3E%0A%3CP%3E2.)%20EnableIMAutoArchive%20%24False%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBoth%20of%20these%20are%20enabled%20by%20default%20in%20the%20SfBO%20default%20Client%20Policy%2C%26nbsp%3Bbut%20changing%20them%20to%20false%20will%20fix%20your%20problem.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EKind%20regards%3CBR%20%2F%3EBen%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-159258%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20-%20Conversation%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159258%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20connected%20to%20Skype%20for%20Business%20Online%20trough%20PowerShell%20you%20could%20use%20this%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fskype%2Fset-csclientpolicy%3Fview%3Dskype-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fskype%2Fset-csclientpolicy%3Fview%3Dskype-ps%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ELet%20me%20know%20if%20you%20need%20any%20more%20explanation.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

I have noticed when I move my account from our on premise Skype for Business server to be homed instead in our Office365 tenant 2 of the Skype for Business client settings getting turned from off to on.

 

They are:

 

Save IM conversations in my email Conversation History folder

Save call logs in my email Conversation History folder

 

How do I force our Skype for Business online policy's to set these options as disabled?

12 Replies

When connected to Skype for Business Online trough PowerShell you could use this:
https://docs.microsoft.com/en-us/powershell/module/skype/set-csclientpolicy?view=skype-ps

Let me know if you need any more explanation.

Best Response confirmed by blue-man (Frequent Contributor)
Solution

Hi Craig, you will need to modify the existing SfBO Client Policy that is assigned to that user, or create a new SfBO Client Policy and assign it to that user (performed through PowerShell).

 

The two settings you need to set within that client policy are;

1.) EnableCallLogAutoArchive $False

2.) EnableIMAutoArchive $False

 

Both of these are enabled by default in the SfBO default Client Policy, but changing them to false will fix your problem.

 

Kind regards
Ben 

Hi Chris, yes found that in my research thanks. Is there no way to sync our policies from our local server to O365? I would prefer the local deployment to be authoritive and any changes we make there to flow up to O365, or is the only way to change the policy directly in O365?

You'll need to manage the policy directly in O365 I'm afraid @blue-man. Client policies are relative to where the user is homed, so on-premises client policies can't be applied to users that are homed in SfBO.

 

Kind regards
Ben

Thank you Ben and I made sure I got your name right this time : )

No problem... sorry it's resulted in more work!

Hi Ben,

 

OK, so I have the following script ready.

 

$credential = Get-Credential

$Session = New-CsOnlineSession -Credential $credential

Import-PSSession $CSSession -AllowClobber

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

set-CsClientPolicy -Identity Global -EnableIMAutoArchiving $false

set-CsClientPolicy -Identity Global -EnableIMAutoArchive $false

 

I picked up the script above from another thread that I have seen. A couple of questions:

 

1. Why is this part of the script needed? I have ran it on its own and it returns no results I have also ran it with the options set to $True and the command also returns no results.

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

 

2. If I run Get-CsClientPolicy the command returns severeal policy including the global policy. For example, policies named like Tag:ClientPolicyNoSaveIMNoArchivingNoIMURL and ClientPolicyNoIMURL.

 

I presume by using -Identity Global this will apply the changes to all policies?

Hi Craig,

 

The global client policy can be considered the default policy. If you don't explicitly assign a client policy to a user then they will use the settings defined in the global one.

 

To answer your questions;

1.) That command is intended to retrieve all client policies that currently have those archiving settings set to false, but is a bit pointless as the rest of the script doesn't use the results.

2.) There are lots of predefined client policies that exist that are configured for common scenarios. The idea is that you can simply assign these rather than have to amend or create new policies. Once upon a time we didn't have the capability to create custom policies so these were all that existed.

 

If you want to change the global (default) policy only then run this;

$credential = Get-Credential

$Session = New-CsOnlineSession -Credential $credential

Import-PSSession $CSSession -AllowClobber

set-csclientpolicy -identity global -EnableIMAutoArchiving $False -EnableCAllLogAutoArchiving $False

 

If you want to make sure that ALL policies have these settings disabled then run this;

$credential = Get-Credential

$Session = New-CsOnlineSession -Credential $credential

Import-PSSession $CSSession -AllowClobber

set-csclientpolicy -EnableIMAutoArchiving $False -EnableCAllLogAutoArchiving $False

 

If you're not using custom policies then you probably only need to modify the global policy.

 

Hope that helps.

Ben

Cheers Ben, I presume I will also need this option setting to false also - EnableServerConversationHistory?

We do not want any server side logging of conversations at this moment.

For completion sake you can also disable that yes. Although that setting provides server-side conversation history, meaning your history is available across all devices rather than just the device you had he conversation on. As you're turning off conversation history anyway I would imagine that it renders this setting irrelevant regardless of what its set to - but yes turn it off for good measure in case I'm wrong - happens all the time!

 

Kind regards
Ben

OK, thanks Ben. Last question, hopefully!

 

If a setting doesn't have True or False against it (blank value) does it mean that the option is enabled (set to true)?

Hi Craig, that's not strictly true no - it means that the default setting for that parameter will apply - this isn't always $True (1).