я тебе еще раз говорю, идеи должны исходить от из их бизнес требований, которые ты, как архитектор, должен из потока сознания вычленить и понять, что же им реально надо
Вот мне заказчик отписался:
Here's what I'm thinking of:
Provisioning: we have done this one so I'm not sure if there's more. Can we provision remotely? E.g. "cloud MDT" Or would that just be a reset? Can we do it remotely and let the computer "come back" to Intune? (vs re-register manually)
Apps: what's being installed, what's not working. Is it normal, or should we do something about it?
Policies: same! Although I hunk its working fine
Endpoint protection: status, actions on infection/suspected infection
Inventory: checking what's installed, hardware available
Overall: anything else that can help us with troubleshooting. Remote access, logs, etc. Does it make sense to go to Intune or is it better to go outside?
You bring a good point about AD. My view is to leave on-premise only for what we still nerd there (mainly RDS), but assume the computers will not register with on-premise, only cloud. Admin PCs may, but that's not even 100% necessary (they could connect remotely to domain joined computers). At some point this starts going outside of Intune's scope, of course.
I think I covered the main areas that Intune covers. Do you believe there is any other area I'm leaving out of this list?