TexRob's Posts

FYI, the workaround worked for me.  Recapping because it's notable, that entry was not in the VMX file, and adding it seems to have fixed the issue for my users.  Long term I will be updating all... See more...
FYI, the workaround worked for me.  Recapping because it's notable, that entry was not in the VMX file, and adding it seems to have fixed the issue for my users.  Long term I will be updating all my software to the latest Horizon and ESXi/Vcenter versions, but this seems to be working for now.
I was experiencing this issue with one of my clients and only where the thin clients were connected to high res monitors.  The workaround suggested in this KB did not work and VMWare support co... See more...
I was experiencing this issue with one of my clients and only where the thin clients were connected to high res monitors.  The workaround suggested in this KB did not work and VMWare support confirmed that the workaround doesn't work consistently.  For me the fix was ESXi 6.0 Update 1 and View 6.2 Ugh.  So, I have applied this workaround to two users, but the value it says to change to false was not even in their VMX files.  I added it, but since the KB does not reference what to do in the case of it not being there, which they would normally do, it makes me less than confident this will work. The problem with upgrading is I have 5 customers on various versions below Horizon 6.2, so I am going to have to update them all first, then all my hosts, just to fix this issue on their one environment that is only affecting a few users.  Good times. I'll post back once I see if the workaround works for them.  Marked correct answer because that KB is definitely my issue, the log matched exactly.
Thank you everyone for the responses.  I'm going to start with the workaround posted on that one KB and go from there.  I will come back and post my results and mark the correct answer/s. Than... See more...
Thank you everyone for the responses.  I'm going to start with the workaround posted on that one KB and go from there.  I will come back and post my results and mark the correct answer/s. Thanks,
I manage about 7 different Horizon View environments for customers, some on prem, and some in our hosted environment.  I have had no problems (lately) with any of them, and some of them exist on ... See more...
I manage about 7 different Horizon View environments for customers, some on prem, and some in our hosted environment.  I have had no problems (lately) with any of them, and some of them exist on this same Vsphere environment, and one other is on the same Horizon View release.  The only discernible difference is I believe the environment not having issues is on hardware version 7, and the problem environment is 11.  The issues are happening across all servers in the cluster, and the cluster includes other working View environments, using the same storage array in some circumstances. So, the issue is that these Win 7 64 desktops are crashing or rebooting, and I can't figure out from the log exactly which.  I don't see "WinBSOD" in the log.  The users report the issue after stepping away for a few minutes, and they come back to a black screen, move their mouse to try and wake it, and usually lose connection.  It looks like maybe there is a video issue, but I can't really figure out what or why.  They all have 35mb of video memory, and most users are running 1920x1080 or lower on a single monitor, so this should be more than enough. Attached is a log from one of the machines having the issue.  Anyone have any insight?  able to point me in the right direction?  I usually figure this stuff out on my own, but this one has me pretty stumped. Thanks
Doesn't really say anything about DPI scaling, and that 4K bit at the end is unclear.
So the problem with this isn't it isn't UI scaling, contrary to what the registry value is named.  I tested it, and while it appears to work, I noticed that the resolution seemed off.  It's just ... See more...
So the problem with this isn't it isn't UI scaling, contrary to what the registry value is named.  I tested it, and while it appears to work, I noticed that the resolution seemed off.  It's just using a lower resolution and then fitting it to the screen.  On a MacBook Pro running Windows 10, View client 3.4, I run at 2880x1800 and UI scalling in Windows 10 at 200%.  When I connect to the View it displays at 1440x900 and is extremely blurry as a result. Are there plans for true UI scaling in the works at VMware?  I am a bit shocked that you guys tried to push off forced resolution as UI scaling, especially in an incredibly pixel conscience world that we live in these days.  I should note that it works fine in OSX with the current Horizon client.
Unfortunately this does not work with Horizon View 6.0 as far as I can tell.  I'll also save you some time and tell you the reverse procedure doesn't work either, of making a manual pool and conv... See more...
Unfortunately this does not work with Horizon View 6.0 as far as I can tell.  I'll also save you some time and tell you the reverse procedure doesn't work either, of making a manual pool and converting to automatic.  When you try and edit the automatic pool it gives you an error.  Now, with THAT said, if you were to manually change every variable the auto pool adds, there is a slim chance it might work, but good luck identifying every entry it puts into ADAM.  The problem on Horizon View 6 appears to be, and I don't have a lot of experience with manual pools, is there is no option to add desktops to an existing manual pool.  This seems incredibly strange, so I am not doubting that maybe I am missing something, but I spent a couple hours last night trying to figure out how to add another desktop to an existing manual pool, but had no luck.  It seems very weird that once you go in and edit the pool, there is no option to add or remove desktops.  In the end, I just made a manual pool for existing users, and then entitled them to it.  Any new users will get the new automated pool with a similar but slightly different name.  Not ideal, but it gets the job done.
It's absolutely absurd that in 2013 VMware forces you to use SQL auth.  From an administration standpoint, using SQL auth is terrible.  It's silly that nowhere in the process does VMware bother t... See more...
It's absolutely absurd that in 2013 VMware forces you to use SQL auth.  From an administration standpoint, using SQL auth is terrible.  It's silly that nowhere in the process does VMware bother to mention that you can't use a Windows AD account to setup an event database, not even in their KBs.