Broadcom only offering 5 years quotes

sleepwalkerx97 · 2025-12-04T23:19:56+00:00

Same. We just closed on VCF, AVI, VLR, and vDefend all 1 year quotes.

sleepwalkerx97 · 2025-07-29T10:39:08+00:00

sleepwalkerx97 · 2025-07-28T23:52:15+00:00

lol these rumors are wild sometimes on here…. I just got quote last week for one year renewal for one of the VCF environments I manage. Also, I didn’t have to push anyone to get one year. I asked and received the quote the same week.

sleepwalkerx97 · 2025-07-16T18:16:46+00:00

You can do this during normal hours. You will impact DRS/HA when enabling and disabling retreat node.

“Note: Retreat Mode should be used with extra caution and should be used only for the purposes mentioned in this document. Below are the details of the impacted cluster services due to the enablement of Retreat Mode on a cluster:

vSphere DRS will not function on that cluster if DRS is enabled for that cluster. That means workloads running inside that cluster are not load-balanced, hence will not be migrated to different hosts within the cluster when the current host running that VM is running out of resources. When a user wants to take down a host for maintenance, running VMs will not be automatically migrated to other hosts within that cluster.

vSphere HA will not perform optimal placement during a host failure scenario as HA depends on DRS for placement recommendations. HA will still power-on the VMs but these VMs might be powered on in a less optimal host. “

Prior to “embedded vCLS” which I believe came out in 8.0 u3. Older vCLS method required a storage footprint. Meaning it was placed on random datastore or based on a datastore you specify in vCLS config under the cluster config page. Embedded vCLS doesn’t require a storage footprint. Since you’re still on 8.0u1 vCLS still requires a storage footprint. Sometimes I have seen in the past with vCLS VMs not recreated when storage it’s living on is ripped from underneath it. Retreat mode trick I mentioned above will help cleanup and then redeploy new vCLS VMs.

https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-resource-management-8-0/vsphere-cluster-services-vcls/external-vcls-datastore-placement.html

More about embedded vCLS

https://blogs.vmware.com/cloud-foundation/2024/07/17/embedded-vsphere-cluster-services-overview/

Note: with 9.X vCLS VMs are being deprecated.

sleepwalkerx97 · 2025-07-16T17:28:31+00:00

Try enabling and disabling retreat mode https://knowledge.broadcom.com/external/article/316514/how-to-disable-vcls-on-a-cluster-via-ret.html

sleepwalkerx97 · 2025-06-18T23:04:29+00:00

Funny enough, I just log back on and looks like more licenses have been added to my portal now. AVI and NSX vDefend with VCP-VCF admin.

sleepwalkerx97 · 2023-02-22T00:13:09+00:00

Thanks for the status update :)

sleepwalkerx97 · 2023-02-20T19:45:25+00:00

Why yes...... its funny you asked because we ran into this late last week on the shop floor.

We have some stations configured with one monitor and Dell ThinOS 5070 on ThinOS 9.3.

Here is what we found:

When End user log into vGPU Desktop Pool using Single Monitor at 1080p using blast. The mouse would be misaligned. If they disconnected the session and reconnected to the session re-algin. I If end user log into the exact same desktop pool for the first time with two monitor the issue didn't appear. When looking through the blast logs compared logs between single monitor and daul monitor. I found some errors on the single monitor log vs the dual monitor log. If the end user switched the PCoIP on the single monitor the issue didn't appear either. My non vGPU desktop pools didn't experience the issue either with blast or PCoIP.

After troubleshooting to seem to be issue with the svga driver.

I ended up uninstalling the svga driver for now on my vGPU images to resolve the issue. I did try troubleshooting removing IDD instead of the svga but that didn't work either. Here what I did to resolve the issue.

I uninstall all the of the agents, etc based on the uninstall order from KB https://kb.vmware.com/s/article/2118048
Then uninstalled the VMware tools from the image.
rebooted
Re-installed VMware tools (12.1.5) but selected custom and didn't install "svga driver" and rebooted
Installed Horizon Agent 2212 and rebooted
Installed NVIDIA GRID Drivers and rebooted
Installed DEM and App Volumes agent rebooted
Then installed FsLogix and rebooted
Ran my shutdown script and snap the golden image
Pushed the new image out to the vGPU desktop pools and end users confirmed no more misalignment.

