Dec 20 2016 05:38 AM
Dec 20 2016 05:38 AM
Hi All,
I need to export an inventory of outlook client versions used by our end users. Can some one please advice?
i tried using Get-ConnectionByClientTypeDetailReport but it doesnot give Outlook versions.
Dec 20 2016 11:13 AM
SolutionGo to the O365 admin portal -> Reports -> Usage -> Email app usage -> press the Export button. No way to get this report via PowerShell afaik (@Anne Michels might prove me wrong here).
If you need even more details compared to what's shown in the report, down to the individual build number, you will have to browse the Audit logs and get the relevant data from them.
Dec 20 2016 11:51 AM
This shows licenses, but not user versions. Like it won't show you if the user is running Office 2013 or Office 2016. That is what would be beneficial - to show what client version the user has installed.
Dec 20 2016 11:03 PM
Use the below EXO PowerShell script, here we use Search-MailboxAuditLog which has the client information. This method needs auditing to be enabled on all mailboxes and will be slower due to the audit log search.
$UserCredential = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic- AllowRedirection Import-PSSession $Session $mailboxs = Get-MailBox $mailboxs | Foreach-Object{ $mailbox=$_ Search-MailboxAuditLog -StartDate ([system.DateTime]::Now.AddDays(-2)) -EndDate ([system.DateTime]::Now.AddDays(+1)) -Operations MailboxLogin -Identity $mailbox.UserPrincipalName -ShowDetails|where-object{$_.ClientInfoString-like "*Client=Microsoft.Exchange.Mapi;*" -or $_.ClientInfoString -like "*Client=Microsoft.Exchange..Autodiscover;*" } |select LogonUserDisplayName,ClientInfoString,LastAccessed,ClientIPAddress -First 1 |fl }
Below is the sample output for a user.
Dec 20 2016 11:26 PM
Dec 21 2016 06:39 AM
I get the following errors when running this script - see attached file
Dec 21 2016 08:34 PM
Attached the powershell script as file, copy/paste and run the script, it should work. The error is due to the line breaks.
Dec 22 2016 05:38 AM
Thanks, Vasil.
Please use the export button as described by Vasil to export any data from the usage reports at this point.
In spring 2017, we will make new reporting APIs available that will allow you to programmatically access the information from the usage reports. Going forward, please use the APIs as the new usage reports will not be accompanied by PowerShell cmdlets.
Thanks,
Anne