Solved: Re: 7.7 View desktops are deleted immediately afte...

gkamermans59 · ‎02-20-2019

I am new to VMWare View but not to VDI or ESXi and vCenter. I have a new environment, Horizon View 7.7, Composer , Connection Server and Replica Server. Connecting to vCenter 6.5.0.23000

I just tried to deploy my first test pool of desktops, selected pretty much all default settings for the pool, selected a fresh snapshot of my Windows 10 Gold image. When the pool is created everything looks fine for the first few minutes, then after provisioning, I see the VDI desktops being deleted from vCenter. View Administrator shows the following error for the vms:

"view composer fault exception:truncatedfault fault for vm: "

the viewevents database reports the following: (substituted domain\user for actual admin user)

"","Info","2/20/2019 10:59 AM","Connection Server","Automatic error recovery for Pool TestVDI: attempting recovery for Machine TestVDI-02","DESKTOP POOL:Test Win10 VDI MACHINE:TestVDI-02 "

"","Info","2/20/2019 10:59 AM","Connection Server","Automatic error recovery for Pool TestVDI: attempting recovery for Machine TestVDI-01","DESKTOP POOL:Test Win10 VDI MACHINE:TestVDI-01 "

"","Info","2/20/2019 10:59 AM","Connection Server","vCenter at address https://vcenter6app.domain.com:443/sdk has been enabled",

"","Error","2/20/2019 10:58 AM","Connection Server","View Composer Fault: ExceptionTruncatedFault for VM TestVDI-02",

"","Error","2/20/2019 10:58 AM","Connection Server","Provisioning error occurred for Machine TestVDI-02: Cloning failed for Machine","DESKTOP POOL:Test Win10 VDI MACHINE:TestVDI-02 "

"","Info","2/20/2019 10:58 AM","Connection Server","vCenter at address https://vcenter6app.domain.com:443/sdk has been temporarily disabled",

"","Error","2/20/2019 10:58 AM","Connection Server","Provisioning error occurred for Machine TestVDI-01: Cloning failed for Machine","DESKTOP POOL:Test Win10 VDI MACHINE:TestVDI-01 "

"","Error","2/20/2019 10:58 AM","Connection Server","Provisioning disabled for Pool testvdi","DESKTOP POOL:Test Win10 VDI "

"","Error","2/20/2019 10:58 AM","Connection Server","View Composer Fault: ExceptionTruncatedFault for VM TestVDI-01",

"domain\user","Audit success","2/20/2019 10:49 AM","Administrator Console","domainogies.com\user was entitled to Pool TestVDI by domain\user","DESKTOP POOL:Test Win10 VDI "

"domain\user","Audit success","2/20/2019 10:49 AM","Administrator Console","domain\user added Pool TestVDI","DESKTOP POOL:Test Win10 VDI "

"domain\user","Audit success","2/20/2019 10:49 AM","Administrator Console","Added deployment group 63be61a5-011f-4ebb-91b7-152ae76c3f0a for /V6 HFX Toll 441.15/vm/vdi-win10-dsktp-01 : snapshot-23205",

"domain\user","Audit success","2/20/2019 10:44 AM","View API","User domain\user has logged in to View Administrator",

"domain\user","Audit success","2/20/2019 10:44 AM","Administrator Console","domain\user has added database configuration",

"domain\user","Audit success","2/20/2019 10:44 AM","Administrator Console","domain\user has attempted to change event configuration",

I am left with two desktops in the pool, but no vms on the hosts.

The only alerts on the dashboard in View Admin refer to self signed certificates. for the connection and replica servers which I will install when testing is complete (unless this is a requirement to fix this issue)

Any advice is greatly appreciated.

gkamermans59 · ‎02-28-2019

Hey everyone, thanks very much for all the suggestions, I now know a lot more about View than I did a week ago.

