Bloating of snapshot using linked clones

Similar Questions

• Using Linked clones with a data disc?

  We expect on the creation of our BASE image with a 50 GB C:\ drive.  For the moment, we will not use Thinapp, so the few apps we need for our people call center will be installed on the base image. We also plan to use the profile unit of Liquidware Labs and will use linked Clones.  My question is, do I have to create a data disc (D:\) to install Apps or just expand the C:\ drive?

  If the user data (documents, computers of desktop, thems and local profiles) will store locally and needed to preserve for the future and use the redirection of the user's data and set separate drive for this.

  In the case where the user data is Vagabond (stored and shared in the Center), then do not use that feature, simply create a bigger drive C.

• linked clone / use of disk space

  However, I am pretty new to LM.

  I was informed that a linked clone would take about 64 MB of disk space per box. I clone a bunch of fees Windosw 2003 OS just to test this linked clone ability out.

  The boxes are 27 GB of space to use before the cloning and 9.79 GB after cloning. This is still an economy but is not considerable 64 MB.

  Can someone give me some real estimates what to expect in terms of disk space using linked clones without and the changes made to the original system.

  Our main reason for the evaluation of the LM was to take advantage of the clones related as one of our servers that clone us is 500 GB in our environments so SAN space gets quickly chewed with each environment.

  I'm curious to know what others are recording using a linked clone.

  Cheers.

  Do not run a clone that is related to your model.

  Create a configuration and add machines based on your model for this configuration.

• Linked Clones remain the 'customisation' stage (composer)

  Hello

  I am trying to Setup automated pools view 4.5. It is my first use of pool automated using linked clones. The work of fine manual pools. When I create the pool all seems good. The replica is created and the clones follow shortly after. They then appear in the admin view in the inventory menu / Desktop, but they have a version of the 'unknown' agent and a status of "customization." They have been at this stage, for about 45 minutes, without change.

  When I look at them in vCenter I see that they are turned on and running, but looking at the Summary tab shows that they are still using the host name of the VM parent, so I guess that the sysprep process command has not yet been executed. They picked up a DHCP ip address correctly, and VMware Tools is running. I tried to manually restart one of the clones to see if it was a blocked process, but she comes back with the same status. The guest OS is Win7. To check the vCenter customization, I deployed a VM from the same model that the parent VM and using the same saved vCenter customization and it works very well, change the host name and join the domain correctly.

  Any suggestion would be appreciated!

  TIA,

  Jules.

  What is the customization you have selected during the creation of pool (Sysprep/QuckPrep)?

  Please not that regardless of the linked clone type (syspre/quickprep) customization will try to join to the domain that you chose in the Create Pool Wizard and * NOT * to that specified in the selected custom VC specification. That is why the domain account that is set up (the server vcenter - Configuration of the server administrator display page properties) should be correct, and the DNS server to resolve this area.

  So make sure you:

  1. the parameters for each client and DNS domain connectivity

  2 Appropritae account domain and ORGANIZATIONAL unit selected in the Create Pool Wizard

  3. the added domain account has enough permissions (see the admin Guide)

  If above settings are proper, then,

  4. check that the ' connect to power on "is enabled for the virtual Parent card computer and consists of the snapshot as the network settings (return tot eh snapshot and check network settings)

• Windows 7 in a pool of office automated with linked clones?

  Hello

  It is possible to set up an office pool automated with Windows 7 clients does not use linked clones? I try, but I have not presented the snapshot of the Windows 7 machine... (I know that it is only the technical preview)

  Thank you, George.

  Because we create and use x 64 VMs of in vCenter/ESX, you expect everything to work independently of the architecture.  Now, I didn't pretend to have a deep understanding of the functioning of view Agent and composer here.  However, since they are the two required components of cloning and or support x 64 OSes, I guess there is some sort of incompatbility.

  I know that I did not give a concrete answer as to why it doesn't work (and I couldn't I a), but I'll throw a few others obvservations I did.  I have already mentioned that the view Agent USB driver does not work on x 64.  When the associated test clones on x 64 OSes, I noticed that I could not select one of the x 64 workstations with snapshots.  Out of curiosity, I created an empty VM Windows XP Professional x 32 (with no OS) and took a snapshot.  I then went through the steps to created an automated pool and was able to pick up the snapshot for the x 32 empty VM XP.  He told me that he has no control on the real operating system for clones related through composer.  They must be carried out an audit on the guest "OS" said when you create the virtual machine and only allow x 32 VMs to serve as parents for the related clones.  I don't know if there is a difference at the level of the virtual material in x 32 vs x 64 XP XP, but it may be useful to create a "Windows XP Professional (32 bit)" VM and install XP (or Win 7) x 64 just to see what happens.

  If I have the chance to test this, I'll post.  I'd be interested to hear what everyone said, because I'm very interested in getting x 64 support as well.

