Problems after upgrade to CU14
Hi, I'm in the process of migrating from Exchange 2013 CU23 to Exchange 2019. I installed Exchange 2019 CU13 on Win2022 Server, in coexistence with our 2013 and everything was looking good. Before starting with the testing to route emails through 2019, I checked that CU14 was released recently, so I download/install the CU14 in upgrade mode (with the no EP flag) to have the last build, and now I'm having problems with virtual directories, mailboxes, and so ON. Already run the healtchecker powershell scripts and nothing out of the ordinary. Some of the problems I'm having: 1. When I clic on the 'authentication' tab in any Virtual Directory (ECP, OWA, EWS) I got this error: "The task wasn't able to connect to IIS on the server <FQDN>. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable." The other tabs don't throw me any errors, but almost all options are greyed-out. 2. In SERVERS > DATABASES, when entering the properties of any Database that are on the new EX2019, I got this error: 'Exchange can't connect to the Information Store service on server <FQDN>. Make sure that the service is running and that there is network connectivity to the server.' I cannot create a new Database neither and the status of the currents 2019 Mailbox databases says Uknown and BadCopyCount = 1. 3. SERVERS > CERTIFICATES: Cannot see any Cert here for the EX2019. The error I get: "Cannot connect to the remote procedure call service on the server named <servername>. Verify that a valid computer name was used and the Microsoft Exchange Service Host service is started." Already check: - Binding of the Certificate 'Microsoft Exchange 'on the BackEnd and our Public Certificate on the Frontend Server. - All Exchange Services are up and running. - Restart of IIS. It appears that is something with permissions and/or with IIS that breakdown after the installation, but still don't know what it is. Al things related to the 2013 environment appears to be normal and functioning. according. Something I noticed, on the Certificate error it says the name of the server, and in the other errors, it says the FQDN of the server. Please guide me here, what could be the problem and what to check/confirm. Thanks in advance.Upgrade from Exchange 2013 CU23 to Exchange 2019 CU14
Hi all, I'm in the process of upgrading or Exchange infrastructure from 2013 CU23 (Hybrid) to 2019 CU 14. A really long time without making Exchange Upgrades... so just want to confirm some things. Doing just the initial Setup/installing of Exchange Server 2019 on our AD does not break anything with the current Exchange 2013 config and connections from users right? to that point there are no changes for the users and it's safe? just confirming. I'm using the 'Exchange Deployment Assistant' for this upgrade, and I assume that installing exchange 2019 doesn't brake anything of the current config because everything will still be pointing out to EX2013 until I change it, but want to make sure. Any additional tips, is welcomed for the upgrade process. Thanks in advance.
Exchange 2019 CU14 PowerShell and ADDriver log history issues
We have two Exchange 2019 Standard servers in a DAG and after updating from CU12 to CU14 one of those servers no longer logs PowerShell or ADDriver history. For example in the Application Log we see: Event ID 6003 Source MSExchange Common - RpsCmdletLogs: Failed to create the log directory: C:\Program Files\Microsoft\Exchange Server\V15\Logging\CmdletInfra\LocalPowerShell\Cmdlet because of the error: Access to the path 'C:\Program Files\Microsoft\Exchange Server\V15\Logging\CmdletInfra' is denied.. Logs will not be generated until the problem is corrected. Event ID 6003 Source MSExchange Common - ADDriver: Failed to create the log directory: C:\Program Files\Microsoft\Exchange Server\V15\Logging\ADDriver because of the error: Access to the path 'C:\Program Files\Microsoft\Exchange Server\V15\Logging\ADDriver' is denied.. Logs will not be generated until the problem is corrected. These events do not appear on our second Exchange server. The issue is with the first server to be updated and they were both updated from the command line as per this article without any errors: http://www.alitajran.com/install-exchange-cumulative-update I have checked security permissions are the same for both servers for the paths mentioned. Has anyone seen this or have any ideas how to troubleshoot ? Thanks DM