you should save the 10th December 2015 in your calender’s. My friend Thomas Maurer is presenting some cool Scripting Stuff for Hyper-V together with Altaro. 🙂
Click here to register for the event.
System Center Virtual Machine Manager (SCVMM) provides some great automation benefits for those organizations that can afford the hefty price tag. However, if SCVMM isn’t a cost effective solution for your business, what are you to do? While VMM certainly makes automation much easier, you can achieve a good level of automation with PowerShell and the applicable PowerShell modules for Hyper-V, clustering, storage, and more.
Are you looking to get grips with automation and scripting?
Join Thomas Maurer, Microsoft Datacenter and Cloud Management MVP, who will use this webinar to show you how to achieve automation in your Hyper-V environments, even if you don’t have SCVMM.
Remember, any task you have to do more than once, should be automated. Bring some sanity to your virtual environment by adding some scripting and automation know-how to your toolbox.
Today one post about things I see sometimes in the field.
Today I want to show you how to fix the issue when you get servers and clients with the same SMBIOS ID. Normally that would be an issue but as soon as you try to management them with System Center Virtual Machine Manager or Configuration Manager it will become one. Both tools use the SMBIOS ID to create a primary key in their databases to identify the system.
Currently I only know the following trick to fix the issue and that one would be extremly annoying on many clients or servers but it actually work.
First you need two tools.
1: Rufus – To create a bootable USB Stick
2: AMIDMI – With that tool you can overright the SMBIOS ID
Now create the Bootstick with Rufus and copy the AMIDMI file on the stick.
Reboot your from the stick.
Navigate to the folder with your AMIDMI file and run the command amidmi /u
Afterwards you can reboot the system and start Windows again.
When you are working with Virtual Machine Manager, you need to remove the host from your management consolte and add it again. After the host is discovered again, you can see the new SMBIOS ID.
I currently saw these issues with following motherboard vendors:
- ASRock (Client & Rack)
- ASUS (Client)
- SuperMicro (Server & ARM)
- Fujisu (Server)
today another story I see most of the days when I do Healthcheck on customer site.
One of the first things I found was a new VMM installation on top of a new Microsoft Hyper-V Cluster. The issue was, that the cluster was installed first and every thing was running on Hyper-V converged network and standard Hyper-V Switches. There was no VMM network configured or the host made compliant within VMM.
Why is that so bad? It’s bad because VMM uses it’s own kind of switches (logical switches) and needs some additional configurations to manage the hosts in the best possible way.
When I ask guy’s why they do it in that way, I normally get the answer “how should I configure the host when no VMM is in place before he install the cluster?”.
So now my answer and how you can do it in the right way.
- Install a Hyper-V Host as Standalone host
- Configure and install the VMs for VMM and SQL Server (if needed) on the standalone host
- Performe the ful VMM configuration
- Install the other Hyper-V Hosts and roll out the VMM configuration to that hosts
- Cluster the Hyper-V Hosts
- Migrate your SQL DB and VMM with shared nothing livemigration to the new Hyper-V Cluster
- Reconfigure the standalone Hyper-V Host with VMM and add it to the cluster
- Run the cluster validation again
That’s all and it will cost you the same amount of time.
Today I had an issue with virtual machine converter during migration of a VM from VMware to Hyper-V. The screenshot below shows the issue.
The issue shows an configuration missmatch which stopped the convert of the VM.
The solution of the issue is pretty easy. You need to check and change the virtual machine configuration in VMware vCenter.
First you need to check the SCSI Bus logic. There you need to configure LSI Logic.
Second and more likely the reason for the issue is that one or more of your disks are configured as independed. Just uncheck the box and your fine. 🙂
The big news of today. Just a few minutes ago Satya annouced an Azure Datacenter on german ground. Together with T-Systems as Datacenter provider and legal owner of the new datacenter, Microsoft start in the 3 quarter of 2016 with the new datacenter region.
I cannot say how proud and happy I am.
Together with the Azure Community Deutschland, msg services ag and Microsoft it’s self, I would be happy to get all of you on board.
Microsoft kündigt Cloud-Dienste aus deutschen Rechenzentren an
Just mail me 🙂