Disable SMB1

In light of the recent details of SMBv1 being incredibly vulnerable¬† to attacks, it’d be a good idea to make sure that SMBv1 is disabled on your systems. There isn’t much reason to leave it enabled, it was deprecated in Windows Vista/Server 2k8, and unless you have an old NAS that requires SMBv1, you should be able to disable it without any harm.

The other benefit of disabling SMBv1, is that it forces your systems to use SMBv2 or v3, which perform better.

So, let’s go through how to disable it quickly and easily.

For Windows 8.1 and above, as well as Windows Server 2012 R2 and above, it’s just a simple PowerShell command.

To run Powershell as an Admin, please do the following:

  1. Click on Start
  2. Type in “Powershell” without the quotes
  3. Right click on “Powershell” and click run as administrator. Do not run Powershell ISE
  4. Click on “Allow” if a prompt comes up


Open a PowerShell window as Admin

Remove-WindowsFeature FS-SMB1

If all goes well, you’ll get a message saying it was successful.


Open a PowerShell window as Admin

Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol

You’ll get a message saying that it has succeeded.

For the remaining versions of Windows, the commands are a little different.


Open PowerShell window as Admin

Set-SmbServerConfiguration -EnableSMB1Protocol $false

Windows Vista/7/Server 2k8/2k8R2

Open PowerShell window as Admin

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 0 -Force

Then restart the computer

Disabling SMBv1 is simple, quick, and highly important both from a security standpoint and a performance standpoint.

Multi-system Lightroom

I’ve been doing photography for years. And, for years, I’ve been using Adobe Lightroom to manage and edit my photos. With the advent of the photographer’s plan and the two-system allowance, I’ve been able to get Photoshop as well, for a low monthly cost.

However, one feature that’s always been missing is catalog sync between systems. While some people will throw the catalog on a network share, and use it from there, I’ve never been comfortable with doing that due to corruption concerns.

Historically, I’ve just used RDP from my tablet or laptop to get to my desktop where I have Lightroom installed. There are some disadvantages to this method. For starters, if my connection dips for any reason, or if RDP decides to throttle my connection, I’ll end up with artifacts as well as a reduced color depth. It also, even at its best, feels less responsive. And, with Lightroom not being the fastest program, these negatives effects are compounded by RDP.

This solution was a two-part solution. First part was to get my 1 TB of photos to a faster, more central location than my desktop hard drive. I have a homeserver with a large RAID10 array. Thanks to dual NICs, I’ve got the network bandwidth to spare, and RAID10 is quite a bit faster than my local hard drive. RAID also lets me lose a drive without having total downtime until I can replace a drive and restore from Crashplan.

So, I fired up Lightroom, and added the share for the drive to my folder list. I then moved a few folders over for testing from my desktop. I decided that if the speed was similar between desktop and server, that there would be no harm in just moving everything before trying the sync. After doing a few tests, I couldn’t really see a difference so I started moving the rest of the photos. I did the photo moving from Lightroom so it’d keep all the data, rather than moving in Explorer and reimporting. It took a little longer, but I feel that it was worth it.

It was at this point that I remembered that I had photos in a second location. Since Lightroom is so sluggish, I have a secondary SSD where I keep photos that I’m actively working on. When I’m done with them, I move them back to the main photo location for storage. I didn’t want to lose access to these photos when I’m working on my laptop, so I set up some mapped network drives to keep everything straight. Luckily, I don’t have drive letter mixing between my laptop and desktop, so it was a quick fix.

Finally, it was time to set up the sync. I used allwaysync, since I wanted to capture the previews as well, and it seems to handle massive syncs better than some of the other tools I’ve used. Once I set it up to sync my lightroom folder to my laptop, and it finished running (It took forever due to there being over 100k small files), it was time to test.

I opened the catalog on my laptop, and all my previews, presets, and filters were right there. To test, I did some edits and browsed through some folders. Even with DNG/CR2 files, there wasn’t any extra lag as compared to running from my desktop. I’m doing this testing on an Asus Ultrabook (16gb ram/I7) running on AC wifi.

All in all, I’m quite satisfied with the performance, and I think that this will make photo editing a lot more mobile. For example, if I’m traveling, all I need to do is move a folder to my laptop via lightroom, and sync up when I get back. Or, I can import some files to my laptop while on a shoot to do in the field edits, and then sync back when I’m home.