How to schedule a snapshot on multiple Virtual Machines.

How to schedule a snapshot on multiple Virtual Machines.

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.

Snapshot auto delete 1

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.

Snapshot auto delete 2

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.

Snapshot auto delete 3

VM Snapshot Name

Give the job a name and descriptionTick 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.

Snapshot auto delete 4

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.

Snapshot auto delete 5

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.

Snapshot auto delete 6Snapshot auto delete 7

Scheduled VM Snapshot Job Notification

You will receive a notification letting you know the job has been scheduled.

Snapshot auto delete 8

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 auto delete 9

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.

Step by step guide on how to install Microsoft’s System Centre Virtual Machine Manager (SCVMM)

Step by step guide on how to install Microsoft’s System Centre Virtual Machine Manager (SCVMM)

How to install Microsoft’s System Centre Virtual Machine Manager (SCVMM)


scvmm install

System Centre Virtual Machine Manager (SCVMM)

 If you run Microsoft’s Hyper-V as your virtualisation platform rather than the ever popular VMware ESX then you probably want a way to manage your Hyper-V hosts as well as the virtual machines that reside on this. Well you can do a lot of the functions that SCVMM does with the free tool for managing Hyper-V, the Hyper-V Manager (which comes as part of the Windows Operating System).

So if they are similar why would we use System Centre VMM over and above the Hyper-V Manager you ask and have to pay more money to Microsoft?

Well I list out the main differences here to hopefully guide you to a decision before going through the installation process of SCVMM later on down the page.

SCVMM vs Hyper-V Manager Key Differences

Hyper-v Manager

  • Can manage the Hyper-V hosts and the virtual machines that reside on it.
  • Can manage a single host or multiple Hyper-V hosts that are members of a failover cluster.
  • Requires Failover Cluster manager to manage multiple hosts.
  • Requires powershell to setup affinity rules.
  • No single pane of glass to manage your complete Hyper-V environment which requires you to utilise the Hyper-V Manager console, Failover Cluster console and then powershell to do only some of what SCVMM can do.

System Center Virtual Machine Manager

SCVMM can do all the Hyper-V Manager does from a single console.;

  • Configure and manage your datacentre components as a single fabric in SCVMM. (Datacentre components include virtualization servers, networking components, and storage resources.)
  • SCVMM can add, provision, and manage Hyper-V and VMware virtualization hosts and clusters. SCVMM can manage VMware ESX servers and its virtual machines in limited capacity. It does however require you to have a VMware vCentre to connect to, to be able to manage your VMware virtual machines.
  • Add networking resources to the SCVMM fabric, including network sites defined by IP subnets, virtual LANs (VLANs), logical switches, static IP address and MAC pools.
    SCVMM provides network virtualization, including support for creating and manage virtual networks and network gateways. Network virtualization allows multiple tenants to have isolated networks and their own IP address ranges for increased privacy and security.
    Using gateways, VMs on virtual networks can connect to physical networks in the same site or in different locations.
  • SCVMM can discover, classify, provision, allocate, and assign local and remote storage.
    SCVMM supports block storage (fibre channel, iSCSI, and Serial Attached SCSI (SAS) storage area networks (SANs)).
  • The SCVMM fabric retains a library of file-based and non file-based resources that are used to create and deploy VMs and services on virtualization hosts.
    File-based resources include virtual hard disks, ISO images, and scripts.
    Non file-based resources include templates and profiles that are used to standardize the creation of VMs. Library resources are accessed through library shares.
  • Integrates with Azure (Though you cannot change settings of the Azure VMs but you can see them and at least stop and start them from your SCVMM console)

The biggest issue with using Hyper-V Manager over System Centre VMM is that it cannot scale to manage large environments, and with having three different consoles (Hyper-V Manager, Failover Cluster Manager and then Powershell) can be quite daunting to use to it’s full ability.

SCVMM Capacity Limits

Planning for your SCVMM deployment is a good practice and you want to make sure to size it right for your environment. The suggested limits of the software Microsoft details for SCVMM deployment are in the table below;

Entity Recommended maximum count
Physical hosts 1000
Virtual Machines 25000
Services 1000
User roles 1000
Clouds 20
Virtual networks 2000
logical networks 20
Library resources 1000
Library Objects (templates, profiles) 100

SCVMM Limits

Recommended hardware requirements are;

Hardware VMM server VMM database VMM library VMM console
Processor (minimum) 8 core Pentium 4, 2 GHz (x64) 8 core Pentium 4, 2.8 GHz 4 core Pentium 4, 2.8 GHz 2 core Pentium 4, 1 GHz CPU
Processor (recommended) 16-core, 2.66 GHz CPU 16 core 2.6 GHz CPU 4 core 2.8 GHz CPU 2 core 2 GHz CPU
RAM (minimum) 4 GB 8 GB 2 GB 4 GB
RAM (recommended) 16 GB 16 GB 4 GB 4 GB
Hard drive (minimum) 4 GB 50 GB Based on size/amount of stored files 10 GB
Hard drive (recommended) 10 GB 200 GB Based on size/amount of stored files 10 GB

SCVMM Operating System Requirements

