Sysadmin

7664 readers

2 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

Are we the only shop with constant login bullshit on Office 365 desktop apps? (lemmy.world)

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

13 comments fedilink hide all child comments

We are facing constant problems with the desktop apps in O365, wheter it's RDS servers that somehow are Azure joined by a user from login 1001 errors to modern authentication Windows that automatically disappear or other generic error 1001 logon bullshit. We have a tome of registry bullshit with shit like EnableADAL to deleting the AAD appx folder from the user profile and/or reinstalling it through Powershell and so it goes on.. usually dicking around with these settings will make it magically work for a few weeks..

The amount of time this costs us and our customers is truly staggering, are we the only shop facing this?

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

[–] HC4L@lemmy.world 2 points 1 year ago (1 children)

Thanks for you insight, your environment sounds ways more complex but then again, miles better configured.

After some research it now seems to point to a registry cleaning script used to clean up bizarre amounts of entries created by certain printer drivers that were added each time a user logs on or off.

We aren't sure yet since it can easily not happen for a few weeks out of itself but fingers crossed!

Thanks for taking the time to respond as I have should way faster..

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

I've seen something similar to this before in remote desktop servers where user redirected printers end up bloating registries to the point login times exceed processing limits and so not all the configuration in the registry or group policy gets processed. Each redirected printer gets created and never pegged, and it's unique to that rdp session so they are duplicated to infinity over time. Glad you found it out, the only point with the complexity is I was trying to explain that it being complex doesn't mean it won't be robust if it's still implemented without conflicts so you can rule that out (if you've ruled out conflicts) . Sounds like you found the culprit in the end! Good work.