Adjust Maximum booking lead time with Powershell and Exchange Admin Center

Adjust Maximum booking lead time with Powershell and Exchange Admin Center 1

When you’re working with Room and Equipment mailboxes, you may have noticed the Maximum booking lead time is set to 180 days by default. As a user, you will receive a notification like Your meeting request was declined. This resource can only be scheduled up to 180 days in advance. Your meeting request was declined. …

Read moreAdjust Maximum booking lead time with Powershell and Exchange Admin Center

Start-HistoricalSearch : Invalid Organization value

Start-HistoricalSearch : Invalid Organization value 2

Today I got the following “Invalid Organization value” error when trying to run Start-HistoricalSearch and Get-HistoricalSearch in Office 365. Start-HistoricalSearch -ReportType MessageTrace -ReportTitle “02-2019” -NotifyAddress admin@itexperience.net -StartDate 02/01/2019 -EndDate 03/01/2019 -RecipientAddress admin@itexperience.net start-HistoricalSearch : Invalid Organization value. At line:1 char:1 It appears this error occurs when I first load Microsoft.Exchange.Management.PowerShell.E2010 with cmdlet: Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 and …

Read moreStart-HistoricalSearch : Invalid Organization value

How to change public folder default reply address in Office 365 (Couldn’t update the primary SMTP address)

Exchange Online

By default a public folders’ email address in Office 365 gets the onmicrosoft.com address as the reply address. It would be nicer to have the company’s default email address as reply address. To adjust the PrimarySMTPAddress, run the Set-MailPublicFolder cmdlet with the PrmarySMTPAddress parameter Set-MailPublicFolder -Identity mypf@itexperience.net -PrimarySmtpAddress mypf@itexperience.net In my case however, I encountered …

Read moreHow to change public folder default reply address in Office 365 (Couldn’t update the primary SMTP address)

FIX: This task does not support recipients of this type. The specified recipient is of type RemoteUserMailbox

FIX: This task does not support recipients of this type. The specified recipient is of type RemoteUserMailbox 3

When I tried to make a Office 365 Exchange Online mailbox visible in my on-premises environment, the following error occurred: PS C:\Windows\System32\WindowsPowerShell\v1.0> Enable-RemoteMailbox user1 -RemoteRoutingAddress user1@tenant.mail.onmicrosoft.com -PrimarySmtpAddress user1@tenant.com This task does not support recipients of this type. The specified recipient Int.tenant.com/Users/user1 is of type RemoteUserMailbox. Please make sure that this recipient matches the required recipient …

Read moreFIX: This task does not support recipients of this type. The specified recipient is of type RemoteUserMailbox

Get-SPOUser : No connection available. Use Connect-SPOService before running this CmdLet.

Get-SPOUser : No connection available. Use Connect-SPOService before running this CmdLet. 4

To run cmdlets on SharePointOnline, you first need to connect to the SPOService. If you don’t this error will return:

The error is pretty obvious. But to solve No connection available. Use Connect-SPOService before running this CmdLet , you must run Connect-SPOService which may lead to another bunch of errors :) I’ve summed up the …

Read moreGet-SPOUser : No connection available. Use Connect-SPOService before running this CmdLet.