• Pommes_für_dein_Balg@feddit.org
    link
    fedilink
    arrow-up
    15
    ·
    3 months ago

    Yeah, that sounds like MS alright.

    I admit I’ve used the steamroller approach before:

    • manually edit all of the AD object’s attribute fields
    • rename the home folder
    • recreate the roaming profile
    • add an e-mail alias
    • force AD synch

    That’s definitely not the way to go, but it’s been 2 years and so far the user is still working.

    • reddfugee@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      3 months ago

      Oh- Lol, I thought you were joking, I work at a uni where AD is mostly mess of groups for permissions & license entitlements; the ERP carries the demo/bio info and not much makes it to AD. I am SO glad my corner of the org doesn’t mess with roaming profiles (outside our VDI at least, but we are hoping to be able to kill that eventually).

      Even more “fun”, the statewide system administration wants to kill off its AD forest in favor of “cloud native” Intune setups, but they can only marshal one FTE and a couple student workers to manage that for 5 campuses, 3 institutes, and like 90 county extension offices. They’ve been at it for 2 years now I think, and departmental IT still can’t even create device groups, add devices to them, or tie configuration profiles to them (poor guy hasn’t even been able to come up with governance or processes to enable that). Woohoo!

      continues to cry in MS admin