Recently, myself and a team of people performed a migration of a database from old and dying hardware to shiny new hotness. Some of the questions I got, well ...
After performing a V2V, P2V or a clone operation in which the VHD/VHDX file is copied to a new VM, a new NIC is installed in the virtual machine. This is evidenced by the need to once again set the IP configuration of the NIC.
In a virtualized environment, we have the ability to create point-in-time snapshots, or checkpoints in Microsoft parlance, of virtual machines. This gives the ability to immediately roll back any changes after the checkpoint operation was performed. This is especially useful when debugging an application, or performing migrations and upgrades to applications.
Any tech professional worth their salt is in the habit of updating their resume every once in awhile. I myself have a quarterly cycle; every three months, I update my info. Unfortunately, this generates a fresh round of spam from questionable headhunters.
In my day job, one of the things I do is maintenance of a farm of servers. All these boxes have local logging, which is picked up by Splunk. However, I still need to clean up those log files. Here is how I automated the process.
From time to time, file associations get broken. This could be the result of malware, "bit slippage", uninstall of an associated program, or even some inadvertant change of settings. Here is how to fix a broken ZIP file association.
System Center Virtual Machine Manager (SCVMM) can be a bit less than helpful when describing reasons for failed operations.