I opened a ticket with VMWare and together we found that port 902 was blocked between the Composer subnet and the management subnet that the esxi hosts are on (unfortunately this was a different subnet than our vcenter is on, this is to be remedied soon). When this had step failed, the entire provisioning process rolled back, causing the desktop vm's to be deleted.

Once this port was opened, the disposable disks were able to be created.

I appreciate the suggestions. Thanks for all of your help.

Cheers

Greg

View solution in original post

sjesse · ‎02-20-2019

Something is failing when the new clones are being created, and once they fail they delete and try again. A few things to checl

1.)Does the user your using for the composer service have correct vcenter and ad permissions

2.)Are your vms getting ip addresses from a dhcp server, if they don't get ip addresses they can't talk to the connection servers to confirm they are setup

3.)Are there any firewalls between your desktops and the connections servers.

4.)Is the AD account the composer service using have correct permissions to create and delete objects.

These are the usual things that I've seen that cause something similar. Try running though any of the work arounds here as well

VMware Knowledge Base

gkamermans59 · ‎02-21-2019

Hi sjesse,

Thanks again for the fast response. I followed your advice, still stuck with the errors below.Please see the response to your original questions.

1.)Does the user your using for the composer service have correct vcenter and ad permissions

- yes, composer service has the correct vcenter permissions

2.)Are your vms getting ip addresses from a dhcp server, if they don't get ip addresses they can't talk to the connection servers to confirm they are setup

- Yes, there is a DHCP server scope configured for the VLAN the VMs connect to ,

3.)Are there any firewalls between your desktops and the connections servers.

- No, there is for the AD servers, that has been resolved

4.)Is the AD account the composer service using have correct permissions to create and delete objects.

- Yes, I've gone as far as to add the AD account to the domain admins group for testing. still getting an error.

Two items of note:

1. I haven't installed SSL certs on the Connection and Replica server yet

2. KMS is not set up in the environment yet.

Are these a requirement to deploy desktops? I was able to do so in a lab environment without issue earlier this week.

Here are the latest log entries on vCenter

Task Name,Target,Initiator,Queued For,Start Time,Completion Time,Server

Delete virtual machine,replica-20487ba3-16ba-4dc4-bc7f-348469c2ed27,domain\\svc-vmware-view,9 ms,21/02/2019 16:16:06,21/02/2019 16:16:06,vCenter6App.domain.com

Delete virtual machine,w10vdi-3,domain\\svc-vmware-view,8 ms,21/02/2019 16:16:05,21/02/2019 16:16:06,vCenter6App.domain.com

Delete virtual machine,w10vdi-2,domain\\svc-vmware-view,6 ms,21/02/2019 16:16:05,21/02/2019 16:16:05,vCenter6App.domain.com

Delete virtual machine,w10vdi-1,domain\\svc-vmware-view,6 ms,21/02/2019 16:16:05,21/02/2019 16:16:05,vCenter6App.domain.com

Delete file,PROD-MFT-LUN121,domain\\svc-vmware-view,6 ms,21/02/2019 16:16:05,21/02/2019 16:16:05,vCenter6App.domain.com

Delete file,PROD-MFT-LUN121,domain\\svc-vmware-view,7 ms,21/02/2019 16:16:05,21/02/2019 16:16:05,vCenter6App.domain.com

Delete file,PROD-MFT-LUN121,domain\\svc-vmware-view,6 ms,21/02/2019 16:16:04,21/02/2019 16:16:05,vCenter6App.domain.com

Delete file,PROD-MFT-LUN121,domain\\svc-vmware-view,9 ms,21/02/2019 16:16:04,21/02/2019 16:16:04,vCenter6App.domain.com

Reconfigure virtual machine,w10vdi-2,domain\\svc-vmware-view,7 ms,21/02/2019 16:14:35,21/02/2019 16:14:36,vCenter6App.domain.com

Reconfigure virtual machine,w10vdi-1,domain\\svc-vmware-view,3 ms,21/02/2019 16:14:35,21/02/2019 16:14:36,vCenter6App.domain.com

