I just though I’d share
Edit: I’m not sure if this actually works. All else fails fall back to Ansible
TD;DR
Too Dull; Didn’t Read?
Too dumb: Don’t read
I thought this stopped working after MS pulled the Unix subsystem, as samba was using those attributes to manage the Linux systems?
Microsoft pulled those from the UI, but if you’re adventurous you can just shove those attributes in to user with power shell and it works the same.
Then just use sssd instead of NIS, surprised me at work when this worked.
Do you have any documentation on this by any chance? I don’t really like messing with ad schemas
sorry I don’t have any real documentation but I have a snippet of powershell that explains it pretty well here this comes from a user creation script I wrote back when they removed the unix UI.
I was using Get-AdUser and discovered that the properties still existed but you have to manually shove those in, when an sssd “domain bound” linux machine has a user with these props login, they get the defined UID and GID and homefolder etc.
$otherAttributes = @{} Write-Host -ForegroundColor Yellow "Adding Linux Attributes" # get the next numeric uid number from AD $uidNumber=((get-aduser -Filter * -Properties * | where-object {$_.uidNumber} | select uidNumber | sort uidNumber | select -Last 1).uidNumber)+1 $otherAttributes.Add("unixHomeDirectory","/homefolder/path/$($samAccountName)") $otherAttributes.Add("uid","$($samAccountName)") $otherAttributes.Add("gidNumber","$($gidNumber)") $otherAttributes.Add("uidNumber","$($uidNumber)") $otherAttributes.Add("loginShell","$($loginShell)") $UserArgs = @{ Credential = $creds Enabled = $true ChangePasswordAtLogon = $true Path = $usersOU HomeDirectory = "$homeDirPath\$samAccountName" HomeDrive = $homeDriveLetter GivenName = $firstName Surname = $lastName DisplayName = $displayName SamAccountName = $samAccountName Name = $displayName AccountPassword = $securePW UserPrincipalName = "$($aliasName)@DOMAIN.COM" OtherAttributes = $otherAttributes } $newUser = New-ADUser @UserArgsbasically the “OtherAttributes” on the ADUser object is a hashtable that holds all the special additional LDAP attributes, so in this example we use $otherAttributes to add all the fields we need, you can do the same with “Set-Aduser” if you just wanna edit an existing user and add these props
the @thing on New-ADuser is called a splat, very useful if you’re not familiar, it turns a hashtable into arguments
lemme know if you have any questions
I think you could boil it down to something like
Set-ADUser bob -otherattributes {uidNumber=1005, gidNumber=1005}
I don’t know. I just found this why looking for something else.
Grid by Zorin, whenever it gets released, will be what you want
But is it distro acrostic?
time will tell once it is released.
If it is at least somewhat distro agnostic and has commercial support available they will get lots of business.
Yep. i imagine the long time between initial announcement and still waiting, is getting it right for realease. At least I hope that is why it has taken so long
Zoin isn’t exactly known for long term stability or regular releases. That why I can’t really recommend it.
We need tooling but Zoin probably isn’t where it will come from.
Why why why would you do that?
Because your insane?
Actually it might be useful in mixed Windows Linux environments.
Compliance. Control. Security. Lots of things?
If you don’t trust your employees, though, why give them Linux at all? Windows and Mac make the perfect locked down / restrictive / don’t trust people platforms out there. I mean, I understand locking down and securing a server, but a Linux desktop? The only value a Linux desktop has is the freedom to configure it how you like with the apps you like.
You cannot give people arbitrary permissions. People are often incompetent. But you dont need to rely on big brother to have control?
No, a Linux desktop is free from single corporation control, is compliant in its privacy settings and often works way better (like KDE) than Windows or MacOS.
No thanks. The entire point of a Linux desktop is to not be micromanaged like that, it’s all about choice. Absolutely no point in a Linux desktop if you take that all away. They should be free to choose the DE/Window Manager, type of Linux, their choice of browser(s), ability to sudo to root, run VM’s, what have you. What it sounds like you want them to have is Linux in a simple kiosk mode. Who would want that? Give them something other than Linux if you think you are hiring ‘often incompetent’ people.
No. That may be for you, but having the choice to be restricted by free software, fully transparently??
I dont get your point. You literally recommend companies to rely on apple or micro$ and to keep Linux incapable of such systems.
Would you have employees have root access, and write access to all other departments files too? This is just the base foundation of how stuff works.
I’m speaking solely about their workstation/laptop. If I am issued a Linux desktop system for work, and I can’t have root on it, heck no. I need to be able to remove Teams and replace it with the web app. I need to be able to install docker and vm’s. Add utilities I often use, replace gnome with a useable desktop environment, add zsh, install nerd fonts, choose the nvidia or intel gpu, modify grub, setup FDE and switch to snapshotting file system, etc etc.
I think we can agree here. But have Win11 with Teams, or Linux? I take Linux.
This seems like a minefield of clashes with distro-specific behavior. What happens if your system is using different software than what it expects or a policy that exists in Windows doesn’t always make sense in the target environment? I wonder how it is being dealt with?
And what about more broad policies like denying filesystem write access?
I’m also interested in this. I’m guessing you’d have to essentially have multiple overlapping sets of policies.
Ansible does some of each.
I hope the global catalog gets finished one day for freeipa.
FreeIPA is very unreliable in my experience. Samba is much more reliable from what I can tell.
My experience is quite the opposite. I have and still use both and find samba one of the more unreliable things. Freeipa does what it does with no issues.
Samba just works. It’s easy to set up and easy to manage.
Ironically I was trying to push for some rnd to run all of the GPOs for windows boxes as local policy ran by ansible. Just could stand all of the wonkyness AD introduced into the system.
Yeah, we need better tools
ran
It’s “run”, here.
Very cool!
What does TD;DR mean? Or did you mean TL;DR?
All else fails fall back to Ansible
Fucking hell. THAT far back?
We were doing everything Ansible does for the 95% case in 2002. Like, for 95% of use-cases, Ansible is absolutely no better than a conglomeration of tools from 2002. Definitely no reason to pay licensing.
Bonus: since it’s version-agnostic (another win over Ansible if you’ve ever managed Tower/AAP/whatever next week) I’m still using that paradigm today because it works SO well. It’s losing to Cinc or mgmtConfig but only because those are 1 and 2 generations newer than Ansible and do offer distinguishing features.
Ansible is foss, free of cost and requires almost no additional overhead or hardware.
It isn’t the best sometimes but if you have a bunch of machines to manage it works great. (Assuming they aren’t behind a NAT)
Keep your filthy Microsoft mitts off my Linux environment
Do you run a Linux environment? If so, you should post about it (don’t reveal to much info obviously)
I run linux on my kettle don’t you know
Can you play doom on it?
Only at “Boil my skin off!” difficulty level
