Linked Clones, Instant Clones keep coming back in deleting (missing) or Error (missing) state

 

Linked Clones, Instant Clones keep coming back in deleting (missing) or Error (missing) state

 

I were testing FsLogix for profile redirection. During the testing phase, I had to delete and recreate the desktop pools.  Since, I was initiating multiple tasks, some of the tasks got stuck, thus affecting the connection server operations.

After proper troubleshooting, I was able to figure out the machine didn’t exist in vCenter, however the affected machines were still present in ADAM database.

To resolve this database inconsistency, I performed the below mentioned steps and I was successfully able to remove the stale machines.

·         Remove the virtual machines from the ADAM Database on the connection server.

·         Remove all affected computer objects from Active Directory.

 

Removing the virtual machine from the ADAM database on the connection server

 

Important: Prior to starting these steps, using the View Administrator, disable provisioning on the pool from which you are deleting the machine.

 

Ø  Connect to the View ADAM database

Ø  Right-click the Connection View ADAM Database [localhost: 389], and click New > Query.

Ø  Provide a query name such as VM Search.

Ø  Under Root of Search, click Browse and select the Servers organizational unit.

Ø  Click OK.

In the Query String, paste this search string:

(&(objectClass=pae-VM)(pae-displayname=VirtualMachineName))

Where VirtualMachineName is the name of the virtual machine for which you are trying to locate the GUID.
 

Ø  Click OK to create the query.

Ø  Click the query in the left pane. The virtual machines that match the search are displayed in the right pane.

Check the properties of the items returned by the query to confirm the correct virtual machine(s) were found, and delete the pae-VM object(s) to remove them from the database.

 

 

Removing the virtual machine from Active Directory

To remove the virtual machine from Active Directory:

1. Log in to the Domain Controller as Administrator.
2. Navigate to Start > Administrative Tools > Active Directory Users and Computers.
3. Remove the virtual machine from Computers.

 

FIXING VMWARE HORIZON ADMIN CONSOLE ERROR FOR GOOGLE CHROME

 

FIXING VMWARE HORIZON ADMIN CONSOLE  ERROR FOR GOOGLE CHROME 

 

Support for Adobe Flash will end at the end of 2020. The good news is that most sites have stopped needing it. For those that do, there's really no alternative. Adobe Flash player is going away at the end of 2020

 

As soon as I read about it, I didn’t feel any good. Very colorful and very much evident, I really liked the flex admin console for VMware Horizon. But when the support for flash ended, everything changed. Now, I have an admin console which was not colorful and to add to my misery, the UI/UX was too distorted. Anything would appear anywhere for no reason at all. I had started becoming pissed off and I would have totally avoided logging into the console, only if I had a choice.

The next thing I did was, I installed Google Chrome on my system. I was hopeful that it might work fine with Chrome. Well, it didn’t. It didn’t work at all.

I have been into EUC for almost 3 years now and VMware has my complete faith. With this faith in my heart and utmost curiosity in my mind, I simply did what I was supposed to do, I googled about it. Actually, I have more faith in google, I guess.

I figured out that the issue is a very common issue and there’s also a KB article from VMware related to this error.

 

Below mentioned is the link to the KB article from VMware

https://kb.vmware.com/s/article/2144768

 

How I resolved it?

 

1.    Login to Connection Server.

2.    Create a text file named locked.properties in C:\Program Files\VMware\VMware View\Server\sslgateway\con or if locked.properties  already exists, Open the  file using a plain text editor.

3.       Add this line:

checkOrigin=false

Note: Ensure the locked.properties file is not in .txt extension after saving

 

4.    Save and close the file.

5.    Restart the VMware Horizon View Connection Server service.

 

Cause:

This behavior is observed with new security feature included in Horizon 7. The View Administration page in Horizon 7 checks the origin URL for the web request, and rejects the request if the URL is not https://localhost/admin or https://URL_used_in_Secure_Tunnel_URL_Field/admin.

Note, Several scenarios within an environment - loadbalancer, VPN's  configuration etc can trigger this feature.