pdbedit

This option lists all the user accounts present in the users database. This option prints a list of user/uid pairs separated by the ':' character.

Example: pdbedit -l

		sorce:500:Simo Sorce
		samba:45:Test User
		

This option enables the verbose listing format. It causes pdbedit to list the users in the database, printing out the account fields in a descriptive format.

Example: pdbedit -l -v

		---------------
		username:       sorce
		user ID/Group:  500/500
		user RID/GRID:  2000/2001
		Full Name:      Simo Sorce
		Home Directory: \\BERSERKER\sorce
		HomeDir Drive:  H:
		Logon Script:   \\BERSERKER\netlogon\sorce.bat
		Profile Path:   \\BERSERKER\profile
		---------------
		username:       samba
		user ID/Group:  45/45
		user RID/GRID:  1090/1091
		Full Name:      Test User
		Home Directory: \\BERSERKER\samba
		HomeDir Drive:  
		Logon Script:   
		Profile Path:   \\BERSERKER\profile
		

This option sets the "smbpasswd" listing format. It will make pdbedit list the users in the database, printing out the account fields in a format compatible with the smbpasswd file format. (see the smbpasswd(5) for details)

Example: pdbedit -l -w

		sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX         ]:LCT-00000000:
		samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX         ]:LCT-3BFA1E8D:
		

This option specifies the username to be used for the operation requested (listing, adding, removing). It is required in add, remove and modify operations and optional in list operations.

This option can be used while adding or modifing a user account. It will specify the user's full name.

Example: -f "Simo Sorce"

This option can be used while adding or modifing a user account. It will specify the user's home directory network path.

Example: -h "\\\\BERSERKER\\sorce"

This option can be used while adding or modifing a user account. It will specify the windows drive letter to be used to map the home directory.

Example: -d "H:"

This option can be used while adding or modifing a user account. It will specify the user's logon script path.

Example: -s "\\\\BERSERKER\\netlogon\\sorce.bat"

This option can be used while adding or modifing a user account. It will specify the user's profile directory.

Example: -p "\\\\BERSERKER\\netlogon"

This option is used to add a user into the database. This command needs a user name specified with the -u switch. When adding a new user, pdbedit will also ask for the password to be used.

Example: pdbedit -a -u sorce

new password:
		retype new password

This option may only be used in conjunction with the -a option. It will make pdbedit to add a machine trust account instead of a user account (-u username will provide the machine name).

Example: pdbedit -a -m -u w2k-wks

This option causes pdbedit to delete an account from the database. It needs a username specified with the -u switch.

Example: pdbedit -x -u bob

Use a different passdb backend to retrieve users than the one specified in smb.conf. Can be used to import data into your local user database.

This option will ease migration from one passdb backend to another.

Example: pdbedit -i smbpasswd:/etc/smbpasswd.old

Exports all currently available users to the specified password database backend.

This option will ease migration from one passdb backend to another and will ease backing up.

Example: pdbedit -e smbpasswd:/root/samba-users.backup

Use a different default passdb backend.

Example: pdbedit -b xml:/root/pdb-backup.xml -l

Display an account policy

Valid policies are: minimum password age, reset count minutes, disconnect time, user must logon to change password, password history, lockout duration, min password length, maximum password age and bad lockout attempt.

Example: pdbedit -P "bad lockout attempt"

		account policy value for bad lockout attempt is 0
		

Sets an account policy to a specified value. This option may only be used in conjunction with the -P option.

Example: pdbedit -P "bad lockout attempt" -V 3

		account policy value for bad lockout attempt was 0
		account policy value for bad lockout attempt is now 3