yukiafronia's Posts

@Chnobli_Globi @Michael_Turconi @klingenbergh @rroodenburg @RetouwNL  Today, Horizon 2309 was released. https://docs.vmware.com/en/VMware-Horizon/8-2309/rn/vmware-horizon-8-2309-release-notes/ind... See more...
@Chnobli_Globi @Michael_Turconi @klingenbergh @rroodenburg @RetouwNL  Today, Horizon 2309 was released. https://docs.vmware.com/en/VMware-Horizon/8-2309/rn/vmware-horizon-8-2309-release-notes/index.html https://docs.vmware.com/en/VMware-Horizon-Client-for-Windows/2309/rn/vmware-horizon-client-for-windows-2309-release-notes/index.html https://docs.vmware.com/en/VMware-App-Volumes/2309/rn/vmware-app-volumes-4-version-2309-release-notes/index.html https://docs.vmware.com/en/VMware-Dynamic-Environment-Manager/2309/rn/vmware-dynamic-environment-manager-2309-release-notes/index.html https://docs.vmware.com/en/Unified-Access-Gateway/2309/rn/unified-access-gateway-2309-release-notes/index.html  
@UHjdavis  For a long time, the Radeon pro series has not received Horizon hardware certification. V340 can also be found in the article, which apparently does not work properly. https://community... See more...
@UHjdavis  For a long time, the Radeon pro series has not received Horizon hardware certification. V340 can also be found in the article, which apparently does not work properly. https://community.amd.com/t5/graphics/radeon-pro-v340-and-vmware-horizon-view/td-p/143943 Thanks
Hi, @adamabel  At least, I have never seen the ability to unlock on the GUI. That is, I have never seen the ability to unlock on the GUI of either Horizon Client , Connection Server, or Agent.
Hi, @Bas00  This is faster to draft an SR to VMware. If I were to do the research, I would want the following information ===== ・I have a PCoIP or VMware Blast problem, which is more likely t... See more...
Hi, @Bas00  This is faster to draft an SR to VMware. If I were to do the research, I would want the following information ===== ・I have a PCoIP or VMware Blast problem, which is more likely to occur, although the problem occurs at random? ・Clone method or user assignment method. If it is an instant clone, I don't think the session will remain because the virtual machine will be recreated after the user is logged off. ・I would like to know more specifics about the state in which a user continues to connect to a virtual machine again after logging off. If possible, it would be nice to have a video of the problem reproduced. ・AutoEndTasks already implemented? ===== Also, Connection Server logs, Horizon Agent logs, and Horizon Client logs are required when problems occur. Please collect all logs with administrative privileges.
Hi, @adamabel  Changing the maximum number of login attempts is configurable in the Connection Server's ADAM database. If no special settings are made, the default number of login attempts is three... See more...
Hi, @adamabel  Changing the maximum number of login attempts is configurable in the Connection Server's ADAM database. If no special settings are made, the default number of login attempts is three. First, log in to the Connection Server as a domain administrator, Open the ADSI editor and connect to the ADAM databases dc=vdi,dc=vmware,dc=int. See KB#2012377 below for details. * Connecting to View ADAM database (2012377) https://kb.vmware.com/s/article/2012377?lan=ja --- Excerpt --- Note: Be sure to make a full backup of the ADAM database before starting the procedure. Windows Server 2008 To connect to the View ADAM database: ... ------------ Then, set the number of login attempts to, for example, 10 Add the following to the attribute [pae-NameValuePair] of [OU=Properties] - [OU=Global] - [CN=Common] in the ADAM database and [OK]. cs-loginattemptslimit=10 To undo the change, delete the above from the attribute [pae-NameValuePair] and [OK]. This will take effect immediately, so there is no need to restart the Connection Server. Thanks!
Hi, @CarlosDLMC  I checked the log. In the section where the problem occurs, it says DX11, so there is a Direct X access violation and the Horizon Client is terminating abnormally. So try disa... See more...
Hi, @CarlosDLMC  I checked the log. In the section where the problem occurs, it says DX11, so there is a Direct X access violation and the Horizon Client is terminating abnormally. So try disabling DirectX. ----------------------------------------------- To disable DirectX on the Horizon Client (1) Open the Horizon Client configuration file config.ini on the client terminal using an editor such as Notepad. If the file does not exist, create a new one. Location: %APPDATA%\VMware   File name: config.ini (* %APPDATA% will jump to the C:\Users\<user name>\AppData\Roaming folder etc.) (2) Add the following two lines (DirectX disable setting) to the configuration file and save it. viewClient.enableD3D11=FALSE viewClient.enableD3D9=FALSE (3) Restart Horizon Client and check the operation. ----------------------------------------------- I hope it will improve.
Hi, @MCintra  Thanks for the detailed explanation. Completely from an acquaintance, when creating a pool of instant clones on Horizon 2111, there was a situation where a snapshot was not created on... See more...
Hi, @MCintra  Thanks for the detailed explanation. Completely from an acquaintance, when creating a pool of instant clones on Horizon 2111, there was a situation where a snapshot was not created on the cp-replica VM. It seems that if the snapshot did not exist in the cp-replica VM, the instant clone could not create the virtual machine, so it was an Image Push error. At that time, he told me the KB he was referring to. UNKNOWN_FAULT_FATAL: Failed to retrieve snapshot for the vm : cp-replica-X Instant Clone Creation Error (91750) https://kb.vmware.com/s/article/91750 My friend seems to have checked to see if the problem reproduces itself on Horizon 2111.1. He said that the error message below no longer appears in Horizon 2111.1 and that the problem has been resolved. ===== BROKER_PROVISIONING_PUBLISH_IMAGE_FAILED Image Publish initiated by SchedulePushImage for Pool xxxxx failed for Image [VM=/xxxxxxxxxx/vm/ xxxxxxxxxx/xxxxxxxxxx/xx/xxx/VM_name ===== But it seems the problem still occurs on Horizon 2303. Maybe I should try following the KB for now? If it doesn't improve, check Horizon 2111.1 to see if the problem is reproducible. If it doesn't go away, I may have to collect the cp-replica debug logs and contact VMware...
Hi, @MCintra  What are the problems? Does the problem occur with instant cloning? Can you reproduce the problem? Do you have a Horizon Agent installed with Instant Clone enabled on the Golden V... See more...
Hi, @MCintra  What are the problems? Does the problem occur with instant cloning? Can you reproduce the problem? Do you have a Horizon Agent installed with Instant Clone enabled on the Golden VM? Are there any error messages in the Horizon Console when the problem occurs? Please give us a screenshot. Without understanding what you are struggling with, I can't comment.
Hi, @M4T  FullClone or Instant Clone? If FullCLone, you will need to create a script in PowerCLI. For Instant Clone, you only need to reinstall VMware Tools installed on the virtual machine in the... See more...
Hi, @M4T  FullClone or Instant Clone? If FullCLone, you will need to create a script in PowerCLI. For Instant Clone, you only need to reinstall VMware Tools installed on the virtual machine in the golden image. So, I think InstantClone is more appreciated by many people than FullClone, which is more tedious. (Just my opinion)
Hi, @nickcannon12  I have installed and tested Horiozn Client 2303 on several PCs. I was able to reproduce the problem of installation failure on some PCs. Net Framework 4.8, the installation of t... See more...
Hi, @nickcannon12  I have installed and tested Horiozn Client 2303 on several PCs. I was able to reproduce the problem of installation failure on some PCs. Net Framework 4.8, the installation of the Horizon Client failed. So, why don't you try installing Horizon Client again using .NET 4.5 Framework? The error message is the same, so it might be worth a try. https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Error-message-when-installing-VMware-Horizon-Client-8/td-p/2968260/jump-to/first-unread-message
Hi, @vDruid @nickcannon12  I have installed and tested Horiozn Client 2303 on several PCs. I was able to reproduce the problem of installation failure on some PCs. Net Framework 4.8, the installat... See more...
Hi, @vDruid @nickcannon12  I have installed and tested Horiozn Client 2303 on several PCs. I was able to reproduce the problem of installation failure on some PCs. Net Framework 4.8, the installation of the Horizon Client failed. So, why don't you try installing Horizon Client again using .NET 4.5 Framework?
Hi, @Luxxadin @Jubish-Jose  I have reviewed the vminst_20230509074113.log you uploaded. The error content was exactly the same as the Horizon Client installer log in another thread. https://commun... See more...
Hi, @Luxxadin @Jubish-Jose  I have reviewed the vminst_20230509074113.log you uploaded. The error content was exactly the same as the Horizon Client installer log in another thread. https://communities.vmware.com/t5/Digital-Workspace-Members/Vmware-Horizon-client-win-11-failed-to-install/m-p/2967670/highlight/false#M96
HI, @ModiMornex @Ddekok24  I went through the vminst_20230510093709.log After doing so, I found an error related to vmusbd (USB Redirection). ===== 2023-05-09T19:41:05.171-03:00| inst-build-21387... See more...
HI, @ModiMornex @Ddekok24  I went through the vminst_20230510093709.log After doing so, I found an error related to vmusbd (USB Redirection). ===== 2023-05-09T19:41:05.171-03:00| inst-build-21387416| E2: DeleteKeyChildren: subkey already deleted: SYSTEM\CurrentControlSet\Services\ vmusb 2023-05-09T19:41:05.171-03:00| inst-build-21387416| E2: VNLDeleteSystemFile: failed to delete 0x00000002 'C:\WINDOWS\system32\drivers\ vmusb.sys' 2023-05-09T19:41:05.171-03:00| inst-build-21387416| E2: VNLDeleteSystemFile: failed #3 to delete 0x00000002 'C:\WINDOWS\system64\drivers\ vmusb.sys' ...snip... 2023-05-09T19:41:05.325-03:00| USBDeviceInstUtil-build-21387416| E1: Inst_InstallService: Service 'VMUSBArbService' already exists| winerror code 1073 (The specified service already exists.) ===== If you can format the OS, that is the best you can do. If you really do not want to do OS formatting, try the following steps. Clear the following path C:\Program Files(X86)\VMware\ (client folder) delete the old Horizon client folder after the un-installation. Delete the VMware VDM folder under "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc. " from regedit Reboot the client machine. Try disabled the Antivirus software in the client machine if you have and try install the Horizon client.
Hi, @fabio1975  Correct and very clear explanation. Indeed, for automatic desktop pools, you need a profile management tool. My response, "it feels like the intended behavior" also assumes that yo... See more...
Hi, @fabio1975  Correct and very clear explanation. Indeed, for automatic desktop pools, you need a profile management tool. My response, "it feels like the intended behavior" also assumes that you are using an automated desktop pool. Well, the advantages of using a manual desktop pool... I'm not sure what you're asking... If you have a small number of users, or if you customize applications for each employee and cannot manage all profiles at once, then a manual desktop pool may be a viable option.
Hi, @tedykgb @fabio1975  I suspect that Horizon is working as intended. In other words, I believe the intended behavior is that profiles cannot be maintained after deploying virtual machines in Hor... See more...
Hi, @tedykgb @fabio1975  I suspect that Horizon is working as intended. In other words, I believe the intended behavior is that profiles cannot be maintained after deploying virtual machines in Horizon unless there is a profile management tool available. Profile management is usually DEM or FSlogix , Roaming User Profile...
Hi, @M4T  Hmmm, I think I need to reproduce the problem and check the vCenter logs to see the process of the virtual machine deleting. It is only a possibility, but it could be vc cache. Please go... See more...
Hi, @M4T  Hmmm, I think I need to reproduce the problem and check the vCenter logs to see the process of the virtual machine deleting. It is only a possibility, but it could be vc cache. Please go to the Horizon Console and select "Servers" -> "vCenter Server" and open the edit screen of the registered vCenter Server. On the Storage tab, you may see the words View Storage Acceralator. Can you disable View Storage Acceralator and reproduce the problem?
Hi, @manwi  Horizon 6.7 or Horizon 6.x is long past EOSL status. VMware does not even accept extended support, It is impossible to obtain a genuine installer. I have also accidentally deleted the... See more...
Hi, @manwi  Horizon 6.7 or Horizon 6.x is long past EOSL status. VMware does not even accept extended support, It is impossible to obtain a genuine installer. I have also accidentally deleted the Agent installer for Horizon 7.5 before. At that time, VMware refused to provide the Horizon Agent. The reason is that it is already EOL. That is why. Any particular reason why I need to get Horizon Agent 6.7?
Hi, @M4T  I assume it was created in a manual desktop pool with a full clone. In such an environment, if a virtual machine is deleted from disk, the virtual machine will be completely deleted in vC... See more...
Hi, @M4T  I assume it was created in a manual desktop pool with a full clone. In such an environment, if a virtual machine is deleted from disk, the virtual machine will be completely deleted in vCenter Server and will maintain the status of being deleted unless Horizon receives a task completion notification. So, is there any chance that the deletion took a long time in vCenter Server? Also, did you finally remove the virtual machine name from the Horizon virtual machine tab without doing anything?
Hi, @normeyj @BenTrojahn @Patrick4 @Le0Getz  It is an older version, with a slightly different message, Page 8 of the following document contains a statement that may be of interest. The warning m... See more...
Hi, @normeyj @BenTrojahn @Patrick4 @Le0Getz  It is an older version, with a slightly different message, Page 8 of the following document contains a statement that may be of interest. The warning may be issued if the load-balancing settings are not similar among the RDSH machines in the farm. - RDSH SESSION LOAD-BALANCING FOR DESKTOPS AND APPLICATIONS IN VMWARE HORIZON 6 AND VMWARE HORIZON 7 www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-horizon-view-rdsh-session-load-balancing.pdf ===== Excerpts from here ===== Mixed load values - When the load balancing configuration is not identical across the RDSH VMs in a farm, the dashboard shows the following status warning: One or more server(s) is either in warning or error state, or servers have a mixed set of reported and unreported load values. ===== Excerpt here: ===== In the Horizon Console screen showing the farm, please select the RDS host and click "Edit", then change the "Number of connections" setting in it to unify the "Maximum number of connections" for all RDSH servers to a number, or to "Unlimited", The message may disappear. Below are the documents related to load balancing. Please refer to the above mentioned documents as necessary. - Configuring RDS Host Load Balancing in the Horizon Console https://docs.vmware.com/jp/VMware-Horizon/2212/virtual-desktops/GUID-83A5A0DD-6274-4432-9812-B2182C5BEAED.html  - Load Balancing Configuration https://docs.vmware.com/en/VMware-Horizon/2212/virtual-desktops/GUID-461B7E5E-183B-4AA0-AB87-A76D07F6BDDD.html 
Hi, @Mei_1225 Is there a registry set up to force the virtual machine to log off? Horizon View Desktops hanging on logoff preventing composer operations, or users from logging in (2151503) https:/... See more...
Hi, @Mei_1225 Is there a registry set up to force the virtual machine to log off? Horizon View Desktops hanging on logoff preventing composer operations, or users from logging in (2151503) https://kb.vmware.com/s/article/2151503 When you deploy virtual machines in Horizon, you should have created a master VM. In the master VM, try to redeploy the virtual machine with the following registry settings ===== Registry Location:HKCU\Control Panel\Desktop String AutoEndTasks Value 1 =====