Server upgrade kinda fails

[BudTheGrey]

I migrated one of our servers from Windows 2012 to Windows 2019. This server also does duty as one of out file servers. We use FileZilla to allow multi-function copier/scanners to scan documents directly to a known destination on the server. The 2012 server was running 0.9.6. I installed that version on the new server, copied over the XML file with the server settings and started it up. Everything worked as it did on the old server. I then installed version 1.2. It migrated all the settings, and when I looked in the server manager it appeared that everything (users, bindings, etc) came over. But in some cases, the devices are failing to log in. In once case, the device logs in OK, but consistently gets a 450 file/folder not found error. The service is running under the system account.

I was kind under the gun to get it back on-line, so only had a limited amount of time to troubleshoot. I tried created a new account for myself, and after some experimenting, it seems that the for some things, such as user name and home folder, the new version is case sensitive. The account on the server is 'Bud', so connecting as 'bud' will fail. Is that true, and are folder references also case sensitive?

For now, I uninstalled 1.2 and re-installed 0.9.6 to keep things running until I can sort this out.

[boco]

At least user names seem to be case sensitive. This can be very inconvenient in some cases, like for anonymous/Anonymous accounts, where all possible kinds of spelling exist.

@botg @oibaf - Could you re-introduce the switch to ignore case for user names? Alternatively, a possibility for entering alternative user name spellings, so I could at least catch the edge cases where clients tend to capitalize the user name.

[botg]

This needs to be platform-specific and unconfigurable, as on *nix case-insensitive usernames simply would not work with impersonation, dealing with the corner-cases would otherwise be very weird.

[boco]

@botg: Usernames are case sensitive on Windows, currently.

How about the aliases for user names? Like, defining an account alias "Anonymous" and telling the server to just link it to the "anonymous" account. That would allow to catch the most common spelling sins some clients commit. Otherwise, one would have to maintain two anonymous accounts with different spellings.