by Mark | Sep 8, 2019 | How To, Microsoft HyperV, Snapshot / Checkpoint, VMWare
How to schedule the snapshot of multiple VMware or Hyper-V Virtual Machines with auto deletion.
Every so often you need to schedule a snapshot on a virtual machine, whether that be a VMware virtual machine or a Hyper-V virtual machine, or even multiple virtual machines because someone or something is going to be changed and you need a quick way to roll them back to a running state, just in case things go belly up. It’s a very common task that administrators need to do. Other times you need to create a snapshot on a schedule, whether it’s a one-off snapshot at a specific date and time, or a recurring one that happens every week or month. Doing this using the standard vCenter console is fairly simple and easy to do. But how do you schedule it for multiple VMs? And to then also automatically remove the snapshot? Or what if you have a combination of VMware and Hyper-V? Doing that usually involves a combination of scheduled tasks via the console and PowerShell with PowerCLI.
But the easiest and simplest way by far is to use Snapshot Master. Hopefully you have installed and are running Snapshot Master in your environment, if not, you can download and request a 30 Day trial key and try it out for yourself.
Creating a schedule to snapshot one or multiple virtual machines and then automatically deleting the snapshot after a period you define is a walk in the park.
OK, so now that I’ve talked up Snapshot Master and how easy it is to create a scheduled snapshot on one or multiple VMs either VMware or Hyper-V with auto-deleting the snapshot, how do you actually do it?
Snapshot Scheduling Use Cases
Use Case |
Why Schedule a Snapshot? |
Testing and Development
|
To quickly roll back changes made to a virtual machine during testing and development. |
Software Upgrades
|
To create a snapshot before performing a software upgrade, in case the upgrade causes issues that need to be rolled back. |
Disaster Recovery
|
To have a recent snapshot available in the event of a disaster or data loss. |
Compliance
|
To maintain compliance with data retention policies or audit requirements. |
Resource Optimization
|
To free up disk space on a virtual machine by automatically deleting old snapshots after a specified time period. |
Performance Tuning
|
To create a snapshot before making changes to a virtual machine’s configuration or performance settings, in case the changes negatively impact performance. |
By scheduling snapshots, you can ensure that you have a recent backup of your virtual machines that can be easily restored in the event of issues or data loss. Additionally, scheduling snapshots can help you meet compliance requirements, optimize resource usage, and improve the overall performance of your virtual environment.
Launch Snapshot Master
The first step is to open Snapshot Master. Ensure that you have already installed Snapshot Master on your system. If not, you can download it and request a 30-day trial key to test it out.

Select the Virtual Machines you want to Schedule a Snapshot
Once you launch Snapshot Master, select the virtual machines you want to snapshot. You can do this by either placing a tick in the checkbox or double-clicking the row.

Take a Virtual Machine Snapshot
Right-click anywhere on the screen, move to Selected VMs, and click Take Snapshot. A dialog box will appear to give the job a name and description. Tick the box to automatically delete the snapshot and use the drop-down list to select the number of days after which it should be deleted, then press OK.

VM Snapshot Name
Give the job a name and description. Tick the box to automatically delete the snapshot and use the drop down list to select the number of days it should be deleted in and press OK.

VM Snapshot Execute Now or Scheduling
Click Schedule job.
Note, if you need to run a pre or post script along with this job, you may call it here.

Schedule VM Snapshot Creation
Click New and setup the schedule for this job.
Press OK when done.
SnapShot Master will now start the snapshot / checkpoint creation process, at the schedule you have created.


Scheduled VM Snapshot Job Notification
You will receive a notification letting you know the job has been scheduled.

Scheduled VM Snapshot Email Alerts
That’s all there is to it. Doesn’t get much easier than that. And if you have setup email notifications, you will receive an email detailing the success and failures of the job.

