Sysadmin

7679 readers

25 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

DarraignTheSane@lemmy.world

00Lemming@lemmy.world

L3s@lemmy.world

Getting Azure joined desktops with multiple users working. (lemmy.world)

submitted 1 year ago by HC4L@lemmy.world to c/sysadmin@lemmy.world

6 comments fedilink hide all child comments

Hey guys,

We are struggling with our Azure joined machines used by multiple people during the day. Each time they log on to a new machine we get a helpdesk call for us to set up OneDrive / Sharepoint libraries synchronization in the client.

We know Intune can do this but Intune settings can take up to 8 hrs to propagate by which the user has already called us. This takes too long.

I've made a support call with Microsoft which has been open for a month now with what I think is a fairly straight forward question but they keep telling me they' re discussing this with their team.

Is there a scenario that sets these settings instantly that minimizes helpdesk calls? Or is this made for 1 user per device scenario's? Apart from reinstating on-prem DC's and whatnot ;)

Hope you guys can point me somewhere because Microsoft doesn't seem to..

you are viewing a single comment's thread
view the rest of the comments

[–] Snowplow8861@lemmus.org 1 points 1 year ago

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.