Monthly Archives: June 2016

This task does not support recipients of this type. The specified recipient ……

While creating new batch to migrate a mailbox , you get this error : This task does not support recipients of this type. The specified recipient MyDomain.com/Users/Migration.8f3e7716-2011-43e4-96b1-aba62d229136 is of type UserMailbox. Please make sure that this recipient matches the required … Continue reading

Posted in Uncategorized | 1 Comment

Set all Exchange service Startup type to automatic , start it , or delete it using powershell

get-service | Where {$_.DisplayName –like “Microsoft Exchange*”} | Set-Service -StartupType Automatic get-service | Where {$_.DisplayName –like “Microsoft Exchange*”} | Start-Service (Get-WmiObject Win32_Service | Where {$_.DisplayName –like “Microsoft Exchange*”}).Delete()

Posted in Uncategorized | Leave a comment

Exchange 2016 Error Database is mandatory on UserMailbox

Error: The following error was generated when “$error.Clear(); if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) ) { Update-RmsSharedIdentity -ServerName $RoleNetBIOSName } ” was run: “Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox. at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation) at … Continue reading

Posted in Uncategorized | Leave a comment

uninstalling adobe Acrobat via Group Policy – multiple versions / releases

My Problem was: 1- Various installation of Adobe Acrobat. 2- Customer is targeting specific Adobe Acrobat build (11.0.16). 3- If you used below articles will help you to uninstall ANY Acrobat with version 11 regardless of minor build version. 4- … Continue reading

Posted in Uncategorized | Leave a comment

Fixing Exchange 2010 OWA and ECP authentication conflicts.

https://exch-main-02.DOMAIN.com/ecp/?ExchClientVer=15 This error (HTTP 400 Bad Request) means that Internet Explorer was able to connect to the web server, but the webpage could not be found because of a problem with the address. For more information about HTTP errors, see … Continue reading

Posted in Uncategorized | Leave a comment