VMware Horizon Community
iJohnny
Contributor
Contributor
Jump to solution

VMware, linked clone crash

Hi. I write this for make a question about linked clones.

Some hours ago i created a new golden image with windows 10 for a new pool.

I installed all the programs & configurations that we will use. Then i installed Horizon agent v7.4, and finally, i installed VMware Optimization OS.

Next i went to horizon to create my new pool & it created succesfully, without errors, the sysprep ran perfectly.

Finally i proceeded to make some tests to the pool.

I logged with a entitle user & for some minutes the VM works normally, then the machine gets freezed & vSphere sends the warning "vSphere HA restarted this virtual machine" & the machine proceed to restart.

pastedImage_0.png

At the same time Connection Server shows "inaccessible agent".

pastedImage_1.png

This ocurr in all the VM of the pool repeatedly.

Anyone has idea what's going on?

Thanks.

1 Solution

Accepted Solutions
iJohnny
Contributor
Contributor
Jump to solution

Hi everyone, i found the solution for this case.

The problem was that the Windows 10 version 1909 (October 19) is unstable to create pools.

For solve the problem, i returned to the 1803 version.

View solution in original post

6 Replies
TomaszGan
Contributor
Contributor
Jump to solution

Try reinstall VMware Tools and Horizon Agent after optimization.

Reply
0 Kudos
HussamRabaya
VMware Employee
VMware Employee
Jump to solution

what is the vsphere version ?

Reply
0 Kudos
iJohnny
Contributor
Contributor
Jump to solution

Hi, thanks for the reply. The pool continues to crash even I have reinstalled VMware Tools and VMware Horizon.

Any other idea?

Reply
0 Kudos
iJohnny
Contributor
Contributor
Jump to solution

Hi Hussam, our vSphere version is 6.5

Reply
0 Kudos
HussamRabaya
VMware Employee
VMware Employee
Jump to solution

it seem it an issue from VM Monitoring settings 

disable the "VM Monitoring" option in VMware cluster.

iJohnny
Contributor
Contributor
Jump to solution

Hi everyone, i found the solution for this case.

The problem was that the Windows 10 version 1909 (October 19) is unstable to create pools.

For solve the problem, i returned to the 1803 version.