Migration Hybride 2013 M365

Question

Hello, i'm setting an hybrid environment Exchange-M365, I migrated an user to M365, but he can't access the calendar of someone on-premises, i think the error comes from the HCW that don't really work well. Indeed i have an error “HCW0 - Could not find property ‘DomainName’ in object ‘Deserialized.Microsoft.Exchange.Data.Directory.SystemConfiguration.AuthServer’.” when i launch the Hybrid configuration Wizard. I searched  everywhere, tried to recreate the authServer but it still don't work, can someone please help me? 

Thanks for your help

My Exchange is currently 2013 but I plan to migrate 90% of my mailboxes on 365 and 10% of my mailboxes on exchange 2019

Answer 1

Hi @Daniel
Thank you again for following up. 

After doing some additional research, I’m happy to share a clearer explanation of what I found. 

To begin with, you will need to enable Partner Applications. This step is important because it allows secure authentication and communication between your on‑premises Exchange Server and Exchange Online. One key Partner Application involved in hybrid scenarios is the application ID 00000002-0000-0ff1-ce00-000000000000, which represents the Office 365 Exchange Online hybrid application. 

 

Reference: Exchange Server Security Changes for Hybrid Deployments | Microsoft Community Hub 

Before enabling it, you will also need to create a new AuthServer. This ensures that the Partner Application trusts the authorization server, as described in step 1 and step 2 of Configure OAuth authentication between Exchange and Exchange Online | Microsoft Learn 

 

There is an important point I would like to highlight. Only Exchange Server 2016 CU23 and later versions support the dedicated Exchange Hybrid Application that uses the Partner Application ID 00000002-0000-0ff1-ce00-000000000000. 

This is outlined in Dedicated Hybrid App: temporary enforcements, new HCW and possible hybrid functionality disruptions… 

 

With this in mind, the error you encountered regarding the property “DomainName” occurs because the New‑AuthServer command did not populate that value correctly. As a result, the Partner Application is unable to complete the authorization process, which ultimately causes the Free/Busy feature to fail. 

To resolve this, upgrading to Exchange Server 2019 CU14 is the recommended path. With this version, the Hybrid Configuration Wizard can automatically establish the required authorization trust between your on‑premises Exchange environment and Exchange Online. Once that trust is created, the Free/Busy feature should work as expected. 

I hope this provides clearer insight into the issue. 

If this information answers your question, please consider marking it as Accepted Answer or giving it an upvote so other users facing a similar situation can easily find this guidance. 

Thank you for your time. 

Answer 2

Thanks Vergil, but do you think its the reason why the calendar is not accessible ? because i don't see anything when i search on internet

Answer 3

Hello Austin, thanks for the time and the answer.

The command Get-authServer gives me indeed Evosts and ACS, but there is no domainname attributes, it means i need to migrate to Exchange 2019 CU14 and then migrate to M365 to make the hybridation works?

Thanks,

Answer 4

Hi @Daniel 

Thanks for reaching out to the Microsoft Q&A forum.  

Based on your description, it appears that the Hybrid Configuration Wizard was unable to create the required AuthServer objects, which is why you are seeing the error message. To verify this, you can run the following PowerShell command: 

Get-AuthServer 

If the command returns no output, it indicates that the AuthServer objects are missing. In that case, you may consider creating them manually using these examples: 

New-AuthServer -Name "WindowsAzureACS" -AuthMetadataUrl "https://accounts.accesscontrol.windows.net/<your tenant initial domain>/metadata/json/1" 
 
New-AuthServer -Name "evoSTS" -Type AzureAD -AuthMetadataUrl "https://login.windows.net/<your tenant initial domain>/federationmetadata/2007-06/federationmetadata.xml"

 

Additionally, based on my research, Exchange Server 2019 CU15 (the latest CU) does not support coexistence with Exchange Server 2013. 

The supported upgrade path from Exchange Server 2013 to Exchange Server 2019 is shown in the image below:

Legacy upgrade – the traditional way of moving to a new major version of Exchange Server. It requires introducing the newer server into the organization, moving all mailboxes and resources from older servers to new servers and uninstalling the old servers. 

 

With that in mind, if you are planning to upgrade to Exchange Server 2019 in the near future, you may consider proceeding with the upgrade to help address the HCW error “Could not find property ‘DomainName’”. The -DomainName parameter in New‑AuthServer is supported only in Exchange Server 2016 CU18 or later and Exchange Server 2019 CU7 or later. Having a supported version in place can allow the HCW to create the AuthServer properly and help prevent issues where online users are unable to access on‑premises calendar information. 

 

References: 

• Get-AuthServer (ExchangePowerShell) | Microsoft Learn 
• New-AuthServer (ExchangePowerShell) | Microsoft Learn 
• Upgrading your organization from current versions to Exchange Server SE | Microsoft Community Hub 
• Can't view Online user free/busy status in Exchange Server 2019 and 2016 - Microsoft Support
• Exchange 2013 servers can't coexist with Exchange Server 2019 CU15 [E19E15CoexistenceRequirement] |…

I hope this additional context helps you move forward with your migration. If you have any updates or further questions, please feel free to reply. 

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".         

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

 

Answer 5

The error message you are encountering, "HCW0 - Could not find property ‘DomainName’ in object ‘Deserialized.Microsoft.Exchange.Data.Directory.SystemConfiguration.AuthServer’,” suggests there may be an issue with the configuration of the Hybrid Configuration Wizard (HCW) related to the authentication server settings.

To troubleshoot this issue, consider the following steps:

1. Verify Auth Server Configuration: Ensure that the authentication server is properly configured in your environment. You may need to recreate the authentication server settings if they are incorrect.
2. Check for Updates: Make sure that your Exchange Server 2013 is fully updated with the latest cumulative updates and patches, as updates can resolve known issues.
3. Run the HCW Again: Sometimes, simply rerunning the Hybrid Configuration Wizard can resolve transient issues. Ensure that you follow the prompts carefully and check for any errors during the process.
4. Review Logs: Check the HCW logs for any additional error messages that might provide more context about the failure. This can help pinpoint the exact issue.
5. Consult Documentation: Refer to the Microsoft documentation for any specific configurations or prerequisites that may have been overlooked.

If the problem persists, you may want to reach out to Microsoft support or consult the Exchange TechNet forums for further assistance.

---

References:

• HCW8004, HCW8009, HCW8016, HCW8017, HCW8029, or HCW8030 error when running the HCW
• HCW8034 or HCW8057 error when you run the Hybrid Configuration wizard