Word – How to pass the password to a net use command without being prompted

Use the commands pushd and popd.

pushd \\server\share will create a temporary drive (starting from Z: and going backwards till it finds an available letter) and go into it. When you're done, popd will delete the temporary drive and get you back where you were.

C:\Users\Snark>pushd /?
Stores the current directory for use by the POPD command, then
changes to the specified directory.

PUSHD [path | ..]

  path        Specifies the directory to make the current directory.

If Command Extensions are enabled the PUSHD command accepts
network paths in addition to the normal drive letter and path.
If a network path is specified, PUSHD will create a temporary
drive letter that points to that specified network resource and
then change the current drive and directory, using the newly
defined drive letter.  Temporary drive letters are allocated from
Z: on down, using the first unused drive letter found.

C:\Users\Snark>popd /?
Changes to the directory stored by the PUSHD command.

POPD


If Command Extensions are enabled the POPD command will delete
any temporary drive letter created by PUSHD when you POPD that
drive off the pushed directory stack.

Checking libpwquality code on github it looks like error message you get comes from this library. Probably called from PAM module, so you should start checking what you have in /etc/pam.d/passwd by default for password it only includes /etc/pam.d/system-auth. I think you were quite close, however, setting module as optional didn't work for you. I'd suggest commenting it out for test and setting gecoscheck=N either in pam or /etc/security/pwquality.conf

Simply commenting out the line in /etc/pam.d/system-auth may not work, however, you can try to update the file password section to something like this (only password section matters): password sufficient pam_unix.so sha512 password required pam_deny.so After that simply execute passwd user at try your favourite password. For me setting exectly the same user name and password worked, which is obviously not recommended from the system security perspective.