When migrating a Symantec Endpoint Protection (SEP) client to the cloud using "smc -cloudmanaged <package>" the client successfully migrates, but the subscription status shows Subscribed, but Not Installed for Application Control Allow List, and Application Isolation.
Client features are maintained from the client's original deployment settings during migration.
Release : 14.3.x
To take advantage of the full feature set when moving an on-premises SEP client to the cloud, execute the cloud installation package as opposed to using the smc commandline.
You can manually initiate a change in the installed feature set after the client has been migrated to the cloud using the following command syntax:
C:\Windows\System32\msiexec.exe /i "C:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Cached Installs\Sep64.msi" ADDLOCAL=Core,SAVMain,Download,PTPMain,TruScan,DCMain,NTPMain,ITPMain,Firewall,Saep,ADDefense,NTR /qn