Capacity planning with vRops
Posted by Michael Ryom on
January 18, 2017
Capacity planning is one of the tasks that every IT organization need to do, but most do very poorly. This is not out of bad will or lack of skills. Most often, it is because they lack a good way of dealing with all the changes, past, present and future. Most of them are also done reactively. Statistics may be pulled from vCenter and put into word or excel where graphs of past data points from a historical trend. This is then used to predict the future growth and based there of cluster sizing and purchasing decisions are made. Alternatively, the all too familiar, “we are out of resources. Hurry we need to buy more”, scenario comes into play. None of these capacity technics are very good. There is most properly a need to do things smarter.
Windows Server 2016 Nano Server – Just enough OS model
Posted by Mikhail Rodionov on
January 13, 2017
We are in 2017 now, and it’s about fourth month since Windows Server 2016 has been RTMed in September 2016. By now, everyone probably heard about one of the big new features of Windows Server 2016 – Nano Server, new installation option which you can’t select during setup 🙂 . But I think there is still a lot of “why” and “how” questions around Nano Server. In this blog post, I will try to provide a bit of a history and compare Nano Server with other installation types.
Exploring VMWare’s VPID Technology
Posted by Gary Williams on
January 11, 2017
I’ve been using VMWare’s VPID (Virtual Port ID) technology for some time now both in work and in the home lab but I was curious to see just how VMWare handled a NIC going down and then coming back up and it turned out to be a lot more powerful and smooth than I first though.
In my lab, I’ve got several HP Microservers and a mix of TP-Link and Netgear switches.
I’ve found the TP-Link switches to be perfect for a lab as they have 48 1GBit ports and 4 1GBit FC ports. They haven’t cheapened out like Netgear have with the link between the last two Ethernet and the first two FC. With Netgear, you can only use last two Ethernet OR the first two FC ports.
You cannot use all of the ports on the switch. With TP-Link, all the ports are available and I find the web GUI a little more initiative although I did experience a bug on the TP-Link where the SNMP Engine kept crashing. This was fixed in a firmware upgrade so it wasn’t a major issue.
Anyway back to VMWare and VPID!
The Virtualization Review Editor’s Choice Awards 2016
Posted by Oksana Zybinskaya on
December 26, 2016
The Virtualization Review Editor’s Choice is a selection of the most outstanding virtualization products of 2016. It is based on the opinions and overlooks by the trusted experts in the fields of virtualization and cloud computing. This is not the “best of the best rating”. No criteria were applied to make the list. This is just the collection of individual choices of writers, who deal with the industry daily, so they have pointed out virtualization solutions they found especially interesting and useful.
How to Deploy and Manage Software-Defined Networking using SCVMM 2016 – Part III
Posted by Charbel Nemnom on
December 9, 2016
In Part I of this series, we created the tenant virtual network and connecting two VMs to it using System Center Virtual Machine Manager, and then we validated that both VMs can route between each other.
In Part II, we created a public Virtual IP Address (VIP) on the Software Load Balancer (SLB) using VMM console and PowerShell through which we were able to access a website on the virtual network. We also created Site-to-site (S2S) VPN to a Remote site.
How to Deploy and Manage Software-Defined Networking using SCVMM 2016 – Part I
Posted by Charbel Nemnom on
December 7, 2016
Software Defined Networking (SDN) in Windows Server 2016 provides a method to centrally configure and manage physical and virtual network devices such as routers, switches, load balancers and gateways in your datacenter. Virtual network elements such as Hyper-V Virtual Switch, Hyper-V Network Virtualization, and RAS Gateway are designed to be integral elements of your SDN infrastructure.
Please note that you must install Windows Server 2016 Datacenter edition for Hyper-V hosts and virtual machines (VMs) that run SDN infrastructure servers, such as Network Controller and Software Load Balancing nodes. However, you can run Windows Server 2016 Standard edition for Hyper-V hosts that contain only tenant workload virtual machines that are connected to SDN-controlled networks.
Recent news for VMware Tools packages for VMware vSphere 6.5
Posted by Alex Samoylenko on
November 29, 2016
Starting from VMware Tools 10.0 version, VMware has done these packages downloadable separately from VMware ESXi distributions. They are available here. To see the active VMware Tools version installed in your VM, simply look at VM properties in vSphere Client:
Azure Offers Backing Up VMware VMs with a Freeware Tool
Posted by Augusto Alvarez on
November 21, 2016
After hearing some news about Microsoft like, largely investing in Open Source hardware, PowerShell open source and for Linux, SQL Server for Linux, MS joining the Linux foundation, and so many others; you may think hell just starting freezing, but no, this is how Microsoft is engaging the world now. Integration is the keyword, and we salute them for that.
Adding a new feature among these is the recent update to their main backup tool for cloud: Azure Backup Server now supports VMware virtual machines. MABS (Microsoft Azure Backup Server) it is not a new tool, it’s been around for a while now offering backups for Hyper-V virtual machines, physical machines, file servers, SQL, SharePoint and Exchange.
PowerShell Modules – Why bother?
Posted by Mike Preston on
November 18, 2016
Ever since PowerShell hit the stage it’s adoption has been increasing dramatically – Finally that Windows-based scripting language that not only appeals to Windows administrators with an easy to use structure but has been widely adopted by the industry surrounding the third-party applications. There aren’t many mainstream products out today that don’t support PowerShell. Don’t get me wrong – adoption is great, but with that needs to come a little organization – we, as administrators have managed to spread those PS1 files all over the place – they are scattered on servers here and there, our PC’s, inside of cloud storage. Basically, when we have discovered issues or needed to apply configuration changes we have created our scripts and just left those files laying around. When the time comes to fix that problem again we sometimes find ourselves hunting down those scripts – which, by taking more time than it needs to, sort of defeats the purpose of the efficiency of automation in the first place.
Nano Server Image Builder tool
Posted by Romain Serre on
November 15, 2016
Nano Server is a new way to deploy Windows Server in your datacenter or in the Cloud. Nano Server is a low footprint operating system which handles what you need and no more. When you create the Nano Server, you choose the role that you want to add to the image (Hyper-V, Storage, containers and so on). Nano Server doesn’t contain Windows Logon, 32-bit legacy or cannot be managed by GPO.
Currently, I don’t really like Nano Server for some jobs as Hyper-V or storage. Nano Server comes with the Current Branch for Business servicing model. So, to be fully supported, your Nano Server has to be upgraded two or three times in a year. You can imagine what happens with hundreds of Hyper-V/Storage nodes? Anyway, Nano Server can run other jobs as IIS and Containers, and in these cases, it could be fine.
In this topic, I’ll show you how to prepare a Nano Server image which will be deployed in a virtual machine. The operating system will be configured to run containers. To create the Nano Server image, I’ll use the Nano Server Image Builder tool which is a graphical interface to prepare the image in VHD, VHDX or WIM file format.