It tends to break when you force power off the machine in my experience, where ext4 is super resilient to that kind of stuff.
Thats my experience at least.
It tends to break when you force power off the machine in my experience, where ext4 is super resilient to that kind of stuff.
Thats my experience at least.
Yeah this is a good analogy, except it comes from tooling that would allow any n64 game to be converted with some work.
Like an openmw generator for any Bethesda game.
I think you could boil it down to something like
Set-ADUser bob -otherattributes {uidNumber=1005, gidNumber=1005}
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 @UserArgs
basically 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 like ydotool, uses a systemd user service, but fulfills my needs of KB shortcuts to paste text into vnc sessions
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.
The blog post they did showing how they do a sort of regression testing is still some of the coolest devops I’ve seen.
Check the FifoCI stuff here.
What a great series that is, I should get the kit
Thankfully editing logs isn’t really a valid use case