Exchange Decommissioning Set-Remotemailbox command
Hi all, I have a situation where someone was with a hybrid Exchange Server configuration was using scripts to provision accounts with Set-RemoteMailbox. Testing was being done with the recipient management using the exchange management and noticed mailboxes are being provisioned and working as expected without even running their set-remotemailbox commands and are curious if this is even needed anymore. So I guess my question is, at this stage where .\CleanupActiveDirectoryEMT.ps1 is the last thing to do, would set-remotemailbox still be necessary, and what would it be used for. I know usually you can just create an on-prem mailbox, synced and license, so I'm not sure if set-remotemailbox is required for new mailboxes or but I'm thinking it's for managing mailboxes that were previously migrated. Thanks for any input.
Exchange on-premise create mailbox or login using access token bearer
hello everyone! We have an external oauth2 server for SSO. Now we must use that server to authenticate our users. We are not allowed to create users, we just have to authenticate the users via SSO and get the information via Access Token, and based on that token we have to either create a mailbox for new users or login to the mailbox if the user already has a mailbox created. the SSO server guys provide us with the ClientID, ClientSecret, RedirectURI, etc... In addition to the below URL: https://< SSO-Server>/oauth2/authorize/?client_id=< ClientID>&response_type=token&redirect_uri=https://< Exchange-Server>/owa/&scope=profile We are using Exchange Server 2019 CU 13 on-premise, I don't know what to do! I'm not sure how to config the server. I'd appreciate any help. I tried to redirect the owa to the above link using "Set-OrganizationConfig -AdfsIssuer" It will redirect to the SSO and then SSO will authenticate the user and redirect the user to the specific link I provide + an Access Token But how can I use that access token to create a new mailbox user?Exchange 2019 - PS remoting over SSL without Basic Auth
I want to do PS remoting over SSL to an Exchange Server 2019: - Using MS Exchange Server 2019 (ExchangeServer2019-x64-CU11.ISO) on MS Windows Server 2019 (17763.737.190906-2324.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us_1.iso) Now i want to do powershell remoting to Exchange Server and it should be all secured with a self-signed SSL certificate and no basic authentication allowed. As basic authentication is insecure and will be deprecated by Microsoft this year and was already removed in MSX O365 what i read. - PS> SessionOpt = New-PSSessionOption -SkipCACheck:$true -SkipCNCheck:$true -SkipRevocationCheck:$true PS> Enter-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://<myexchangeserver>/PowerShell/ -Authentication Kerberos -Credential MYEXCHANGE\Administrator -SessionOption $SessionOpt - PS> SessionOpt = New-PSSessionOption -SkipCACheck:$true -SkipCNCheck:$true -SkipRevocationCheck:$true PS> Enter-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<myexchangeserver>/PowerShell/ -Authentication Basic -Credential MYEXCHANGE\Administrator -SessionOption $SessionOpt - The remote box with PS is not part of the domain, no Windows trusts in place. So in my opinion kerberos authentication does not work et all ? Correct ? - Connection via http protocol '-ConnectionUri parameter' is required to use. No other command. - Basic Authentication is disabled by default in WinRM, so it wont work unless i lighten the security. Questions i have: - In 2019 Exchange Server is Kerberos a valid option when the server is not part of the domain ? - Does Exchange Server 2019 support another authentication method via -ConnectionUri over https (not Basic Authentication) ? Thank you