BarryUWSEFS's Posts

That sounds reasonable. The images may have been in the same folder. I had created a brand new image and pool for the user group "staff" and it was when I deleted the old staff pool that the new VM image was also removed. Being in the same folder was really the only thing I can think of they would have in common. Still does not make sense, but you have given me some good ideas to further lock down Horizon.

I see, so when adding the vCenter to Horizon, create a special account, good idea. I see that now in the documentation, thanks. I do still believe however, since I am the only person who does anything in vSphere/Horizon, the command to delete the pool in Horizon, nevertheless, also deleted this other VM, for whatever reason. Do you think using a dedicated account would have prevented this? Or still important, just made it easier to analyze? Thanks for your input, much appreciated!

I was logged into Horizon Administrator with a Windows domain account when I deleted the pool. xxx\administrator is the vCenter SSO. I assume Horizon invokes the vCenter account for the actual VM removal. I am the only person on our team who supports VMware/vSphere/Horizon so no one else would have been involved. Thanks!

I opened a VMware support case. Unfortunately the first tier Horizon tech was pretty unhelpful, and never even recognized my question of how this could happen. He escalated to a vSphere engineer who confirmed the VM was not recoverable, but not being a Horizon engineer could not speak to why this happened. The case is still open so if I get any answer I will update, otherwise this will go down as the strangest mystery in my years of Horizon/View administration.

I know it seems impossible. The deleted VM that was deleted was a master for a different pool altogether. Check this query and you can see the obvious VM's from the pool that were deleted, the the staff-1909-M and a couple replicas. Look at the time stamps. I marked it in red towards the bottom. $start = (Get-Date).AddDays(-6) Get-VIEvent -Start $start -MaxSamples ([int]::MaxValue) | where{$_ -is [VMware.Vim.VmRemovedEvent]} Template             : False Key                  : 27992993 ChainId              : 27992989 CreatedTime          : 5/19/2020 7:16:42 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-016 on xxx.25.182.204 from Madrona ChangeTag            : Template             : False Key                  : 27992995 ChainId              : 27992990 CreatedTime          : 5/19/2020 7:16:42 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-003 on xxx.25.182.204 from Madrona ChangeTag            : Template             : False Key                  : 27992997 ChainId              : 27992991 CreatedTime          : 5/19/2020 7:16:42 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-004 on xxx.25.182.204 from Madrona ChangeTag            : Template             : False Key                  : 27993024 ChainId              : 27993016 CreatedTime          : 5/19/2020 7:17:13 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-009 on xxx.25.182.202 from Madrona ChangeTag            : Template             : False Key                  : 27993029 ChainId              : 27993019 CreatedTime          : 5/19/2020 7:17:14 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-018 on xxx.25.182.202 from Madrona ChangeTag            : Template             : False Key                  : 27993035 ChainId              : 27993031 CreatedTime          : 5/19/2020 7:17:15 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-015 on xxx.25.182.204 from Madrona ChangeTag            : Template             : False Key                  : 27993037 ChainId              : 27993030 CreatedTime          : 5/19/2020 7:17:15 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-017 on xxx.25.182.204 from Madrona ChangeTag            : Template             : False Key                  : 27993040 ChainId              : 27993038 CreatedTime          : 5/19/2020 7:17:16 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-005 on xxx.25.182.204 from Madrona ChangeTag            : Template             : False Key                  : 27993043 ChainId              : 27993041 CreatedTime          : 5/19/2020 7:17:18 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-019 on xxx.25.182.204 from Madrona ChangeTag            : Template             : False Key                  : 27993063 ChainId              : 27993061 CreatedTime          : 5/19/2020 7:17:45 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-022 on xxx.25.182.202 from Madrona ChangeTag            : Template             : False Key                  : 27993068 ChainId              : 27993066 CreatedTime          : 5/19/2020 7:17:50 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-024 on xxx.25.182.204 from Madrona ChangeTag            : Template             : False Key                  : 27993081 ChainId              : 27993075 CreatedTime          : 5/19/2020 7:17:55 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-025 on xxx.25.182.203 from Madrona ChangeTag            : Template             : False Key                  : 27993085 ChainId              : 27993082 CreatedTime          : 5/19/2020 7:17:57 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-021 on xxx.25.182.201 from Madrona ChangeTag            : Template             : False Key                  : 27993087 ChainId              : 27993083 CreatedTime          : 5/19/2020 7:17:57 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-020 on xxx.25.182.203 from Madrona ChangeTag            : Template             : False Key                  : 27993103 ChainId              : 27993101 CreatedTime          : 5/19/2020 7:18:29 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Staff-023 on xxx.25.182.204 from Madrona ChangeTag            : Template             : False Key                  : 27993152 ChainId              : 27993106 CreatedTime          : 5/19/2020 7:21:11 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed replica-bd5bb126-58c0-4bdd-ad00-4739b4ea0e8d on xxx.25.182.203 from Madrona ChangeTag            : Template             : False Key                  : 27993157 ChainId              : 27993153 CreatedTime          : 5/19/2020 7:21:13 AM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed Staff-1909-M on xxx.25.182.202 from Madrona ChangeTag            : Template             : True Key                  : 27838858 ChainId              : 27838858 CreatedTime          : 5/14/2020 11:47:51 PM UserName             : User Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed FV-Student-12 on vxrail4.xxx from Madrona ChangeTag            : Template             : False Key                  : 27831062 ChainId              : 27831016 CreatedTime          : 5/14/2020 7:33:13 PM UserName             : xxx\Administrator Datacenter           : VMware.Vim.DatacenterEventArgument ComputeResource      : VMware.Vim.ComputeResourceEventArgument Host                 : VMware.Vim.HostEventArgument Vm                   : VMware.Vim.VmEventArgument Ds                   : Net                  : Dvs                  : FullFormattedMessage : Removed replica-a47a5597-8b03-4ee0-9c23-05a8152c5b9d on xxx.25.182.204 from Madrona ChangeTag            : PS C:\WINDOWS\system32>

