smc -importconfig fails when no user is logged in on a system running Endpoint Protection
Last Updated July 11, 2019
You use a scheduled task or other method to run smc -importconfig when no user is logged in on a system running Symantec Endpoint Protection (SEP). Contrary to expectations, you find that the command fails with error 3. SEP's System Log shows an "Import new policy failed" error message. While logged in to the system, running the same command returns exit code 0, with SEP's System Log showing "New policy has been imported".
SEP for Windows
Symantec is aware of this issue and will update this article when a solution becomes available. Click the Subscribe to this Article button to be notified of future updates through email.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe