Back in July we had published a Support Insider blog post about using the ViewDbChk command to remove invalid linked clone entries, which applied to Horizon View 5.3 and later. Apparently a similar situation can arise in earlier versions of the product as well, but the steps to fix it are different.
For users of View 5.2 or earlier, we have created KB article: Manually deleting linked clones or stale virtual desktop entries from the View Composer database in ....
(view original post)
