A Deployment Policy defines the rules that control how and when a software package is deployed to target devices. It links a package from the Software Repository to a set of delivery instructions, including execution permissions, network conditions, retry behavior, and schedule.<\/p>\n\n\n\n
Once published, a Deployment Policy is ready to be assigned to device groups or individual devices.<\/p>\n\n\n\n
Navigation:<\/strong> Go to Manage \u2192 Deployment \u2192 Deployment Policy<\/strong>, then click Add Deployment Policy<\/strong>.<\/p>\n\n\n\n Policy Name<\/strong> (Required)<\/em> Enter a clear, descriptive name to identify this policy. Example: Deploy Microsoft Office 365 \u2013 Q1 Rollout, Install Zoom \u2013 Remote Workers<\/em><\/p>\n\n\n\n You can optionally click Add Description<\/strong> to include additional context about the policy’s purpose.<\/p>\n\n\n\n Category<\/strong> Select the type of deployment this policy will perform:<\/p>\n\n\n\n Operation Type<\/strong> Choose the action this policy will perform on target devices:<\/p>\n\n\n\n Select Package<\/strong> (Required)<\/em> Choose the software package you want to deploy from the dropdown list. This list is populated from your Software Repository.<\/p>\n\n\n\n If the package you need does not yet exist, click Add Package<\/strong> to create a new one directly from this screen without leaving the policy creation flow.<\/p>\n\n\n\n The Execution Context determines the user account under which the installer runs on the target device. Selecting the correct context is important for ensuring the installer has the permissions it needs.<\/p>\n\n\n\n System (Run as System)<\/strong> (Default)<\/em> The installer runs under the local System account with elevated administrator privileges. This is the recommended option for most enterprise software deployments.<\/p>\n\n\n\n Use this when:<\/p>\n\n\n\n Logged-in User<\/strong> The installer runs within the session of the currently active user on the device. The user must be logged in for the deployment to proceed.<\/p>\n\n\n\n Use this when:<\/p>\n\n\n\n Run as User<\/strong> The installer runs using a specific user account with credentials you provide. This is useful when the installer needs access to network resources, shared drives, or domain-protected directories.<\/p>\n\n\n\n Use this when:<\/p>\n\n\n\n \ud83d\udca1 Note:<\/strong> When using Run as User, credentials must be configured in advance. Click Manage Credentials<\/strong> to add or update stored credentials.<\/p>\n<\/blockquote>\n\n\n\n These rules control how Zecurit behaves when a deployment encounters problems or connectivity issues.<\/p>\n\n\n\n Network Conditions<\/strong> Specify the network type under which deployments are allowed to run:<\/p>\n\n\n\n Retry on Failed Targets<\/strong> Enable this toggle to automatically retry the deployment if it fails on a device.<\/p>\n\n\n\n When enabled, configure:<\/p>\n\n\n\n \ud83d\udca1 Tip:<\/strong> Enabling Retry After Reboot<\/strong> is useful for packages that require a system restart as part of the installation process.<\/p>\n<\/blockquote>\n\n\n\n The Schedule determines when the deployment begins on target devices.<\/p>\n\n\n\n Deploy Immediately<\/strong> The deployment starts automatically as soon as the target device next contacts the Zecurit server. Use this for urgent deployments that need to reach devices as quickly as possible.<\/p>\n\n\n\n Schedule Deployment<\/strong> Set a specific date, time, and time zone for the deployment to begin.<\/p>\n\n\n\n If a device is offline at the scheduled time, the deployment will begin automatically the next time the device connects to the Zecurit server, no manual intervention is needed.<\/p>\n\n\n\n \ud83d\udca1 Tip:<\/strong> Use scheduled deployments for off-hours installations to avoid disrupting users during business hours.<\/p>\n<\/blockquote>\n\n\n\n Notify Administrators About the Deployment Status<\/strong> Enable this toggle to receive notifications when the deployment completes or fails on target devices. Notifications are sent to the administrators configured in your account settings.<\/p>\n\n\n\n Enabling notifications helps your team stay informed about deployment outcomes without having to manually check the console.<\/p>\n\n\n\n At the bottom of the page, you have three options:<\/p>\n\n\n\n \u26a0\ufe0f Note:<\/strong> A policy that is saved as a draft will not deploy to any devices until it is published.<\/p>\n<\/blockquote>\n\n\n\n <\/p>\n","protected":false},"featured_media":0,"parent":3015,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-3027","docs","type-docs","status-publish","hentry"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/docs\/3027","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/comments?post=3027"}],"version-history":[{"count":1,"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/docs\/3027\/revisions"}],"predecessor-version":[{"id":3038,"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/docs\/3027\/revisions\/3038"}],"up":[{"embeddable":true,"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/docs\/3015"}],"wp:attachment":[{"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/media?parent=3027"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/doc_tag?post=3027"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Section 1: Policy Details<\/h2>\n\n\n\n
\n
Section 2: Package Settings<\/h2>\n\n\n\n
\n
Section 3: Execution Context<\/h2>\n\n\n\n
\n
\n
\n
\n
Section 4: Deployment Handling Rules<\/h2>\n\n\n\n
\n
Setting<\/th> Description<\/th><\/tr><\/thead> Retry Count<\/strong><\/td> The number of times Zecurit will reattempt the deployment after a failure<\/td><\/tr> Retry Interval<\/strong><\/td> The time (in minutes) Zecurit waits between each retry attempt<\/td><\/tr> Retry After Reboot<\/strong><\/td> When enabled, if a deployment fails and the device is rebooted, Zecurit will attempt the deployment again after the device comes back online<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n \n
Section 5: Schedule<\/h2>\n\n\n\n
Field<\/th> Description<\/th><\/tr><\/thead> Start Date<\/strong><\/td> The date and time when the deployment should begin<\/td><\/tr> Time Zone<\/strong><\/td> The time zone used to interpret the start date and time<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n \n
Section 6: Notification<\/h2>\n\n\n\n
Saving and Publishing the Policy<\/h2>\n\n\n\n
Action<\/th> Description<\/th><\/tr><\/thead> Cancel<\/strong><\/td> Discard all changes and return to the Deployment Policy list<\/td><\/tr> Save as Draft<\/strong><\/td> Save the policy without activating it. Use this to complete configuration later before going live<\/td><\/tr> Publish<\/strong><\/td> Save and activate the policy. Once published, it is ready to be assigned to groups or devices<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n \n