The latest version of the SMA fails to address SMB vulnerabilities by continuing to utilize SMB v1 to share out the client folder and Agent installers it contains. Quest KB articles suggest workarounds of re-enabling this knowingly vulnerable protocol to avoid losing access to the file shares; shares that are necessary to provision agents to new Windows 10 1709 PCs (and other wise OSs which have disabled SMB).

I would suggest that, rather than asking clients to either 1. Create and troubleshoot their own custom scripts to work around the vulnerabilities you failed to address in the latest update or 2. Actually re-enable these knowingly vulnerable protocols, Quest offer their "professional services" time free of charge to clients who wish to stay safe AND use the Provisioning portion of their Kace SMA to keep their end-points updated.