XSavior's Posts

Has there been any progress on this issue? I am facing this issue as well. Windows 10 (1803) /w AppVolumes 2.17.0 on Horizon 7.9 and Office 2016 on Gold Image with Projects and Visio each p... See more...
Has there been any progress on this issue? I am facing this issue as well. Windows 10 (1803) /w AppVolumes 2.17.0 on Horizon 7.9 and Office 2016 on Gold Image with Projects and Visio each placed on their own AppStack. You can open any of the core Office Apps (Words/Excel and ect) over and over just fine... but if you open Projects or Visiso it will open the first time just fine but then after that any Office App will run the Setup again every single time you open an Office App. Really frustrating. The only work-around I know is to have all of the apps on the gold image and then they all work fine together. Originally if I installed Office on the Gold Image and Projects and Visio into Appstacks they would all work together AS LONG AS YOU DID NOT RUN WINDOWS UPDATE to update office. This problem has started when you try to update Office in any way (both on Gold Image and on AppStacks). AppVolumes 4 is on the way soon but I have no idea if this issue is fixed??? I just noticed in 2.18.0 Release notes: https://docs.vmware.com/en/VMware-App-Volumes/2.18/rn/VMware-App-Volumes-218-Release-Notes.html VMware App Volumes 2.18 Release Notes Resolved Issues When Office 2016 is installed in the base, an installer pop-up is displayed as follows: Please wait while Windows configures Microsoft Office 2016 [2336096] I will be updating and checking if the issue is resolved as well.
Sorry for bringing this back from the dead but yesterday I was working with VMware support and we made a discovery on why some apps are loading very slowly. This has been tested on AppVolumes 2.1... See more...
Sorry for bringing this back from the dead but yesterday I was working with VMware support and we made a discovery on why some apps are loading very slowly. This has been tested on AppVolumes 2.14.0 I had this problem with a few apps and this fix below immediately solved the problem. I had M-Print Pro that would take 2.5 mins to load and with this fix it reduced it to 5 seconds. When creating the AppStack before finishing provisioning the stack go to: C:\SnapVolumesTemp\MountPoints\****random stuff**** Then edit snapvol.cfg with notepad In Section: "# Registry" paste the following line (at bottom of section with similar looking entry) reverse_replicate_registry_key=\MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Fonts                           # Fixes Loading Time For Lots of Programs This problem can occur when this registry location no longer exists in Windows (Possibly removed during optimization such as OSOT or might have been removed in certain versions of Windows 10) VMware has noted this and has forwarded it to their senior engineers. This is the result of nearly 2 months of work investigating with VMware. Thank You!
I know what you mean. We started out looking at Zero clients but they are quite limited in the big picture. Just remember Windows 10 IoT is not an OS that gets patched often. I re-deploy the i... See more...
I know what you mean. We started out looking at Zero clients but they are quite limited in the big picture. Just remember Windows 10 IoT is not an OS that gets patched often. I re-deploy the image about 2 - 3 times a year and usually because of Horizon Client updates and a few software updates (not OS updates). with HP the HPDM (HP Device Manager) allows you to push out if needed a new image to every client with only about 30 seconds of work. You setup a single client (Development Client) with all changes. You then image it using the HPDM. Then you push that image out to as many clients as you want at the same time. I usually do an entire branch each night. Thin Client management has come a long ways in recently years as having the extreme flexibility of the Windows 10 platform has been great.
I agree. I have hated this so much. I wish this would get fixed. I have a Horizon 6.2.4 Deployment and use Dedicated Desktops. When we terminate an employee we nuke the VM and a new one gen... See more...
I agree. I have hated this so much. I wish this would get fixed. I have a Horizon 6.2.4 Deployment and use Dedicated Desktops. When we terminate an employee we nuke the VM and a new one generates to replace it. It always goes to the bottom of the list adding a new one. I wish Horizon was smart enough to see the missing VM and replace it instead of running up the VM ID's. Does not take long to get the VM ID's int he naming to get out of control over time. If I could ask VMware for something I would ask them to get smarter about VM generating looking for gaps in the naming scheme so you could slot in replacements in missing holes.
I just thought I would throw my 2 cents in. We have a Horizon 6.2.4 Deployment with Nvidia Grid M10's using the M10-1B Profile for most users. I decided on us using the HP T520 Thin Clients... See more...
I just thought I would throw my 2 cents in. We have a Horizon 6.2.4 Deployment with Nvidia Grid M10's using the M10-1B Profile for most users. I decided on us using the HP T520 Thin Clients. They have been amazing and perform extremely well. We have had 0 issues and the admin tools (HP Device Manager) is pretty slick. We have done a dual monitor deployment for all users (except training computers) using a pair of Asus IPS PB238Q screens. The config is nice using Display Port (and the monitors come with every cable) and the T520 uses Dual Display Port and also has a VGA if you need to adapt to any older monitors kicking around. Hope this helps.
Hi There, This is normal. That extra monitor is part of the Nvidia Grid system. We have a large Nvidia Grid Deployment on Horizon 6 and we have the same thing. If you remove it you will bre... See more...
Hi There, This is normal. That extra monitor is part of the Nvidia Grid system. We have a large Nvidia Grid Deployment on Horizon 6 and we have the same thing. If you remove it you will break you Grid Deployment on the VM. From my understanding from Nvidia is that it is part of the "auto-magic" of Grid. Hope this helps (Nothing to be worried about).