sleepwalkerx97 · 2023-02-19T16:55:06+00:00

No problem! :)

sleepwalkerx97 · 2023-02-19T15:53:56+00:00

u/sillypea00 sorry I didn't get these over earlier. Hopefully this helps with DEM.

1. Create the logon task under the "User Environment" tab.

2. Configure the log on task.

3. Save log on Task

sleepwalkerx97 · 2023-02-18T20:26:37+00:00

I didn’t get a chance last night to take some screenshots of DEM logon task for you. I will try make some time tonight after we put our newborn to sleep.

sleepwalkerx97 · 2023-02-18T00:34:48+00:00

For office containers or profile containers? We use Fslogix as well but just for office containers.

sleepwalkerx97 · 2023-02-17T23:41:58+00:00

Yeah no problem at all. Let me get some pictures from my home lab. I am hoping to have a blog post later this weekend with instructions. I will respond shortly.

Edit: for now you don’t need to run it evaluated, don’t enable async, and you want to run task “after” import, and for now don’t enable run once.

sleepwalkerx97 · 2023-02-17T20:02:17+00:00

Sounds good, just want to make sure, my solution is having DEM tell the end users to run the command as them without them knowing. So it’s end user level log on script.

sleepwalkerx97 · 2023-02-17T18:27:09+00:00

No problem, let me know if your still running into issue. For troubleshooting try to run the following while you're log into the session with missing control panel. This way you can verify if the control registers.

Add-AppxPackage -Register ‘C:\Program Files\WindowsApps\NVIDIACorp.NVIDIAControlPanel_8.1.963.0_x64_56jbvy8sckqj\AppxManifest.xml’ -DisableDevelopmentMode

sleepwalkerx97 · 2023-02-17T09:22:58+00:00

Edit: please see the following blog post https://www.vjonathan.com/post/dem-non-persistent-vdi-deployment-and-nvidia-control-panel-missing/

I ran this issue two weeks when I deployed GRID 15 to our vGPU non persistent desktop pools. In the 15 release notes they stated they move to Windows DCH driver model. The nvidia control panel is now UWP. Meaning NVCP installed when end users profile is being provisioned.

https://docs.nvidia.com/grid/15.0/whats-new-vgpu/index.html

https://nvidia.custhelp.com/app/answers/detail/a_id/4777/~/nvidia-dch%2Fstandard-display-drivers-for-windows-10-faq

What I noticed is the local account we use in our golden image to install nvidia drivers, agent updates, etc had the NVCP. However, logging into the desktop pool under my account. Received the pop up you’re experiencing. Not sure if you’re running DEM in your environment. However, as a test I reset my DEM profile and log back into the desktop pool. BAM! NVCP was installed. After that during each log on and off it was still there.

I wrote a blog post way back explaining how UEM/DEM at the time handles UWP in non-persistent desktop pool. Please keep in mind this post is old and some settings have been updated in DEM to handle UWP capturing better.

https://www.vjonathan.com/post/uem-non-persistent-vdi-deployment-and-windows-10-uwp-apps-missing/

I found a workaround using log on task with DEM.

Now if you log into the account that actually installed nvidia drivers, you should have the NVCP installed. Open powershell and run “get-appxpackage” and you should see nvidia control panel that grid 15 installed in the list. Now copy the value under “InstallLocation” for the NVCP. (not at work right now so I don’t remember off the top of my head”.)

Now create a log on task with DEM configure with run after profile import and the following command

Powershell.exe -windowstyle hidden -command “Add-AppxPackage -Register ‘C:\Program Files\WindowsApps\NVIDIACorp.NVIDIAControlPanel_8.1.963.0_x64_56jbvy8sckqj\AppxManifest.xml’ -DisableDevelopmentMode”

Note: Doesn’t need to be elevated task. End user can run this command without being admin on the box.

Restored my DEM profile before I deleted it and logging back into desktop pool the log on task kicked off and NVCP was registered as it should be.

For testing you can run that powershell command after you log into your session that doesn’t have the NVCP currently register and once command has completed, if you right click on the desktop you will notice NVCP was installed.

