Announcing a Co-management with Microsoft Intune and System Center Configuration Manager AMA!
We are very excited to announce an upcoming opportunity to 'Ask Microsoft Anything' (AMA) about Co-management with Microsoft Intune and System Center Configuration Manager! The AMA will take place on Thursday, October 19, 2017 from 9:00 AM to 10:00 AM Pacific Time in the System Center AMA space. Add this event to your https://aka.ms/Co-managementama/invite.
Greater visibility of errors
Are there any plans to give the community greater visibility to errors that we see in stand alone intune? e.g instead of seeing that an error occurred. It would be nice to see what the error was, and what service is affected within the tenant rather than just a generic error code. If we could have access to reporting tools and logs, then it would greatly help speed up the process when it came to troubleshooting issues that arise from time to time.
Migration tool
hi, I heard of about this tool : https://docs.microsoft.com/en-us/sccm/mdm/deploy-use/migrate-import-data , which is supposed to migrate the SCCM content to Intune. You say that it migrates policies/packages/CIs/VPN or Wifi profiles, and stuff like this : I understand there are some limitations, explained in the documentation, but are you not afraid that vast majority of users will not be able to use this tool in a prod way, because of the various current Intune limitations like no PS script support yet available, not all GPOs are existing in the "LocalSecurityPolicies" CSP, packages that are EXE-based or contains several MSI files, and so on... ?
Co-management support many relationships
Will co-management support many to many relationships ? Ie. if we have a prod and dev azure tenant can we manage devices from both of those tenants with a single config client? And Vice versa, if we have numerous SCCM hierarchies, can devices in different SCCM hierarchies be managed by disparate intune instances?SCCM/Intune
If we moved to an integrated SCCM/Intune platform, would we be limited by features within the SCCM environment in regards to features we can implement? or has the intune features cycle and the SCCM integration aligned better so that the SCCM/Intune integrated environments isn't lagging behind the stand alone intune platform? Would moving to the integrated platform provide us with better logging for troubleshooting diagnosis for example or give us better visibility as to when there are issues in the environment?
Is co-management (or hybrid) required for Azure-joined machines to access domain services?
Our company is using ZenWorks for our Windows 7 machines. We have begun deploying Windows 10 machines under Intune MDM (joining to Azure) with great success so far. We do not have SCCM in place (yet). However, our biggest pain point right now is Windows 10 users accessing on-prem domain services like printing, file share, etc. These services are not going to the cloud anytime soon. As we all know, we cannot domain join a machine that is already Azure AD joined. Is co-management required for Windows 10 MDM'ed machine to gain access to these services? Or can we leverage AAD Connect to solve this issue?
