Well this is new. Suddenly I don’t have an adapter / graphics card to run modern warefare 2.
Step 1: Update drivers.
Step 2: Reboot
Hmmm same issue. No supported DXGI adapter were found, please verify that your graphics card is within the minimum requirement and that your drivers are up to date.
Step 3: Check for updates in Battle.net
Looks like we were already up to date.
Step 4: Scan and repair
The scan seemed to have corrected the issue. Special thanks to TheSneezingMonkey for his video help.
There are currently 3 keycards to acquire in Call of Duty Warzone Pacific season 2… The Perseus Keycard, Vikhor’s Keycard and my personal favorite: The Forgotten Keycard.
I’ve started looking into various computer designed artwork and how they are created. It put me into a large internet rabbit hole of various resources so I’m using this page to record some of the good ones.
AI Animating: https://www.youtube.com/redirect?event=video_description&redir_token=QUFFLUhqbnFLdXhwN21UX0RRUzFjcHh4QnJkZ0R1cWU2QXxBQ3Jtc0ttMXBYdDh4UXhYUGI3UjRjX2xpa0ZSbGM0RmE2dU80RE9HRTBSbklyTFItc1lEMEVNamxCdTlHMjFTTlpjdE5oWm9lQV9tRlo4a2t3dVl5bFJUUk4zUmtEUllyeUFfV3FfQkJWclVVWTJBVmFLZnpLZw&q=https%3A%2F%2Fcolab.research.google.com%2Fdrive%2F1_MckQnU0mCF8FJ7PoV21nhVvoOeotHGy%3Fusp%3Dsharing
When trying to install the latest version of Windows 11 on my lab ESXi 7.0 host, I encountered the following message:
This PC can’t run Windows 11
I verified that I had met the minimum system/hardware requirements: Windows 11 System Requirements Proc: 1 Ghz RAM: 4 GB Storage: 64GB System firmware: UEFI, Secure boot capable TPM: version 2.0 Graphics card: directx compatible
What I soon realized was that my ESXi host did not have TPM 2.0…
Time to work around the issue…
When you get the error picture above simply press Shift + F10 and this will bring up a dos prompt. Type regedit and hit enter.
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup and create a new Key called: LabConfig
Create inside the LabConfig Key a ByPassTPMCheck DWORD (32-bit) with the value of 1
Click OK after editing the value data and then close out of all of the screens. Once you click on the red x in the corner of the setup screen, the setup will start again and ignore the TPM requirements.
Let me know if this helped you or didn’t work for you in the comments below.
Well I thought this was fixed in the latest version (7.0U1c) according to the release notes but apparently it wasn’t. If you are like me you are simply trying to deploy the vCenter appliance with standard IPv4 network settings and the setting will not take.
I’ve had various error messages like: ‘IP configuration not allowed‘ and ‘IP configuration failed‘ as well as: “This vCenter Server cannot be used or repaired because a failure was encountered. You need to deploy a new vCenter Server. Failure details”
This should be a relatively easy deployment but this bug definitely throws a wrench into the mix.
Luckily I’ve put some time into troubleshooting this so you don’t have to.
The best way I’ve found to work around this, is to simply just redeploy the appliance and to not fill out any of the networking configuration settings. (Make sure to set a password)
This will allow the appliance to inherit a DHCP address and allow you to complete the setup once deployed. You can also try to manually adjust the DHCP setting on the appliance.
You will first need to get to the shell. In the browser console of the vCenter VCSA press Alt + F1
Then login with root credentials and type: shell
then run /opt/vmware/share/vami/vami_config_net
this will allow you to temporarily set DHCP for your appliance to gain access to the setup.
You can reboot the appliance and you should now have an IPv4 address to continue the setup with. Let me know if this helps you or if you found an easier way to fix in the comments below.
I’m sure many of you have scratched your heads on this one… for some reason “Common” weapons aren’t really a common thing on rebirth island. As you can see in my screenshot I’ve completed all of the other challenges but have beat my head against the wall trying to solve the Heroic Sacrifice challenge of “Get 30 kills with a Common weapon on Rebirth Island.”
Luckily I’ve found the way…
Naturally common weapons can be spawned from small areas or from some Rebirth crates, but as we all know they are few and way too far between.
So in order to guarantee a common weapon on Rebirth Island, you need to build a loadout. That’s right! A loadout with some very specific weapons will count towards the challenge.
Here they are: The FFAR, Milano, RPD, and the Diamatti are the only weapons that can be use as a Common weapon and count towards the challenge.
However there is a catch… you cannot add any attachments. But as I see it, not a bad sacrifice for all of the frustrated attempts we have already made.
My common loadout for rebirth challenge
I Equipped a Milano and a FFAR for my Custom Loadout (no attachments), and was off to the races. Let me know what you used for your loadout.
Whether I’m gaming or sending out business emails, my alienware monitor has always been right in front of me. It has great performance for gaming and amazing color range for editing videos or photos. Long story short, there are many things I love about the monitor… but switching inputs is definitely one of the things that can be improved. Let’s explore two ways to make changing the inputs quicker and easier.
Solution 1:
Depending on your model (mine is the aw2518h) you may have the option to set “Shorcut Keys” under the Personalize option using you monitor buttons.
This will be the easiest way to quickly switch from either input directly from the monitor.
Solution 2:
This solution requires some additional software to be installed but will make for an easy switch using a simple command.
I’ve been working today to get my home lab updated and came across a vcenter update message while running the Pre-Update.
It appears that I need to change the root password for the OS as it expired.
A quick google search and I found a VMware KB article on how to update the password.
Connect to the vCenter Server Appliance with an SSH session and the root user credentials.
Use the following commands to get to the command prompt:
shell shell.set --enable true
shell
3.Change the root password using passwd command. 4.Verify the root account password has been changed using:chage -l root 5.Re-attempt the upgrade again.
