Jeramy Thompson

 Looks like VMware is already on it https://www.vmware.com/security/advisories/VMSA-2021-0028.html

Update -- https://kb.vmware.com/s/article/86398  On 11/12 VMware released 7.0 U3B for bot ESXi and vCenter However vCenter appears to have been pulled as its completely missing  https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3b-release-notes.html https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3a-release-notes.html This appears to be an issue with HA: https://kb.vmware.com/s/article/86191 IMPORTANT NOTE : vCenter Server 7.0 U3b is no longer available for download due to further complications with HA configuration post-upgrade. If a vCenter has already been upgraded to vCenter 7.0 U3b(or earlier) and is experiencing the symptoms mentioned above, please follow the steps in the Workaround section below.

Looks like Synology had a significant oversight when they allowed customers of the DS416Play to upgrade to the latest DSM 7 OS. The default configuration comes with 1GB of memory, this was adequate for the version 6 DSM, however it appears the version 7 clearly has a larger memory footprint and does not leave enough room for file operations. In my case I purchased a 8GB stick of memory: https://www.amazon.com/G-Skill-Ripjaws-204-Pin-SO-DIMM-F3-1600C9S-8GRSL/dp/B00EOUFEG2 Or This one has been reported to work as well: https://www.amazon.com/Crucial-Single-PC3-12800-Unbuffered-204-Pin/dp/B006YG8X9Y Followed this YouTube tutorial on disassembling the NAS https://www.youtube.com/watch?v=zE6P7F16X7Q And booted back up. It now runs like it did previously and my backups function again. More info here.  https://community.synology.com/enu/forum/1/post/146281?page=1&reply=463033 I wish i would have taken a screen shot before the upgrade, but here is TOP after the upgrade:

Needed a place to put my notes for installing Unifi an UNMS on an ubuntu server. Install Ubuntu with only openssh SSH in  Setup the Java 8 environment that is required and remove default java: -------------------------------------------------------------------- sudo apt-get autoremove default-jdk openjdk-11-jdk sudo apt install openjdk-8-jdk export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 -------------------------------------------------------------------- Next lets get some updates, and add ui to the apt sources -------------------------------------------------------------------- sudo apt-get update && sudo apt-get install ca-certificates apt-transport-https echo 'deb https://www.ui.com/downloads/unifi/debian stable ubiquiti' | sudo tee /etc/apt/sources.list.d/100-ubnt-unifi.list sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 06E85760C0A52C50  -------------------------------------------------------------------- Put a hold on openjdk-11 files --------------

 Windows 11 has finally GA'ed so now its time to do some testing. If you don't have the required hardware no problem, we can apply some work arounds. In our Setup we will be using the following Setup Horizon 8 vSphere 7.0U3 Windows 11 GA First download the Windows 11 ISO, put it on a datastore Create a new VM for the parent VM. I chose Windows 10 as the Guest OS Confirm that Secure Boot is enabled And left everything as Default Now Console into your VM and power it on, Once you get to the  'Windows Setup' screen press Shift +F10 This will bring up a command prompt, from here type regedit and hit enter From this point navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup Right-click on Setup key and select New -> Key option.  Name it LabConfig  Select LabConfig key and then create the following 3 new DWORDs and set their values to 1 to bypass or disable TPM 2.0, Secure Boot and RAM amount checks BypassTPMCheck BypassSecureBootCheck BypassRAMCheck Close regedit, and the command

-----------Update 3------------ And it looks like they are working on it: https://kb.vmware.com/s/article/85962 --------------------------------------------------- Upgraded last night So far Lifecycle manager appears not to be working. "Authentication Failed, Lifecycle Manager server could not be contacted" A quick look at the logs says it thinks im not authenticated [#18] 2021-10-06T11:38:51.077Z warning vmware-vum-server[13587] [Originator@6876 sub=SimpleConnection] [simpleConnection 85]  Connection requested for ><, returning  default connection [#18] 2021-10-06T11:38:51.077Z info vmware-vum-server[13587] [Originator@6876 sub=VcIntegrity] Session: [sessionId masked]; user jthompson@HOME.LAB [#18] 2021-10-06T11:38:51.079Z info vmware-vum-server[13587] [Originator@6876 sub=VcIntegrity] Active? false [#18] 2021-10-06T11:38:51.079Z error vmware-vum-server[13587] [Originator@6876 sub=SessionMgr] [sessionMgr 189] Login: User's VC session is not active; User: jthompson@

 Found this link that is a simple walkthrough through the upgrade https://communities.vmware.com/t5/vSphere-Upgrade-Install/Step-by-step-procedure-to-update-vCenter-sever-7-0-appliance/ta-p/2848957

It gets quite annoying when you need to deploy a lab and need to keep the same password (or your just too lazy to change\ remember a new one). to clear the password history in a VC appliance, simply type:  echo “” > /etc/security/opasswd this will clear your password history , now you can change your password to any previous password you had before.

I used this to update my lab power shell scripts so that during the sleep cycle , I have some indication of where we are at. You can read about these scrpits here https://jeramythompson.blogspot.com/2021/08/powercli-script-creating-instant-clone.html https://jeramythompson.blogspot.com/2021/08/vmware-vsphere-vcenter-and-esxi-home.html The End result will look like this This is achivied by creating a simple function at the top of the script and calling it later: ----------Here is the Function ------------------- function Get-SleepTimer{ param ( [int]$Time ) $Lenght = $Time / 100 For ($Time; $Time -gt 0; $Time--) { $min = [int](([string]($Time/60)).split('.')[0]) $text = " " + $min + " minutes " + ($Time % 60) + " seconds left" Write-Progress -Activity "Watiting for..." -Status $Text -PercentComplete ($Time / $Lenght) Start-Sleep 1 } } -----------------End Function--------- And we can simply call this function and pass the number of s

Some times you need to shut down your lab in as efficient way as possible. I do this quite often as I don't like leaving my home lab running during various events (thunderstorms, weekends , vacation etc). And I really dont like having to click , wait, click, wait, click.... wait some more to get every thing down. So I wrote this script to power down my lab, Ill walk you through what it does and the completed version will be at the end of this post. (I'm also including a start-up script I use as well) First we need to import our power CLI modules and tell the script to ignore any self-signed or Invalid certificates ( If you want more info on setting up powerCli see the beginning of this post for more info) ------------------------------------------------------------------- Import-Module VMware.PowerCLI Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -Confirm:$false ------------------------------------------------------------------- Now we need to setup our credential

 One task I run into quite often is deploying Instant Clone pools to test one thing or another. I dont always leave my lab running, so all the pools get deleted , and then recreated when needed. If you have ever created an instant you know you have to click about 20 settings, while not a monumental task, it is a bit reparative. So we are going to go through the process of creating our own script , so we only need to click once to deploy our instant clone pool. You are going to need a couple of things: Internet access PowerCLI installed PowerCLI Example Scripts (Optional) A dedicated workstation to store your password on. Ok lets start with installing PowerCLI. Open power shell as an administrator And run the following command to install PowerCLI Install-Module VMware.PowerCLI Type A and hit Enter Wait for the progress bar to complete  the install of the modules Once Complete run the following to verify it was installed and get the Version number if you need it at some point Get-Module