SnapShot Master FAQs
Question |
Answer |
What is Snapshot Master?
|
Snapshot Master is a software tool that simplifies the process of creating and managing snapshots of VMware and Hyper-V virtual machines. |
How does Snapshot Master work?
|
Snapshot Master provides a user-friendly interface for scheduling and creating snapshots of virtual machines, as well as automatically deleting old snapshots after a specified time period. It also supports pre- and post-snapshot scripts for more advanced customization. |
Can Snapshot Master handle both VMware and Hyper-V virtual machines?
|
Yes, Snapshot Master can create and manage snapshots for both VMware and Hyper-V virtual machines. |
Is Snapshot Master easy to use?
|
Yes, Snapshot Master is designed to be simple and user-friendly, with an intuitive interface that makes it easy to schedule and create snapshots of virtual machines. |
Can I try Snapshot Master before purchasing it?
|
Yes, a free 30-day trial version of Snapshot Master is available for download. |
What are the system requirements for Snapshot Master?
|
Snapshot Master requires Windows 7 or higher and .NET Framework 4.5 or higher. It also requires administrative privileges to install and run. |
Does Snapshot Master provide email notifications?
|
Yes, Snapshot Master can send email notifications to inform you of the success or failure of snapshot jobs. |
Can Snapshot Master automate the snapshot creation and deletion process?
|
Yes, Snapshot Master can automatically create and delete snapshots on a schedule that you define. |
What other features does Snapshot Master offer?
|
Snapshot Master also includes the ability to clone virtual machines, and provide email reports of your virtual environment. |
Automate VM Snapshot creation and deletions
Taking snapshots on multiple VMs has never been easier than with Snapshot Master. It’s a simple, automated process that helps to ensure the protection of your virtual machines. Snapshot Master is also capable of managing other aspects of your virtual machines. You can download a free fully functioning trial of Snapshot Master to explore its capabilities.
Free Fully Functioning Trial available to download.
by Mark | May 27, 2017 | How To, Microsoft HyperV, Patch Management, SCCM, VMWare
Automate Snapshot Creation Before Deployment
Reduce Patching Risks with SnaPatch
System administrators are responsible for ensuring the smooth functioning of their organization’s computer systems. They are the ones who deploy new software and updates, perform maintenance tasks, and troubleshoot any issues that arise. However, keeping these systems up-to-date can be a daunting task, especially when new updates and patches are released frequently. This is where taking a snapshot before patching comes into play.
A snapshot before patching is a crucial tool that system administrators can use to protect their systems from vulnerabilities. In this article, we will discuss why taking a snapshot before patching is essential and how it can help system administrators safeguard their systems.
What is a Snapshot Before Patching?
A snapshot before patching is a backup copy of your system’s current state. This copy can be used to restore your system to its previous state in case something goes wrong during the patching process. Taking a snapshot before patching ensures that you have a stable and reliable system to fall back on if the patching process fails.
Why is a Snapshot Before Patching Important?
Taking a snapshot before patching is essential for several reasons. Here are some of the main reasons why system administrators should make this a standard practice:
- Protects Against System Failure: Patching can sometimes cause system failures. Having a snapshot before patching ensures that you can quickly restore your system to its previous state in case of such failures.
- Provides a Safe Environment for Testing: Taking a snapshot before patching allows system administrators to test the patches in a safe environment. This ensures that any issues that arise during the testing process can be addressed before the patches are applied to the live system.
- Helps in Disaster Recovery: Snapshots can be used as part of a disaster recovery plan. In case of a disaster, snapshots can be used to restore your system to a previous state.
Best Practices for Using Snapshots Before Patching
Here are some best practices for using snapshots before patching:
Always Test Patches:
Test patches in a safe environment before applying them to the live system.
Schedule Regular Snapshots:
Schedule regular snapshots so that you always have an up-to-date backup of your system.
Name Your Snapshots:
Give your snapshots meaningful names so that you can easily identify them.
Store Snapshots Securely:
Store your snapshots in a secure location to prevent unauthorized access.
Snapshots Before Patching FAQs
What is the difference between a snapshot and a backup?
A snapshot is a point-in-time copy of your system, whereas a backup is a copy of your system’s data that is stored separately.
How often should I take a snapshot before patching?
It depends on your organization’s needs. However, it is a good practice to take a snapshot before each patching session.
Can I take a snapshot of a virtual machine?
Yes, you can take a snapshot of a virtual machine. In fact, taking snapshots of virtual machines is a common practice in virtualized environments.
What happens if I don’t take a snapshot before patching?
If you don’t take a snapshot before patching, you run the risk of losing important data or causing system failures.
How to Snapshot before deploying Patches.
How SnaPatch Can Help You Take Snapshots Before Patching
When it comes to taking snapshots before patching, it can be a time-consuming and manual process for system administrators. However, there is a tool that can simplify the process and make it more efficient: SnaPatch.
What is SnaPatch?
SnaPatch is a software application that interacts with your Microsoft System Centre Configuration Manager (SCCM) environment to pull in all your machine information. It uses SCCM as the source of truth for all your VM information.
Next, it interfaces with either your vCentre or System Centre Virtual Machine Manager (SCVMM), or both. It takes control of your VM environment, allowing it to create and delete snapshots of your VMs.
How does SnaPatch work?
SnaPatch simplifies the snapshot process by automating it. It creates a snapshot of any virtual machine before allowing it to be patched. If the snapshot fails, the VM will not receive updates and will be removed from the patching schedule. SnaPatch streamlines the process and frees up your time by automating the snapshot and patching processes, while keeping you updated on progress via email notifications.
How do you deploy SnaPatch?
Deploying SnaPatch is easy and straightforward. After installation, the application discovers your SCCM environment and allows you to configure various settings such as email notifications, snapshot creation, and patch deployment.
Why use SnaPatch?
SnaPatch helps you take snapshots before patching in a more efficient and streamlined manner. It complies with SOX regulations and minimizes risk, and its automated snapshot creation feature ensures that you can easily roll back updates if necessary, giving you peace of mind and more time to focus on other critical tasks.
Conclusion
In conclusion, taking snapshots before patching is a critical step in ensuring the security and stability of your systems. SnaPatch can help simplify and automate this process, allowing you to deploy Microsoft updates in your VM environment safely and efficiently. Try SnaPatch today and streamline your patching process!
by Mark | Aug 9, 2016 | How To, Microsoft HyperV, Snapshot / Checkpoint, VMWare
How to snapshot multiple VM servers with SnapShot Master
SnapShot Master is a software that helps to create or delete snapshots of multiple VMs in unison. It is a useful tool for VMware’s Vsphere and Microsoft’s HyperV users. With this software, taking snapshots of multiple VMs is a relatively easy task. In this article, we will guide you through the process of snapshotting multiple VM servers using SnapShot Master.
Installing SnapShot Master Before you can use SnapShot Master, you need to install it in your environment. If you haven’t done so, you can download the software and request a 30-day trial key. Once you have installed and are running SnapShot Master in your environment, you can proceed to snapshot multiple VMs.
Synchronous or Asynchronous Snapshotting SnapShot Master can perform snapshotting synchronously or asynchronously. This means that it can keep systems that need to be in sync, have snapshots taken at the same time, or one after the other. To learn more about the functions of SnapShot Master, click this link.
Syncing with Your Virtual Environment Open your SnapShot Master console and let it synchronize with your VMware or HyperV environment. Depending on your virtual environment, this may take some time.
The need arises at times for the creation or deletion of snapshots of multiple VMs in unison. Creating snapshots of multiple VMs (virtual servers) for VMware’s Vsphere or even for Microsoft’s HyperV with SnapShot Master is a relatively easy task. Hopefully you have installed and are running SnapShot Master in your environment, if not, you can download and request a 30 Day trial key and try it out for yourself.
SnapShot Master can do this synchronously or asynchronously. This can keep systems that need to be in sync, have snapshots taken at the same time, or one after the other. To learn more about the functions of SnapShot Master, click this link.
VM Console Screen
Open you SnapShot Master console and let it synchronise with your Vmware or HyperV environment. Depending on your virtual environment, this may take some time.
Virtual Machines Populated.
Now that the console has populated, Tick the checkboxes of the corresponding virtual machines that you wish a snapshot to be performed for.
Virtual Machine Selection
Once you have selected the multiple VMs for a snapshot, right click on any VM and scroll down the drop down menu to Selected VMs then across to Take Snapshot.
VM Snapshot Name
Once you have selected the multiple VMs for a snapshot, right click on any VM and scroll down the drop down menu to Selected VMs then across to Take Snapshot.
Execute or Schedule VM Snapshot Job
You are now prompted to either Execute Now or Schedule Job. If you choose to execute now, the job will start to immediately snapshot multiple VMs. To schedule the snapshot for a later time, choose Schedule Job.
Schedule Snapshot Time
We now need to create a schedule for when you wish the snapshots to be performed. Click on New in the scheduling window and set the Date and Time then close the Windows.
Scheduled Snapshot Notifications
So thats all there is to it. You have chosen the virtual machines that require a snapshot, set your snapshot schedule and SnapShot Master will complete all this. If you have setup email notifications, you will receive emails detailing success and any failures.
Taking a snaphot multiple VMs has never been easier than with SnapShot Master. To learn what else SnapShot Master can do, other than snapshot multiple VMs, click this link.
Download a trial of SnapShot Master today.
To trial SnapShot Master, fill in the form below to get access to download the trial software.
FREE DOWNLOAD
SnapShot Master FAQs
Disaster Recovery
SnapShot Master can be used to create snapshots of multiple VMs at once, ensuring that all the VMs are captured at the same point in time. This makes it easy to restore the VMs in case of a disaster.
Testing and Development
SnapShot Master can be used to create a snapshot of a VM before making any changes. This allows developers and testers to revert back to the original state if anything goes wrong during testing.
Reporting and Auditing
SnapShot Master can be used to create snapshots of VMs on a regular basis for reporting and auditing purposes. This ensures that you always have a historical record of the VMs.
Performance Tuning
SnapShot Master can be used to create snapshots before making any performance tuning changes. This allows you to compare the performance of the VM before and after the changes.
Patch Management
SnapShot Master can be used to create snapshots before applying patches to the VMs. This ensures that you have a backup of the VM before applying any changes.
Overall, SnapShot Master is a versatile tool that can be used for a variety of use cases, providing a simple and efficient way to create and manage snapshots of multiple VMs.
by Mark | Aug 8, 2016 | How To, Snapshot / Checkpoint, VMWare
How to Schedule a VMWare Snapshot.
Before I show you how to use SnapShot Master to create and schedule a VMWare Snapshot I will briefly describe what a snapshot is.

