![]() (no more receive computer, pull out of box, image, put back in box, ship to user. HUGE savings in setup time and headaches. It is absolutely worth upgrading to Win10 pro - that is how we are doing the AutoPilot deployments. IF you have CIFS/SMB shares then you have to have hybrid joined machines (AzureAD, On-prem AD) - then you have to watch out for GPO conflicts with Intune (GPO used to win always, but they may be changing that now). Network shares - IDEALLY migrate everything to OneDrive/SharePoint then local file sync is a snap. Intune has a lot of Compliance and Configuration policy options that will likely do what you need, though sometimes we have to resort to OMA-URIs for specific settings. You can have the user Add Work/School account (AzureAD Join) - this MAY be achievable with Win10 Home. You can have the user AzureAD enroll manually (I think MUST be on pro or higher) We went with AzureAd Enrolled using Autopilot (computer vendor creates XML of systems on build (win10 Pro), uploads to Azure, ships computer direct to end user, end user logs in with AzureAD credentials and system fully provisions from Intune - Win10 Ent upgrade, Security Tools, OneDrive file sync. Our MS license grants us Win10 Enterprise but we had several groups that went BYOD and bought Win10 Home. ![]() We ran into the same issue and we ended up bumping everyone up to Win10 Pro at a minimum.
0 Comments
Leave a Reply. |