this post was submitted on 17 Oct 2023
13 points (81.0% liked)

Sysadmin

7676 readers
85 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
13
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
[โ€“] themoonisacheese@sh.itjust.works 4 points 1 year ago (1 children)

Microsoft wants you to buy 1 PC and license per user. They pretend to support multi-user systems but in reality most of their admin tools suppose a machine is dedicated to a user, or that users are at least generally always using the same machine.

If you can programatically fix the issues causing the calls, put the fix in a login script using traditional mechanisms.

[โ€“] HC4L@lemmy.world 1 points 1 year ago

We were expecting the same and wishes MS just admitted this to us so we can go on.

We have no good mechanisms to deploy startup scripts and try to rely as much as possible on the best-practises Microsoft has. If we ever get those anyway..