Maybe that's the problem I need to create and then shift the horizon agent into a platform layer? Everything created and built and tested/run on the same vmware platform. We all connected to the Internet all the time and TiWorker.exe checking new updates regularly via the Internet and once the Microsoft releases the updates then. I don't have a platform layer (put a separate post about that). There is only 1 layer on the image which is horizon agent.
When you see the Windows Task Manager, you may see that this system process uses more than 50 of CPU resources and sometimes more than that. Horizon agent 7.3.2 and I deleted the UDP ports from the layer. Windows Modules Installer Worker usually is one of the most common system processes which take up computer resources and it is also known as TiWorker.exe. So I built a new desktop and in the browser it just gives a grey screen and then drops out (like the horizon agent has crashed). (goes around in circles and never completes). Recomposed desktop with new image and it hangs on the hi, welcome we're making things for you screen. However I forgot to run NGEN so I added a new version of the OS layer.
After reboot, it still ran hard after a bit (i think cant remember). I turned off sophos auto-deployment and it still ran at 100%. I created a few desktops they are all running at 100%. I checked in the desktop it is still disabled. I removed the windows store apps, disabled Windwos UPdates via local GP in the OS layer.
0 kommentar(er)
