You can deploy AirPrint settings for Mac and iOS – https://docs.microsoft.com/en-us/intune/air-print-settings-ios-macos
You can configure some printer settings under device restrictions for Windows 10 – https://docs.microsoft.com/en-us/intune/device-restrictions-windows-10
But I’m hearing from a few people that this still doesn’t really help users get to local printers, and that seems the original intent. (@Henrik, if you’re getting this, please weigh in!)
We won’t call this one complete. I’m switching this to “noted”, meaning we know you want it. Thanks again for the feedback!
People will slowly go away from SMB-based printing, and SMB and Domain Controllers will soon die (AD-joined devices will be replaced by AAD-joined devices)
So please add also an option to deploy printers for Win10 desktop devices...over your new MS Hybrid Cloud printing.
We use badge-enabled printers (we have few hundreds of them over the world), so it does not really matter anymore to which printer the user is sending his job (the job is retrieved by the printer once you show your badge physically to the printer, in order to save paper...). So most likely, with Hybrid Cloud printing, we will have/offer 1 unique printer queue, and this way, we (IT admins) do not need to continuously maintain an insane amount of print queues on the enduser devices.
Why not use directly the CSPs offered by MS, and configure entries in Intune using custom OMA-URIs? (https://docs.microsoft.com/en-us/windows/client-management/mdm/configuration-service-provider-reference)
I believe this feature request has now made obsolete :
In Win10 RS2, Ms made available the "Update/EngagedRestartSnoozeSchedule" key (see https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-engagedrestartsnoozeschedule), so that nobody will have a forced restart in the middle of his presentation, as the user will have the choice to postpone temporary the reboot.
Marking as noted, meaning we are aware of the request and it’s been discussed. If we take any action, we’ll update the status,
This feature request should be also valid for PowerShell scripts for Win10 devices.
Currently, I have a very bad experience when you want to deploy new PS scripts to already-enrolled Win10 desktop devices (bad experience means "seems doesn't work at all on my side"...)
This is not really a feature request. It already exists from what I understand, but you just have to open your wallet ;-).