Dear all,I upgraded directly from 1.6ST to 1.9ST and testing the new environment. osticket 1.6ST is running on CentOS Server. the new 1.9ST is running on a Windows 2012 R2 server. MySQL DB was successfully exported and being imported into the new environment. osticket 1.9 run recognized the DB and updated it as well. I can log my self successfully on the new osticket system. When other user try to login there, they fail. The warning is mostly just wrong password. There are times where a little warning is shown top left of the screen and mentioning token taken or smth like this.- When i put my md5 has code into the field of another college, they can logon with my password.- I put hash password code into my username and try to logon with users password it does not work.- After first logon (when successfully logged on) the hash code is changed from md5 to salt.Problem:When i set my password (on the 1.6ST environment) new, and use one users password i see a hash code difference between my new password and that from my college. But i can type in the same password for both users and the can logon in the old platform. If i use any md5 web generator, my newly crated hash is equal to that in osticket. normally it should always show the same hash code.Is any idea what I did wrong? how can I export/import the DB in order to keep users password in the new environment running, so that they don't have to reset them on go live?Thanks for any adviceBledar