Newguy 123
asked on
Exchange powershell command: Set-OrganizationConfig -MapiHttpEnabled $false, not replicating to mailboxes.
Hello Experts. In our staging env, we have exchange 2013, with AD 2012 R2. All test mailboxes, when opening Outlook 2013, or Outlook 2016, it kept of prompting for credentials, and would not accept them. so outlook was not able to make a successful connection to exchange. i noticed Outlook was using Http to make a connection. in production, we use RPC over HTTP with NTLM, so for my individual test account in staging, i ran the following command in Exchange PS:
set-CasMailbox <user email address> -MapiHttpEnabled $false (this was set to true before), and now for my test account, outlook is connecting via RPC over HTTP with NTLM (which is what i want), and my outlook is now able to make a successful connection to Exchange.
I ran the following command in Exchange PS: set-OrganizationConfig -MapiHttpEnabled $false (before it was set to true), but when i test with other test accounts, i see their outlook still trying to make a connection with HTTP, and it is failing.
1. when i run this command at the organization level, Why is this not replicating to all the test mail accounts that we have in exchange, currently all the mail accounts(except for mine) are showing blank when i run the first powershell command against them, neither $true or $false? mine is showing $false, because i ran the 'set' command against it.
2. do i need to run the command on each seperate mailbox like i did with mine in the first step for Outlook to use RPC over HTTP with NTLM?
Please let me know, and thanks in advance
set-CasMailbox <user email address> -MapiHttpEnabled $false (this was set to true before), and now for my test account, outlook is connecting via RPC over HTTP with NTLM (which is what i want), and my outlook is now able to make a successful connection to Exchange.
I ran the following command in Exchange PS: set-OrganizationConfig -MapiHttpEnabled $false (before it was set to true), but when i test with other test accounts, i see their outlook still trying to make a connection with HTTP, and it is failing.
1. when i run this command at the organization level, Why is this not replicating to all the test mail accounts that we have in exchange, currently all the mail accounts(except for mine) are showing blank when i run the first powershell command against them, neither $true or $false? mine is showing $false, because i ran the 'set' command against it.
2. do i need to run the command on each seperate mailbox like i did with mine in the first step for Outlook to use RPC over HTTP with NTLM?
Please let me know, and thanks in advance
Systech Admin
Kindly try to restart the CAS services and check if that works for outlook
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1. when i run this command at the organization level, Why is this not replicating to all the test mail accounts that we have in exchange, currently all the mail accounts(except for mine) are showing blank when i run the first powershell command against them, neither $true or $false? mine is showing $false, because i ran the 'set' command against it.
An organization setting does not set or change individual mailbox settings.
2. do i need to run the command on each seperate mailbox like i did with mine in the first step for Outlook to use RPC over HTTP with NTLM?
Yes.