VMWare Snapshots are a crucial feature of the VMWare environment that allows you to roll back to a specific point in time in case of any issues. Snapshots can be created manually but, it is essential to have an automated process to make the process easier and more efficient. This is where SnapShot Master comes in.
What is a VMWare Snapshot?
VMWare Snapshots are a quick and easy way to provide a previous point in time in which you can revert your virtual machine to. Snapshots are a great feature to use prior to performing any risky upgrades, applying Windows updates or hardware reconfiguration as they give you the benefit of a fast roll back point should any issues occur.
When creating a VMWare Snapshot a differencing disk is created with *–delta.vmdk extension and an .vmsn file for configuration changes. the VMWare Snapshot preserves the state of the virtual machine at a specific point in time. (These new files leave the original VMDK files intact, hence allowing you to have a role back position.)
The more Snapshots you create, the more disk space you will utilise. It is also worth noting that the VM will also have its performance effected by each snapshot created.
VMWare Snapshot Tree
From within VMWare’s Vcentre, you can select the VM you want and view the VMWare Snapshot Tree. This shows each and every snapshot created for the virtual machine selected.
Each subsequent snapshot stems from the previous one with the delta changes stored on the snapshot’s disk which is the difference between the current state and the last snapshot created.
Scheduling a VMWare Snapshot
VMWare sheduled snapshot creation
Now that you understand VMWare Snapshots a little better, we can now start automating and scheduling their creation and deletion
Open your SnapShot Master console and let it sync with your VMWare environment and populate the console with your virtual machines.
VMWare VM snapshot Selection
Once all your virtual machines have shown up, choose the VMs you want to create a snapshot for by checking the checkbox. You can choose to either do a single machine or multiple machines. In this example Ill create a snapshot for multiple VMs. Right Click any VM and from the menu go to Selected VMs then Take Snapshot.
VMWare VM snapshot Name
Give the Snapshot a Name and Description then click OK.
This makes it easier to identify what the scheduled snapshot was created for at a later date.
VMWare VM snapshot Options
Next we can choose to Execute Now or Schedule Job. I have chosen to schedule the Vmware snapshot creation.
If you choose Execute now, SnapShot Master will immediately create a snapshot of the VMs you have selected.
VMWare VM snapshot Description
You can now give the Scheduled VMWare snapshot job a name then click OK.

