Deleted manually linked clone VM, recreated but composer skipped numbers

I did a rebalancing huge after the addition of new data warehouses and everything is fine... until the last few VM, it appears the account display uses to communicate with the database of the composer and vCenter Server has been locked (another story) so several virtual machines have been rebalanced partially who they are inactive and could not remove them via the display connection Server Admin console.

I removed the ADAM ADSI Edit Database virtual machine and removed the remains of the database of the composer (manual method).  I removed the virtual of Active Directory machine and vcenter Server using the vSphere Client and navigating data warehouses when necessary.

When I re-activated the available pool, all virtual machines have been recreated, but a VM number has been omitted.  The pool is Win7VM 60 but VM7 is not re-created, it made a VM61 to reach the minimum of 60.

How can I force VM7 do?  We are required to list all computer names in a security profile and a gap in the numbering will be a pain in the thigh.  Not to mention my OCD will make me crazy!

I posted a reply until I had carefully read your entire post. I think that the key is the part where you say that "delete you VM from Active Directory and vcenter Server using the vSphere Client and navigating data warehouses when necessary." While ADAM and composer databases had no remains of virtual machines has left in them, it is possible that there are always some piece of VM7 left in the database of vCenter which is originally composer to consider as already here. I'm not DBA SQL, so I'm not going to pretend to give instructions on how to fix this, but if you have someone with the right knowledge and skills (or if you are such a person) you will be able to flush out the offending record and return VM7 again. It's a place to start anyway. I hope this helps.

Dave

Tags: VMware

