VMXNET3 and Exchange 2016
According to HealthChecker in our Exchange, the script is warning us that ("Large packet loss at the guest operating system level on the VMXNET3 vNIC in ESXi (2039495)). I do not see any connectivity issues. There is a KB article from VMware to look at the firmware to see if they are okay, then change the buffer size. I do not want to change the buffer size since I do not see any connectivity issues. Has anyone else seen this warning in their Exchange Server/SQL environment? Is this a real problem? Or can it be ignored?
Exchange 2016 Hybrid - Hybrid Modern Authentication only for external connection
We want to use Outlook for iOS / Android with Hybrid Modern Auth to take advantage of CA and Intune. After activation via Set-OrganizationConfig -OAuth2ClientProfileEnabled $ true Set-AuthServer -Identity EvoSTS * -IsDefaultAuthorizationEndpoint $ true all internal Outlook 2016 clients also try to establish a connection via OAuth. Since not all users are synchronized in the AAD, a connection is not possible for these users. Does anyone have an idea how we can activate OAuth only for external connections or only for ActiveSync and the local clients still connect via Negotiate / NTLM?
Modern Authentication in on premises Exchage
Dear All Recently CISA commanded all online exchange authentication should be done by Modern Authentication in place of Basic Authentication. (https://www.cisa.gov/sites/default/files/publications/switch-to-modern-authentication-in-exchange-online-062822-508.pdf) My question is, for more security to the Exchange Server, can anyone suggest to me, is there any way to implement this Modern Authentication in place of Basic Authentication in MS Exchange 2016 with AD 2016? Both of my servers are on-premises.
Implementing CBA for mobile device users to access their email
Hi all I found a document on how to that on exchange but i need a full guide on how to do the active directory part as mentioned in this document https://docs.microsoft.com/en-us/exchange/plan-and-deploy/post-installation-tasks/configure-certificate-based-auth?view=exchserver-2019#step-1-use-the-exchange-management-shell-to-install-the-client-certificate-mapping-authentication-feature-on-all-of-your-exchange-servers I don't want to mess up our domain controller, i need a clear guide on how to implement a CBA on Domain controller to use it later for exchange on-prem users to authenticate instead of username and password again, I don't need the exchange part...i know how to do it through the above document what I need is the part on AD in details please thanksout of office not working from outlook client
I have an Exchange 2016 server which is updated to the latest CU and security updates. out of office from the outlook client has quit working and I have been unable to get it working. It works fine from OWA. There are some WAS 5011 warnings in the event log.A process serving application pool 'MSExchangePowerShellFrontEndAppPool' suffered a fatal communication error with the Windows Process Activation Service. any ideas would be greatly appreciated.
Exchange 2016 removing apostrophes from addresses
We have two Exchange 2016 servers in a DAG with CU19. We haven't performed any patches for a couple months now. All of our addresses that contain apostrophes are being truncated for no obvious reason. The apostrophes are just removed and started occurring last week. Active Directory still contains them in the username and last name, so we have no idea how this could happen. The Default Policy is applied to the organization with First Initial, Last Name... Email Address Format SMTP Primary: JSmith@ourdomain.org Address 2: alias@ourdomain.org X400 The last name fields requiring apostrophes are still present, as stated. Any thoughts?Query for PR_HIERARCHY_SERVER property returns MAPI_E_INVALID_PARAMETER.
Hi, Our application(IBM Content Collector - ICC) is trying to query PR_HIERARCHY_SERVER property. We use the MSMAPI32.dll, acting as client to Exchange servers. However MAPI call HrGetProp for the property PR_HIERARCHY_SERVER = 0x6633001F fails with MAPI Error 'MAPI_E_INVALID_PARAMETER'. We noticed the issue is not seen when we use Outlook 2010 as client. Below are all the scenariosand results: 1) ICC with Exchange 2019 : Outlook 2019 : Public folder archiving fails 2) ICC with Exchange Online : Outlook 2019 : Public folder archiving fails 3) ICC with Exchange 2016 : Outlook 2016 : Public folder archiving fails 4) ICC with Exchange 2016 : Outlook 2010 : Public folder archiving works! Do we have to make any changes to code when using newer Outlook client versions? Kindly provide suggestions as this is a blocker for one of our Customers(env: ICC with Exchange Online : Outlook 365). Regards, Salil Verlekar(saverlek@in.ibm.com) Mob: 9823961730
PublicFolder CN=Schema,CN=Microsoft Exchange System Objects,DC=contoso,DC=com
I'm in the preparation stage of migrating our Public Folders from an on-premises Exchange 2016 CU19 server to Exchange Online. Running the SourceSiceValidation.ps1 script outputs several orphaned MEPFs in our Active Directory, and I get a similar output from the ValidateMailEnabledPublicFolders.ps1. The recommendation is to delete the orphaned MEPFs, but I'm running into an oddity that I just don't feel comfortable deleting. There's a PublicFolder named "Schema" in our MESO OU, and it just feels wrong to delete anything named "Schema" in a database. Get-ADObject "CN=Schema,CN=Microsoft Exchange System Objects,DC=***,DC=***" | fl DistinguishedName : CN=Schema,CN=Microsoft Exchange System Objects,DC=***,DC=*** Name : Schema ObjectClass : publicFolder ObjectGUID : 9*******-8***-4***-8***-2*********** Any advice on how to determine if this object really is safe to remove? Thanks!