The recommended Windows Operating System requirements for SCVMM 2019 are

  • Windows 2016 Server Core
  • Windows 2016 Full Desktop Experience
  • Windows 2019 Server Core
  • Windows 2019Full Desktop Experience.

SCVMM Database Requirements

The last piece to the SCVMM puzzle, is the database it requires. Obviously this database is another Microsoft product, SQL Server.

The supported Microsoft SQL database versions for SCVMM 2019 are;

  • SQL 2016
  • SQL 2017

How to install System Centre Virtual Machine Manager.

A step by step guide to install SCVMM.

Now that you can see the benefits to installing and using SCVMM to manage your Hyper-V hosts and it’s Virtual Machines. We will now get to the installation part to guide you through the process. I am going to assume here that you already have your Hyper-V hosts up and running and are ready to start your installation. To continue on with this installation guide I will run you through my current infrastructure setup. I have a newly deployed Hyper-V host and have prebuilt some generic virtual machines that are running on it. I am using a demo version of SCVMM which you can download for yourself from the Microsoft site (link here) and I have already predownloaded the files ready to start the installation.

So what are the prerequisites to install SCVVM? Obviously besides the requirements detailed up above, you will need a functioning Hyper-V environment to install the SCVMM on to, as well as administrator access to manage the Hyper-V hosts. As I have downloaded an image from Microsoft and if you are doing the same you will need Domain Administrator access to add the SCVMM Windows server to the domain.

Launch SCVMM Installer

Since the files are downloaded to my location machine, browse to the SCVMM install files through windows explorer. To start the install, just run the Executable file


Installing SCVMM

Now the installation starts, click on NEXT on the SCVMM install welcome screen.


scvmm installation

SCVMM License Agreement

Accept the license agreement (make sure to read them if you wish) and click on NEXT.


scvmm install license agreement

SCVMM Installation Location

The SCVMM install needs to extract the downloaded files. Choose an appropriate folder location and make sure you have enough free disks space (approximately 28GB is needed) then click on NEXT.


scvmm install location

SCVMM File Extraction

You are now ready to extract the SCVMM files needed for the installation. Confirm the settings and folder looks right then click on EXTRACT.


scvmm install file extraction

SCVMM Install Extracting

The installation files will now extract from your downloaded media. This will take a little bit of time to complete the extraction process.


scvmm install extracting

SCVMM File Extraction Completed

Now the extraction of SCVMM is complete. Click on FINISH.


scvmm install extraction complete

SCVMM Import

Next we need to connect to one of your Hyper-V hosts with the Hyper-V Manager console to start the import of the SCVMM Virtual Machine. Open up your Hyper-V console and connect to your host.


scvmm hyper-v

SCVMM New Virtual Machine

We now need to build a new VM for the SCVMM server. Click on ACTIONthen NEWthen VIRTUAL MACHINE.


scvmm new vm

New Virtual Machine Wizard

The New Virtual Machine Wizard starts up, click on NEXT to proceed.


scvmm new virtual machine

New Virtual Machine Location

On the Specify Name and Location tab give your VM a name and you can choose where to store the VM files. When you have done that click on NEXT.


scvmm new vm location

VM Generation Selection

The Specify Generation window, make sure that Generation 1 is selected then click on NEXT


VM Memory Settings for SCVMM

Remember the minimum memory suggested by Microsoft above? Well if you dont, the minimum memory recommended was 4GB so as this is just a lab but I want some performance Im changing that to 8GB. When you have selected the memory size click on NEXT.


VM Virtual Switch Settings

Choose with virtual switch you want to deploy this VM to then click NEXT.


scvmm install networking

SCVMM Virtual Hard Disk Settings

This is one of the most important parts of the install process, make sure to change the virtual hard disk to Use an existing virtual hard disk and browse to the extracted location of the SCVMM download. When you have done that click NEXT.


SCVMM VM Deployment

Review everything on the Summary Tab and if you are happy to proceed with the SCVMM deployment click on Finish


scvmm install vm deployment

Power ON SCVMM VM

Now go back to your Hyper-V console and browse through your virtual machines until you find your newly deployed SCVMM virtual machine


Start SCVMM Installation

To start the installation you will need to power it on and open a console session so you can see what is happening.


scvmm start installation

Install Windows 2019 Server

We have to now run through the Windows 2019 server installation. Choose your country / region then click NEXT


win2019 install

Windows 2019 Server License Agreement

More license terms for you to read through, when you are happy to accept them, click on ACCEPT.


win2019 license agreement

Local Administrator Password Creation

Now provide a local administrator password and then click FINISH then the server will restart


local admin password

Login to SCVMM Server

Once Windows 2019 server has installed, log on to the server with the local administrator credentials you put in previously


win 2019 logon screen

SCVMM join Active Directory Domain

We now need to join the SCVMM virtual machine to the domain, so open up CONTROL PANEL then go to SYSTEMChange the virtual machine name so you can easily identify it in the future and add the VM to your Active Directory Domain and dont forget to Reboot the server.


Install SQL Server for SCVMM

So after your SCVMM server has rebooted and is joined to your domain, we next need to start the installation of the SQL Database if you have not got one already. On the desktop of my Windows 2019 VM, I can see Microsoft has placed two icons for me to use to start the SCVMM installation. Luckily in this case they tell me to start the SQL Server install first, so we need to DOUBLE CLICK on that.