Reconfigure virtual machine,w10vdi-3,domain\\svc-vmware-view,3 ms,21/02/2019 16:14:35,21/02/2019 16:14:36,vCenter6App.domain.com

Add Tag,w10vdi-2,domain\\svc-vmware-view,3 ms,21/02/2019 16:14:35,21/02/2019 16:14:35,vCenter6App.domain.com

Add Tag,w10vdi-1,domain\\svc-vmware-view,6 ms,21/02/2019 16:14:35,21/02/2019 16:14:35,vCenter6App.domain.com

Add Tag,w10vdi-3,domain\\svc-vmware-view,5 ms,21/02/2019 16:14:34,21/02/2019 16:14:34,vCenter6App.domain.com

Clone virtual machine,replica-20487ba3-16ba-4dc4-bc7f-348469c2ed27,domain\\svc-vmware-view,14 ms,21/02/2019 16:14:32,21/02/2019 16:14:34,vCenter6App.domain.com

Clone virtual machine,replica-20487ba3-16ba-4dc4-bc7f-348469c2ed27,domain\\svc-vmware-view,4 ms,21/02/2019 16:14:32,21/02/2019 16:14:34,vCenter6App.domain.com

Add Tag,replica-20487ba3-16ba-4dc4-bc7f-348469c2ed27,domain\\svc-vmware-view,5 ms,21/02/2019 16:14:32,21/02/2019 16:14:32,vCenter6App.domain.com

Create virtual machine snapshot,replica-20487ba3-16ba-4dc4-bc7f-348469c2ed27,domain\\svc-vmware-view,6 ms,21/02/2019 16:14:31,21/02/2019 16:14:32,vCenter6App.domain.com

Configure virtual disk digest,vCenter6App.domain.com,domain\\svc-vmware-view,7 ms,21/02/2019 16:11:46,21/02/2019 16:14:31,vCenter6App.domain.com

Event Log from View Connection Server shows the following

"User","Severity","Time","Module","Message","Objects"

"","Error","2/21/2019 4:16 PM","Connection Server","View Composer Fault: ExceptionTruncatedFault for VM w10vdi-3",

"","Error","2/21/2019 4:16 PM","Connection Server","Provisioning error occurred for Machine w10vdi-3: Cloning failed for Machine","DESKTOP POOL:Windows 10 Desktop MACHINE:w10vdi-3 "

"","Error","2/21/2019 4:16 PM","Connection Server","Provisioning error occurred for Machine w10vdi-2: Cloning failed for Machine","DESKTOP POOL:Windows 10 Desktop MACHINE:w10vdi-2 "

"","Error","2/21/2019 4:16 PM","Connection Server","View Composer Fault: ExceptionTruncatedFault for VM w10vdi-2",

"","Error","2/21/2019 4:16 PM","Connection Server","Provisioning disabled for Pool win10vdi","DESKTOP POOL:Windows 10 Desktop "

"","Error","2/21/2019 4:16 PM","Connection Server","Provisioning error occurred for Machine w10vdi-1: Cloning failed for Machine","DESKTOP POOL:Windows 10 Desktop MACHINE:w10vdi-1 "

"","Error","2/21/2019 4:16 PM","Connection Server","View Composer Fault: ExceptionTruncatedFault for VM w10vdi-1",

RealQuiet · ‎02-21-2019

Check to see that you have the correct View Agent and options are installed. I recall running into an issue when I was doing upgrades of the View Agent and removed it but did not reinstall it in a timely manner. The View Composer thought the link-cloned system was bad, deleted it, and provisioned another one in its place.

If that is all good then it is possible that the domain join is failing. Check to see of the computer object is being created in the OU that you are joining system to. As you stated, you added the service account into the Domain Admins group... so if you are not seeing the computer object being created and deleted, then it may be that your VDIs are having issues with resolving the DC during the domain join. I ran into this issue when we had DNS issues, my work around was an ipconfig /renew on the systems before the domain join. While an ipconfig /renew may not be possible to script in this scenario, you can tweak your DHCP settings as needed (set the Primary DNS to a DC that you know you can join systems to and, if needed, confirm that you set the suffix search list).

