×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Basically you are encouraged to have every Windows user change their passwords right away after the change. Because the initial move to 2 or 3 will store the password all upper case and all lower case. Once they change their password after the change it will store it in it's true case and thus mixed case passwords are a possibility.
So, don't be surprised if users with mixed case passwords in Windows cannot connect until after they change their passwords.
Memo that out to your user base.
From a midrange-l post:
<snip>
We changed all the passwords (except the q* passwords) to
expire and force a password change.
We did not want death by a 1000 tickets to our help desk over the
next 4 weeks as user passwords normally expire
Help desk tickets skyrocketed for 2-3 days with password issues but
settled down quickly after that.
</snip>
https://archive.midrange.com/midrange-l/201604/msg01195.html
Some other errata:
https://www.ibm.com/support/pages/considerations-changing-qpwdlvl-0-3
https://www.mcpressonline.com/security/ibm-i-os400-i5os/moving-your-ibm-i-to-a-higher-password-level
Rob Berendt
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
