Archive : VMware

Migrating from Windows vCenter to VCSA 6.7

Important Note: Before you start this work make sure you have a full backup of vCenter and backup of Database.

Logon to MyVMware and download VMware-VCSA-all-6.7.0-10244745.iso (latest version).

This image has an empty alt attribute; its file name is image-48.png

Once downloaded Mount iso (by right clicking on file and selecting mount)

Copy migration-assistant to C drive

Goto migration-assistant folder on C drive and double click on VMware-Migration-Assistant.

You should then get the screen above. Then minimise the screen DO NOT CLOSE THIS CONSOLE UNTIL THE MIGRATION IS COMPLETE.

Goto CD drive VMware VCSA – vcsa-ui-installer – win32 – double click on installer.exe

Click on Migrate

Select Deploy appliance and Next

Accept the terms of Licence aggreement and click Next

Enter your Window vCenter FQDN, Username and Password and click Next

Yes

Enter details for ESXi host where you want to install vcsa

Yes

Enter Name for vcsa, root password and confirm root password. Next

Choose deployment size

Selct Datastore for vcsa. Next

Enter network details. Step 4 you will need to provide a tempory IP address for vcsa at the end of the migration vcsa will have the original IP of your vCenter.

Check details are correct before clicking Finish

Progress bar will now show

Click Continue

Next


Next

Enter details to join vcsa to AD Domain. Next

Select Migration Data. Next

This one is up to you, I would recommend you join CEIP. Next


Make sure you have done what step 1 says before you tick this box. Finish

OK

Progress bar for Data transferfro vCenter to new vcsa

Click on Launch VSPher Client (HTML5) to access your new vcsa

Upgrading ESXi 6.5 hosts with VUM

Using Runecast (great tool, more posts to come) we can see this ESXi host has been selected has 89 issues that need to be resolved:

I personally check the following before starting as these are common reasons for post remediation issues:

Cluster – Configure – Services – make sure vSphere DRS is set to Manual:

Cluster – Configure – Services -untick vSphere HA and Proactive HA:

Cluster – Configure – Configuration – VMware EVC – Enable  for the chipset you are using

Highlight the ESXi host you want to patch, then under the Update Manager tab select Scan for Updates:

Select what you want to Scan for and click OK:

Once Scan has completed Click on Stage Patches:

Note that if you click Remediation, everything will take place in one go (staging is where the patches are uploaded to the host pre-install)

Select the Baselines you want to apply and then click next:

Verify the host you want to patch is selected and the click next:

Select Patches and Extensions you want to be staged and click next.

Click Finish:

Wait for the staging of patches to complete:

Click on Remediate:

Select Baselines you want to apply and click Next:

Verify the Host and click Next:

Verify that the patches selected are ones you want to install and click Next:

Options 1 and 2 is for you to decide. I choose to do this when I am available to monitor, however a lot of admins to it out of hours. Click Next:

The depends on your environment and the situation, for example you might want VMs to reboot at the same time. It is safer to leave VMs as-is for this update. Click Next:

Same as before. Click Next:

Running Pre-check Remediation is a safe way to see if you will have any issues, if you do, resolve them and come back to this step.

If you get no issues click Finish as above.

Wait for the Remediation to complete.

Check Update manager for host and it should now show it is Compliant.

Runecast still reports issues for this host, but there are a lot less to action now!

Step out of your Comfort Zone? Hell Yes.

Sometimes in IT, when you are the infrastructure person in the company, you may spot a product or a solution that could be a good fit internally, or for a customer. Not only will this help you learn something new, but could bring a genuine benefit to the business or customer.

Sometimes we are too scared to build our case for why we think it should be implemented. What if it goes wrong? Luckily I work for a great company, where there is no blame culture, and we are encouraged to suggest and try new things.

I was at work one day and we were discussing storage expansion for a large customer (14x ESXi hosts across 2 sites). Internally, our expertise has always been HPE-oriented, and somebody suggested a HPE MSA as a cost-effective way of expanding the storage. My suggestion was “why not use VSAN?” I then proceeded to talk about the benefits of VSAN, and performance vs cost/GB. That was the last I heard about it!

About 3 weeks later my boss says “Right, you are going to site to install drives and deploy VSAN for our customer.” I had clearly made a decent suggestion, then!

Although we support existing customers running VSAN and have installed it in the past, this particular customer is a Blue Light Service; an NHS 111 provider. VSAN would be installed directly into their brownfield environment to extend their existing storage.

I would be lying if I said that I wasn’t a bit nervous about making this change on such a critical service. It actually forced me to brush up on VSAN, relearn everything I already knew and take a quick test drive around existing environments. But I still felt I needed a bit more help.

So, in preparation I signed into the VMware Hands-on Labs and refreshed my memory on VSAN installation specifically. It is an incredibly simple thing to do, and actually seems too good to be true.

Along came the installation day, which was a huge success and has been up and running for nearly a year now. That’s the thing with VSAN I guess, it just works!

Moral of the story is to always strive to operate outside of your comfort zone; that’s where the real fun takes place.