VMWare VM snapshot scheduled task
The task scheduler window now starts up. Click on NEW to create a new scheduled task.
Date and Time for the Scheduled Snapshot
Choose a date and time that you want to schedule the VMWare Snapshot for then click OK and then Click OK again on the task scheduling window. The VMWare Snapshots will now be automated and created at the time you have scheduled.
Scheduled Snapshot Status
To view Job Status of your scheduled tasks within SnapShot Master, go to the JOBS tab and then Scheduled Jobs. You can see Active / Recent Jobs, Scheduled Jobs as well as Job History.
Scheduled Snapshot Email Alerts
Now when the time you have scheduled the creation of the VMWare Snapshot comes, SnapShot Master will automate this. If you have email notifications setup within SnapShot Master, you will receive emails detailing when the job started and finalised.
AUTOMATE AND SCHEDULE SNAPSHOTS EASILY WITH SNAPSHOT MASTER
Want to simply Schedule Snapshot Creations and Deletions?
Now when the time you have scheduled the creation of the VMWare Snapshot comes, SnapShot Master will automate this. If you have email notifications set up within SnapShot Master, you will receive emails detailing when the job started and finalized.
Conclusion Automating and scheduling VMWare Snapshots with SnapShot Master is an easy and efficient process that can save you time and effort. It is essential to have a robust backup and disaster recovery strategy in place, and SnapShot Master can play a crucial role in this. If you want to simplify the process of scheduling and managing VMWare Snapshots, consider downloading a trial of SnapShot Master today.
Download a trial of SnapShot Master today.
To trial SnapShot Master, fill in the form below to get access to download the trial software.
FREE DOWNLOAD
To learn more about the features of SnapShot Master to simply automate and schedule snapshots.
by Mark | Jul 5, 2016 | Deployment, How To, Patch Management, Patch Releases, Risk, SCCM, Security
Deploying a Zero Day Exploit Fix with Microsoft SCCM 2012
Zero Day exploits are vulnerabilities that are found and can be used by hackers to exploit and use for malicious or personal intent. These exploits have been known to affect both software and hardware, causing issues to programs, data, computers, and networks. Once a patch or fix is released by the vendor, the issue is no longer known as a Zero Day vulnerability. In this article, we will discuss how to remediate Zero Day attacks and how to deploy a Zero Day exploit fix using Microsoft SCCM
Remediating Zero Day Attacks
Unfortunately, there isn’t much that can be done until a fix or update is released that patches the security hole. Once a patch is released, it is best to deploy and apply the patch as soon as possible. To reduce the risk of unknown vulnerabilities, it is good practice to keep your hardware and software up to date. This will remove any previously found vulnerabilities from your environment as patches are applied. Having a patching process in place and suitable infrastructure to do so (e.g., Microsoft SCCM and SnaPatch) where you can deploy updates easily and often are also good practices.
Deploying a Zero Day Exploit Patch Using SCCM
Unfortunately, there isn’t much that can be done until a fix or update is released that patches the security hole. Once a patch is released, it is best to deploy and apply the patch as soon as possible. To reduce the risk of unknown vulnerabilities, it is good practice to keep your hardware and software up to date. This will remove any previously found vulnerabilities from your environment as patches are applied. Having a patching process in place and suitable infrastructure to do so (e.g., Microsoft SCCM and SnaPatch) where you can deploy updates easily and often are also good practices.
Zero Day Exploit Overview
So what exactly is a Zero Day Exploit you ask? To be exact, a Zero Day Exploit is a vulnerability that is found that a possible Hacker can use to exploit and use for malicious or personal intent. The Vendor (software or hardware) has Zero Days to plan, mitigate and fix the issue so that there is no further exploitation of the vulnerability. The exploits have been known to be for either software (Operating Systems and Software) and hardware. They have been known to cause issues to programs, data, computers and to the network.