JohnTwilley · ‎02-22-2019

I've seen this happen when you setup a "Post-synchronization script" on the pool, and the script fails for some reason. (like a bad path)

gkamermans59 · ‎02-22-2019

Hi RealQuiet,

Thanks for the assistance.

I recently removed and re-installed the agent on my Gold image vm to make sure I am running the same software release for all components. and created a new snapshot. Since I am using linked clones, are there any agent components that I should make sure to avoid?

I can see the VM's added to the OU specified in the pool setup, I extended the QuickPrep timeout to 200 seconds and can see that the VM's take longer to be deleted (about 3 minutes longer). They are then deleted from the OU so it looks like I have sufficient permissions in both vCenter and AD. I still get the ExceptionTruncatedFault and Cloning failed for Machine for each VM created in the Horizon Admin portal.

Any other thoughts?

gkamermans59 · ‎02-22-2019

Thanks John,

I am not running any Post-synchronization scripts. I have kept this is vanilla as possible.

sjesse · ‎02-22-2019

your best bet is to get in a customizing one from the vcenter console and go to

%system_drive%\Windows\Temp\VMware\vmware-viewcomposer-ga-new.log

This is the internal customization log. Its annoying since the vms will shut off on you, but try and see if you can get into the log before its shutoff. It should show any errors in the customization process before it shuts off

If not I'd open a ticket if you haven't

gkamermans59 · ‎02-22-2019

sjessee

You were right, it was a pain to get access to teh folder. I managed to copy all the files to the Composer server:

From vmware-viewcomposer-nga I have this

2019-02-22 11:02:38,880

2019-02-22 11:02:38,880 ----------------------------------

2019-02-22 11:02:38,880 svmNga run on 2/22/2019, 11:02

2019-02-22 11:02:38,880 ----------------------------------

2019-02-22 11:02:38,880 NTProcessStartup: About to call RtlCreateHeap

2019-02-22 11:02:38,880 NTProcessStartup: Done calling RtlCreateHeap

2019-02-22 11:02:39,005 SvmFindPersistentDisks: Drive map is 0x0000000C.

2019-02-22 11:02:39,005 Status: 0xC0000034 NtCreateFile(\??\C:\simvol.dat)

2019-02-22 11:02:39,005 SvmFindPersistentDisks - Could not find config volume.

2019-02-22 11:02:39,474 NtQueryValueKey Failed: 0xC0000034

2019-02-22 11:02:39,474 SvmRegQueryValueKeyA Failed 0xC0000034

2019-02-22 11:02:39,474 SvmApplyPolicy: Failed to find policy on persistent volumes. Status: 0xc0000182.

2019-02-22 11:02:39,474 SvmApplyPolicy: Done setting the clone's identity with error.

From vmware-viewcomposer-ga-new, for the same batch.....

2019-02-22 11:02:43,632 [1288] INFO CSvmGaService - ["svmGaService.cpp", 87] Initialized the Service

2019-02-22 11:02:43,639 [1288] INFO CustomizationPersistentInfoReg - ["CustomizationPersistentInfoReg.cpp", 98] Opened guest registry key for accessing customization info.

2019-02-22 11:02:43,671 [1288] DEBUG CSvmGaService - ["svmGaService.cpp", 323] In RunService

2019-02-22 11:02:43,677 [1288] INFO CSvmGaService - ["svmGaService.cpp", 295] No Policy or SVM disks found

2019-02-22 11:02:43,677 [1288] INFO CSvmGaService - ["svmGaService.cpp", 347] In the master VM

2019-02-22 11:02:43,687 [1288] INFO CSvmGaService - ["svmGaService.cpp", 411] Service is in state: 4

