Check Warranty

COMPUTER PRODUCT

HP
http://support.hp.com/us-en/checkwarranty

DELL
http://www.dell.com/support/home/us/en/19/Products/?app=warranty

LENOVO
https://support.lenovo.com/hk/zh/warrantylookup

APPLE
https://checkcoverage.apple.com/

Office365 Powershell Disable Clutter

Enter the Powershell with administrator right

https://technet.microsoft.com/en-us/library/jj984289(v=exchg.160).aspx

Connect to Exchange Online








On your local computer, open Windows PowerShell and run the following command.










$UserCredential = Get-Credential






In the Windows PowerShell Credential Request dialog box, type your Office 365 user name and password, and then click OK.


Run the following command.










$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection






Note   If you are an Office 365 operated by 21Vianet customer in China, use the following value for the ConnectionUri parameter:https://partner.outlook.cn/PowerShell.


Run the following command.












Import-PSSession $Session









Note:
Be sure to disconnect the remote PowerShell session when you're finished. If you close the Windows PowerShell window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you'll need to wait for the sessions to expire. To disconnect the remote PowerShell session, run the following command.














To Enable or Disable Clutter for one user

To enable clutter for one user run:
PS C:\Scripts> Set-Clutter -Identity user@domain.com -Enable $true


To disable clutter for one user run:
PS C:\Scripts> Set-Clutter -Identity user@domain.com -Enable $false


To Enable or Disable Clutter for all users

To enable clutter for all users run:
PS C:\Scripts> Get-Mailbox | Set-Clutter -Enable $true


To disable clutter for all users run:
PS C:\Scripts> Get-Mailbox | Set-Clutter -Enable $false


Some users have reported that they do not have access to this cmdlet within Microsoft Office 365. Hopefully they will receive access to it shortly