Add SMB v2/v3 support when scanning user states.
To scan user states with USMT from the K2000 web UI, SMB v1 must be enabled on the client pc. Support has confirmed this. There are known vulnerabilities with SMB v1 and most network admins have disabled it in their environments. Please provide support for newer versions of SMB.
Anonymous
shared this idea
This feature request was implemented in SDA 8.2.
-
Anonymous
commented
This is something that definitely needs to be addressed sooner rather than later from a system security standpoint
-
Jimmie
commented
USMT is completely dead in the water for us because we can't use SMBv1 in our environment. Being able to automate user migration to new systems would be an amazing enhancement, and I would really hate to have to go to another vendor to get it because I like a lot of what KACE does for us.
-
Israel
commented
This would be a great addition,,,
-
Leslie
commented
We definitely need this feature. Our orginization is CJIS compliant for the justice system and we need to have SMB1 turned off. There has to be a way to scan userstates with another protocol. SMBv2/v3 or UPD maybe? This has become a problem with Windows 10 as the feature cannot just be turned on or off in the registry but needs to be installed and cannot be pushed.
-
Anonymous
commented
I second this... "This is a deal breaker for most admins. You will lose customers if ignored!"
-
Jesse Mack
commented
SMB v1 on Windows 10 now has SMB v1 disabled by default.
https://support.microsoft.com/en-ca/help/4034314/smbv1-is-not-installed-by-default-in-windows
https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2016/ms16-114I am seeing USMT failures across all my RSA's it appears to scan, and but the file turns out to be 0 bytes.
-
Anonymous
commented
This is a real problem and it will be a deciding factor moving forward.
-
Anonymous
commented
Hope Quest addresses this soon. This is a deal breaker for most admins. You will lose customers if ignored!