srinivasaddagat
Contributor
Contributor

linked clones boot using Parent VM image after Refresh

I am not sure if its expected but a Image Refresh of the Linked clones in Automated Persistent Pool booted with the name of the Parent VM thus conflicting in the network. We could deploy 2 linked clone from the Parent VM and with the option of "both OS and User data in the same disk" and was trying to see what exactly Refresh Operation does and surprised to see it booting with the name of the Parent VM. This is as good as do a clone of the exiting VM an then boot the clone which actually takes the name of the VM its cloned from. Did anyone notice the issue?

Also it seems "Allow multiple sessions per user" is not available with persistent pools, expected? I remember it was there with VDM 2.1 but surprisingly removed in latest version.

Thanks

0 Kudos
11 Replies
admin
Immortal
Immortal

Have you done a ipconfig /release before taking the snapshot?

Blog: http://communities.vmware.com/blogs/dommermuth

0 Kudos
srinivasaddagat
Contributor
Contributor

Yes, i did it and then took the snapshot of the Parent VM when its down.

0 Kudos
admin
Immortal
Immortal

Does the View Composer create the computer accounts in the AD?

Is the network correct configured for the virtual machines?

Blog: http://communities.vmware.com/blogs/dommermuth

0 Kudos
srinivasaddagat
Contributor
Contributor

This is how it goes. I could configure "Automated Persistent Pool with Linked clones" and it creates the clones in VC, creates account in AD and i could use them for a while through View client from other PC. To test how Refresh works, i did edit image -> Refresh and selected to refresh all workstations and saw that VMs were shutdown in VC. I waited for more than 30 mnts and then tried to connect to the pool using View Client and saw VC powering on the first VM in the pool and surprisingly it had name of my Parent VM. Due to pool configuration, another VM got powered on and reported duplicate name exists on the network because its also trying to boot using Parent VM name.

0 Kudos
srinivasaddagat
Contributor
Contributor

Hi,

Any clues about this issue?

We have different issue for Automated Persistent Desktop Pool with separate user data disk that machines will be lost trust with the domain after refresh?

Thanks

0 Kudos
admin
Immortal
Immortal

I haven't heard that before. Take a look into the composer logfile. You'll find it on the vCenter/View Composer server C:\program files\vmware\View Composer\logs






Blog: http://communities.vmware.com/blogs/dommermuth

0 Kudos
srinivasaddagat
Contributor
Contributor

Sure, i missed checking view composer logs and was looking at only connection server logs. Thanks for the hint, let me know check what view compose logs say for this error

0 Kudos
srinivasaddagat
Contributor
Contributor

Turns out to be an AD related issue but not sure why. The account i am using with view composer actually has full control on computers container as well as on the computer object that i am refreshing but it says can't find the object on the server. It fails while creating the account, which i guess is obvious as the account already exists. It looks a bit strange.

================================

2009-03-23 21:51:32,753 | 25 | INFO | Sim.ServiceCore.SimServiceApiVal - Call GetVersion.

2009-03-23 21:51:33,268 | 25 | INFO | Sim.ServiceCore.SimServiceApiImpl - ResyncSviClones called for deployment group 3c407dc3-ba9f-4095-a8c7-a7f05be28f6e, for 1 clones, with resync spec replication datastore MoID = , force resync = True. CloneIds: dc3c2ae6-f3d6-4c4e-b106-fa51d8285760.

2009-03-23 21:51:33,268 | 25 | INFO | Sim.ServiceCore.SimServiceApiImpl - Received a request to create 1 clones for deployment group 3c407dc3-ba9f-4095-a8c7-a7f05be28f6e. Filed as request id d70e3580-d98d-4a39-b25b-324d94cb44c5

2009-03-23 21:51:33,268 | 25 | INFO | ServiceCore.LockManager.LockManager - A lock is requested for DeploymentGroup with id: 3c407dc3-ba9f-4095-a8c7-a7f05be28f6e

2009-03-23 21:51:33,268 | 25 | INFO | ServiceCore.LockManager.LockManager - Multiple lock are required for SimClone with ids:

2009-03-23 21:51:34,174 | 25 | INFO | ServiceCore.Action.UfaInitializeDiskAction - Created an UfaInitializeDiskAction with total disks 1.

2009-03-23 21:51:34,737 | 25 | INFO | Sim.ServiceCore.SimServiceApiImpl - Received a request to resync 1 clones for deployment group 3c407dc3-ba9f-4095-a8c7-a7f05be28f6e. Filed as request id d70e3580-d98d-4a39-b25b-324d94cb44c5

2009-03-23 21:51:35,190 | WFE thread 5 | INFO | ServiceCore.WorkflowEngine.SingleCloneTask - Task 061b50f2-01a4-4142-b4a5-a407df736f28 is set with non-cancellable.

