{"id":3452,"date":"2026-08-21T07:38:26","date_gmt":"2026-08-21T07:38:26","guid":{"rendered":"https:\/\/zecurit.com\/help\/?post_type=docs&p=3452"},"modified":"2026-08-21T07:38:27","modified_gmt":"2026-08-21T07:38:27","slug":"manual-patch-deployment","status":"publish","type":"docs","link":"https:\/\/zecurit.com\/help\/endpoint-management\/patch-management\/manual-patch-deployment\/","title":{"rendered":"Manual Patch Deployment"},"content":{"rendered":"\n

Overview<\/h2>\n\n\n\n

Manual Deployment lets you install or uninstall specific patches on chosen devices or groups, on your own schedule, instead of waiting for an automatic rollout. Each deployment is saved as a profile you can track, re-run, or review later.<\/p>\n\n\n\n

What is Manual Deployment?<\/h2>\n\n\n\n

Manual Deployment, found under Secure \u2192 Deployment<\/strong>, is used to deploy specific patches to selected devices or groups. It is useful for one time fixes, urgent patches, or controlled rollouts where you need direct control over the deployment timing and target devices.<\/p>\n\n\n\n

Every deployment you create appears in the profile list with its own status, so you can track whether it succeeded, is still running, or needs attention.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Step 1: Navigate to Manual Deployment<\/h2>\n\n\n\n
    \n
  1. Log in to the Zecurit portal.<\/li>\n\n\n\n
  2. Go to Endpoint Manager \u2192 Secure \u2192 Deployment \u2192 Manual Deployment<\/strong>.<\/li>\n\n\n\n
  3. Click Install \/ Uninstall Patch<\/strong>.<\/li>\n<\/ol>\n\n\n\n

    Step 2: Configure the Deployment<\/h2>\n\n\n\n

    Configure the Policy Details, Deployment Handling Rules, Schedule, and Scope of Target sections.<\/p>\n\n\n\n

    Policy Details<\/h3>\n\n\n\n
    Field<\/strong><\/th>Required<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
    Policy Name<\/td>Yes<\/td>A descriptive name for the deployment (e.g., “Patch deployment policy”). Shown in the profile list to identify it later. An Add Description<\/strong> link sits next to the field, letting you attach an optional, longer description of the deployment’s purpose.<\/td><\/tr>
    Operation Type<\/td>Yes<\/td>Whether this deployment installs or uninstalls the selected patches. Choose Install<\/strong> or Uninstall<\/strong>. Install is selected by default.<\/td><\/tr>
    Patches<\/td>Yes<\/td>The specific patches to deploy or uninstall.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Adding and managing patches:<\/strong><\/p>\n\n\n\n

      \n
    1. Click Add Patch<\/strong> to open the patch picker and select one or more patches.<\/li>\n<\/ol>\n\n\n\n
        \n
      1. Selected patches appear in a table below a Total Selected Patches<\/strong> counter (e.g., “Total Selected Patches: 1”), which updates as you add or remove patches.<\/li>\n<\/ol>\n\n\n\n
          \n
        1. The table has the following columns:<\/li>\n<\/ol>\n\n\n\n
          Column<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
          (checkbox)<\/td>Select one or more rows before using Remove Patch.<\/td><\/tr>
          Patch ID<\/td>The internal identifier for the patch, for example 51871.<\/td><\/tr>
          Title<\/td>The patch name and version, for example “Git – 2.50.1.” If the title is truncated, hover over it to see the full name in a tooltip.<\/td><\/tr>
          Severity<\/td>A badge showing the patch’s severity rating, for example “Unknown,” Critical, High, or Low, depending on how the patch is classified.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
            \n
          1. Remove Patch<\/strong> is disabled (greyed out) until at least one patch row’s checkbox is selected. Check a row first, then click Remove Patch to remove it from the deployment.<\/li>\n<\/ol>\n\n\n\n

            Deployment Handling Rules<\/h3>\n\n\n\n
            Field<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
            Network Conditions<\/td>Choose Any Network<\/strong> to deploy regardless of connection, or Lan Only<\/strong> to deploy only while the device is on the local network.<\/td><\/tr>
            Retry on Failed Targets<\/td>When turned on, automatically retries the deployment on any device where it failed.<\/td><\/tr>
            Retry Count<\/td>How many times to retry a failed deployment before giving up.<\/td><\/tr>
            Retry Interval<\/td>How long to wait, in minutes, between retry attempts.<\/td><\/tr>
            Retry After Reboot<\/td>When turned on, retries the deployment after the device restarts, in case the failure was reboot-related.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

            Schedule<\/h3>\n\n\n\n
            Option<\/strong><\/th>Effect<\/strong><\/th><\/tr><\/thead>
            Deploy Immediately<\/td>The deployment starts automatically as soon as the device contacts the Zecurit Server.<\/td><\/tr>
            Schedule Deployment<\/td>The deployment begins at a chosen Start Date and Time Zone. If a device is offline at that time, it starts when the device next contacts the Zecurit Server.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

            Scope of Target<\/h3>\n\n\n\n

            Targets are configured one row at a time, and each row is numbered as you add it the first is labeled Target 1<\/strong>, the next Target 2<\/strong>, and so on.<\/p>\n\n\n\n

            For each target row:<\/strong><\/p>\n\n\n\n

              \n
            1. Use the type dropdown<\/strong> on the left (e.g., “Devices”) to choose whether this target row applies to Devices<\/strong> or Groups<\/strong>.<\/li>\n\n\n\n
            2. Use the search field<\/strong> next to the dropdown to find and select the specific devices or groups. Each selection appears as a removable chip inside the field (for example, campbell ). You can select multiple devices or groups within the same target row.<\/li>\n\n\n\n
            3. To add another target, click the +<\/strong> icon at the end of the row. This creates a new numbered target row (Target 2, Target 3, …), which can use a different type (Devices or Groups) and its own selections.<\/li>\n\n\n\n
            4. To exclude specific devices from the overall scope, use Exclude Target<\/strong> and select the devices to leave out of the deployment, even if they belong to a selected group.<\/li>\n<\/ol>\n\n\n\n

              Note:<\/strong> Confirm the Exclude Target control’s exact location in your environment before publishing this section it may only appear after at least one target has been configured, rather than being visible from the start.<\/p>\n\n\n\n

              Step 3: Publish or Save as Draft<\/h2>\n\n\n\n

              Click Publish<\/strong> to run the deployment according to the configured schedule, or click Save as Draft<\/strong> to complete the deployment later.<\/p>\n\n\n\n

              Option<\/strong><\/th>Effect<\/strong><\/th><\/tr><\/thead>
              Publish<\/td>Activates the deployment according to the chosen schedule.<\/td><\/tr>
              Save as Draft<\/td>Stores the deployment configuration without activating it, so it can be reviewed or completed later.<\/td><\/tr>
              Cancel<\/td>Discards changes and exits without saving.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

              Understanding the Profile List<\/h2>\n\n\n\n
              Column<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
              Profile Name<\/td>The name given to the deployment when it was created.<\/td><\/tr>
              Platform<\/td>The operating system the deployment targets.<\/td><\/tr>
              Created By<\/td>The user who created the deployment.<\/td><\/tr>
              Created Time<\/td>The date and time the deployment was created.<\/td><\/tr>
              Version<\/td>The current version number of the deployment profile.<\/td><\/tr>
              Associated Devices<\/td>How many individual devices the deployment targets.<\/td><\/tr>
              Associated Groups<\/td>How many device groups the deployment targets.<\/td><\/tr>
              Profile Status<\/td>The current outcome of the deployment.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

              Profile Status Values<\/h3>\n\n\n\n
              Status<\/strong><\/th>Meaning<\/strong><\/th><\/tr><\/thead>
              In Progress<\/td>The deployment is currently running on its targeted devices or groups.<\/td><\/tr>
              Executed<\/td>The deployment completed successfully.<\/td><\/tr>
              Failed<\/td>The deployment did not complete successfully on one or more targets. Check the target devices for connectivity or agent issues.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

              Best Practices<\/h2>\n\n\n\n
                \n
              • Name deployments clearly enough that they’re identifiable later in the profile list without opening them.<\/li>\n\n\n\n
              • Turn on Retry on Failed Targets for unattended deployments, so temporary connectivity issues don’t require manual follow-up.<\/li>\n\n\n\n
              • Use Lan Only for large patches where you want to avoid consuming bandwidth on remote or metered connections.<\/li>\n\n\n\n
              • Review Failed deployments promptly rather than assuming a retry will resolve the issue on its own.<\/li>\n\n\n\n
              • Use Schedule Deployment for planned maintenance windows instead of deploying immediately during business hours.<\/li>\n<\/ul>\n\n\n\n

                Troubleshooting Tips<\/h2>\n\n\n\n
                Issue<\/strong><\/th>Resolution<\/strong><\/th><\/tr><\/thead>
                Publish button is disabled<\/td>Confirm a Policy Name is entered and at least one patch has been added.<\/td><\/tr>
                Profile Status shows Failed<\/td>Check the target device’s connectivity and agent status; enable Retry on Failed Targets if not already on.<\/td><\/tr>
                Profile Status stuck on In Progress<\/td>Confirm the target devices are online; offline devices only pick up the deployment once they reconnect.<\/td><\/tr>
                Deployment didn’t run at the scheduled time<\/td>Confirm the Start Date and Time Zone were set correctly, and that the profile was Published, not left as a draft.<\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"featured_media":0,"parent":3147,"menu_order":8,"comment_status":"open","ping_status":"closed","template":"","meta":{"_is_vendor_doc":"0","footnotes":""},"doc_tag":[],"class_list":["post-3452","docs","type-docs","status-publish","hentry"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/docs\/3452","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=3452"}],"version-history":[{"count":18,"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/docs\/3452\/revisions"}],"predecessor-version":[{"id":3564,"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/docs\/3452\/revisions\/3564"}],"up":[{"embeddable":true,"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/docs\/3147"}],"prev":[{"title":"Patch Scan","link":"https:\/\/zecurit.com\/help\/endpoint-management\/patch-management\/patch-scan\/","href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/docs\/3427"}],"wp:attachment":[{"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/media?parent=3452"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/zecurit.com\/help\/wp-json\/wp\/v2\/doc_tag?post=3452"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}