2013
275 TopicsArbitration Mailboxes not available
I have an environment with an Exchange 2013 (15.00.1497.048) and an Exchange 2019 CU14 server installed. The new 2019 server appears to be fully operational with the exception of the system mailboxes, which means I cannot migrate the mailboxes off the 2013 server. What I have tried to resolve this issue: Re-run /PrepareAD - This did create the AD accounts; however, the system mailboxes were not created and when attempting to enable them getting the following error: "The user's Active Directory account must be logon-disabled for linked, shared, or resource mailbox." Checked for disabled or soft-deleted mailboxes - none that match the GUIDs for the system mailboxes Deleted the system accounts from Active Directory and re-ran /PrepareAD. It ran successfully and created the AD accounts; however, still getting the same error when attempting to enable the mailboxes. Looking for any insight into how to resolve this issue.37Views0likes1CommentInstall 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 helpSolved68Views0likes1CommentUser'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 settings20Views0likes1Commentuninstall 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 helpSolved36Views0likes1CommentHow to Backup OST Files from Outlook to Live Exchange?
In recent days I have been sitting in front of my Desktop and trying to convert outlook ost files into Live exchange but it seems so difficult because for some reason my ost files are not converted into PST and without conversion, I can not export the files on the Live Exchange server. If someone knows the solution then please answer it.73Views1like1CommentQuestion about outgoing traffic.
Hello! Colleagues, There are two MS Exchange 2013 servers located on different sites, united in a DAG. Please tell me, is it possible to configure certain mailboxes to send outgoing messages only from the second server? Logically no. I did not find such functionality in the transport rules. Thank you. Regards , Max.29Views0likes1CommentCorrect path in SharedWebConfig.config for ClientAccess
Hello, community. After installing the next update, I received a non-working OWA. As you may know, Microsoft recommends that you create the file SharedWebConfig.config in ClientAccess folder again using the utility DependentAssemblyGenerator.exe. But, when command DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%\bin" -exchangePath "%ExchangeInstallPath%\ClientAccess" -configFile "%ExchangeInstallPath%\ClientAccess\SharedWebConfig.config" done, I got the next I am getting the following content in the file <codeBase version="4.2.0.0" href="file:///C:\Program Files\Microsoft\Exchange Server\V15\\bin\AntiXssLibrary.dll" /> or <codeBase version="1.1.5274.28150" href="file:///C:\Program Files\Microsoft\Exchange Server\V15\\bin\AsyncDnsManaged.dll" /> So I have a question. Why does there appear another \ character in the path before \bin? And when I check the server status with script from PSGallery, one of the items is that the file SharedWEbConfig.config is missing. Could this be related?1.4KViews0likes3CommentsExchange server transport logs reading tool
Hi Exchange Brain Trust, I need to get rid of any inactive IP addresses out of my SMTP receive connectors in Exchange 2019 server (Hybrid environment). Is there a free tool to monitor/study transport logs which provides a good UI as opposed to notepad readings? Appreciate any suggestions. Thank you!144Views0likes1CommentHelp with migration concepts
Good morning to everyone. I have a couple of questions that I hope you can help me resolve. These questions are related to Exchange Server 2013 (I know that this product is out of support and that is why we are migrating it to Exchange Server 2019). This is my scenario: I have a main site with 2 Exchange Server 2013 CU10 servers, I have a site with 1 Exchange Server 2013 CU23 server, I have another site with 1 Exchange Server 2013 CU23 server. The main idea is to migrate all mail servers to Exchange Server 2019. These are the questions: 1. Is it possible to install a new server with Exchange Server 2019 on the main site without upgrading the remaining servers with Exchange Server 2013 to CU23? 2. What will happen to the mail flow after installing the new server with Exchange Server 2019? Will the main server with Exchange Server 2013 continue to manage the internal and external mail flow? Or will the new server with Exchange Server 2019 manage the mail flow? 3. In case the new server with Exchange Server 2019 is the one that manages the mail flow, is there a possibility that the server with Exchange Server 2013 will manage the mail flow until the migration is finished? Thank you for your time and collaboration217Views0likes0CommentsExchange 2019 and Outlook 2016 and above
Dear Community, I have Exchange 2019 CU 12 running on Windows Server 2022. The problem that we are facing is with Outlook 2016 and above clients that fail when configuring their email profile for the first time. We do not have the problem with Outlook 2013 clients, ware Autodiscover works without problem. The Outlook 2016 and above prompt for username and password, however, no matter how often I provide the right credentials, I'm prompted again and again. Strangely, Outlook 2013 does not have this problem. When I right click on Outlook with CTRL and run Test Email AutoConfiguration on Outlook 2013 no problem, all URL are correct, when I run against existing Outlook 2016 client I am prompted for credentials. Can anyone explain why Outlook 2016 and above have Autodiscover issues and Outlook 2013 does not? Thank you b.lSolved452Views0likes3Comments