OWA new user timezone and regional settings error

SecureAuth IdP Version affected: 9.2 and below

Description:

When trying to log into OWA as a new user, it asks you to set your timezone and regional settings as expected. 

However, when trying to save the settings, the following error occurs

"This method or property is not supported after HttpRequest.Form, Files, InputStream, or BinaryRead has been invoked."

In addition to the above error, the Mailbox server HTTP.SYS log (C:\Windows\System32\LogFiles\HTTPERR\httperrXX.log) will have a correlating 400.2 error

E.G

2018-01-30 17:02:31 ::1%0 49134 ::1%0 444 HTTP/1.1 POST /owa/lang.owa - 400 2 BadRequest MSExchangeOWAAppPool

Cause:

Defect EE-550. 

Resolution: 

The issue was resolved in SecureAuth v9.3 using a new integration method.

For earlier versions see the following workarounds:

The workaround is to provision the users with the timezone and regional settings already set.

To save time, you can do this through Powershell:

Method A

This applies to one User

1. Open Powershell on your Exchange server

2. Run

Set-MailboxRegionalConfiguration -Identity tester12 -TimeZone "Pacific Standard Time"

Some customers have found that they need to set further options 

Set-MailboxRegionalConfiguration -Identity tester12 -Language en-US -LocalizeDefaultFolderName -TimeZone "Pacific Standard Time" -TimeFormat "h:mm tt'

Method B

This applies to all Users
If you wish to apply this to all users, you would run the following command but be warned it will change existing user settings too
1. Open Powershell on your Exchange server
2. Run

get-mailbox | Set-MailboxRegionalConfiguration -Timezone "Eastern Standard Time"

Additional information
To find out the correct names of all the timezones, you can run the following Powershell command:

$TimeZone = Get-ChildItem "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\Time zones" | foreach {Get-ItemProperty $_.PSPath}; $TimeZone | sort Display | Format-Table -Auto PSChildname,Display

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.