Automatically deploy Intune PC Client for Azure AD joined computers
Not entirely sure if this belongs here, or in Azure AD, however....
From reading the documentation, it appears that the for Windows 10 Enterprise PCs, they can be managed automatically upon joining the Azure AD domain as mobile devices only.
For corporate issued PCs, it would aid SMBs greatly if adding the Intune PC Client can be done automatically upon joining the PC to Azure AD. This would lower IT department's involvement in issuing new devices, so that company administration could just buy (for example) a Surface Pro and hand it to a new employee, along with the Azure AD/Office 365 credentials.
On October 16, 2019, we announced that support for the Intune PC software client (PC agent) will end on October 15, 2020, along with the Silverlight-based Intune Classic console. You should plan to move to use the MDM channel to manage your Windows PCs as soon as possible. Learn more: https://aka.ms/intune_silverlight_console
Charles Roller commented
I agree with Michael, this should be closed. The intune agent has never been a part of the new experience in the Azure portal and I do not believe there are plans for it to be. The agent should only be used for Win7 devices, and even then those should be migrated to Win10
Michael Mardahl commented
The new Devicemanagement portal offers all you need now.
I would say that this request should be closed, as Intune does fulfill this now,
Chris King commented
Good news from Ignite conference.. The Windows 10 MDM version of Intune management will soon allow the deployment of MSI, EXE, and MSP files. Pair this with Windows Autopilot and Microsoft has almost fulfilled this request.. https://microsoftintune.uservoice.com/forums/291681-ideas/suggestions/17309767-extend-mdm-msi-deployment
Finally ready to chew on BYOD but we need a actual easy way to deploy our things which includes intune please fix
Craig Debbo commented
We use Azure intune. We can't do an intune join unless our PCs are in-joined from their on-prem AD domain. So, we unjoin our local domain, enroll in inTune with a enrollment management account, then re-join our local domain.
We already have the settings to 'auto' join AAD. Would be nice if there was an extra step where the PC just auto-joined inTune too (while being locally joined to AD)
Screwy or broken? Anyways, please streamline this whole process. By comparison, iOS devices are enrolled when we order from Apple, and Chromebooks are enrolled immediately after we hit some key combo and log in with a google domain account.
Mark ter Weele commented
We want also automatically deploy Intune Client for computers who joining to Azure AD. Is there already a solution? It's a must have in our organization.
Aaron Marks commented
Agree with James... we really need all the PC-enrolled functionality from the classic Intune to be rolled over to Azure AD joined devices. It would be great if we got all of this (and more) without the need for an agent.
Tim Wootton commented
How about intune actually recognising Azure AD connected PC's, or even better if we deploy an Azure AD Virtual machine to do Group Policy management in Azure AAD, allow us to use this (with the full intune agent installed on the pc) to deploy Group Policy settings to Azure AD connected devices. The Intune Windows management capabilities are woefully lacking.
James Schwarzmeier commented
Or even better...let us manage all Azure AD-joined computers AS computers without the need for a separately installed client.
You have all my votes. Wow, this request dates back to August 2015... @Microsoft: Are you actually still developing Intune? We have just started contracting EMS and you are squeezing a **** lot of money for a product that doesn't address such salient cases within more than 18 months...
Alan Dooley commented
The main reason people want the Intune agent over using MDM is the greater flexibility in running MSI with transforms/msp patches or .Exe. if this was supported via MSN then needing the client would be less relevant.
Microsoft should just start including some form of Intune connector pre-installed in Win 10 ENT. If they want to push it as a management option, have it already on PCs and ready to go.
Better if the client isn't needed, but currently it is. It's bonkers that this is released as anything other than beta.
This provides some useful insight - https://social.technet.microsoft.com/Forums/en-US/71c182a7-3509-48cd-bfb8-3ac23d8dbf5a/maddening-windows-10-and-intune-problem?forum=microsoftintuneprod#73091780-a12d-4630-b38d-126bfe863c93. (Now over 12 months old at the time of posting this).
Chris Mills commented
Only in early test phase at the moment but we've had some success with this:
Has anyone found a solution for this yet?
Jan Ketil Skanke commented
The MDM API gives you even more flexibility for management. All the policies, certficate distribution, wifi setup, conditional access and then some is not available if you are using the Intune legacy agent insted of managing Windows 10 through the MDM Channel.
I suggest you all read up on what you get by doing this, you really dont need the agent.
Nima Gharib commented
I just tried Peter's link, and you're right "Anonymous". It just deploys the Company Portal through Windows Store.
Pretty useless not being able to install the full client on a Windows 10 device automatically. Why would anyone ever want to manage a computer as a mobile device. What are the gains.
J Crowley commented
Peter, this doesn't fix the issue as far as I can see. That's deploying Windows Store apps, not the InTune client?
Peter Selch Dahl commented
I think they fixed your request with this update:
/Peter Selch Dahl
The Intune client installation doesn't work automatically:
So please vote for this "idea"!!