Self Serve Portal stops working with removal of SMB1 protocal on Windows 10

Self Serve Portal stops working with removal of SMB1 protocal on Windows 10

After all of the WannaCry action over the summer - today I finally got around to removing the SMB1 protocal from several WIndows 10 ENT workstations. It tried it first on a few test VMs and did not see any impact.

However - when I tried this on a real workstation on the floor running Windows 10 1607 - I immediately noticed that the Self Serve Portal started kicked out some odd ball errors.

To be clear - I am going in through COntrol Panel->Programs->Add Remove WIndows Features (see attachment)

I simply remove the checkbox by the SMB option and restart the machine.

When the machine comes back up and I try to install a program from the Portal - I get this message (see Self Serve attachment)

"Could connect the share from the client computer: The Network path was either typed incorrectly, does not exist or the network provider is not currently available. Please try retyping the path or contact your network administrator".

Then if I re-enable SMB1, restart the machine and retry the install from the portal - it installs without issue.

Please tell me that here in 2017 - you are not using this 30 year old protocol which the whole world is saying to get rid of as fast as possible - as a required element of supporting your self serve portal?

Appreciate an update on this as soon as possible.

Thanks,

Bruce

                New to ADSelfService Plus?