Zero Day Attack Timeline
In the case of a breach being found in some software, a Zero Day Exploit normally follows this;
- A hacker finds a vulnerability with a product (software/hardware).
- The hacker writes an exploit and uses it either to be malicious or financial gain.
- Exploit is detected either by Users, Security Companies or the Vendor themselves.
- The Vendor studies the new exploit and develops a fix.
- The Vendor releases a new patch to fix the exploit
- Users install the Patch or Virus Definition update.
The biggest issue with a Zero Day Exploit is that they are generally unknown until they have been used to breach systems, leaving everyone vulnerable until the Vendor releases security advice on how to remediate the issue or a patch or update. This could be days, weeks, months or even years before the Vendor learns of the vulnerability. Once a Patch or Fix has been released by the Vendor, then the issue is no longer known as a Zero Day Vulnerability.
How to remediate Zero Day Attacks
Unfortunately there isnt much that can be done until there is a fix or update released that patches the security hole. Once a patch is released it is best to deploy and apply the patch as soon as is possible.
To also reduce the risk, it is good practice which will aid you in mitigation of vulnerabilities that are unknown to yourself if you keep your hardware and software patched up to date. This will remove from your environment any previously found vulnerabilities as patches are applied. Having a Patching Process in place and suitable infrastructure to do so (ie Microsoft SCCM and SnaPatch for instance) where you can deploy updates easily and often are also good practice.
Using SCCM to deploy a Zero Day Exploit Patch
If you are using Microsofts SCCM 2012, you can easily deploy an update that addresses a Zero Day Vulnerability by following these steps;
- Log on to your SCCM console, then go to Software Library, then expand Software Updates and highlight All Software Upates. Now Right Click and choose Synchronise Software Updates. This will synchronise your SCCM server with your WSUS updates server. Allow a few minutes for the new updates to populate the view. You can check the Wsyncmgr.log to view the update synchronisation.

