Drive more efficient patching with flexible patch deployment policies

You're adaptable. Your patching tool should be, too. With Patch Manager Plus, tailor your patching policies to meet specific industry needs. Select the deployment features you want most with native OS and third party application patching. In simpler words, Patch Manager Plus will work the way you do.

Patch Manager Plus lets you create patching policies to enable patching across all your enterprise's endpoints irrespective of their location and despite them being mobile, remote, or asleep.

Device a deployment policy for your organization

One deployment doesn't fit all, because enterprises vary with different sizes and different patching needs. Create a Deployment Policy to specify the installation and reboot options to be performed on the client computers while deploying a patch, software or a service pack. The multiple deployment settings will help decide when to deploy a patch to the operational environment, to plan how and when that deployment will take place, in order to ensure that it does not compromise business critical systems and applications.

  • You can determine the best time to deploy patches to networks of different sizes by specifying the start and end time in 'Deployment window.' Deployment will happen within the time limit specified here. If deployment is not completed, it will be continued during subsequent deployment window.
  • You can specify the preferred days for deployment by selecting on which weeks and which all days you want the patches to be deployed. For example, if you want to patch during weekends, you can select 'Saturday' and 'Sunday' and select 'All weeks'.

  • If you wish to schedule the deployment based on Patch Tuesday of that month, you can pick 'Based on patch Tuesday' as your preferred week split. Doing so, you will get the options in 'Preferred week(s) of deployment', based on Patch Tuesday. You can either choose the Patch Tuesday week or any consecutive week after Patch Tuesday as per your requirement.

  • You can also have multiple deployment windows for the same deployment policy by selecting "Add more schedules". This creates an additional deployment window and will come in handy in scenarios where a single deployment window won't suffice. For example, as an IT administrator, you can choose to have one deployment window post 8 pm on weekdays, and a second deployment window throughout the day on weekends.
  • Device policies that will meet the patching needs of different time zones. The User can set the time interval according to their time zone. The deployment will happen within the time limit specified by the User.
  • This policy based approach allows set-and-forget simplicity. Any policy can be marked as default patching policy so that it will be applied by default for all subsequent patch tasks created.
  • Notify the user about the deployment

    • Enables administrators to set a consistent time frame when a device can be patched and maintained.
    • Notify users about patch deployment via a notification message window. Users can also skip deployment if its seems to be a disturbance during their work-hours. This limits the impact on the end-user and their overall productivity.
    • Once you click on the checkbox of 'Notify Users about Deployment' you can customize your notification settings. You've to fill in the Deployment message title, Notification message during deployment, Notification Timeout in minutes, etc. The User can skip deployment. There's another checkbox which when enabled will show the Deployment Progress on the client computers.
    • Patch systems at the right time and under the right circumstances to avoid disrupting business operations.

    Turn ON computers before deployment

    If you wanted the updates to be deployed to the computers, which are turned off, then you can enable the check box to "Turn On Computers before deployment". Enabling this option, will allow the administrators to deploy the configuration to the target computers, which are within the network but turned off. If the target computers are available in the Corporate LAN/WAN network, then those computers will be turned on using Patch Manager Plus 's Wake On LAN feature and the configuration will be deployed. This feature will not work for computers which are not available in the corporate LAN/WAN.

    Download Patches/Software during subsequent Refresh Cycle

    This feature will download the binaries to the client computers prior to the deployment window. The binaries will be downloaded during the subsequent refresh cycle, system startup or deployment window whichever is earlier and the deployment will be initiated only during the specified deployment window. For instance, say the deployment window is from 4pm to 10pm. The policy has been created at 2pm. The next refresh cycle is at 3:30pm. Once the deployment window starts, these patches are deployed to the respective client machines.

    Choice of reboot policy

    Deployment of certain patches that are related to OS components, may force an immediate reboot; a critical operation for many environments especially when production servers are involved. Business-critical computers may have specific times at which changes and computer restarts are permitted. Here, the deployment of a software patch or any system restarts that are required should not be scheduled. Patch Manager Plus lets you customize reboot policies post deployment. Patch Manager Plus offers a choice of the following reboot options:

    • Force reboot when user has logged in
    • Force shutdown when user is logged in
    • Allow user to skip reboot/postpone reboot
    • Allow user to skip shutdown/postpone shutdown