13
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Oct 2023
13 points (81.0% liked)
Sysadmin
7679 readers
1 users here now
A community dedicated to the profession of IT Systems Administration
No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
!lemmy@lemmy.ml
!lemmyworld@lemmy.world
!lemmy_support@lemmy.ml
!support@lemmy.world
founded 1 year ago
MODERATORS
So aside from using machine wide installers and ensuring that users are licensed for those products, you also need to setup enterprise roaming.
By the way, intune policies if they aren't changing don't take 8 hours to propogate to the machine, they take hours to propogate world wide like group policy takes hours to propogate in international sized ad forests.
So if you've got your intune policy set to auto sign in one drive and teams and whatever apps, assuming all your devices are intune registered, that setting doesn't take hours to get to the machine. It's immediate on first login. If you change that setting, it's some hours to get it across every single machine. By the way in my experience, generally 80% of the time with a forced sync from the company portal app you should deploy with intune, it's practically as fast as gpupdate. There's a few times where you need to patiently wait 15 minutes but you can see that if you name your configuration profile like (v12) and you'll see it's either still (v11) or immediately (v12) and you stuffed a setting and it's still not working.