Question 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.
Adding member to DAG error
Hey all, Details first: 2 x Server 2022 each with Exchange 2019 CU13, different subnets. I created a DAG. Created a DAG network with the subnets the two servers are in. I added one server as a member no worries. When attempting to add the second server I get this error. A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "AddClusterNode() (MaxPercentage=12) failed with 0x80070005. Error: Access is denied". [Server: first-server.domain] Looking through logs there is no indication what access is being denied where. I can see a thousand other queries online with this exact error but none of the suggested solutions seem to solve my issue. The share and folder security on the Witness server shared folder has permissions set for the Exchange Trusted Subsystem. I added permissions for the 2 exchange servers to the DAG computer object as per somewhere online. Our existing 2013 servers are in a dag and are all on the same subnets, so no firewall or network connectivity issues. Anyone have any other theories? thanks jc
Upgrading Exchnage DAG member from CU10 to CU23
Upgrade failed ad step 13 Client Access role: Client Access Front End service FAILED The following error was generated when "$error.Clear(); $FEOWAVdirIdentity = $RoleNetBIOSName + "\OWA (Default Web Site)"; $FEOWAVdir = get-OwaVirtualDirectory -Identity $FEOWAVdirIdentity -Dom ainController $RoleDomainController; if ($FEOWAVdir -ne $null) { Set-OwaVirtualDirectory -Identity $FEOWAVdir.Identity -ExternalUrl $ FEOWAVdir.ExternalUrl -InternalUrl $FEOWAVdir.InternalUrl -ExternalAuthenticatio nMethods $FEOWAVdir.ExternalAuthenticationMethods -BasicAuthentication ([Convert ]::ToBoolean($FEOWAVdir.BasicAuthentication)) -WindowsAuthentication ([Convert]: :ToBoolean($FEOWAVdir.WindowsAuthentication)) -DigestAuthentication ([Convert]:: ToBoolean($FEOWAVdir.DigestAuthentication)) -FormsAuthentication ([Convert]::ToB oolean($FEOWAVdir.FormsAuthentication)) -LiveIdAuthentication ([Convert]::ToBool ean($FEOWAVdir.LiveIdAuthentication)) -OAuthAuthentication ([Convert]::ToBoolean ($FEOWAVdir.OAuthAuthentication)) -AdfsAuthentication ([Convert]::ToBoolean($FEO WAVdir.AdfsAuthentication)); } " was run: "Microsoft.Exchange.Data.InvalidObjectOperationException: Pro perty DefaultDomain can't be set on this object because it requires the object t o have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6. 5.6500.0). at Microsoft.Exchange.Data.PropertyBag.set_Item(PropertyDefinition key, Objec t value) at Microsoft.Exchange.Data.Directory.ADPropertyBag.set_Item(PropertyDefinitio n key, Object value) at Microsoft.Exchange.Data.ConfigurableObject.set_Item(PropertyDefinition pro pertyDefinition, Object value) at Microsoft.Exchange.Management.SystemConfigurationTasks.WebAppVirtualDirect oryHelper.UpdateFromMetabase(ExchangeWebAppVirtualDirectory webAppVirtualDirecto ry) at Microsoft.Exchange.Management.SystemConfigurationTasks.WebAppVirtualDirect oryHelper.FindWebAppVirtualDirectoryInSameWebSite[T](ExchangeWebAppVirtualDirect ory source, IConfigDataProvider dataProvider) at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOwaVirtualDirect ory.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fun cName, Action func, Boolean terminatePipelineIfFailed)". The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
Exchange 2016 DAG to 2019 DAG
So let's do this! I have an Exchange 2016 2 server DAG environment and we are wanting to upgrade it to an Exchange 2019 DAG environment. With all the wonderful press Microsoft released about the amazing safety you get from a DAG environment, there seems to be very little on how to upgrade it to 2019! Please help! Can it even be done? TheExchange Deployment Assistant is very vague about it, I have 2 questions: 1) Can you migrate from a 2016 Exchange DAG to a 2019 Exchange DAG? 2) If so, how? I've gone through theExchange Deployment Assistant. I have the 2 new 2019 Servers setup, but I can't join them to the existing DAG and I get an error when I try to create the new DAG for 2019. What's the next step? Thank you for any assistance you can give.