If you are like me and you tried to perform an upgrade of vIDM 3.3.x to 3.3.4 you were most likely greeted by no network connectivity after upgrade with the following screen: If you made a backup of the network configuration this is where we would restore it. If not we can perform it manually by running /opt/vmware/share/vami/vami_config_net Press 6 and go through the screens to configure the ip ...
I wanted to go through the upgrade of vIDM 3.3.4 outside of lifecycle manager. I wanted to do it using the online upgrade via the console. Official documentation can be found here. First step is to log on to the console via the root credentials and upgrade the upgrade manager to 3.3.4 /usr/local/horizon/update/updatemgr.hzn updateinstaller Set the upgrade version that you are upgrading from in my case was 3.3.2 so i ran ...
In this guide i will go over the steps of getting an existing 8.x vRSLCM appliance upgraded to the latest 8.3 release The first step is to lo in to vRealize Suite Lifecycle Manager under the Lifecycle Operations section Go to settings -> System Upgrade ...
I recently ran in to a situation where one of the events in vCenter wasn’t showing up in Operations Manager Doing some research and i found this kb article: 65106 Basically theres a file called eventlist.txt under /usr/lib/vmware-vcops/user/plugins/inbound/vmwarevi_adapter3/conf/ on the master node so i logged on to master node via ssh and did vi /usr/lib/vmware-vcops/user/plugins/inbound/vmwarevi_adapter3/conf/eventlist.txt Comment out the event that we want to get alerts for and restart the service by running ...
I would try the restore options first. You can find instructions for the restore menu here If the recovery menu doesn’t work put the Mac mini in DFU mode by following the instructions I have here One the device is in DFU open Apple Configurator 2 (Mac Only sorry Windows folks). Make sure you are at least at version Version 2.13.2 Connect the USB-C cable to the Mac and the Mac mini to the port closest to the ethernet port ...
Disconnect the power cord from the Mac Mini. Plug USB-C/Thunderbolt cable into the USB-C port next to the ethernet port. Plug the other end into the Host Mac. While holding down the power button, connect the Mac Mini to power and continue to hold the power button for about 3-5 seconds You should now see the DFU logo on the Host Mac. Once the Mac mini is in DFU mode, you can do a full restore of the Mac mini M1.
I recently purchased one of the newer Mac mini devices with the new M1 chipset. Unfortunately I went with the lower edition that had 256 GB and I wanted to send it back to purchase the bigger 512 GB edition, but I wanted to clean my installation. In order to to boot in the recovery mode to reinstall the os I had to perform the following steps: Make sure the Mac mini is off, if its not off just shut it off Hold the power button until the options appear, it might seem like a long time but keep holding it. It took about 15 seconds for me. A menu should appear that shows the hard drive and Options. Select options and continue You will see the apple logo and then a new menu should appear with additional options. It would look like this: ...
While i was trying to perform an upgrade to my ESXi installation i ran in to the below error: The fix was pretty simple. The hypervisor doesnt have enough space to download and install the package so we need to enable one of the available datastores for the function. For vCenter go to the host in question to Configure -> System -> System Swap ...
With the release of of VCF 4.1 i wanted to get my lab upgraded. The release blog can be found here and the release notes are here In my case i pre downloaded the VMware Cloud Foundation Update 4.1.0.0 by going to Repository -> Bundle management -> Download now The next step is to upgrade VCF by going to Inventory -> Workload Domains -> Select the workload domain -> Update/Patches -> Update Now ...
After upgrading my vCenter Server to the latest vSphere 7.0 Update 1, I was unable to see ESXi 7.0 Update 1 Image. When I attempted to sync the updates I got the error “Download patch definitions task failed while syncing depots. Error: ‘integrity.fault.HostPatchInvalidVendorCode’.” Seeing as the error mentioned the depots, navigate to Menu->Lifecycle Manager and then select the Settings tab and then Patch Setup. ...