Plain Virtualization

I started this blog when I was doing technical implementation and design back in IBM days. The term always use is Post Sales engineer/consultant. It was held up and I never get to start anything until I left and joined BT Frontline which is the now British Telecom. I started this blog in Apr 2011 with one main purpose, paying forward for what I have benefited from the community. I remembered clearly, during my early years when I was building a VMware View in my home lab, someone from LinkedIn VCP group was so willingly helping over message and a call from oversea to help me troubleshoot and guide me to configure a vyatta virtual router. Since then, I decided to share what I have learned if not I would not have gain as much as I have. That very year, I got an opportunity at VMware and join the company as a System Engineer which industry term it as Presales engineer. It was my dream company and I never looked back since. I carry on to share what I learned without any plan in my career. J

If you are not aware when vSphere 7.0 Update 1 was release, there is one improvement made to Cross vCenter Migration. For those who didn't follow, in the past, Cross vCenter Migration can only be done between vCenter Servers within the same SSO domain. This created a limitation especially when one company merge or acquire another, they are unable to move the workloads but have to resort to the traditional methods either from backup and restore, etc. With vSphere 7.0 Update 1, vCenter Server 7.0 Update 1 improve this function. There is no longer a requirement of having both the vCenter Servers to be part of the same SSO domain. This resolve lots of use cases out there in the field. This feature came as a Fling and eventually made it to be part of the official product. However, there are some things need to be clear on the requirements. You need to make sure the vSphere edition needs to be at least Enterprise Plus. For Standard and the old Enterprise edition (if you didn't upgra