• View office patches and linked Clone pool

  I'm mobile torwards a deployment of Thin Clients using the Wyse P20 and View 4 and I was wondering if anyone has had experience using the linked clone and Altiris Agent Office pool?  If this is not the case, what practices of patching are used?

  What practices of patching are used?

  If you use linked clone you way the main image, not the desktop images.

  Power on the mask, path, clipping, create a new snapshot.

  Then (with View Manager Administration) redial your pool with the new snapshot.

  André

• Fusion 6 Linked Clones - not a spectacular featured :(

  I was happy to finally have the opportunity to work with clones related to the merger 6.

  However, now that its here... I find this feature useful.

  It is easy to build a linked clone.   But... I need to be able to add additional disks to the linked clone.  It is not possible.

  

  I was hoping to create a single image master 'gold' a Windows 2012 R2 server.
  Then quickly deploy a number any of servers by using linked clones.

  Some of my guests require additional disks to support other applications.

  Unfortunately... related clones do not allow adding additional disks.   Why this limitation is imposed?

  To work around this limitation.

  https://communities.VMware.com/message/2286998#2286998

• How to change the computer name of existing desktop computers linked clone pool?

  Hello

  I'm curious about something that has developed in our Organization.  New guidelines came down and we have to change the name of the computer for all of our offices to meet the new criteria.

  I have many of our users is on the offices of Linked-Clone (automated pool, dedicated, assignment see 5.1) which will have their names have been changed.  I use a 'model' for the name of the computer.

  I tried this before by simply change the settings of the pool, and then recompose the pool.  Recompose worked well, but NONE of the virtual machine names have been changed.  All machines, recomposed just fine, but keep the old name of the computer (non-compliant).

  How can I change the name of the computer of my clone in an existing pool offices?  Maybe I have something wrong.  I'm doing it instead of having to create a new pool and move the persistent disks.  I would like to change the name in the settings of the pool and recompose, but it did not work.

  Scenario:
  See 5.1

  Automated cloning related pool

  Assignment of dedicated (persistent disks)

  Thanks in advance

  It is not possible to change the name of existing workstations by modifying the settings of the pool. There is no way to make this happen automatically and in doing so manually would not seen happy.

  Unfortunately, for dedicated pools, you will have more work to do. If you do not use Persona you detach the persistent disks and recreate virtual machines in the pool with this disk to create a new virtual machine with a new name to be generated.

  If you use Persona you could remove all virtual machines and have Persona to extract profile data down to the virtual machine that would be entitled to the user when they connect then. This will cause all user installed programs go, but I hope that's not common if you are already using linked clones.

  I encourage to go to the next page, click on the feature request form link and publish information on what you're trying to do:

  https://www.VMware.com/support/policies/feature.html

  Notifications about features are reviewed by VMware and if you can get enough of your friends/colleagues notice to users to ask something often a solution will grow in any kind, nature or form.

  Hope this helps.

  -Mike

• Graphical support for linked clones

  I would use linked clones in order to improve the commissioning of virtual servers that share large amounts of common data. I have the budget for upgrading vSphere and/or purchase additional software, and I tried to ask the VMware sales people to get advice on what products would allow management of related clones. The saleswoman, I spoke with possibly suggested vCenter Server v5. My company already uses v4, and I see nothing in it for me to create a linked clone. Maybe it's a new feature in v5, but it is not mentioned in the list of the new features. I think that the seller was probably misinformed about this possibility.

  Does anyone have experience create clones related with a graphical management interface? If so, what is the combination of products VMware would be optimal to allow clones related to a small environment (e.g. 2 physical hosts)?

  If you want to use linked clones, right now your options are to use vCloud Director or VMware View.  There is no support of base level for the creation of a clone that is bound in the GUI (just support of the API for it).

• View 5 POC, Windows 7 Enterprise, linked Clones and VMXNET3

  I spin a CEP for Views5 and experiencing major issues with the VMXNET3 device when configuring desktop using linked Clones. About half of the configured computers have errors NIC with the fact that he is unable to see the network.

  Has anyone else had similar problems?

  Apply the fix mentioned in: http://pubs.vmware.com/view-50/topic/com.vmware.ICbase/PDF/view-50-administration.pdf

  This will fix the problem as it did for me.

  Read also: http://www.vmware.com/files/pdf/VMware-View-OptimizationGuideWindows7-EN.pdf

• Automatic creation of pools (linked Clone) using powerCLI

  Hello

  I am using powerCLI to create automatic pool (linked clone). I came across the following cmdlet in theVMware powershell integration white paper:

  Get-ViewVC - serverName < IP/domain FULL name >. Add-AutomaticLinkedClonePool-pool_id

  TestAutomaticLinkedClonePool - namePrefix pad - parentVMPath / < Center > < parentVM > /vm/

  -parentSnapshotPath / < cliché - > vmFolderPath / < Center > /vm - resourcePoolPath

  / /host/ < Center > < ESX > / resources - dataStoreSpecs / < Center > /host/ < ESX > / < datastore >

  -composer_ad_id < id ad composer >

  Now, I want to help discover (with an example will be very useful) how you specify and how find you each of the following (as what do I put after each other):

  -parentVMPath

  -parentSnapshotPath

  -vmFolderPath

  -resourcePoolPath

  -dataStoreSpecs

  -composer_ad_id

  Please give an example of each if possible.

  Thank you!

  OK, I'll give it a try.

  The parentVMPath parameter expects the path to the virtual machine that you want to spawn the pool (obviously).

  Such a path looks like this: / MyDC/vm/MyVM

  Where MyDC is the datacentername, the vm folder is hidden folder that contains the hierarchy of models and virtual computers, and finally the name of the virtual machine itself.

  If your master VM is deeper in the structure of folders, just add the folders in the path.

  Ex: / MyDC/vm/Folder1/Folder2/MyVM

  The parentSnapshotPath is similar to the previous setting, but obviously needs to point to the snapshot pool should clone.

  Alan has a nice feature to recover the snapshotpath Updateand re-view pools calm.

  The vmFolderPath is where the virtual machines that are created for the pool to be stored.

  Similar to the previous settings, but now for the record once again.

  Ex: / MyDC/vm/PoolFolder

  resourcePoolPath must point to a resourcepool.

  Such a path will look something like this: / MyDC/host/MyCluster/Resources/MyResourcePool

  Note that host and resources are again hidden folders!

  datastoreSpecs: this is not the most obvious.

  He wants the full path to a data store in a cluster that is specified by a resource pool.

  See the function VVGetDatastorePath to determine the paths to vSphere Datastore objects

  The composer_ad_id wants that the ID of the AD domain, in which the composer is a member server.

  You can get this through to: ComposerDomain-Get | select composer_ad_id

  
  

  As side note, take a look at the Integration of PowerShell with view 5.0 white paper. Perhaps, it is not intended for the latest version of the view

  but he explains some settings a lot better than I could

• Linked Clones and snapshots - which can be removed and when?

  Hello

  Sorry if this is a stupid question. I'm new to the linked clones.

  I was able to create clones related win2k8r2 invited.  Everything seems to work ok.  However, once a linked clone is created, is it still necessary to keep the parent snapshot?  That is to say, snapshot of the parent is necessary after related cloning?

  My env:

  VMware ESXi 4.1.0 build-433742

  VMware vSphere PowerCLI 4.1 build 332441 U1

  Thank you

  T

  It must be remembered that a clone is based on the parent machine and a snapshot that you see in the server view.  Multiple snapshots can be consolidated or "rolled up", but depends on the clone.  The parent can put off when the do not need to save on resources in your environment, because that's what the replica is for.  I do not agree with Andre and suggest that you keep the snapshot that you clones are configured to use, with the exception on the consolidation of old clichés.

• Linked clone failed: the operation is not supported on the object

  Hi all - I would appreciate help on a related clone operation that is a failure.

  I use Quest vWorkspace to create linked clone VM in my environment.  It integrates with virtual Center and creates from a VM snapshot parent according to normal related clones.  It has just stopped working and I am trying to track down the cause.  The task fails with the error message in the console of VMware vCenter: the operation is not supported on the object.

  The vCentre is 5.5 and esxi.  vWorkspace is v8.0 MR1.  The parent VM is located on an iSCSI datastore.  I tried to put the clones of destination on premises and warehouses of NFS data with the same result.  Unfortunately I can't (don't want really to) move the VM parent from the data store that I have of many VM related to this virtual machine.

  The failure message is a bit generic, so I looked on through the vmkernel.log and vpxa.log and it is an excerpt from the vpxa.log whereby it shows failed task 153.  Can someone please indicate something in the newspaper that had to be examined or another newspaper to look at?

  vWorkspace attached error and below:

  Linked clone has not CreateLinkedClone_Task of CloneVmLinked failed! Task of VMware CreateLinkedClone_Task status error - the operation is not supported on the object. -Call stacks-VmLinkedClone.VmLinkedCloneService.CloneVmLinked String vmInvPath, String strSnapshotMor, String strNewVmName, String strSysprep, ManagedObjectReference morFolder, ManagedObjectReference morResPool, ManagedObjectReference morHost, String strDatastoreName, Boolean bQuickPrep, String domainNameIP, String

  See attachments

  Thank you very much
  Wikus

  Additional accessories:

  • 
    Untitled picture.png

  Hello guys,.

  For those of you already on 5.5, I did a few tests these days. I did find a magic bullet yet as a single parameter that is sure to break but I came up with a workaround.

  I found that if my ESXi server was still on the 5.1, vWorkspace could deploy clones linked via vCenter 5.5 - it's only when the ESXi is also on 5.5 that you have a problem.

  If any of you have ESXi hosts still on 5.1, you can deploy there for now.

  In ESXi 5.x, it is easy to have an ESXi virtual machine. You might want to consider creating some virtual boxes ESXi to deploy on while the vworkspace dev team look at why it does not work.

  I know that this is not the best solution in the world, but it's better than no work around

  Thank you, Andrew.

