robinsonjl3 Tracker

Re: Connection server console message shows "DETECTED UNRECOGNIZED REQUESTS"

robinsonjl3 — Wed, 23 Aug 2023 13:53:58 GMT

Just to chime in and add my two cents. I have a small environment with no load balancers and running 2303 with only internal customers and I get the same message.

Re: License Reporting Strangeness

robinsonjl3 — Mon, 14 Aug 2023 10:31:53 GMT

Yes, this particular cluster was rebuilt and I am assuming that is why there is a double listing of the cluster. I'll stand-by for support to provide guidance. Thanks.

License Reporting Strangeness

robinsonjl3 — Thu, 10 Aug 2023 14:10:13 GMT

I am experiencing a strange issue with how my vSAN licenses are being reported in vCenter.

I have a 32CPU vSAN license and I currently have two vSAN clusters using this license. Each cluster is 8CPU which means I am using 16CPU of the 32CPU license, however, it is showing 24CPU being used in Administration -> Licenses -> Products. If i look into it, one of my clusters is listed twice.

I have a ticket open with support but so far they have not provided a solution. I just wanted to open this up to the wider community in case someone has experienced the same issue.

Re: Downgrade of vSphere 8 Essentials to 7 and later upgrade possible?

robinsonjl3 — Thu, 10 Aug 2023 13:57:46 GMT

I just did this with my licenses. We purchased new vSphere licenses and I downgraded them to version 7 and I still have the option to upgrade them back to 8.

Re: PVSCSI drivers 1.3.25.0 not signed

robinsonjl3 — Sun, 18 Dec 2022 13:15:45 GMT

I ran into this problem as well and ended up using the Win8 drivers as those were signed.

Re: VCSA 6.5 'Failed to start File System Check'

robinsonjl3 — Thu, 06 Jan 2022 18:27:08 GMT

I literally just had this issue and was in absolute freakout mode. I tried all of the suggestions above this one and none of them worked until I came to this one. I am running the latest version of vCenter 7.0.3. Although mine was fsck /dev/vg_root_0/lv_root _0.

Thank you so much.

Re: Horizon 2103 Single Monitor Issue

robinsonjl3 — Fri, 27 Aug 2021 14:19:03 GMT

This particular GPO has been in place since before I started managing this environment and apparently it was due to some bizarre behavior with an nVidia driver and dual monitor fat-clients. So the GPO was a simple logon script that called DisplaySwitch.exe /extend. The GPO was labelled nVidia Dual Monitor Fix and since I am not using nVidia cards in my servers I completely ignored the GPO since I assumed it was specific driver related stuff. Apparently, this was forcing the desktop image to try and extend the display to a second monitor which is fine if the zero-client had a second monitor attached but when only one monitor was connected it locked up the display until you changed the resolution. Mouse clicks were still being registered just the display wasn't refreshing.

How I figured this out was disabling inheritance on the VDI OU and logging in with nothing but the default domain policy being applied. I then attached specific GPO's necessary for our domain leaving out the nVidia GPO. I then investigated the GPO to see what it did. It definitely made me feel stupid but I'm just glad I got it figured out before these need to be deployed.

Re: Horizon 2103 Single Monitor Issue

robinsonjl3 — Tue, 24 Aug 2021 17:25:51 GMT

You can go ahead and mark this resolved. I finally figured out what was causing it. I overlooked a particular GPO that was being inherited by the VDI OU that fixed an issue with our dual monitor fat-clients. Once I disabled inheritance the image began working as intended.

Re: Horizon 2103 Single Monitor Issue

robinsonjl3 — Tue, 24 Aug 2021 14:02:45 GMT

Very discouraging that no one has any suggestions or hasn't seen this issue. I am still battling it and have nothing good to report. I did get a PM saying to disable Print Redirection but that did not help in my situation.

I have been digging through logs and I found the following:

The driver \Driver\WudfRd failed to load for the device ROOT\VMWUSM\0000

and

The driver \Driver\WudfRd failed to load for the device ROOT\VMWVIDD\0000

Not sure if this has anything to do with anything but they stuck out.

Horizon 2103 Single Monitor Issue

robinsonjl3 — Thu, 12 Aug 2021 16:58:24 GMT

Here is my current problem. I have Dell Wyse 5070 clients running ThinOS 9.1.3112. I have two systems setup to do some testing. One has a single monitor while the other one has dual monitors.

I can connect to a desktop using the Blast protocol however, the zero-client with a single monitor locks up at the desktop with the Project to a Connected Screen dialog box. It will stay frozen until the resolution is changed on the zero-client. That seems to unfreeze the desktop. I attached an image of what the desktop looks like when it freezes.

The zero-client with dual monitors does not have this issue and works as intended and all is right with the world.

I thought this was strictly a Wyse issue until I tried accessing the desktop through the web browser. Once again, the desktop loads but freezes up at the same spot but if I resize the browser window it resolves the problem.

I have tried changing the master image hardware config from 2 monitors to 1 monitor to automatically detect settings in the video card settings. I have adjusted the video memory. I tried setting the screen resolution to different settings, nothing seems to help and I really need to get this resolved.

I attempted to force PCoiP instead of Blast but that is causing other issues that I don't have the time to troubleshoot.

Any suggestion will be greatly appreciated. Thanks.

Re: Horizon and Outlook 2016 Problem

robinsonjl3 — Sat, 24 Jul 2021 04:35:23 GMT

I had meant to post a follow up to this a while ago but forgot about it.

