User Profile
AnnTaeYoun
MVP
Joined Apr 12, 2017
Since 2017 Microsoft MVP | M365 Exchange
User Widgets
Recent Discussions
Re: Exchange 2019 Certificate Error
Hello! Neymar The certificate name mismatch occurs because the newly added Exchange Server 2019 is being accessed directly by users' Outlook clients. To resolve this issue, block inbound TCP port 443 traffic from client networks to the Exchange Server 2019 IP address at the firewall level. This will prevent direct client connections to the backend server and ensure that Outlook connects only through the designated load balancer or Client Access endpoint.39Views0likes2CommentsRe: Exchange Server 2019 to Subscription Edition (SE) Licensing and Migration Guidance
narayandas4one Yes, if your Exchange Server 2019 license & CALs includes SA, migration to Exchange Server SE is possible under your active SA coverage. However, licenses without SA or with expired SA are not eligible for migration, and you must purchase new Exchange Server SE licenses & SE CALs.284Views1like0CommentsRe: Help~After installing Exchange 2019, mail is stuck in Draft in OWA
Thanks a lot! Please run command. Remove-MailboxPermission -Identity "info" -User "C mailbox" -AccessRights FullAccess Add-MailboxPermission -Identity "info" -User "C mailbox" -AccessRights FullAccess -AutoMapping:$true And than Outlook retry.51Views0likes3CommentsRe: Exchange Server 2019 to Subscription Edition (SE) Licensing and Migration Guidance
Hello! narayandas4one Please review below answer! 2-1. Answer: Support is a mandatory requirement. Without support, support will end according to the Exchange Server 2019 EOS schedule. 2-2. Answer: SA cannot be purchased additionally. You must purchase a completely new license. 2-3. Answer: You need to purchase new CAL for Exchange Server SE. 3. Answer: option B383Views1like1CommentRe: Creation of customrole that allows only creation of Mailenabled Security groups.
Thanks for answer HansYolo This is because only distribution groups are visible in ECP. New-DistributionGroup is designed to create distribution groups by default. Security groups are created based on New-DistributionGroup parameters. The order is as follows: New-DistributionGroup (Base) New-DistributionGroup -Type Security (Security Group) Therefore, it is impossible to restrict or expose only security groups through RBAC in the GUI.87Views1like0CommentsRe: Creation of customrole that allows only creation of Mailenabled Security groups.
HansYolo In Exchange, mail-enabled security groups and regular distribution groups are created through the same cmdlet (New-DistributionGroup), so limiting the creation to only security groups is not supported.102Views0likes2Comments
Recent Blog Articles
No content to show