2009-03-23 21:51:49,956 | WFE thread 7 | INFO | ServiceCore.ActiveDirectory.AdUtil - Attempting to add a computer account using DC 1 of 1

2009-03-23 21:51:49,956 | WFE thread 7 | FATAL | ServiceCore.Action.AddToAdDomainAction - Error: fail to execute AddToAdDomainAction,guest:hydtestvd_lc13, AD config Id:cdfa9585-bb64-48e4-a619-67ba1188d2e9. AD FQDN: foo.com

VMware.Sim.CommonLib.Exception.SimAdsException: Error in adding machine to domain. COM error code -2147016656 AdConfigId=cdfa9585-bb64-48e4-a619-67ba1188d2e9, Fqdn=deshaw.com ---> System.DirectoryServices.DirectoryServicesCOMException (0x80072030): There is no such object on the server. (Exception from HRESULT: 0x80072030)

at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName)

at VMware.Sim.ServiceCore.ActiveDirectory.AdUtil.TryAddAccount(DirectoryEntry containerEntry, String name, String password, String fqdn, String description)

at VMware.Sim.ServiceCore.ActiveDirectory.AdUtil.AddAccount(AdConfigEntryDo adConfigDo, String containerDn, String name, String password, String description)

--- End of inner exception stack trace ---

at VMware.Sim.ServiceCore.ActiveDirectory.AdUtil.AddAccount(AdConfigEntryDo adConfigDo, String containerDn, String name, String password, String description)

at VMware.Sim.ServiceCore.Action.AddToAdDomainAction.Execute(ActionInParam actionParams), Machine Name: VCHYD1, Timestamp: 3/23/2009 4:21:49 PM, App Domain Name: SviWebService.exe, Thread Identity: , Windows Identity: foo\vmadmin, OS Version: Microsoft Windows NT 5.2.3790 Service Pack 2, Reason: AdsComError, AdConfigId: cdfa9585-bb64-48e4-a619-67ba1188d2e9, ContainerDN: CN=Computers, Fqdn: foo.com

2009-03-23 21:51:49,956 | WFE thread 4 | INFO | ServiceCore.WorkflowEngine.ResyncSingleCloneTask - Action VMware.Sim.ServiceCore.Action.AddToAdDomainAction failed. Task 061b50f2-01a4-4142-b4a5-a407df736f28 finished in Failed state.

2009-03-23 21:51:50,472 | WFE thread 3 | INFO | ServiceCore.LockManager.LockManager - Multiple releases are reuiqred for SimClone with ids:

2009-03-23 21:51:50,472 | WFE thread 3 | INFO | ServiceCore.LockManager.LockManager - A release is requested for DeploymentGroup with id: 3c407dc3-ba9f-4095-a8c7-a7f05be28f6e

0 Kudos
admin
Immortal
Immortal

It seems that the computer account was not created in the domain! Is that right?

2009-03-23 21:51:49,956 | WFE thread 7 | FATAL |

ServiceCore.Action.AddToAdDomainAction - Error: fail to execute

AddToAdDomainAction,guest:hydtestvd_lc13, AD config

Id:cdfa9585-bb64-48e4-a619-67ba1188d2e9. AD FQDN: foo.com

VMware.Sim.CommonLib.Exception.SimAdsException: Error in adding machine

to domain. COM error code -2147016656 AdConfigId=cdfa9585-bb64-48e4-

Regards,

Christoph

Don't forget to award the points if this answer was helpful for you.

Blog:

http://communities.vmware.com/blogs/dommermuth |

0 Kudos
admin
Immortal
Immortal

Did you install the View Agent in the Parent VM?

Regards,

Christoph

Don't forget to award the points if this answer was helpful for you.

Blog:

http://communities.vmware.com/blogs/dommermuth |

0 Kudos
srinivasaddagat
Contributor
Contributor

Hi,

>It seems that the computer account was not created in the domain! Is that right?

I mean the computer account can't be created because the old account already exists. Should it delete and recreate the AD account when we do a refresh?

>Did you install the View Agent in the Parent VM?

Yes, View Agent is installed on Parent which includes composer agent in it. BTW, i tried this using a domain admin account as well but no luck Smiley Sad

I noticed another strange issue with View Client that i can't access any client's $ share. i.e. if i go to start -> run and give it asks for authentication which is expected but doesn't display anything after it but if i do
<computer1> it opens the shares available on it. Now if i go to console of the VM in VI-client or take a direct RDP of computer1 it shows that folder opened on it and when i come back to View Client its then visible. This looks a bit strange and happens for any user using View client in our domain. I am suspecting it to be related to our environment but not sure if its wide spread.

0 Kudos