We are having the same issue here, have you found a solution to the issue? I am also trying to disable Windows Defender services on my golden image as we speak to see if it helps.
Device Guard is now part of Windows Defender. Device Guard is currently not supported on vSphere or Horizon (it is in the roadmap). Did removing it from the golden image help?
I have tried as you suggested to disable various Device Guard options in the local Group Policies but to no avail. Here is the message I get in the View Admin Console.
Oct 19, 2017 3:53:15 PM EDT: View Composer agent initialization state error (6): Unknown failure (waited 0 seconds)
Attempted theft by:
@angelage1 : Are you faced with this exact same issue?
I don't think you can remove device guard without group policy. My deployment just hangs at the customizing stage, and won't proceed.
I'm the on the product management team for Horizon 7. My engineering team is currently going through the qualification of Horizon 7.3.1 with 1709, they have not encountered this issue yet, but I wanted to make them aware.
FYI : We are running VMware View 7.3.1 with Windows 10 1709 VMs on VMware ESXi, 6.5.0, 6765664
Hello. We also have this problem. Provisioning a VM with windows 10 1709 fails during customization with Unknown failure (waited 0 seconds).
We are running VMware View 7.2.0 build-5735293 with Windows 10 1709 VMs on VMware ESXi, 6.5.0, 5969303
We also have this problem.
We are running VMware View 6.2 with Windows 10 1709 VMs on VMware ESXi 6
We're running 7.0.3 Horizon and it doesn't work.
Same with us "Provisioning a VM with windows 10 1709 fails during customization with Unknown failure (waited 0 seconds)"
We running Horizon View 7.3.1 and ESX 6.5 U1.
I did some testing. Adding the same Desktop in a MANUAL POOL does work fine. So the biggest issue is really the Linked Pool deployment which seems to fail under any Horizon View / ESXi combination with Windows 10 1709.
Has anyone found any additional info?
4 people found this helpful
We are currently using View 6.2.2 and are having the same issue with receiving this error:
View Composer agent initialization state error (6): Unknown failure.
The linked-clones are being created.
AD objects are being created.
They have IP Addresses.
They are being renamed correctly.
We are using QuickPrep.
They are registered in DHCP but don't seem to be in DNS, possibly?
Issues we have seen:
They are not being joined to the domain.
We have tried:
Disabling all the firewalls.
Reinstalling VMware tools and agent.
I was able to manually Sysprep a clone without error.
This occurred on a pool that was 1703 and we ran the upgrade on the parent.
This occurred on a new pool created from the ISO and then customized.
That's pretty much where I am as well.
Same here. View 6.2.3 with Windows 10 1709
Add machine to domain manual works but Quickprep by view composer gives View Composer agent initialization failed error