2019-02-22 11:02:43,687 [1288] DEBUG WaitableManagerWin32 - ["WaitableManagerWin32.cpp", 87] Updating callback for event SviServiceStopEvent (00000264)

2019-02-22 11:02:43,687 [1288] DEBUG WaitableManagerWin32 - ["WaitableManagerWin32.cpp", 90] adding callback for event SviServiceStopEvent (00000264)

2019-02-22 11:02:43,688 [1288] DEBUG WaitableManagerWin32 - ["WaitableManagerWin32.cpp", 179] Dispatching callback for event WaitableManagerInternal (0000025C)

2019-02-22 11:03:47,987 [1096] INFO CSvmGaService - ["svmGaService.cpp", 442] user logon.

That was when the file stopped.... the following was present for the previous batch after the User Logon entry

2019-02-22 10:27:59,644 [1372] INFO CSvmGaService - ["svmGaService.cpp", 448] user logoff.

2019-02-22 10:28:16,532 [1652] DEBUG WaitableManagerWin32 - ["WaitableManagerWin32.cpp", 179] Dispatching callback for event SviServiceStopEvent (00000264)

2019-02-22 10:28:16,532 [1652] INFO CSvmGaService - ["svmGaService.cpp", 391] CSvmGaService::RunService: Stop requested.

2019-02-22 10:28:16,532 [1652] INFO CSvmGaService - ["svmGaService.cpp", 482] Shutting down the service

2019-02-22 10:28:16,532 [1652] INFO CSvmGaService - ["svmGaService.cpp", 487] Stopped the SVM state machine

Any ideas?

sjesse · ‎02-22-2019

First question is this a clone of a linked clone to try and recreate the parent image? If so that causes all kinds of problems, you need a fresh volume

If not try disabling hotlug, its in this article, under optimize vm hardware.

Creating an Optimized Windows Image for a VMware Horizon Virtual Desktop | VMware

I'm basing this of all old kb that has at least one line of your error, the setting is in there latest guide for creating parent images so I'd try it.

VMware Knowledge Base

gkamermans59 · ‎02-27-2019

Sorry, its been a few days, I am back at this. I disabled the device.hotplug setting, I have tried a brand new image without antivirus, same issue. I continually get the following entries in the vmware-viewcomposer-nga.log file

2019-02-27 10:47:51,874 svmNga run on 2/27/2019, 10:47

2019-02-27 10:47:51,874 ----------------------------------

2019-02-27 10:47:51,874 NTProcessStartup: About to call RtlCreateHeap

2019-02-27 10:47:51,874 NTProcessStartup: Done calling RtlCreateHeap

2019-02-27 10:47:52,019 SvmFindPersistentDisks: Drive map is 0x0000000C.

2019-02-27 10:47:52,019 Status: 0xC0000034 NtCreateFile(\??\C:\simvol.dat)

2019-02-27 10:47:52,019 SvmFindPersistentDisks - Could not find config volume.

2019-02-27 10:47:52,988 NtQueryValueKey Failed: 0xC0000034

2019-02-27 10:47:52,988 SvmRegQueryValueKeyA Failed 0xC0000034

2019-02-27 10:47:52,988 SvmApplyPolicy: Failed to find policy on persistent volumes. Status: 0xc0000182.

2019-02-27 10:47:52,988 SvmApplyPolicy: Done setting the clone's identity with error.

I have looked to find a GPO policy that may be blocking but have not been able to. I have blocked inheritance on the OU the VDI desktops are created in. I have attached the log files from today along with an export of teh HKLM registry that I found in a support article VMware Knowledge Base.

Cheers

RealQuiet · ‎02-28-2019

For the View Agent, I believe the only options required are Core and VMware Horizon View Composer Agent. Per your usage, you may have other options enabled. When using View Composer Agent the Instant Clone Agent cannot be installed.

All

7.7 View desktops are deleted immediately after provisioning, why?