I have just seen the alerts from CloudIQ that they recommend to disable smbv1

i think restarting the smb service will be disruptive for all smbv1-2-3 clients, however if you dont do it it might just be that no additional smbv1 connections will be negotiated, so slowly over time they will all drop off? but would need to test that on a simulator. 

I came to ask this as well.  The documentation noted by the OP suggests that only SMB1 connections are affected by restarting the SMB service but I can't believe that is correct:

"This step disconnects any current SMB1 clients and updates the configuration to prevent new SMB1 connections."

I mean, it *could* be correct if you didn't have/care about your v2 and v3 connections but I kind of do have/care... :)

I am also thinking of just running the command to disable the v1 and was hoping the next firmware install that forces a reboot will take care of the restarting part so I can schedule the potential disruption all together but I don't know for certain if that will work.

@rgmule05,

disable enable smb service by

isi services -a smb disable
isi services -a smb enable

@Ryan_CSULB​ ,

You need a maintenance period to disable SMB1 is best.