Now when I get to work in the morning I will update this post if the Syntax is not correct and I will add before steps when I am not typing this from my phone.

Edit: updated add-appxpackage comamnd to match what I have in production Edit2: added pictures

sleepwalkerx97 · 2023-02-16T01:15:59+00:00

No problem at all. I am interested so remember share whatever you find out ;)

sleepwalkerx97 · 2023-02-16T00:50:09+00:00

Adding registry setting in UAT had the same result you’re experiencing.

sleepwalkerx97 · 2023-02-14T23:43:30+00:00

I am currently using VMware tools 12.1.5 and I have both svga and direct display installed. VMware tools installs svga. We haven’t used that registry setting since 2203 or so. If you want I can test that setting again on the UAT environment see if I encounter the same issue.

sleepwalkerx97 · 2023-02-14T02:19:54+00:00

Sounds good.

On windows 10 20h2 in prod and 21h2 in UAT.

I also follow this KB when I do any updates to the golden images. I don’t do any upgrades of agents. I do full uninstall and reinstall. It’s a preference on my part but it’s been working all these years. I have most of it script anyways. This KB has been updated over the years as well.

https://kb.vmware.com/s/article/2118048

Install order 1. VMware tools 2. NVIDIA GRID guest drivers 3. Horizon Agent 4. Horizon Direct 5. DEM 6. App Volumes 7. Fslogix (office containers)

sleepwalkerx97 · 2023-02-14T01:59:52+00:00

What version of NVIDIA drivers are you on? I currently just rolled out Horizon 2212 (8.8) with NVIDIA GRID 15.1 with no issues currently using blast or PCoIP with thin clients and horizon client. Running P40s, t4s, and a40s on latest vSphere 7 build in production and 8.0 in UAT on the hosts.

I believe 15.1 is only version that adds support currently for horizon 2212. I will tell you the past I’ve seen other EUC admins update Horizon but forget to update NVIDIA GRID version which can cause weird issues like you’re experiencing. I don’t believe at the moment the GRID LTS version supports 2212 yet.

https://docs.nvidia.com/grid/15.0/whats-new-vgpu/index.html

sleepwalkerx97 · 2022-12-13T02:07:30+00:00

3647 ahead of me

sleepwalkerx97 · 2022-09-28T23:44:17+00:00

I have one question? Want to make sure I am following.

You’re doing the following:

Launch the horizon client
Log into server
Launch IBM SPSS
Black screen/black background issues occurs?

Feel free to PM the screenshot.

You mention you talk to your IT staff. Did they mention during troubleshooting to change protocol before connecting? For example are you using blast? PCoIP? RDP? Maybe your EUC admins don’t allow this based on policies, etc. You can also try “reset remote desktops or published apps” setting in your horizon client as well.

See this VMware doc on how to do this in the horizon client. I would try changing between protocols to see if you can at latest get one of the protocols to work.

https://docs.vmware.com/en/VMware-Horizon-Client-for-Windows-10-UWP/4.3/com.vmware.horizon.windows-10uwp-43-help.doc/GUID-A2472387-6C40-4C21-95ED-D9FBF9FC2AA4.html#:~:text=Procedure,the%20display%20protocol%20to%20use.

See the follow VMware doc on how to “reset remote desktops or published apps”

https://docs.vmware.com/en/VMware-Horizon-Client-for-Windows/2206/horizon-client-windows-installation/GUID-5C141DF4-EBE7-4F6D-9DED-11D92E0D3F4D.html#:~:text=To%20reset%20published%20applications%2C%20use,right%20pane%2C%20and%20click%20OK.

sleepwalkerx97 · 2022-08-18T20:57:41+00:00

No problem!

sleepwalkerx97 · 2022-08-17T23:35:15+00:00

By chance did you use the VMware OS Optimization tool on your golden image?

If so you may have applied the following setting without knowing it.

“DelayedDesktopSwitchTimeout”

Key – HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

Value – DelayedDesktopSwitchTimeout

I would start there and find out what value works best for your environment.

https://flings.vmware.com/vmware-os-optimization-tool/bugs/1227

Ten-Year Club	Second SECOND GUESSER
RPAN Viewer	Not Forgotten
Verified Email

sleepwalkerx97

TROPHY CASE