Well, for troubleshooting purposes I already suggested trying Full Screen instead of All Monitors, and also in task manager see what is causing the 60% CPU usage. Also look at Windows Events and see if there is anything. Is there any IT folks supporting Horizon you can ask? Perhaps something has changed on their end.

Hi, you don't mention, or I do not understand what you are connecting to with the Horizon client, you only say "work related materials." If you are connecting to a Horizon desktop pool VM, it determines the number of supported monitors, although three can be supported, it is very typical that only two are, just depends how it was configured. Instead of All Monitors try Full Screen and see if it still freezes up (you will not get all three monitors though). The video cards on your local machine do not interact with the Horizon client performance. Also what is utilizing the CPU? That could be a culprit as well.

Not exactly sure what you mean by "Tried to create some linked clone dedicated VDIs in a pool." You were adding VM's to an existing pool? Creating a new pool? If it is a linked clone pool, recomposing shouldn't hurt anything to existing, unless perhaps you are not using any kid of user management, meaning Persona, FSlogix, roaming profiles etc. The only time I ran into a folder mismatch was when a  master image got moved to a different folder, then a recompose pointing to the new location solved it.

This happened to me and it was simple. I assumed you enter the DNS name in Horizon admin, but that did not work. In UAG advanced settings you give the UAG a "friendly" name, not the DNS name. Enter this friendly name in horizon administrator. That worked for me. It also may have mattered that I had a dash in the DNS name, but not the friendly name, not sure.

Thanks for the info. When I open the redirections.zip it is empty, for some reason. Right now my redirection mostly just has some Chrome exclusions. We are going to keep an eye on profile bloat. Our desktops are for student labs and classes rather than day to day personal PC's, so I am not expecting a lot of profile bloat, but we will see. We have also previously redirected desktop, documents and download folders, and we are still doing that, so they are not in the profile. I also watched my profile balloon by 2GB when I opened Outlook, so I added the Office admx to the image and restricted the email download to three months, which is fine for these being classroom and lab computers. Class starts tomorrow, so I only had a few days to get FSlogix up, running and tested. Looking forward to further research into many of the options. Thanks for the tips, I'll check out ShrinkFSL.

I was finally able to determine that our school has an agreement that covers FSlogix. Previous to this I didn't even know Microsoft had bought the technology, so thank you. The initial setup was rather easy, and had my first test in a couple hours. The start menu worked great.  I was also able to continue to use our redirected folders so nobody loses data, no data has to be migrated. With concerns about profile bloat, I started using exclusions from "app-data."  I started with an example redirect.xml file I found. It broke the start menu. I started removing every exclusion that seemed could affect the start menu, with no luck. Due to time constraints I removed every appdata - Microsoft exclusion, and the start menu started working again. I cannot yet say exactly which folder was responsible for breaking the menu, but it sure is obscure.  If profile growth becomes an issue we will revisit the exclusions. But right now everything is working. So I do not have an answer for traditional Microsoft roaming profiles and 1909. Perhaps this is the breaking point. FSlogix is free with certain Microsoft agreements, including RDS cals,  but I read in a recent release they stopped license checking... Here is a very succinct article that got me started.