For a customer I’m migrating their legacy vSphere 5.5 environment to vSphere 6.5 U3. The migration is from a windows vCenter to the VCSA. First, we tried to use the GUI and stumbled over an issue.
The GUI, is of course a nice, friendly way to do this process. But when we got at the stage to select the size of the VCSA, we only had the ‘xlarge’ option. And well… that was a bit too much. Because we were aiming at the ‘small’ size.
So we did some searching on the internet and found out that we were not alone. Although it was an encouraging thought, we still didn’t find what we were looking for. Most of the threads and blog posts pointed to database size, log size etc.. And yes, they need to be checked. We had a vcenter database table of 7 million records, the size of the database was 80 GB. After some cleaning up and shrinking the database it was only a few GB. But al this effort, didn’t persuade the GUI to give us the desired ‘small’ size option.
Hoping that the validation in the GUI was different than when using the CLI, we decided to migrate using the vcsa-deploy CLI method.
Yes, it involves creating a json file. But the .iso file for the vcsa contains several template files, for several migration scenarios. We used on of the templates, customized it to our needs (setting the size to ‘small’. And after some trial and error we finally got it working.
If you want to read more about the CLI way of migration, check the vmware docs here.
vcsa-deploy creates for every run a new log folder . When we checked the logs we found out that vcsa-deploy was content with the ‘small’ size option we configured in the json file.
Why not 6.7 U3, well due to dependencies 6.5 U3 is at the moment the most current version we can run. Although this post is about migrating to 6.5 U3, it could also work for 6.7 U3, but no guarantees. The gist of this all is, if the GUI doesn’t work, try doing it the CLI way.
I know, it is not the most interesting subject to blog about. VMware gives you the opportunity for your My VMware account to use MFA. And I would advise to use MFA.
Well, depending on the situation, your my vmworld account can have access to different company accounts. Giving you, depending on roles and permissions, the ability to create support requests, download software, access licenses etc… And that is great. But it is a risk when your account gets hacked. That is where MFA can help. It is an extra line of defense.
MFA stands for, multi factor authentication. And when MFA is enabled,a person needs to present multiple pieces of evidence to authenticate (see https://en.wikipedia.org/wiki/Multi-factor_authentication ) Most of the times these pieces are a password and a token, generated by a authentication app or device. So, when you would know my password, you still can’t use my ‘my vmware’ account because I’ve enabled MFA. And the token is generated on my phone, which I have with me, and is locked.
Use a strong password. Strong doesn’t mean a lot off difficult characters, although there are some rules you have to follow. Study has shown that also the length of your password is a big key in having a strong password.
Enable MFA. Check this VMware KB on how to enable MFA for your My VMware account.
Maybe you think, we’ll how hard can it be ?? Yes, that was the same question I had. And to be honest… it is not that hard. But there are some quarks or gotchas. In this post I’ll explain the route I took for patching a vCenter HA setup.
Why don’t you use the VAMI ?
VAMI stands for ‘ Virtual Appliance Management Infrastructure ‘. It can be accessed via port 5480 like https://<FQDN VMware appliance>:5480 . The VAMI of a vCenter Appliance (VCSA) has an update section, which you can use to patch the VCSA. This is a nice and easy way for patching the VCSA, but when you have vCenter configured as vCenter HA then this option won’t work. (I know from experience….) After trying (and failing) I thought, why not read the manual…. VMware has a nice article about patching a vCenter in HA and you can find it here. I still use the VAMI, but not for patching but for making a backup.
This article is part of a series of articles about issues I encountered during implementation of a vSphere stretched cluster based on vSphere 6.7 U1. You can find the introduction article here
This issue is irritating, to say at least. You configured your first ESXi host in a cluster, polished it etc… and created a host profile from this host. And then it should be easy to configure the other hosts. But, when you apply the host profile…. the host disconnects (because of a reboot….)… but never comes back…. What happened ??
What happened is that in the wisdom of the vSphere environment the vCenter instructed the host to delete vmk0… yes the kernel interface that vCenter uses to connect to ESXi (assuming the vSphere host is clean installed and has just one kernel port). Delete it to create vmk0 again….. But it never gets to that part…. Do you recognize this issue ??
I googled for this issue and found blog posts going back to vSphere 5.1. So it looks like a difference in interpretation of how it should work.
For several versions of vSphere vCenter it is possible to logon with your windows credentials. Making it easier to only tick a box and logon instead of typing your username and password. This nice and neat trick is done via the VMware Enhanced Authentication Plugin. The only issue… it does need to work every time, else it is going to be an annoyance. And , yes, it became an annoyance for me… especially when using Firefox. So let me give you to possible solutions
A blog on my experience in using postman to change the All Services icon off vRA 7.2
Since vRA 7.1 you can change the “All Services” icon.
VMware has an article here on how to change this through the API.
I thought, maybe you could also do this via Postman. Which would also be a good exercise (for me) in understanding and using the Rest API via Postman.
The article below is one of many ways to solve this issue, feedback is welcome in the comments below.
For a while now I’m looking for ways to implement kanban in my workflows.
I do see the benefits, and I’m aware that it is not the golden solution for everything.
I need a visual representation of my WIP (work in progress)
not too much hassle like, logging on to different websites
not in public enviroments
direct accesible from my tooling (a.k.a. business laptop)
Intergration with task functions already available in my tooling (a.k.a. outlook tasks)
So I did a google on outlook and kanban. And after some searching I found this site. Which looks like a nice solution, using my outlook software etc…
So I tried to implement it.
And had one problem…. For security reasons the functionality to add a home page to an outlook folder has been disabled. And I understand it. But still wanted to see how this free solution would work.
So I found a site about enabling the home page function again. This site
The first option didn’t work for me, but adding the key “EnableRoamingFolderHomepages”=dword:00000001 to [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Security] was the magic I needed.
For now this solution will do. Using familiar software to get accustomed with using kanban.