Finally!!! I hate to have a Hybrid environment but we don't have a choice for now.. so this solution comes to the rescue. I am looking forward the demo :)
Informative video. Thanks for that. By the way, on your last Autopatch video you promised a follow up video. Are you still intending to do this? Thanks again!
Thanks! Very true, I definitely did promise to go through some of the new features, and completely forgot about it. I'll get started on that as soon as I get back from the MEMS conference!
Thanks, - All our Azure AD-Connected devices has the Join Type "Azure AD registered", I belive the Join Type needs to be "Azure AD Joined" in order to be able to enroll them in Intune. I now know this is not changed with the "Intune Connector for Active Directory" ;-) - Do you know how do I change the jJoin Type ?
No, it doesn't matter whether the device is Azure AD registered or Azure AD joined. Azure AD registered: It is registered in Azure AD and you log in to the device with local user and you get access to corporate data with Azure AD credentials. You can enroll it in Intune by Company Portal and it will be a personal device. Azure AD Joined: You log in to the computer with an Azure AD account. I will be a corporate device.
intune connector is for joining computers to your active directory, while certificate connector acts like intermediate PKCS server between your on premise certification authority server and intune - that will give you option request certificates for your cloud devices from your on-prem CA templates on behalf of the server with connector installed.
Very simply put, thank you! Gotta appreciate the straight forward answers!
Yea, we are in that situation right now! We are building autopilot computers that need to join onprem AD as well as intune
Finally!!! I hate to have a Hybrid environment but we don't have a choice for now.. so this solution comes to the rescue. I am looking forward the demo :)
This video is perfect.
Thank you!
Informative video. Thanks for that. By the way, on your last Autopatch video you promised a follow up video. Are you still intending to do this? Thanks again!
Thanks! Very true, I definitely did promise to go through some of the new features, and completely forgot about it.
I'll get started on that as soon as I get back from the MEMS conference!
I wonder do we need device writeback with this in cloud ad connect ???
Thanks, - All our Azure AD-Connected devices has the Join Type "Azure AD registered", I belive the Join Type needs to be "Azure AD Joined" in order to be able to enroll them in Intune. I now know this is not changed with the "Intune Connector for Active Directory" ;-) - Do you know how do I change the jJoin Type ?
No, it doesn't matter whether the device is Azure AD registered or Azure AD joined.
Azure AD registered: It is registered in Azure AD and you log in to the device with local user and you get access to corporate data with Azure AD credentials.
You can enroll it in Intune by Company Portal and it will be a personal device.
Azure AD Joined: You log in to the computer with an Azure AD account. I will be a corporate device.
What are the differences between Intune connector and Certificate Connector for Intune
intune connector is for joining computers to your active directory, while certificate connector acts like intermediate PKCS server between your on premise certification authority server and intune - that will give you option request certificates for your cloud devices from your on-prem CA templates on behalf of the server with connector installed.
@@nex7053 wouldn’t ad connector do the same function as Intune connector?