Exactly one of --password / --password-hex / --password-b64 is required. Identity inputs are only needed for the secrets that use them: with no --realm the Kerberos keys are skipped, with no --netbios the WDigest hashes are skipped (each with a stderr note).
sAMAccountName. Case matters for the user/trust salt — see Casing.
--realm DNS
DNS domain — AD's Kerberos realm. Kerberos uppercases it, so any input case is fine.
--account-type {user,computer,trust}
Selects the salt rule. Defaults to computer for --managed-blob or a $-suffixed --user; else user. Pass it explicitly to override — notably trust (which also ends in $, but uses the krbtgt salt).
--netbios NAME
NetBIOS domain name. Required to emit the 29 WDigest hashes.
--dns-domain FQDN
DNS domain FQDN for WDigest (defaults to --realm).
--upn UPN
userPrincipalName for WDigest (defaults to <sam>@<dns-domain>).
--salt SALT
Override the computed Kerberos salt verbatim — the escape hatch for accounts whose salt isn't derivable from the identity (Administrator, krbtgt).
DES & WDigest of non-ASCII passwords are locale-dependent: DES uses the DC's ANSI codepage (cp1252), WDigest uses ISO-8859-1. A password outside that codepage (e.g. Cyrillic) or a binary gMSA blob can't be reproduced for those two algorithms — NT and AES still are. Such fields are skipped with a stderr note.
Administrator / krbtgt carry frozen install-time salts — use --salt.
NoLMHash (the modern default) means AD stores a blank LM; this tool emits the true LM hash of the password.
Out of scope (by design): AES-SHA2 (etype 19/20), Primary:CLEARTEXT, the random NTLM-Strong-NTOWF, NetNTLM wire responses, DCC1/DCC2, DPAPI pre-keys.