1 of 1 people found this helpful
Deploying using the CSA is a policy-only deployment.
Here's how the scheduled task will look based on the Task type":
Deployment will fail as the core cannot communicate directly with the device
Policy (task settings set policy to required)
The core does not communicate with the device at all. It makes a policy.xml file available for the client to download. The client will check for these policies based on the setting you have configured in your "Distribtion and Patch" settings under the "Policy sync schedule". This prompts the agent to run policysync.exe in the LDClient folder. PolicySync.exe attempts to communicate with the core based on your client connectivity settings. Normally the communication attempts core server directly, if that fails it will fall back to the CSA traffic. As long as you are able to communicate with the CSA, it should download the policy file via that connection and process it. At that point things get grey depending on what you are doing. If the package/patch files are on the core server, everything will download like normal (although it's normally slower via CSA). If the files aren't on the core server, you'll likely have download failures.
Attempt Push. If device shows offline, make policy available.
NOTE - if you use Policy/Policy-supported push (which falls back to policy for offline) and have the task settings set to Optional or recommended, the device will make the package available via Portal Manager/Workspaces but will not process it until the user initiates via one of the self-service portals.
Thank you very much!