Windows 10: Azure Hybrid Connection manager is using up all ports

Azure Hybrid Connection manager is using up all ports until it crashes TCPIP on the server.When I run a netstat this is an example of what I see. [Microsoft.HybridConnectionManager.Listener.exe] TCP 192.168.0.5:61099 52.242.20.174:https CLOSE_WAIT 8220 [Microsoft.HybridConnectionManager.Listener.exe] TCP 192.168.0.5:61100 40.86.221.200:https CLOSE_WAIT 8220 [Microsoft.HybridConnectionManager.Listener.exe] TCP 192.168.0.5:61101 40.69.97.99:https CLOSE_WAIT 8220 [Microsoft.HybridConnectionManager.Listener.exe] TCP 192.168.0.5:61102

:)

 

Hybrid Azure AD Join device didn't show managed by "Org name" and unable to enable co-manage

I've got a few device with a weird issue where it's perfectly Hybrid Azure AD Join but inside Work or School Account > Info didn't show Managed by any organization and the last sync date.

Our environment enables co-management so all devices must be Hybrid Azure AD Join and co-managed.

Please help to advise if anyone encounters this issue. Rejoin on-premise domain, re-enroll to Azure AD and reinstall the MECM client didn't work.

 

Azure and on-prem (hybrid) and NTP best practices

Hello all

For those of you in an Azure hybrid environment (i.e. on-prem and Azure with DCs in each) did you make any changes to NTP on Azure machines or are you using the out of box configuration when using NTP? I assume people are leaving the default for all machines in Azure and following best practices for on-prem and pointing to the PDC? Can you please advise? What is best practice?

 

Azure AD Hybrid environment with on prem

I have an existing domain in PA but I want to avoid purchasing a lot of equipment to start a domain in MIA. If I were to choose Azure AD instead on purchasing an On-prem and a server license; purchase all the equipment needs for a on-prem setup isn't neccessary, I can create a Hybrid Environment where I have Azure AD for any other location and an on-prem server in one?