Similar Questions

  • Cannot delete the linked clone pool

    Hello

    Please bear with me, as I'm still not a lot of experience with this product. I can't remove a linked clone automated pool manager. Virtual machines and records (including records perisitant) associated with this pool have all been previously removed (deleted from the drive) of vCenter. The pool remains Gray and in the State of "suppression", in the display manager.

    around every 45 seconds, this event is logged in the display manager:

    module = connection to the server. message = error commissioning took place the Pool win-xp-related-clones due to a configuration problem.

    I don't know yet where to start troubleshooting. Pool seems to think again its status of "supply", meanwhile, the menu pool bed and the pool is actually disappeared for a long time that the "deletion" status.  It seems that my SQL db view can be somewhat altered and that maybe I need to delete some data manually.

    What newspapers I consider to facilitate troubleshooting? I searched the journal of composer for the name of my pool (win-xp-related-clones), but there is no match.

    I run see 4.5 and vCenter 4.1.

    Any help is greatly appreciated! Thank you!

    Hello

    Take a look at this KB (1008658):

    http://kb.vmware.com/selfservice/microsites/search.do?

    language = en_US & cmd = displayKC & externalId = 1008658

    The same thing happened to me once, and that KB has been very helpful.

    Best wishes / Saludos

    -

  • addition of CPU/memory for desktop computers in composer linked clone pool

    Hi all

    I want to add more CPU/memory for desktop computers in a pool of composer linked clone but I want to build a pool of test out changes first, while the production area is still in place. Can you screw with virtual material in the main image and then take a snapshot and build the pool of test out of it without him bring the clones in the production pool?

    I think that the process would be as follows...

    1. modify the parameters of material on the main image of Win7

    2. run the main image and let it recognize the CPU and additional memory (probably needs to restart the CPU I think)

    3. close the main image and take a snapshot

    4 create a new pool of test off the coast of this new snapshot

    Thank you!

    Yes it may seem straight, it won't cause any problems. If you want to be very careful with your prod environment, you can just clone the base image and make your tests on it.

  • What Linked Clone VM after having deleted the Parent model?

    Hi all

    I deleted the models and all VM related clones still works fine

    Looks like that model files still sitting on the data store.

    It will be really difficult for me to keep track of which is where?

    It will be really useful if we could come up with a report or something to achieve exact file structures

    Thank you

    As long as a VMDK is necessary for all child VM still in Lab Manager (or a child of this VM) it will stay on the drive in its original folder.  You can eliminate some of the records/VMDK by consolidating the configurations that have been cloned from a template.  We do it with most of the configurations captured at the library.  You must be careful if or it will cost you a lot of space if

    In Lab Manager you can see this in a graphical representation on the way to resources, Datatstores and then choose the data store for configuration model / you want to watch.  The mouse on the virtual machine, and then select the context.  Not only that you get a graphical view, but when you hover over each box it tells you the name of the folder and the size of it.  He also tells

    I've been searching in the database to figure out how I can get this information and export it.  I'm only able to track down the parent folder for a current VM inside Lab Manager so far and not the parent of one that no longer exists (but always as a linked clone).

  • 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)

  • Search bar on the Macbook Air doesn't work, will allow me to load the pages of Favorites and links to these pages, but not let me google from the bar or manually enter Web sites, however, it works perfectly on the guest user

    Search bar on the Macbook Air doesn't work, will allow me to load the pages of Favorites and links to these pages, but not let me google from the bar or manually enter Web sites, however, it works perfectly fine on the guest user. Have you tried restarting and it still does not work.

    The problem should be solved now.

    Otherwise:

    OS X

    iOS

    Workaround for problems with the Safari address bar

    http://osxdaily.com/2016/01/05/fix-Safari-freezing-address-bar-use/

  • Linked clone is not the deletion of the Horizon view administrator

    I am trying to remove a linked clone (and pool that linked clone). However, he advised that is the removal of more than 12 hours. I think that the problem is that someone has tried to connect to this virtual machine before fully completing commissioning. The only other VM in the pool view Horizon has deleted without argument. Is there another way to remove this virtual machine?

    See you soon

    Linked Clone.jpg

    Hello

    Please find the following article to remove orphan console machines manager view. It will be useful.

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1013760

  • Best practice help to spend again vCenter with linked Clones

    Hello everyone

    I searched for days, but couldn't find a way clear of hover over our view 5.2 installation of a new vCenter.  The equipment was aging, and we decided to upgrade and move to 5.5.

    We have rebuilt and forwarded via our guests not VDI to the new vCenter 5.5 environment. I found a few documents, but nothing that tells us if it can be done actually.

    We tried to go in the service of the composer initially to the new instance of vCenter and maintenance, we do the DB on the old Victoria Cross, if it worked I émigrerait the DB above the new Victoria Cross

    We first tried these steps however VMware Documentation Library after removing the old VC service composer and installed on VC New (with ODBC connections mapped to the old VC) it wouldn't work.  We were moving to the VC 5.1 leaving guests ESXi running VDI attached to 5.1

    Then I did more research and discovered the related clones are all related to the database of the old VC and moving them is not possible per this KB KB VMware: workstations managed by moving between servers view vCenter is not supported

    I saw an article here that suggested dumping a bunch of DB and rebuild the new VC with the same name and IP address, but I can't do so because the new instance is already upwards and on a new host name / IP migrate view VCenter (with linked Clones) to new hardware

    I also found this where someone is in the same boat and suggested to recreate pools.  The discussion is not in the details so I wonder if someone can clarify this: migration View Composer and vCenter

    I have about 20 people on VDI in a combination of clones using 3 connected pools and personal drives.  Given that all the info from linked clone was linked to the former base of VC, it doesn't seem wise to move it to the wire.  This would be possible: I still have the base image with all the snapshots for each pool.

    • Persistent backup drives
    • Note the configuration of each pool
    • Disable the commissioning
    • Create DB on VC 55 composer vacuum
    • Create the ODBC connection for composer on VC 55
    • **
    • Do more ESXi hosts to 55 VC
    • Remove existing VMs (will be not able to connect to them at this point anyway)
    • Remove the old VC entry admin view / delete existing pools
    • Install the composer on 55, and then tap new ODBC
    • Create new instance vCenter in Admin 55-pointing mode
    • Recreate pools
    • Import and attach persistent disks (http://pubs.vmware.com/view-50/index.jsp?topic=/com.vmware.view.administration.doc/GUID-BDFCCEC8-682F-4421-8810-06108CBE8D20.html)
    • Recreate events empty DB on 55
    • Reconfigure the parameter DB events in Admin mode

    Any help would be greatly appreciated as I can't find an exact way to do

    Well, I'm pleased to say it worked! I had a few problems by removing existing pools. View repeated deletion but nothing happened. In the end I had to use ADSIedit to connect to the server to manually remove all the old discs VM and pool

    After the installation of the composer on the VC 5.5, I was able to create a login in admin mode and then start to re - create the pools.

    We were able to successfully reattach each disc persistent owners planned.  Did some spot checks and desktop users, bookmarks etc. all worked

    It is a tedious process, but it does not work. I hope that VMware can create an article for it.  God knows that I searched for days, I had to read a lot of things just for this plan.

  • Expand a service end of vPC linked clone disc

    We have the following text:

    ESXi 5.0.0 build 1311175

    vCenter Server 5.0.0 Build 455964

    vSphere Client 5.0.5.0.0.37933

    See Horizon 5.1.0 build 704644

    See compose 3.0.0.691993

    vShield Manager 5.0.2 - 791471

    Version of VMware Tools 8.6.15 build 2495133

    The image of Windows 7 has 2 discs of interest:

    C:\ OS (provided slim 30 GB)

    Profile of user D:\ (10 GB persistent independent disk)

    The issue is that the C drive is 30 GB thin Provision in total, with 6 GB of free space.  I have disabled disk defragmentation, System Restore is 3% (900 MB).

    The only thing that is installed are the Windows updates on patch Tuesday.  The programs we use are static they don't really change.

    So no new installations of any kind except updates of Java and Adobe.  I have install a piece of software once a year.

    Users do not have the rights to install the software on their virtual machine.

    I regularly run cleaning disc for drive C, but is that not a lot of space is recovered.

    I would like to extend the C drive of the 30 GB, but the option is grayed out for the vPC (see screenshot).

    I went into the display of VMware administrator to see if I can expand the C drive on impossible to locate the area where I can expand it.

    I do not see the area where I can expand the persistent drive, but not for the OS disk.

    The plan was to extend the OS disk, then recompose the specific office according to the needs arise.

    Can you please indicate if it is possible to extend the 30 GB VMware View operating system?
    This vPC is also a linked clone

    Unfortunately Yes. Alternatively, you can create a complete clone of the current state of the virtual machine and use it as a new basic disk. This can not only be faster than to delete all snapshots, but also allows you to maintain the State of the current virtual machine in case you need more later.

    André

  • Best way to rebalance local drives with linked clones?

    Hello

    • 5.2 seen running, looking to update soon.
    • We use local storage (FusionIO).
    • Each pool is distributed over 4 servers running these local storage.
    • Our related clones are not persistent - users do not get a specific office, and workstations are deleted on logout.

    So, I want to patch servers.

    My thought on this is:

    1. Edit the pool to remove local storage on the server to be patched.
    2. Rebalance.
    3. Perform the update (mode maintenance, blah blah blah).

    So the rebalance operation is having limited success in my first try

    I am aware of that: VMware View 5.2 Documentation Library : you cannot balance the load of the virtual machines on a pool of resources. For example, does not allow the operation of rebalancing View Composer with linked clones that are stored in local warehouses of data.

    So I can't rebalance (first of all, I'm not sure why? In my case, cannot not machines just be deleted and recreated elsewhere - whereas a rebalancing is also a refresh anyway)?

    What is the best approach?

    • I need to make desktop computers available to local specific server storage exist anymore (once there are multiple sources available on another server storage) so that users don't connect/don't have not logged when I do the maintenance.
    • I need to make sure that desktop computers connected to local specific server storage are removed on logout (as usual) and does not get recreated on this storage again.

    Of course, when the server comes back to the top, I need to reverse the process and get the desktop on it and maintain a balance between other servers.

    Any advice?

    Thanks in advance.

    Rebalancing is not a simple delete and action of re - create. Even the workstations are not persistent, there are persistent records associated with it. as (internal drive)

    These door data as approval of the membership of domain and all. Therefore, without a shared, preserving data store and the migration of this internal drive are impossible (and prevented).

    Now for you case, because she is floating desktop computers (non - persistent).

    1. Deselect the host data store to be corrected by changing the pool.
    2. Logoff of active sessions (if any) for VMS specific / put the virtual machine in maintenance mode.
    3. Delete these specific through VMs * Administrator display inventory pool *.
    4. Configure back the technical provision of data after having patched host store,
    5. And then increase the size of the pool the desired number
  • 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

  • Bloating of snapshot using linked clones

    I have currently a VMware view test the configuration of the environment as follows:

    1 host ESXi 4.1

    NetApp SAN with a volume of 250 GB configured

    1 120 GB lun for the linked clones, 1 lun 60 GB for the VMs parent

    vCenter vsphere, running on a windows 08 R2 vm Server (also houses see composer)

    1 discovers the connection to the server running on a server 03 R2 vm windows

    1 view security server running on a windows 08 R2 vm Server

    So far, I was able to get the environment view work just fine.  It's a project pilot in its beginnings, there is not a lot of users (usually 1 or 2 to a maximum of time, with maybe of 5 overall users).  I noticed recently that storage that I allocated is being consumed way more that I thought it would be.

    There are two parents VM, which have 2 GB of RAM with a 25 GB HD and 1 GB of RAM with a 15 GB HD, respectively.  They are sitting on their own separate logical unit number.  The first virtual machine (25GB / 2GB) has 2 clones and the second a 3 clones in a 120 GB LUN.  When I browse this data store in vSphere, I find this:

    When you look at this picture, I see that the size of the virtual disk is 32 GB, which is fine for Replica 2, VMs and 5 related clones.  The part that I find confusing is that snapshots take 31,75 Go.   After further investigation by browsing the actual data store, I see this:

    This clone also has a snapshot file, which is about 7 GB in size.  I checked each clone, they all have this snapshot file.  In addition, even the clones that are in the pool, but currently unfunded have this snapshot file sitting on the LUN.

    Is there a setting within the opinion that took me unintentionally allowing this behavior, or each linked clone have / need this snapshot?  If it is not possible to turn it off, can someone explain to me his relevance/importance and whether or not I can remove these files?  It seems to me that to have a glimpse of a linked clone is redundant and a waste of space, I have a snapshot of the parent which I can return at any time if I need to.

    Andre, it talks about the snapshot is created on the clone in 4.5.  This snapshot, allowing a quick return to the base image when you do updates where as in previous versions should be deleted the clone and build new.

    Suiname if you need to remove (commit) the snapshot he would place all of the changes that had accumulated on the initial VMDK, so I don't think you would save any space out there.   If you return to this snapshot, it would open the entire space, but which is identical to a discount.

    If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

    Twitter: http://twitter.com/mittim12

  • 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.

  • Force linked Clones to check the live servers to KMS for Activation

    Hi all.

    Apparently, linked clones will check the KMS server that was used to activate their master gold.

    (Centre of Documentation of VMware View 5.0) - Note This is display 5 documentation, but we use 6.1 view now.

    " For the approval of KMS, View Composer uses the KMS server that is configured to activate the virtual machine parent. »

    It is a problem if the KMS is taken out of service, or generally a problem - all the linked clones fail to activate.

    How can we prevent the clones related to use the same KMS server?

    How can we get the clones related list and choose the first KMS server, which is returned by the DNS SRV records?

    Thank you

    Update:

    High level of the DNS entry works very well.

    • We have added a DNS record called kms.domain.com that uses repetition alternate for our KMS server two.
    • We made the VM Golder Master point to the folder. slmgr.vbs /skms kms.domain.com:port
    • We rode to the top of some related clones.
    • Check where the clones linked when pointing to slmgr.vbs /dlv- both pointing the DNS record and not a specific server.
    • Made a second activation and performed a capture of packets at the same time slmgr.vbs /ato

    We found that the clones related to different servers and respond accordingly.

    The same thing can be done with office by using the ospp.vbs script (although different switches).

  • I can locate all the linked Clones Parents

    Hello!  I am an instructor and have tons of old VMS using all my disk space.  I want to do a cleanup, but I don't want to accidentally delete a parent of a linked clone until I have a chance to remove anything important with the linked clone.  Is it possible to determine if a virtual machine is used as the parent of a linked clone?

    Thank you!

    Post edited by: alwweb - I forgot a Word.

    If you look at the Snapshot Manager for the parent of the linked clone VM, you will find that a snapshot is created automatically when you bind the clone. The snapshot icon has a "lock". Please see my attachment 'linkclonesnapshot.png '.

Maybe you are looking for