scvmm install sql

SQL Product Key

On the Product Key page for the SQL install, put in your license details and click on NEXT.


sql install product key

SQL License Agreement

Accept the license terms and click NEXT.


sql license agreement

SQL Global Rules

On the Global Rules tab, the SQL installation will check to see if the prerequisites are met for the installation. If all went well as in the picture click on NEXT.


sql install global rules

SQL Features

The Select Prepared Features tab check the settings are correct and click NEXT


sql install features

SQL Features Confirmation

The SQL installation for SCVMM now lets you review the Features are correct. Again, review the features you have chosen are right for your environment then click NEXT


sql install confirmation

SQL Instance Selection

On the SQL Instance Configuration you need to change this to the Default Instance (if you are installing a fresh copy of SQL, if you are using another server please point the instance to what you have setup. Click  NEXT to proceed.


sql install instance

SQL Service Account

Confirm the Server Configuration tab is correct (if you want to change the accounts you can, but Im leaving this all default.) Click NEXT.


sql install service account

SQL Database Engine Configuration

The Database Engine Configuration tab make sure to add your account so that you can manage the SQL instance. In my screenshot below I added the Domain Admins for my lab environment. Click Next to continue.


sql install database engine

Review SQL Installation Options

We are almost ready to start the SCVMM SQL server installation. Double-check all these settings look correct for your environment then click on COMPLETE to start the install.


sql install review

SQL Installing

The installation will now run through the process to install the SQL server components on your Virtual Machine. Maybe go grab a coffee to give this sometime to complete and if all went well you should see something similar to the following screen.


Starting SCVMM Installation

Finally we are on to the fun bit, we can start the configuration of SCVMM. I rebooted the server after the SQL install just to be sure that the services all started correctly and there was no errors detected.
Locate the Configure VMM icon and then DOUBLE CLICK IT.


start scvmm installation

SCVMM Setup

Once the Microsoft System Centre 2019 Virtual Machine Manager setup wizard starts up, put in your details, your company details and your SCVMM licence key then click NEXT.


SCVMM Diagnostics and Usage Information

The SCVMM Diagnostics and Usage Data page describes that Microsoft does collect some data from you. Please read through this then click NEXT.


scvmm install diagnostics

SCVMM Update

It is always a good idea to turn on Microsoft Update to patch the system should any vulnerabilities be found, but this is up to you and your environment. I chose to turn on Microsoft Update, then clicked on NEXT.


scvmm microsoft update

SCVMM Database Configuration

On the Database Configuration tab make sure the settings are correct for SQL server install you did previously and when confirmed click on NEXT.


scvmm install database configuration

SCVMM System Account

Now to the Configure service account and distributed key management tab, change it to Local System account, and then click NEXT


scvmm install account

SCVMM Library Configuration

For Library Configuration you can choose to create a new library or an existing share. Im leaving it default here as its a new install of SCVMM. Click NEXT to proceed


scvmm library configuration

SCVMM Installation Summary

Finally we are almost there, SCVMM is almost configured. Review the details on the Installation Summary page and when you are happy with the details click INSTALL. 

This will start the install so be sure everything is correct.


scvmm install summary

SCVMM Installation Summary

Hopefully you got a successful screen saying that SCVMM is now installed and configured, but if you didnt the best place to look is at the SCVMM install logs located %SYSTEMDRIVE%ProgramDataVMMLogs ServerSetup.log.


scvmm installation successful

Schedule a Hyper-V Checkpoint

Now that you have SCVMM installed in the next blog post I will cover off how to add your Hyper-V Hosts and perhaps while you are already here you can see how easy it is to schedule snapshot creations and deletions of your Hyper-V or VMware virtual machines with SnapShot Master.

 Download and try it for yourself with a free and fully functioning 30 day trial.

Update SCCM to Version 1906 – Easy Update Instructions

Update SCCM to Version 1906 – Easy Update Instructions

Step by Step guide on how to update to SCCM 1906​

SCCM 1906 upgrade

Hi all, Microsoft has just recently released their latest iteration to SCCM, version 1906. With this update of SCCM comes quite a few welcome features and to find out more go to this link on the Microsoft site.

But you are here to see how easy it is to upgrade your SCCM to the current branche 1906.

So let’s get started on the upgrade process for SCCM 1906.


  1. As always when performing any upgrades, make sure that you have a good known valid backup or snapshot of the servers you are targeting. Once you have confirmed you have both or either of these in place, open your SCCM console with your SCCM administration account.
    SCCM Console Main Window


  2. Now click on Administration then highlight Updates and Servicing.
    SCCM Administration Pane


     

  3. Now in the main Window you should hopefully see the SCCM 1906 update is Ready to Install. If not, click on Check for Updates and allow for sometime for SCCM to download the latest branch update from the Microsoft site. Remember to refresh your window as it wont show up automatically.SCCM 1906 download ready

  4. As you can see from the prior picture, our environment has the SCCM 1906 update all ready to install and that our previous SCCM 1902 updates had been installed. First thing we need to do is to Run prerequisite check. Highlight the Configuration Manager 1906 update, right click and choose Run prerequisite check.SCCM 1906 Run Prerequisite Check

  5. This check will take a little time, you can see the status of the check by refreshing the window.
    SCCM 1906 checking prerequisites
    You can also select Monitoring in the SCCM console Window, navigate to Updates and Servicing, highlight the Configuration Manager 1906 update, right click that and choose show status for a more detailed display of the status of the prerequisite check of SCCM 1906.
    (now this may take sometime to allow the 1906 upgrade to confirm that your SCCM environment is ready for the install, so always be patient)
    SCCM 1906 checking prerequisites detailed

  6. OK, hopefully your SCCM environment passed all the checks to confirm it is ready for the SCCM 1906 installation. Now go back to the Administration and you should see that the Prerequisite Check Passed for the Configuration Manager 1906 update as below.
    SCCM 1906 checking prerequisites passed

  7. Now to the gritty stuff, we are ready to start the upgrade process for SCCM 1906. Again, highlight the Configuration Manager 1906 update, right click and choose Install Update Pack.SCCM 1906 install update pack

     

  8. You are now presented with the Configuration Manager Updates Wizard. Click on Next when you are ready to start the installation, this will take around 30 – 45 minutes to complete so make sure you have a big enough change window for the update process.SCCM 1906 Configuration Manager Updates Wizard

  9. On the second windows of the SCCM updates wizard, carefully choose any options / features  that you require and then click on Next.SCCM 1906 Configuration Manager Updates Wizard Options

     

  10. Client Update Settings window allows you to choose if you would like to validate the client update on members of a Pre-Production collection so that you can test there are no issues with the update. As this is one of SmiKar’s software test environments, I am going to just Upgrade without Validating. When you are ready to proceed click on Next.SCCM 1906 Configuration Manager Updates Wizard Client Updates

     

  11. We are almost ready to start the installation and upgrade to SCCM 1906. On the License Terms window, you can read the License Terms if you wish to do so, click on Next when you are ready for the next step.
    SCCM 1906 Configuration Manager Updates Wizard License Acceptance

  12. Now the last step before the upgrade process starts off. On the Configuration Manager Updates Wizard Summary Window, check the settings and details you want have been selected and then finally click on Next. This will start the upgrade to SCCM 1906 so make sure you want to do this.SCCM 1906 Configuration Manager Updates Wizard Summary

     

  13. The last window you can now close and the SCCM 1906 update will complete in the background.SCCM 1906 Configuration Manager Updates Wizard Completed

  14. Now what if you dont want to refresh the SCCM console window and wish to see more details about what is happening with the update to SCCM 1906. Well you can easily get a more detailed view of the upgrade process by going to the local C Drive of your SCCM server and opening the ConfigMgrSetup.log file. If you have Trace32 installed to read your log files, it will display this in a nice and easy to read fashion.SCCM 1906 ConfigMgrSetup Log

  15. Alternatively to see the update, in your SCCM Console go to Monitoring then Updates and Servicing Status, highlight the Configuration Manage 1906 update, right click and choose Show Status. In the Update Pack Installation Status window, highlight Installation and you can also see the what the SCCM 1906 update is doing.SCCM 1906 Update Status Window

  16. Hopefully after some time (it took around 30 minutes to complete the upgrade to SCCM 1906 in our test environment), everything should have installed and updated your SCCM to the latest branche. You may get a warning that your Configuration Manager console needs to be updated as well.SCCM 1906 Console Update

  17. Close the console then reopen to update. (the SCCM 1906 update took a few minutes to complete in the lab)SCCM 1906 Console Update

  18. Finally after quite a few easy steps, we can confirm that the SCCM environment successfully installed to the current branche, SCCM 1906.SCCM 1906 install successSCCM 1906 Installed

Now that you have updated your SCCM to version 1906, perhaps you use SCCM to patch your virtual server environment. While you are here, check out SnaPatch and see how it allows you to have an easy roll back position should any issues with your patch deployment occurs.

How to clone a Azure VM

How to clone a Azure VM

How to clone a Azure VM

If you ever need to duplicate or clone your Azure VMs or perhaps even migrate your Azure VMs from Azure Service Manager (ASM) to Azure Resource Manager (ARM) you can use one of our Azure Management Tools, Azure VM Cloner (AVMC) to quickly and easily do this for you. (You can download a fully functioning trial here)

In the last blog post I showed you how you could schedule the deployment of Azure VMs. Using those same VMs and Azure Subscription I will now show you how we can clone your Azure VMs.

Why clone your Azure VM?

Use Case Description

Disaster Recovery

In case of a disaster or outage, having a cloned VM in a different Azure region or datacenter can provide a quick failover option and ensure business continuity.

Testing and Development

Cloning a VM can provide a safe and isolated environment for testing and development purposes without affecting the production environment.

Scaling Out

Cloning a VM can help quickly and easily scale out an application or service by creating multiple copies of the same VM to distribute the workload.

Migrating to a New Subscription

When migrating to a new Azure subscription, cloning a VM can help ensure that all the necessary configurations and settings are preserved.

Creating a Backup

Cloning a VM can also serve as a backup option in case the original VM experiences any issues or failures.

Cloning an Azure Virtual Machine

Start cloning your Azure VM

Start up the Azure VM Cloner tool then click on Clone Virtual Machine in the home window


Clone Azure VM

Select the Azure VM to Clone

Next we are presented with a list of the Azure VMs you have in your subscription. Highlight one of the Virtual Machines and then click on Next.


Shutdown your Azure VM to be Cloned

Note if the VM is running you will get the following error. Best to shutdown any virtual machines within Azure that you need to clone.


Clone Azure VM running VM

Choose the Destination for your cloned Azure VM

We are next presented on some destination settings we need to migrate the cloned Azure VM to. Choose your Azure Target Subscription (you can clone your Azure VMs across subscriptions only if you have access)
Select a target Azure Resource Group and then finally the Azure Location for the VM to reside in.
Click on NEXT to continue with the cloning process.

Clone Azure VM Destination

Cloned Azure VM Destination Storage Account

Now we need to choose which Azure storage account to place the cloned Azure VM in.

Highlight the correct storage account then click on NEXT.


Clone Azure VM Storage Account

Cloned Azure VM Destination vNet

The next selection window we are presented with is the Azure Virtual Network that you would like the cloned virtual machine in.

Highlight the correct Azure vNet and again click on NEXT.  The Azure VM Cloner will read the vnet configuration before continuing.


Clone Azure VM vNet

Choose the VM Size for your cloned VM

The last configuration window before the cloning of the Azure VM kicks off is the VM sizing window. Choose an Azure VM size and give the server a name.

You can also select whether to shutdown the cloned VM on completion, Send an email to let you know once done and even convert the disks to Azure Managed Disks if they were in an Azure Storage Account before.
Click on START CLONE to continue.


Clone Azure VM Sizing

Ready to start the cloning of your Azure VM

You are now ready to proceed with the cloning process. The Cloning Warning screen informs you that may have two servers with the same SIDs and computers names after the server has been cloned, this is of course not something you want to have happen in a Production environment.

Read the warning and when you are ready to do so, check the Understood and Accepted then click on START.


Clone Azure VM Warning

Cloning process for your Azure VM

In the Console Output you can see the tasks and status of your Azure VM cloning and as seen in the Azure Portal you can see that the VM has now cloned successfully.

Now the last things you will need to do if it is a Microsoft Windows virtual machine that you cloned, is to login with its local Administrator account and password and possibly run a Sysprep to change the server name and SSID before you rejoin it to the domain.


Clone Azure VM Azure Portal

Download a Trial of Azure VM Cloner today.

To trial our Azure VM Cloner, fill in the form below to get access to download the trial software.


The cost of our Azure VM Cloner is $500 USD.


 

FREE DOWNLOAD

Send download link to:

I confirm that I have read and agree to the End User License Agreement.

Download a trial of the Azure VM Cloner and see all of our Azure Management Tools.

Cloning an Azure VM is an important process that can save you a lot of time and effort. With Azure VM Cloner (AVMC), you can easily and quickly clone your Azure VMs, ensuring that you have an exact replica of the original virtual machine. By following the steps outlined in this guide, you can clone your Azure VMs with ease, without any errors or issues.

How to Schedule Azure VM Deployment – Step-by-Step Guide

How to Schedule Azure VM Deployment – Step-by-Step Guide

How to schedule the deployment of Azure VMs

Automate Azure VM Deployment

If you need to schedule the regular deployment of your Azure VMs, you can do this easily with one of our Azure tools, AVMD (Azure VM Deployer). With the Azure VM deployer you can deploy single and multiple Virtual Machines quickly, easily and repeatably.

AVMD is completely FREE, you can download it from here and start using it right away.

Hopefully you have AVMD all setup and an azure admin account with the appropriate permissions to your Azure tenant to start the scheduled deployment of your Azure VMs.

Azure VM Deployment Use Cases

Use Case Description

Dev/Test Environments

Scheduling Azure VM deployment for development and testing environments allows for efficient use of resources by creating and deleting VMs as needed. For example, a development team might schedule VM deployment during business hours and delete them at the end of the day to avoid wasting resources.

Batch Processing

Scheduling Azure VM deployment for batch processing can help optimize resource utilization by only creating VMs when needed. This can be particularly useful for applications that require large amounts of compute resources for short periods of time, such as data analysis or video encoding.

Disaster Recovery

Scheduling Azure VM deployment for disaster recovery can help ensure that backup VMs are always available and up-to-date. This can be critical in the event of a system failure or other outage.

Scheduled Maintenance

Scheduling Azure VM deployment for scheduled maintenance can help minimize the impact of maintenance on users by automatically redirecting traffic to other VMs while maintenance is performed.

High Availability

Scheduling Azure VM deployment for high availability can help ensure that VMs are always available to users. This can be achieved by automatically creating new VMs when existing ones fail or become unavailable.

Cost Optimization

Scheduling Azure VM deployment can help optimize costs by only creating VMs when they are needed, and deleting them when they are no longer needed. This can be particularly useful for organizations that have variable workloads or need to closely manage their cloud spend.

Launch the Azure VM Deployer

To start automating and scheduling deployment of your Azure VMS, simply open up Azure VM Deployer and let is synchronise with your Azure environment.

Schedule Azure VM Deployment

 

Scan your Azure Tenancy First

First, ensure that you have the AVMD tool downloaded and set up on your machine. You’ll also need an Azure admin account with the necessary permissions to your Azure tenant to deploy VMs. Once you’re ready to begin, launch the Azure VM Deployer and allow it to synchronize with your Azure environment.

Azure VM Deployment Settings

  • You can now start filling out all the settings to deploy your VMs to your Azure subscription.
    Provide a Name for your Virtual Server
    Choose the Servers Operating System
    Azure Subscription
    Azure Availability Zone Location
    Azure Resource Group
    Choose the Azure Virtual Machine size
    Provide a local Administrator account and password
    Join the VM automatically a domain (You will need an account with Domain Join Permissions)
    Which Azure Storage account you wish to deploy the VM to
    Any additional disks you want to add to the VM during deployment
    The Azure vNet and Subnet
    Further additional options if you want VM diagnostics, Azure Log Analytics, a Basic NSG, Public IP, Azure Resource Tags and finally if you want to shutdown the VM post deployment.Click Add to queue when you have filled out all the Azure VM details and it will populate these settings to the Deployment Queue.

Schedule Azure VM Deployment Selection

Provide a name for your Azure VM

For any additional VMs, keep filling out the details and add them to the queue too. If the servers are all the same type and settings you just need to update the server name before adding them to the deployment queue.

Schedule Azure VM Deployment Server

Azure VM Details

Now when you have added all the Virtual Machines you wish to deploy to Azure you are now ready to start deployment, but you may want to just confirm that your VM settings are correct. Simply right click the blue icon next to each Virtual Machine in the Deployment Queue and choose Show Details

Schedule Azure VM Deployment Server Overview 2

Azure VM Deployment Schedule Creation

Now lets start the deployment of your Azure Virtual Machines. Click the DEPLOY button in the bottom left hand corner and you are now presented with the options to deploy right now or schedule the VM deployment of your Azure VMs.

  1. Schedule Azure VM Deployment Now

Azure VM New Deployment Schedule

In this example we will schedule the deployment of the Azure VMs, so click on schedule, then on OK to start the schedule creation.

Schedule Azure VM Deployment 3

Azure VM New Deployment Schedule

We are now prompted to create the schedule to deploy your Azure Virtual Machines, click on New.

Schedule Azure VM Deployment New

Scheduled Deployment Execution

In this example we will schedule the deployment of the Azure VMs, so click on schedule, then on OK to start the schedule creation.

Schedule Azure VM Deployment 3

Schedule Creation

We are now prompted to create the schedule to deploy your Azure Virtual Machines, click on New.

Schedule Azure VM Deployment New

Schedule Settings

Simply put in the date and time you wish for your Azure VMs to deploy at then click OK. (You can set to schedule this once off, or a reoccurring daily, weekly or monthly schedule.)

Schedule Azure VM Deployment Trigger

Schedule Date and Time Settings

Confirm that the date and time you want to schedule the VMs for deployment to your Azure subscription is correct.

Schedule Azure VM Deployment Trigger 2

Confirm the Schedule is Correct

Click on OK in the scheduler window and the deployment task is now confirmed.

Schedule Azure VM Deployment confirmed

Scheduled Deployment is underway

My scheduled deployment has now kicked off and we can see in my Azure Portal that the machines are now deploying.

Schedule Azure VM Deployment Creation

Scheduled Deployment Alerting

If you had set up your email alerts, you will receive an email letting you know that your VMs have now deployed to Azure.

Schedule Azure VM Deployment Finished Email


  1. After some time your Azure Virtual Machines should have now deployed. As seen in the Azure Portal I can see that our Azure VMs are up and running, in the correct resource group, Azure Subscription and Azure Location.Schedule Azure VM Deployment Complete


Dont forget that the Azure VM Deployer is completely free and one of our Azure Management Tools.

Azure VMs are now deployed

After some time your Azure Virtual Machines should have now deployed. As seen in the Azure Portal I can see that our Azure VMs are up and running, in the correct resource group, Azure Subscription and Azure Location.

Schedule Azure VM Deployment Complete

Dont forget that the Azure VM Deployer is completely free and one of our Azure Management Tools.

Azure FAQs

Question Answer

What is Azure VM deployment?

Azure VM deployment is the process of creating and managing virtual machines in the Microsoft Azure cloud platform.

What are the benefits of using Azure VMs?

Azure VMs offer a wide range of benefits, including scalability, flexibility, security, and cost-effectiveness.

How do I create a new Azure VM?

You can create a new Azure VM through the Azure portal, Azure CLI, or Azure PowerShell.

What operating systems are supported on Azure VMs?

Azure VMs support a wide range of operating systems, including Windows Server, Linux, and various distributions of Unix.

What are the different VM sizes available in Azure?

Azure offers a variety of VM sizes, ranging from small, low-cost instances to large, high-performance instances.

How can I manage and monitor my Azure VMs?

You can manage and monitor your Azure VMs through the Azure portal, Azure CLI, or Azure PowerShell, as well as third-party tools such as Azure Monitor and Azure Log Analytics.

What are availability sets in Azure VM deployment?

Availability sets are used to ensure high availability for VMs by distributing them across multiple physical servers in a data center.

How can I secure my Azure VMs?

You can secure your Azure VMs through a variety of measures, including network security groups, firewall rules, and encryption.

What is Azure Site Recovery and how does it work with VMs?

Azure Site Recovery is a disaster recovery solution that can be used to replicate and recover VMs in the event of a site outage or other disaster.

How can I optimize the performance of my Azure VMs?

You can optimize the performance of your Azure VMs through various means, such as selecting the appropriate VM size, optimizing disk performance, and using caching.
How to update SCCM 1902 Hotfix Rollup KB4500571

How to update SCCM 1902 Hotfix Rollup KB4500571

How to update SCCM 1902 Hotfix Rollup KB4500571

 

SCCM Hotfix rollup KB4500571

SCCM Hotfix rollup KB4500571 bug fix overview

Microsoft has released yet another update for SCCM, hotfix rollup KB4500571.

First off, we will cover the update fixes issues with SCCM including; (how to update your SCCM environment to Hotfix rollup KB4500571 is further down the page)

  • The Download Package Content task sequence action fails and the OsdDownload.exe process terminates unexpectedly. When this occurs, the following exit code is recorded in the Smsts.log on the client:
    Process completed with exit code 3221225477
  • Screenshots that are submitted through the Send a Smile or Send a Frown product feedback options cannot be deleted until the Configuration Manager console is closed.
  • Hardware inventory data that relies on the MSFT_PhysicalDisk class reports incomplete information on computers that have multiple drives. This is because the ObjectId property is not correctly defined as a key field.
  • Client installation fails on workgroup computers in an HTTPS-only environment. Communication with the management point fails, indicating that a client certificate is required even after one has been provisioned and imported.
  • A “success” return code of 0 is incorrectly reported as an error condition when you monitor deployment status in the Configuration Manager console.
  • When the option to show a dialog window is selected for app deployments that require a computer restart, that window is not displayed again if it is closed before the restart deadline. Instead, a temporary (toast) notification is displayed. This can cause unexpected computer restarts.
  • If it is previously selected, the “When software changes are required, show a dialog window to the user instead of a toast notification” check box is cleared after you make property changes to a required application deployment.
  • Expired Enhanced HTTPS certificates that are used for distribution points are not updated automatically as expected. When this occurs, clients cannot retrieve content from the distribution points. This can cause increased network traffic or failure to download content. Errors that resemble the following are recorded in the Smsdpprov.log:
    Begin to select client certificateUsing certificate selection criteria ‘CertHashCode:’.
    There are no certificate(s) that meet the criteria.
    Failed in GetCertificate(…): 0x87d00281
    Failed to find certificate ” from store ‘MY’. Error 0x87d00281
    UpdateIISBinding failed with error – 0x87d00281

    The distribution points certificates are valid when you view them in the SecurityCertificates node of the Configuration Manager console, but the SMS Issuing certificate will appear to be expired.
    Renewing the certificate from the console has no effect. After you apply this update, the SMS Issuing certificate and any distribution point certificates will automatically renew as required.

  • A management point may return an HTTP Error 500 in response to client user policy requests. This can occur if Active Directory User Discovery is not enabled. The instance of Dllhost.exe that hosts the Notification Server role on the management point may also continue to consume memory as more user policy requests arrive.
  • Content downloads from a cloud-based distribution point fail if the filename contains the percent sign (%) or other special characters. An error entry that resembles the following is recorded in the DataTransferService.log file on the client:AddUntransferredFilesToBITS : PathFileExists returned unexpected error 0x8007007b
    The DataTransferService.log may also record error code 0x80190194 when it tries to download the source file. One or both errors may be present depending on the characters in the filename.
  • After you update to Configuration Manager current branch, version 1902, the Data Warehouse Synchronization Service (Data_Warehouse_Service_Point) records error status message ID 11202. An error entry that resembles the following is recorded in the Microsoft.ConfigMgrDataWarehouse.log file:
    View or function ‘v_UpdateCIs’ has more column names specified than columns defined.
    Could not use view or function ‘vSMS_Update_ComplianceStatus’ because of binding errors.
  • User collections may appear to be empty after you update to Configuration Manager current branch, version 1902. This can occur if the collection membership rules query user discovery data that contains Unicode characters, such as ä.
  • The Delete Aged Log Data maintenance task fails if it is run on a Central Administration Site (CAS). Errors that resemble the following are recorded in the Smsdbmon.log file on the server.
    TOP is not allowed in an UPDATE or DELETE statement against a partitioned view. : spDeleteAgedLogData
    An error occurred while aging out DRS log data.
  • When you select the option to save PowerShell script output to a task sequence variable, the output is incorrectly appended instead of replaced.
  • The SMS Executive service on a site server may terminate unexpectedly after a change in operating system machine keys or after a site recovery to a different server. The Crash.log file on the server contains entries that resemblie the following.
    Note Multiple components may be listed, such as SMS_DISTRIBUTION_MANAGER, SMS_CERTIFICATE_MANAGER, or SMS_FAILOVERMANAGER. The following Crash.log entries are truncated for readability.
    EXCEPTION INFORMATION
    Service name = SMS_EXECUTIVE
    Thread name = SMS_FAILOVER_MANAGER
    Exception = c00000fd (EXCEPTION_STACK_OVERFLOW)Description = “The thread used up its stack.”
  • Old status messages may be overwritten by new messages after promoting a passive site server to active.
  • User targeted software installations do not start from Software Center after you update to Configuration Manager current branch, version 1902. The client displays an “Unable to make changes to your software” error message. Errors entries that resemble the following are recorded in the ServicePortalWebSitev3.log::GetDeviceIdentity – Could not convert 1.0,GUID:{guid} to device identity because the deviceId string is either null or larger than the allowed max size of input
    :System.ArgumentException: DeviceId
    at Microsoft.ConfigurationManager.SoftwareCatalog.Website.PortalClasses.PortalContextUtilities.GetDeviceIdentity(String deviceId)
    at Microsoft.ConfigurationManager.SoftwareCatalog.Website.PortalClasses.Connection.ServiceProxy.InstallApplication(UserContext user, String deviceId, String applicationId)
    at Microsoft.ConfigurationManager.SoftwareCatalog.Website.ApplicationViewService.InstallApplication(String applicationID, String deviceID, String reserved)

    This issue occurs if the PKI certificates that are used have a key length that is greater than 2,048 bits.

  • Audit status messages are not transmitted to the site server in an environment with a remote SMS provider.
  • The Management Insights rule “Enable the software updates product category for Windows 10, version 1809 and later” does not work as expected for Windows 10, version 1903.

SCCM Hotfix rollup KB4500571 additional changes

Further improvements and additional functional changes to SCCM included in the KB4500571 hotfix are;

  • Manager and the Microsoft Desktop Analytics service.
  • Multiple improvements are made to support devices that are managed by using both Configuration Manager and a thirty-party MDM service.
  • Client computers that use IPv6 over UDP (Teredo tunneling) may generate excessive traffic to management points. This, in turn, can also increase load on the site database.
    This traffic occurs because of the frequent network changes that are associated with the Teredo refresh interval. After you apply this update, this data is filtered by default and is no longer passed to the notification server on the management point. This filtering can be customized by creating the following registry string under HKEY_LOCAL_MACHINESoftwareMicrosoftCCM:
    Type: String
    Name: IPv6IFTypeFilterList
    Value: If the string is created without any data (blank), the pre-update behavior applies and no filtering occurs.
    The default behavior of filtering Teredo tunnel data (interface type IF_TYPE_TUNNEL, 131) is overwritten if new values are entered. Multiple values should be separated by semicolons.
  • The Configuration Manager client now handles a return code of 0x800f081f (CBS_E_SOURCE_MISSING) from the Windows Update Agent as a retriable condition. The result will be the same as the retry for return code 0x8024200D (WU_E_UH_NEEDANOTHERDOWNLOAD).
  • The SMSTSRebootDelayNext task sequence variable is now available. For more information, see the “Improvements to OS deployment” section of Features in Configuration Manager technical preview version 1904.
  • SQL database performance is improved for operations that involve a configuration item (CI) that has associated file content by the addition of a new index on the CI_Files table.

How to update your SCCM to Hotfix rollup KB4500571

Now we get to the nitty gritty of the update process for KB4500571.

  1. Open your SCCM Console, and navigate to Administration, then highlight Updates and Servicing.
    KB4500571 Administration
  2. Now with Updates and Servicing highlighted in main window you should hopefully see the KB4500571 update has downloaded and is ready to install.
    (If you cant see it downloaded, right click on Updates and Servicing and choose Check for Updates.)
    KB4500571 Downloaded
  3. Firstly we need to run the prerequisite check for SCCM KB4500571 to ensure your environment is ready for the update.
    Right Click the downloaded update and choose Run Prerequisite Check.
    KB4500571 PrerequisiteCheck
  4. The prerequisite check will take around 10 minutes or so to complete the check.
    You can use the ConfigMgrPrereq.log located in the root of the SCCM server’s C Drive to see the status and it’s completion.
    SCCM KB4500571 Prerequisite Check
  5. Now on to the fun bit, let’s start the installation of SCCM KB4500571. Again right click the update in the main window and choose Install Update Pack.
    SCCM KB4500571 Install Update Pack
  6. The first window of the Configuration Manager Updates Wizard pops up. Choose Next to continue the installation
    SCCM KB4500571 Updates Wizard
  7. The Client Updates Settings window lets you choose whether you want to validate the update against a pre-production collection. We wont bother with that here as this is our test environment. Choose Next to continue when ready to do so.SCCM KB4500571 Client Update Settings
  8. Accept the License Terms – only if you are happy with them 🙂 – and click Next.
    SCCM KB4500571 License Terms
  9. Now the Summary tab of the Configuration Manager Updates Wizard details the installation settings you have chosen. If you are happy to proceed with the installation click Next.
    This did take some time in the SmiKar SCCM lab environment, so best go make yourself a cup of coffee and come back. 🙂
    SCCM KB4500571 Install Confirmation
  10. Hopefully all went well with your upgrade to SCCM KB4500571 and you are presented with a screen similar to this.
    SCCM KB4500571 Completed
  11. If you had any issues or want to view the status (rather than look in the logs) go to Monitoring, then high Updates and Servicing Status. Highlight and Right Click the update and choose Show Status.
    SCCM KB4500571 Updates and Servicing Status