Thanks for the comments, just a few questions to the gallery.
What platform is this issue with. I’m only seeing IOS devices in your comments, so wanted to double check.
Also, are you having this issue with shared devices or just re-deployment? Unclear from all the comments. Do you want to keep all installed apps on the devices? Depending on your platform, you should be able to already do this for shared devices.Andrew commented
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!
In case you haven’t seen it, at Ignite in September we introduced the concept of co-management with Configuration Manager and Intune both managing the same device. https://channel9.msdn.com/Events/Ignite/2016/BRK2138-TS
If you already have ConfigMgr, it makes sense for now to consider this configuration to address app deployment.
Today we released support for assigning Office 365 ProPlus apps to devices that run Windows 10. Does that count as “adding predefined deployment packages”? Or is there something we’re missing here? If you think we covered it, I’ll mark it complete.