• VMware Linked Clones in vWorkspace

  Hi all

  I am currently working on a proposal where client insist on the use of the VMware hypervisor as the note of calculation. I have some research in the related Clones and basically its similar to what the differencing disk VHD got to offer. My main concern here is so we can use the technology VMware Linked Clones to deploy persistent desktop or is it only for non-persistent desktop mode? How about storage if economies compared to the disk hard virtual differencing disk? What is the estimate of the use of the delta of a typical user based on your experience? Thanks for the advice!

  Kind regards

  Cyril

  Hi Cyril,.

  I can answer some of your questions.

  You can use a clone bound like a persistent desktop computer, it does not work.

  After a while, however, the linked Clone will be so different from the image of the mother, it will become very swollen (for example, updates of Windows to go it would be applied to each clone bound, user installed Apps, etc.)

  I know some customers like to capture profiles on persistent desktop computers so that they can periodically update the image of the mother and redeploy related clones from there. It works well to keep the machine day and bloating under control. The obvious drawback being any user installed apps would disappear, but it all depends on if you allow them this level of customization.

  Thank you, Andrew.

• Cannot expand the hard drive of a virtual computer that is a linked clone.

  I have a virtual machine that is a linked another clone.

  I did a lot of development and changes to the linked clone, and now ran out of disk space.

  Now I want to extend the drive, but I get this error:

  "Disks of virtual machines that are linked clones cannot be extended.

  So I then try to extend the drive of the virtual machine that he was cloned from:

  "Disks of VMS with snapshots cannot be extended. You must delete the snapshots or use VMWare vcenter converter. »

  What can I do? If I remove the snapshots of the original machine, do not lose the 'link' to the linked clone? What he suggested that I use the "VMWare vcenter converter" for?

  Does anyone have a solution?

  Kind regards

  James

  Create a complete clone of the virtual machine in the current state. Which can be extended.