RE: SMBV1 issue

If I could sell the shortcut idea with one more benefit. I just remembered one other issue they eliminated. If for some reason, a share drive is not accessible, then you have to wait for the connection to error out as you sign into windows (assuming you clicked the reconnect at logon checkbox). If a server or group of servers is down, and you're trying to get into Windows to start figuring out why, the delay is very annoying. Shortcuts to these network folders are not connected until they're tried, so, no sign-in issues for unavailable network shares.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Darren Strong
Sent: Thursday, September 26, 2019 8:59 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: SMBV1 issue

Given the various issues we've had with SMB over the years, what I did was abandon share drives entirely, and use shortcuts instead. Where you would normally map a drive, create the shortcut in a "Network Drives" folder. That folder is on my desktop, and I also pinned that folder in file explorer for fast access. As another benefit, the share drives sometimes play with locks on files with the folder open, probably due to SMB issues again, but with these explorer shortcuts, I don't see that problem anymore.

It sounds complicated at first, but, once setup, it's just as easy as share drives.