I ended up opening a support ticket with VMware and this is what they told me to do which fixed the issue:

On the master image, go to the following key in the registry: HKLM\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator

Delete everything but the (default) key

Reboot the master image and test Outlook.

Once I did this, I refreshed the desktop pool and all was good again.

Re: Horizon Desktop Locks up at Black Screen

robinsonjl3 — Fri, 23 Jul 2021 19:19:39 GMT

After rebuilding my image, the problem still exists. However, if I connect a second monitor to the zero-client the image loads just fine. Take the second monitor away and the screen will lock up. The client config is setup for dual monitor. My image is also setup for 2 monitor in the VM setting and I also adjusted the video memory to what VMware recommends.

I have no idea what to look for to resolve this one.

Re: Horizon Desktop Locks up at Black Screen

robinsonjl3 — Fri, 23 Jul 2021 15:55:43 GMT

Thanks for the feedback. I am using a Wyse 5070 zero-client which I believe uses Teradici. I'll definitely look into the resolution and see if I am getting the same errors. Currently rebuilding my image as I did make a couple of changes so trying to eliminate one of those changes as a possible culprit.

Horizon Desktop Locks up at Black Screen

robinsonjl3 — Wed, 21 Jul 2021 18:13:49 GMT

I have a Windows 10 image deployed and when I attempt to login via a zero-client the desktop freezes at a black screen. However, if I attempt to login to my session through a web browser the session loads fine and I can access and use the desktop. This also works in reverse, if I attempt to login from a web browser, I will get the locked up black screen but then logging in with the zero-client the session loads just fine.

Once I am in the desktop, the only error I get is the following:

An unmarshaling policy check was performed when unmarshaling a custom marshaled object and the class {CDC82860-468D-4D4E-B7E7-C298FF23AB2C} was rejected.

Googling the error leads me down a bunch of rabbit holes with virus removal. This is a Windows 10 image that does not connect to the internet and does not have a virus or malware.

That particular class listed in the registry as ShellItemArray Shell Namespace help and the subkey InProcServer32 is %systemroot%\System32\windows.storage.dll

I did find something that said to give System and Administrator full control of those keys but that did not change anything.

Has anyone seen this before. I'm on a time crunch to get this image sorted out. Thanks in advance for any assistance.

Re: Horizon and Outlook 2016 Problem

robinsonjl3 — Tue, 08 Jun 2021 23:45:27 GMT

With the writable out of the equation I still get the same errors.

I literally just finished setting up the writable and tested it 30 minutes ago. I'm at my wits end as I'm on a time crunch to get VDI up for a few users.

Prior to using the writable I was just using DEM, same issues.

Horizon and Outlook 2016 Problem

robinsonjl3 — Tue, 08 Jun 2021 23:37:56 GMT

I am currently testing Horizon 2103 with a Window 10 1909 image. Office 2016 is installed on the image. I am also using DEM.

The issue I am having is that I cannot launch Outlook. Depending on whether or not Cached Mode is enabled gives me a different error.

With Cached Mode off, I get this error:

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to logon to Microsoft Exchange has failed.

With Cached Mode on and not redirecting the OST:

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. Your profile is not configured.

With Cached Mode on and redirecting the OST to DEM User Profile share or App Volume Writable:

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The file is not an Outlook data file.

I have Googled and Googled which is why I have tried both redirecting the OST to the DEM User Profile share and also trying App Volumes Writeable Volume as those seem to be the most common solutions I found.

The funny thing is, in my lab, this works fine by just redirecting to the DEM profile. In production, this is the problem. My only assumption is there is a GPO in production that I don't have in the lab that is causing the problem.

Does anyone else have any other ideas of what I can do to fix this? Would creating an App Package be a better solution or will I hit the same wall with the OST?

SDDC Manager UI Issue

robinsonjl3 — Sun, 31 Jan 2021 07:07:07 GMT

SDDC Manager is broken. I was following along with the VVD documentation and was installing the certificates. Everything was going just fine until I ran this:

sh /opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh

Now when I try to login to SDDC Manager I get this

{"message":"500 - \"{\\\"errorCode\\\":\\\"IDENTITY_INTERNAL_SERVER_ERROR\\\",\\\"arguments\\\":[],\\\"message\\\":\\\"Identity Internal Server Error\\\",\\\"referenceToken\\\":\\\"CSQLJJ\\\"}\""}

The URL is showing https://vcf01.lab.io/ui/api/internal/login/callback and if I try to change it to https://vcf01.lab.io/ui the UI looks like the attached image.

Any ideas of where to look?

Re: BGP, pfsense, and vCF

robinsonjl3 — Sat, 30 Jan 2021 07:36:46 GMT

I finally got it working. I ditched the eBGP package on pfsense and switched to FRR. After some tinkering here is what I had to do:

Created a "loopback" address which is a VLAN assigned to my LAN interface with a /32 address.

Enabled FRR and set the router ID to the loopback /32 address in the global settings.

On the BGP settings I set the Local AS and configured the peers.

Once I did that all of the edge nodes picked it up and BGP routing is working.

Re: BGP, pfsense, and vCF

robinsonjl3 — Tue, 26 Jan 2021 00:51:21 GMT

I apologize for the delay, just got home.

BGP state = Active

And I am only showing directly connected routes which are basically the uplinks.

Re: BGP, pfsense, and vCF

robinsonjl3 — Mon, 25 Jan 2021 14:39:45 GMT

I'll have to doublecheck this when I get home but I'm pretty sure the answer will be no.