- If you know the Bulletin ID number (the update number released by Microsoft in the format MSXX-XXX. In this example I am choosing MS16-082), you can now search for this within the console.

- Make sure that the update has downloaded and if not, right click the update and choose Download. You will obviously need to give the update sometime to download in to your environment and be ready for deployment. Click this link to see how to manually download updates if you dont know how.

- When the update is downloaded and ready for deployment, you are now ready to deploy the Update. (If you are using SnaPatch to deploy the updates, go straight to the SnaPatch Section below.)
Right Click the update (or updates) and choose Deploy.
Enter in a Deployment Name, a Description, and choose the collection you wish the Zero Day exploit to deploy to. Once you have chosen the correct settings, click on Next.
- On the Deployment Tab, leave the type of deployment as Required and choose the level of detail you want then click on Next.

- Now to schedule when you want the update to deploy. As this is a Zero Day Exploit that you want patched quickly, schedule the patch to be available As Soon As Possible for both the Software Available Time and Installation Deadline. Please note, that more often than not, the installation of an update will cause systems to restart. Please make sure you have informed the appropriate people and that you have approval for deployment. Nothing worse than deploying an update and having to answer to Management as you caused unwarranted system outages.

- The User Experience Tab is where you set how the deployment will interact with Users. You can set if the users are notified within the Software Centre that an update is available for installation, when the deployment deadline is reached whether the update can install and restart the system outside a maintenance window, and finally whether you wish to suppress a system restart. As this is an urgent deployment, I have chosen to allow installation and restart to be allowed outside any maintenance windows. Choose the settings you require and click on Next.

