yukiafronia's Posts

Hi, @shadowfruit8  Use my host file. I have not written anything. It is the default. Please download the attached file to " C:\Windows\system32\drivers\etc ". After that, as shown in the screensh... See more...
Hi, @shadowfruit8  Use my host file. I have not written anything. It is the default. Please download the attached file to " C:\Windows\system32\drivers\etc ". After that, as shown in the screenshot, Refer to the area circled in red and check the box.   Screenshots are in Japanese. You can proceed by looking at the icons. After setting up the screenshot, hosts - edit the name of copy.txt to hosts. When you are done, make sure Horizon Client can be installed.
Hi , @mlindgren1  I'm glad you were able to resolve the issue successfully. If everything is OK, please mark it as "resolved." @scott28tt  I suspect that quite a few people experience this proble... See more...
Hi , @mlindgren1  I'm glad you were able to resolve the issue successfully. If everything is OK, please mark it as "resolved." @scott28tt  I suspect that quite a few people experience this problem. Can Scott spread the word about this thread?
Hi, @M4T  The minimum components required to use Horizon 8.x are =====Minimum Required ===== ESXi vCenter Server Active Directory Connection Server Master VM for full or instant clone deployme... See more...
Hi, @M4T  The minimum components required to use Horizon 8.x are =====Minimum Required ===== ESXi vCenter Server Active Directory Connection Server Master VM for full or instant clone deployment (Windows 10) ================== ===== needed for full functionality ===== SQL Server (for Connection Server event recording) ==================================   Connection Server "registered server" is not required.
Hi, @fishizza1  Thanks for taking the screenshot. If you want to see it from the logs, you might want to look at the following Horizon Client logs. ===== C:\ProgramData\VMware\VDM\logs\Scanner*.t... See more...
Hi, @fishizza1  Thanks for taking the screenshot. If you want to see it from the logs, you might want to look at the following Horizon Client logs. ===== C:\ProgramData\VMware\VDM\logs\Scanner*.txt C:\ProgramData\VMware\VDM\logs\Netlink*.txt ===== You may want to search for the scanner model number in the logs to make sure the scanner is reading them. You should always reproduce the problem before looking at the logs. Also, make a note of the date and time you reproduced the problem or something like that.
Hi, @OliverGl  I have also submitted a SR to VMware, but it is taking a long time to investigate. Oh well, it's a spec check... It's hard work... Once I do, I am waiting for VMSA to post it. If t... See more...
Hi, @OliverGl  I have also submitted a SR to VMware, but it is taking a long time to investigate. Oh well, it's a spec check... It's hard work... Once I do, I am waiting for VMSA to post it. If there is any update from VMware, I would be glad if you could share it. Sorry, I can't offer any advice...
Hi, @jc296  You are correct, if you tried to upgrade to Windows Server 2019 with Connection Server installed on Windows Server 2012, VMware would not have approved that action because it would be an... See more...
Hi, @jc296  You are correct, if you tried to upgrade to Windows Server 2019 with Connection Server installed on Windows Server 2012, VMware would not have approved that action because it would be an in-place upgrade! Not only Connection Server, but also for Horizon Agent, if you want to apply Windows Feature Update, you should uninstall Horizon Agent , VMware Tools, and then perform Windows Update. Windows Update should be performed after uninstalling the Horizon Agent and VMware Tools.
Hi, @fishizza1  Can I launch Device Manager from Windows in a virtual machine, assuming I can redirect the scanner? I would like to see the Device Manager tab, select "devices by connection" and ta... See more...
Hi, @fishizza1  Can I launch Device Manager from Windows in a virtual machine, assuming I can redirect the scanner? I would like to see the Device Manager tab, select "devices by connection" and take a screenshot.
Hi, @mathewdsa  I see no problem with the procedure. The procedure for removing a Connection Server running on Windows Server 2012 is also fine as long as you remember to remove the ADAM software. ... See more...
Hi, @mathewdsa  I see no problem with the procedure. The procedure for removing a Connection Server running on Windows Server 2012 is also fine as long as you remember to remove the ADAM software. Excellent.!!
Hi, @RobMerritt  If there is an error, I would like a screenshot. Also, the virtual machines deployed on Horizon inherit the master VM's CPU count. It is not possible to change the number of CPUs ... See more...
Hi, @RobMerritt  If there is an error, I would like a screenshot. Also, the virtual machines deployed on Horizon inherit the master VM's CPU count. It is not possible to change the number of CPUs in each virtual machine assigned to each user.
Hi, @jlorang @vDruid  @vDruid  is right to look at the debug log. I would want to know when the Horizon Console becomes inaccessible, so I would keep throwing scripts at the Horizon Console all day... See more...
Hi, @jlorang @vDruid  @vDruid  is right to look at the debug log. I would want to know when the Horizon Console becomes inaccessible, so I would keep throwing scripts at the Horizon Console all day long to check the http status every 5 minutes or so, maybe every 10 minutes. It is normal for it to return a status of 200, but it is unlikely that throwing the script around would affect the user's connection; if the Connection Server fails just by checking the http status, then there are not enough resources in the virtual machine to begin with. So, you should keep checking the http status towards the Horizon Console, and if you see anything other than status 200, you should look at the debug log as @vDruid  said  
Hi, @VMWaremcp826  Hmmm... I created a verification environment to try, but was unable to reproduce the event. Is it possible to access vCenter Server from a Windows Server with Connection Server i... See more...
Hi, @VMWaremcp826  Hmmm... I created a verification environment to try, but was unable to reproduce the event. Is it possible to access vCenter Server from a Windows Server with Connection Server installed by FQDN? This is a basic requirement, but just a confirmation.
Hi, @MaryR333  I generally draft a SR for VMware when I get a black screen. Also, everyone is still installing the SVGA driver from VMware Tools and not using IDD (VMware Indirect Display Driver), ... See more...
Hi, @MaryR333  I generally draft a SR for VMware when I get a black screen. Also, everyone is still installing the SVGA driver from VMware Tools and not using IDD (VMware Indirect Display Driver), which is why the event occurs, so I tentatively addressed it in the registry and it was cured. I then uninstalled VMware Tools and installed the Horizon Agent, being careful not to install SVGA. Now I am able to operate without the registry without any problems.
@Windyy  I don't know if it can be cured, but please extend the java heap area of the Connection Server where the problem occurs and disable any anti-virus software on the Connection Server, includi... See more...
@Windyy  I don't know if it can be cured, but please extend the java heap area of the Connection Server where the problem occurs and disable any anti-virus software on the Connection Server, including Windows defender if there is any. If the problem persists, you will need to have VMware check the logs, etc. If the possibility of a memory leak is suspected, the first priority is to disable any anti-virus software and Windows Defender installed outside of Connection Server and check for reproducibility.
@tgrwa @Desktop_enginee  Sorry for the delay in confirmation. At 19:00 (JST) on 4/18, I was able to download Horizon Client 2303. Is the problem still occurring?
HI, @CEDCHelp  Thanks for reply.! We think we should look at Windows events first. Because if there is still a session in Horizon, I believe it is recorded as ERROR-CODE=AGENT_ERR_LOGOFF_IN_PROGRES... See more...
HI, @CEDCHelp  Thanks for reply.! We think we should look at Windows events first. Because if there is still a session in Horizon, I believe it is recorded as ERROR-CODE=AGENT_ERR_LOGOFF_IN_PROGRESS in the debug-yyyy-mm-dd-hhmmss.txt of the Horizon Agent. ERROR-CODE=AGENT_ERR_LOGOFF_IN_PROGRESS is a record that the OS is processing the logoff. Therefore, after reproducing the event, it is recommended to look for the logoff operation in System-log.evtx , Application-log.evtx around the date and time of the logoff operation from the Windows event. For keywords and such in the event log, "Application Hang" or something like that? If it is too difficult to check by yourself, you can submit the event log to Microsoft for confirmation, and if it is caused by a VMware module, identify the library name and present Microsoft's view to VMware, which may lead to a quick reinvestigation procedure on the development side If the problem is caused by a VMware module, you can identify the name of the library and present Microsoft's opinion to VMware, which may lead to a quick reinvestigation procedure on the part of the developer. Currently, to fix AGENT_ERR_LOGOFF_IN_PROGRESS, Currently, the most effective way to fix AGENT_ERR_LOGOFF_IN_PROGRESS may be to restart the virtual machine where the problem occurred.
Hi, @ring22  Please follow the steps below to see if it works. Check the KB for manual deletion, not ViewDbchk, Try to see if you can perform machine deletion from each component. * Manually d... See more...
Hi, @ring22  Please follow the steps below to see if it works. Check the KB for manual deletion, not ViewDbchk, Try to see if you can perform machine deletion from each component. * Manually delete link clone or steal virtual desktop entries from the View Composer database in VMware View Manager and VMware Horizon View (2015112) https://kb.vmware.com/s/article/2015112 ------------------ 1. Delete the virtual machine from the ADAM database on the connection server. 2.Delete all desktop references in the View Composer database. 3.Delete all affected computer objects from Active Directory. 4. Delete desktops from vCenter Server. ------------------ 1. Delete the virtual machine from the ADAM database on the connection server. Regarding. I assume you have already deleted the machine from the Connection Server, However, we would appreciate it if you could check if there is any machine information left in the ADAM database just to be sure. ------------------ Deleting a virtual machine from the ADAM database on the connection server Important: Before you begin these steps, use the View Administrator to disable provisioning on the pool from which you want to remove machines. Note: Before deleting an entry from the ADAM database, the name of the desktop virtual machine to be deleted, Composer database for reference when editing the database. 1. Connect to the View ADAM database. For more information on connecting to the ADAM database using ADSI Edit, Connecting to the View ADAM Database (2012377). * Connecting to the View ADAM Database (2012377) https://kb.vmware.com/s/article/2012377 2. Search for the virtual machine to be deleted. 2-1. Right-click [Connections] View ADAM database [localhost:389] and click [New] > [Query]. 2-2. Enter a query name such as "VM Search" for example. Under Root of Search, click Browse and select the configuration unit of Servers. 2-4. Click OK. 2-5. Paste the following search string into Query String. (&(objectClass=pae-VM)(pae-displayname=VirtualMachineName)) where VirtualMachineName is the name of the virtual machine whose GUID is to be searched. * and ? as wildcards to match multiple desktops. 2-6Click OK to create the query. 2-7Click Query in the left pane. The virtual machines that match the search will appear in the right pane. ------------------ 2. "2. Delete all desktop references in the View Composer database." For more information about As with Connection Server, please check to see if any machine information remains in Composer, If so, delete it. ------------------ To remove a reference to a linked clone from the View Composer database, perform the following steps: 1. 1. open SQL Manager > Databases > View Composer Database > Tables. 2. Open the dbo.SVI_VM_NAME table and delete the entire row where the virtual machine is referenced in the NAME column. 3. Open the dbo.SVI_COMPUTER_NAME table and delete the entire row where the virtual machine is referenced in the NAME column. 4. Open the dbo.SVI_SIM_CLONE table and find the reference to the virtual machine in the VM_NAME column and write down the ID. If you delete this row, dependencies with other tables will be an issue. 5. Open the dbo.SVI_SC_PDISK_INFO table and delete the entire row where the dbo.SVI_SIM_CLONE ID is referenced in the PARENT_ID column. 6. Open the dbo.SVI_SC_BASE_DISK_KEYS table and delete the entire row where dbo.SVI_SIM_CLONE ID is referenced in the PARENT_ID column. 7. If the link clone was in the process of deployment when the problem occurred, Additional references to the clone may remain in the dbo.SVI_TASK_STATE and dbo.SVI_REQUEST tables. 7-1. Open the dbo.SVI_TASK_STATE table and find the row in the SIM_CLONE_ID column that references the dbo.SVI_SIM_CLONE ID. Write down the REQUEST_ID for that row. Open the dbo.SVI_REQUEST table and delete the entire row where dbo.SVI_TASK_STATE REQUEST_ID is referenced. 7-3. Delete the entire row from the dbo.SVI_TASK_STATE table. 8. Delete the entire row in the dbo.SVI_SIM_CLONE table where the virtual machine is referenced. ------------------ 3. Delete all affected computer objects from Active Directory. 4. Delete desktops from vCenter Server. Regarding I assume that the information on the machine is still there, so can you please delete it? ------------------ Delete virtual machines from Active Directory To remove a virtual machine from Active Directory, perform the following steps Log in to the domain controller as an administrator. 2. Navigate to Start > Administrative Tools > Active Directory Users and Computers. 3. Delete the virtual machine from Computers. Note: The virtual machine may not be in the computer's OU (Organizational Unit). If so, it may be in a different OU. Deleting Virtual Machines from vCenter Server To delete a virtual machine from vCenter Server, perform the following steps Log in to the vCenter Server using the vSphere Client. Right-click the virtual machine in the linked clone and click Power > Power Off. Right-click the virtual machine in the linked clone and click Remove from Disk. 4. Enable pool provisioning. ------------------   YouTube https://www.youtube.com/watch?v=Tm1kUXIKek8 (Japanese) https://youtu.be/ayG5SBJZRpE (Part1 - English) https://youtu.be/APd5mTmKOnM (Part2 - English)
Hi, @CEDCHelp  Have you checked the AutoEndTasks registry to force logoff? Horizon View Desktops hanging on logoff preventing composer operations, or users from logging in (2151503) https://kb.v... See more...
Hi, @CEDCHelp  Have you checked the AutoEndTasks registry to force logoff? Horizon View Desktops hanging on logoff preventing composer operations, or users from logging in (2151503) https://kb.vmware.com/s/article/2151503 The AutoEndTasks registry was used heavily mainly for link clones, but it is also effective for instant clones.  
Hi, @LeHongTung  This is the communication flow when PCoIP/Blast Secure Gateway is not used, but when PCoIP/Blast Secure Gateway is used, the communication from the Connection Server onward is also ... See more...
Hi, @LeHongTung  This is the communication flow when PCoIP/Blast Secure Gateway is not used, but when PCoIP/Blast Secure Gateway is used, the communication from the Connection Server onward is also encrypted, so it is safe. https://techzone.vmware.com/resource/network-ports-vmware-horizon#about-this-guide:~:text=external%2C%20or%20tunneled.-,Internal%20Connection,-An%20internal%20connection     So, I think your opinion is correct.
Hi, @mbrundage  Do you have the AutoEndTasks registry set up in the master VM for instant clonesz AutoEndTasks is enabled for instant cloning.
Hi, @Gyro1987  Are the Horizon Agent versions compatible with the Horizon Client? To find out, please visit the URL below and then select the version of each product. You can select more than one v... See more...
Hi, @Gyro1987  Are the Horizon Agent versions compatible with the Horizon Client? To find out, please visit the URL below and then select the version of each product. You can select more than one version. https://interopmatrix.vmware.com/Interoperability?col=569,&row=108, Also, if you intentionally create problems, Note the time of the reproduction and exit the Horizon Client. After that, please refer to the VMware docs and locate the following text file https://docs.vmware.com/jp/VMware-Horizon/2212/horizon-console-administration/GUID-3127B73A-B6DB-44F3-856B-5FDB8E5C21FD.html ==== text file you want==== vmware-horizon-viewclient-YYYYYY-MM-DD-XXXXXX.txt debug-YYYYY-MM-DD-XXXXXX.txt ====================== I would also like the Horizon Agent logs, though, If you go that far, it would be faster to submit a support ticket to VMware.