What you should do to prevent broken NTFS permissions when performing a live migration of a Hyper-V virtual machine. Step-by-step guide with detailed advice
Ran into issues after you added or replaced a Hyper-V Cluster Node? Here’s a checklist of items to run through to find out what could be causing trouble.
Linux doesn’t always run smoothly on Hyper-V. Have you had issues shutting down or restarting a guest using Ubuntu Linux on Hyper-V? Here’s a post from Eric to help you out!
Things in Active Directory get deleted. Sometimes, it’s an accident (or maliciously done) and the object really shouldn’t have been deleted. Other times, something happens that causes great chunks of Active Directory to become corrupted. The oldest technique for dealing with these problems is called an “Authoritative Restore”. In the past, this process involved restoration of the System State of a domain controller. If your domain controllers are virtualized and you’re using a hypervisor-level backup tool like Altaro, you can’t perform just a System State restore. Fortunately, that’s not a problem at all.
As an IT Professional, you might find yourself blessed with the unfortunate scenario of working on a Hyper-V server that is not able to authenticate to the domain and the cached domain credentials are no longer working. In addition to this predicament, you learn that there is no documentation for the local administrator password. Either the client who you’re working for doesn’t know the local administrator password or the previous engineer who built the server is no longer working for your company and the standard passwords aren’t working. A 3rd party password cracker application will allow you to reset the local administrator password. The drawback is you have to pay for it and in my experience they don’t always work. Follow the steps below and use the Ease of Access Exploit to change the local administrator password. The Ease of Access Exploit modifies the windows system files to enable… Read More»
These two topics may not seem to have a lot in common, but it turns out that they live and die together. The host agent is a small service that System Center Virtual Manager installs on each managed host in order to control it. VMM’s services are pre-defined groupings of templates and guest settings that are intended to ease deployment and management. Agent failures can be frustrating under any circumstances, but they can have dire consequences for VMM’s services. VMM Agent Upgrade Failures in a Cluster I discovered this issue while updating VMM 2012 R2 to the latest update rollup. The server update worked fine, but, for whatever reason, the agent update on only one of the nodes didn’t work. I didn’t save the error and when I went back to retrieve it, VMM had wiped it. As I recall, it was neither informative nor useful, so you’re probably not… Read More»
When creating an SCVMM 2008 R2 template from a virtual machine that does not support Sysprep (such as Linux), it sometimes gets stuck during the Sysprep phase. It never ends in an error or proceeds past that point, and you are unable to delete it or restart the job. Depending on your scenario, the template may not be immediately visible, but an attempt to create a new template with the same name results in “The template TEMPLATENAME already exists. Specify a unique name for the template, and then try the operation again. ID: 804”.
A customer using Altaro Hyper-V Backup on a Windows 2008 R2 Enterprise SP 1 contacted us to report that his attempts to back up a Virtual Machine failed due to a VSS error.
A customer using Altaro Hyper-V Backup on Windows 2008 R2 Enterprise SP 1 contacted us because attempts to back up a virtual machine that had Small Business Server 2011 (SBS) installed were failing due to a VSS error. We began troubleshooting by collecting the Altaro Error Logs, Windows Application and System Event Logs, and a dump of the VSS Writers and Providers from the Hyper-V host.