Forum Widgets
Latest Discussions
Exchange 2019 - Exchange SE - In-Place upgrade
Hello, we’re currently running an Exchange Server 2019 hybrid environment (DAG on-prem + Exchange Online) with a few on-prem user mailboxes used for automated system communications (SMTP) - the mailboxes are not being used in Outlook. We migrated from Exchange 2016 to Exchange 2019, using a trial installation of Exchange 2019, which has expired. We are planning to upgrade to Exchange Server Subscription Edition (SE) and want to ensure the following is supported: - Can we perform an in-place upgrade from the expired Exchange 2019 trial to Exchange Server SE, or do we need to relicense/reactivate Exchange 2019 first? - What is the right / best action plan for us in this case Kindest Regards Leon
Increase space on Exchange Servers
Hello, We have a 2016 DAG exchange enivrement made by Two Windows server 2016, lastly the disks start getting full and i want to increase disks space from vCenter. is the operation safe on a production environnement ? is there any thing should be aware about ? Thank youExchange Server SE Hybrid License and Upgrades
Hi, I have a question about Exchange Server SE. Reading the FAQ I found this: As with previous versions, Exchange Server SE will continue to provide free licenses for qualified hybrid use via the Hybrid Configuration Wizard (HCW); however, unlike previous versions, you will need to either purchase SA for this license to get Exchange Server updates or have a cloud subscription license that satisfies the requirements. Does this mean I need to have SA to do the updates? Which cloud licenses do I need to buy to be able to update Exchange Server SE? Thanks RegardsExchange Server Subscription Edition Now Generally Available
July 1 marked the general availability of Exchange Server SE (subscription edition), the latest in a long line of server releases going back to Exchange 4.0 (1996). Exchange Server SE will soon be the only game in town after Exchange 2016 and 2019 reach end of support in October 2025. In other news, Defender for Office 365 now boasts protection against "email bombs." https://office365itpros.com/2025/07/04/exchange-server-se-ga/
Can't connect with GDAP using ExchangeOnlineManagement 3.7.0/3.8.0, but 3.6.0 works
Since upgrading to ExchangeOnlineManagement version 3.7.0, I've been unable to connect to any of my clients using GDAP. I thought I'd try upgrading to 3.8.0, but I still get the same error: PS C:\Users\username> connect-exchangeonline -userprincipalname email address removed for privacy reasons -DelegatedOrganization contoso.com ---------------------------------------------------------------------------------------- This V3 EXO PowerShell module contains new REST API backed Exchange Online cmdlets which doesn't require WinRM for Client-Server communication. You can now run these cmdlets after turning off WinRM Basic Auth in your client machine thus making it more secure. Unlike the EXO* prefixed cmdlets, the cmdlets in this module support full functional parity with the RPS (V1) cmdlets. V3 cmdlets in the downloaded module are resilient to transient failures, handling retries and throttling errors inherently. REST backed EOP and SCC cmdlets are also available in the V3 module. Similar to EXO, the cmdlets can be run without WinRM basic auth enabled. For more information check https://aka.ms/exov3-module Starting with EXO V3.7, use the LoadCmdletHelp parameter alongside Connect-ExchangeOnline to access the Get-Help cmdlet, as it will not be loaded by default ---------------------------------------------------------------------------------------- The role assigned to user email address removed for privacy reasons isn't supported in this scenario. Please check online documentation for assigning correct Directory Roles to User. At C:\Users\username\OneDrive - MSP\Documents\WindowsPowerShell\Modules\ExchangeOnlineManagement\3.7.2\netFramework\ ExchangeOnlineManagement.psm1:758 char:21 + throw $_.Exception; + ~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (:) [], SystemException + FullyQualifiedErrorId : The role assigned to user email address removed for privacy reasons isn't supported in this scenario. Please check online documentation for assigning correct Directory Roles to User. You'd think there'd be something wrong with my GDAP permissions, but there doesn't appear to be. I can do anything via the Microsoft 365 Admin Center. Plus, most notably, if I manually load ExchangeOnlineManagement 3.6.0, everything works perfectly. I'm running Windows 11, and this behavior is reproducible on Windows PowerShell 5.1 as well as my preferred PowerShell 7.5.2. How can I troubleshoot this?
Program for Exchange Gets Contacts with Duplicated "OrganizationalIDNumber"
We have an old VB program that copies contacts from Microsoft Exchange to our SQL database. This worked fine for many years until 2017 when it started getting duplicated OrganizationalIDNumber from new contacts. I have been manually worked around this problem ever since (because I was busy and I am not familiar with this VB program). Now that I get some time, I want to fix this problem for good. We are expecting the OrganizationalIDNumber to be "1", "2", "3", .... But the new contacts all get the same ID "4303". I am under the impression that OrganizationalIDNumber is 32-bit. This should represent a very large number. Moreover, the program is using it as a string, and it is saved in our database as a varchar(255) data field. The ID should not be truncated (or so I thought). This certainly appears like the ID is being truncated though. My questions are: Does this look like something that you have come across? What is the solution? Where is the configuration setting in Microsoft Exchange that defines the data type of OrganizationalIDNumber? Our Exchange is version 2016. Please help if you can. Thanks. jchaniPhone Unable to Add 365 Account After Password Change – Hybrid Exchange
Hi all, We have an Exchange Hybrid setup. All mailboxes are hosted in Exchange Online, and our on-prem Exchange server is only used for SMTP relay (e.g., for MFPs). One of our users is currently unable to add their account to their iPhone. It was working fine until a few days ago. The issue started right after the user changed their password. Since then, the Outlook app or Office apps on the iPhone doesn't accept the user's credentials. However, everything works perfectly fine on their PC and even on another test iPhone using the same credentials. It validate the credentials but then throws a generic error after entering credentials. What we’ve tried so far: Resetting the user’s MFA settings Resetting the password again Excluding the user from MFA temporarily Factory resetting the iPhone Despite all that, the issue persists. Since the account works on a different iPhone, and even a full reset didn’t resolve it on the affected device, I’m at a bit of a loss. Has anyone encountered this or have any ideas? Any suggestions would be much appreciated. Thanks in advance!
Supported / recommended .Net versions Exchange SE on Windows Server 2019
I’m reading up on the Exchange SE upgrade, but there’s something I don’t understand. We are currently running Exchange 2019 CU15 on a Windows Server 2019 server (desktop experience). My initial plan is to perform an in-place upgrade from Exchange 2019 CU15 to Exchange SE, while remaining on Windows Server 2019 for the time being. From what I’ve read, this should be possible: https://techcommunity.microsoft.com/blog/exchange/why-%E2%80%9Cin-place-upgrade%E2%80%9D-from-exchange-2019-to-exchange-se-is-low-risk/4410173 https://learn.microsoft.com/en-us/answers/questions/2182463/upgrade-exchange-2019-to-exchange-se According to the supportability matrix, this should also be supported: https://learn.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix Exchange Server SE is supported on Windows Server 2019. What I don’t understand is the table for .NET Framework support. It seems like Windows Server 2019 is missing for Exchange Server SE in that table, just like Exchange Server 2019 CU15 on Windows Server 2019 with its corresponding .NET version. https://learn.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019#additional-requirements-and-information Does anyone have an explanation for this? I’d love to hear it!EXRCA autodiscover test failure
Preparing to configure Exchange Hybrid between the On-Prem Environment and O365 we ran the ExRCA connectivity test for outlook access. The test fails at the autodiscover testing for XML response Attempting to send an Autodiscover POST request to potential Autodiscover URLs. Autodiscover settings weren't obtained when the Autodiscover POST request was sent. The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.XXXXX.com:443/Autodiscover/Autodiscover.xml for user email address removed for privacy reasons. Additional Details Exception details: Message: The operation has timed out Type: System.Net.WebException The Exchange server is published by a simple DNAT The On prem environment is made of two Exchage 2016 CU23 Servers in DAG . thanks SCRoomfinder x onprem rooms
Some users are starting to report that they can't see the room status in room finder that used to work. The roomlist where there are rooms whose accounts are on-prem, all rooms appear as unchanged, the list where there are rooms that have already been migrated, the status is fine. If the user opens the scheduling assistant and adds an on-prem room, the status is also fine. The status is the same in outlook desktop and online outlook, but mobile outlook works without a problem. Has anyone encountered this?
