Why do Apple macOS and Ubuntu clients display Exchange meeting times one hour earlier than scheduled
If a meeting is generated from Apple macOS and Ubuntu clients showing the meeting time as one hour earlier than the actual scheduled time email solution is exchange server 2019, what will be the issue.
Exchange 2010 to Microsoft 365 Migration – Recommended Approach and Tools
I’m looking for guidance on migrating Exchange 2010 (on-premises) to Microsoft 365 / Office 365. Is a direct migration from Exchange 2010 supported, or is an intermediate hop (such as upgrading Exchange or setting up a hybrid configuration) required? Additionally, could you please recommend any reliable tools that can help with this migration? I also have a few PST files that need to be migrated as part of the process. I’d appreciate insights on best practices, common challenges, and lessons learned from real-world migrations. Thanks in advance for your help.
Administratively retract a user's email
I was recently asked to retract a message that was sent in-error to staff. I ran a discovery/search, and saved it, but when I ran the powershell script after connecting to Exchange, the script could not find the search, something like name not found. I verfied the name was correct, and I am a global admin so permissions should not have been an issue. Does anyone know of any accurate documentation to run a search and retract? I had to use an old YouTube video and could not find anything in Microsoft's documentation.Exchange 2016 CU23 breaks Outlook 2010 connection
Hello, I have an environment with an Exchange 2016 CU22, that connects to a public folders in legacy, which resides on an Exchange 2010. We have many users still using Outlook 2010 and all is working fine. Yesterday we decided, to my great regrets, to install CU23 and a nightmare began, Outlook 2010, on the first start since CU23, connects no issue, but if we close Outlook then reopen it, no more connections, it just shows disconnected and if I look deeper, I see it just keeps retrying but Exchange refuses it to connect. I looked everywhere in the CU23 documentation for changes and nowhere there is mention about Outlook versions and legacy connections being affected by it! Anything I can do to get Outlook 2010 going again? What happened on the first connection, what did Exchange tell Outlook to reconfigure? Newer Outlook works fine. All Outlooks connect with RPC because of the legacy public folders.
Install exchange server Error :
Hi teams, i have a problem with installing exchange server , I want to install Exchange again on a server that has already uninstalled Exchange after uninstalling exchange i delete manulay the folder C:\Program Files\Microsoft\Exchange Server, now when i try to install exchange server i have this error : also with GUI : any idea , i find also these services in server : any help
User's mailbox Limit not retained after cross forest migration
We're performing Cross Forest migration with the "prepare" and "move" scripts from microsoft, after migrating the users with ADMT. We noticed that the user's specific mailbox limits are not preserved, is there a way of migrating the mailboxes preserving such settingsuninstall error exchange server CAS role:
hi teams , i have an error when i try to uninstall exchange server : in role CAS at 70% : the iis admin service not started , and i delete all folder (owa, mapi, ...) in http folder Configuration > CN=Configuration> CN=Services > CN=Microsoft Exchange > CN=EXOIP > CN=Administrative Groups > CN=Exchange Administrative Group (FYDIBOHF23SPDLT) > CN=Servers > CN=srv_name > CN=Protocols > CN=HTTP. and i delete also the folder http any help
decommision resource forest and install Exchange 2016 in account domain with existing hybrid
Following situation at a customer: - Account and Resource forest - Office 365 tenant - Azure AD Connect machine running in Account forest, syncing both directories - ADFS in Account forest - Exchange 2010 in Resource forest with Hybrid setup What we want: - decommision resource forest/domain and Exhange 2010 - install Exchange 2016 in account forest - make 2016 the hybrid I was wondering which steps we had to take. We are now already migrating user to Exchange Online. For a new user we create a user with Linked Mailbox in Resource domain. We ADMT it to the Account forest, we trigger ADSync. A mailuser is made in Office 365 and we iniate a mailbox move. Then in the resource forest we have a Mail Contact in Ex2010 and a disabled account in AD. 1- How can we get rid off these migrated users? 2- When can we install 2016 in the account forest, can it do any harm when we install it next to Ex 2010 which is in the other forest(ofcourse we have a trust) 3- How to move on from here? Thanks for your support! (sorry, I also posted this by accident in the Office 365 community. I realized later it should be here?)
Exchange 2010 SP3 Upgrade failing Organization Checks
Hi I'm working on a project to remove the last Exchange 2003 server from the Exchange 2010 organization, which has now completed. Next phase is to introduce an Exchange 2016 Server into the existing 2010 org and setup for coexistence prior to migration. The main issue is that I need to upgrade all Exchange 2010 SP1 servers to SP3 to support Exchange 2016 and in production this is failing the Organization checks. The upgrade worked fine in UAT, which uses the same AD functional level (Windows Server 2008R2) and consists of all Windows Server 2016 DCs, same as production. Since starting to update production 2010 servers I receive the following message after the Organization checks fail: I have tried to update to SP2, which was a mission to find the installer as it is ancient (same as Exchange 2010 I know!), but to the same result and have tried everything to resolve the issue but to no avail. Current Prod AD Schema version = 87 (Windows Server 2016) Exchange Schema rangeUpper = 14726 Current UAT AD Schema version = 87 (Windows Server 2016) Exchange Schema rangeUpper = 15334 I have read that the solution may be to add a legacy Windows Server 2012 as there is a problem with SP3 updates on Server 2016 DCs, but it worked on these fine in UAT so I'm rather perplexed as to this being the only solution. Can anyone give me further advice as to what could be attempted next please? - Before we bite the bullet and introduce a legacy 2012 server just to upgrade to Exchange 2010 SP3 and then remove as soon as done, assuming it works!! Please any suggestions would be greatly received? Thank you MB
