- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We have an issue when users log off their VDI, the machine will have the message" Instant Clone agent initialization state error (6) unknown failure".
We deployed a dedicated instant clone pool, the user can login at the first time, but if the user choose logoff, the machine will start to auto-refresh. After it, the issue will happen, can't repair via restart or recover the machine.
I would like to ask if anyone can provide help to resolve the issue.
Many thanks
Horizon agent version: 7.13
App volume agent: 4.6.6
Windows Pool version: Windows 10 22h1 and Windows 7 Enterprise SP1 (Already installed all patches)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Anyone could provide help?
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Having same issue, ever get this fixed?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm getting this same error too. Testing Instant Clones now on Horizon 7.13.2, App Volumes 2203. The machines will provision successfully, but sometimes after a user logs off, it throws this same error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Because of issue with cp-replica or compose not properly in desktop pool or might be storage issue.
Remove Error machine:
When we got type of error ,1. try to delete error machine from VC(delete from Disk). 2. try to delete error machines from ADAM database (from connection server).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have found the issue and resolved the problem.
I would like to share it, domain controller caused my issue. There are multi-domain controllers and sites in the environment. Few domain controllers have problems which caused the issue. I did a configuration to make the VDI link a healthy Domain Site to resolve the problem.
- Tags:
- domain controller caused my issue. There are multi-domain controllers and sites in the environment. Few domain controllers have problems which caused the issue. I did a configuration to make the VDI link a healthy Domain Site to resolve the problem.
- I have found the issue and resolved the problem. I would like to share it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What configuration changes did you make exactly?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In connection server, edit the vdi to connect specific domain controllers via ADSI Edit.
In Domain controller, configurated the VDI IP range subnet to use a specific Domain Controller Group Sites.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
we have the same issue since 2 days. Could it be that this is a global issue from the Domain Controllers (e.g. last MS Patches)?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Not sure, you could check a VDM log in the Virtual Desktop, and you will get more information.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The best part of all of this is that VMware claims that Instant Clones are the better product than the older linked clones.
So far I am not convinced.
This stuff is a nightmare.