- If you have System Centre Operations Manager (Microsoft SCOM) in your environment you can choose to generate an alert with criteria you specify. In this example we are not going to specify any settings. Click on Next when you have made your selections.

- The Download Settings tab allows you to choose client download settings. If a client is on a slow or unreliable network boundary you can choose if they dont install the update or from another distribution point. Allowing clients to share content between themselves is a great feature of SCCM as it will stop other client machines downloading the same updates and possibly flooding a network link. The clients will all share the update between themselves if they are on the same subnet. Also if they cannot download the update from a SCCM distribution point, allowing them to download from Microsoft Update is available as well.
Click on Next when ready to.
- Now you can review all the settings on the Summary Tab. Confirm you are happy with all the settings and then click Next.

- The progress of the deployment will now be shown.

- Your Zero Day Exploit deployment should now be ready to be deployed to your SCCM clients as per the settings you have set.

Using SnaPatch for Zero Day Exploit Deployment
If you are using SnaPatch to aid you with the deployment of Windows Updates with Microsoft’s SCCM, you can follow on from Steps 1 to 4 from above.
- Open the SnaPatch console and choose the SnaPatch Icon to start the snapshot and patch deployment process.

- Now you are presented with all the SCCM Collections and Systems available to deploy the Zero Day Exploit to. Choose the systems you want to receive the patch and click on Add.

If the machines are virtual (either a VMWare or HyperV virtual machine) you can choose whether to take a snapshot of the servers prior to deployment of the zero day patch. Should the servers not have a successfully snapshot completed, then they will not receive the update deployment. The snapshot of the virtual machines gives you a quick rollback position should the update cause an issue in your environment.
When you have chosen all the machines you wish and if you would like a snapshot, click on the green arrow to continue.
- The next window in the SnaPatch process, is to chose the update you wish to deploy. As this is a Zero Day patch and we know the Microsoft article number (which in this example is MS16-082), type in the KB or MS article number and choose search.
Select the update, confirm that it has been downloaded (as per step 3 above) and now choose if you want the update to deploy to an existing Update Group or to create a new one. 
- As this is an urgent deployment, I am choosing Create & Deploy Update Group. Give the Software Update Group a Name and Description and click Create.

- Confirmation that the Software Update Group has been created. Click OK.

- Next we have to schedule deployment. Click Schedule Job.

- Now on the scheduling window, click on New.

- Choose an appropriate schedule when you would like the deployment to happen. This will set up the update deployment for the time you specify. Click OK when you are ready to proceed, then close the scheduling Window.

- On the Maintenance Window choose the duration you want the snapshots to be performed and the updates to be installed during. Click on Finish when complete.
Thats all there is to it. SnaPatch will now create a deployment of the Zero Day Exploit Patch within Microsoft SCCM and set the Maintenance Window. When the maintenance window is reached, SnaPatch will interact with your Vmware or HyperV hosts and start a snapshot of the servers you have selected. Once the snapshot is complete SnaPatch then contacts SCCM and allows SCCM to deploy the patch to those servers. You will also receive email notifications throughout the snapshot and deployment process.
Click for further information on SnaPatch Patch Management.
Zero Day exploits can cause serious issues to programs, data, computers, and networks. It is essential to deploy patches and fixes as soon as possible to reduce the risk of exploitation. Using Microsoft SCCM 2012 to deploy a Zero Day exploit fix is an easy process that can be completed by following the steps outlined above. Keeping your hardware and software up to date and having a patching process in place are good practices to mitigate the risk of unknown vulnerabilities.