Hi,
Just wondering if you setup Linked Clones, are they dynamically created and destroyed as users log on and log off or do they stay around and take up storage space?
Thanks
One thing I am kind of suprised is that it seems the clones take up about 1Gb of space in my case as I set them up for 512MB of RAM and then it is also using 384MB or space for something else. The other thing I am suprised with is the amount of storage needed to deploy this linked-clone. Basically you need the Parent VM with snapshots and basically a duplicate of this a folder called something like "replica..." and then of course my clones.
That is for performance. by putting a replica on each LUN you are reducing he strain on the master disk. and if you are only doing a small amount of clones you will not see as much storage saving as when you are increasing the numbers
>It does not seem like a very clean deployment or a huge space saver.
That is an eronous statement, the lager numbers you do the greater saving you gain
>I am not exactly sure how other like Citrix or doing this one-many deployments.
Exactly the same way
On top of the storage requirements is the AD / DNS clean up which adds to administration time. I am sure VMware will work to clean up and streamline some of these issues (hopefully).
Short of running a remove from domain script when the machine is logged off, not much you can do really.
On another note: I am looking for find instructions on creating a bare bones XP VM with the basics required for AD, Antivirus, Office, Outlook, VMware, NAS & Netowrk shares etc. I really would like to get it down as small as I can without removing too much functionality. It has to be useful for normal user.....???
Do as search on the forums there are ateast 40 threads on this subject.
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points
Tom Howarth
VMware Communities User Moderator
Blog: www.planetvm.net
There's a setting for this when you setup your VDI Pool, I forget it's like the 6th page in and you have a few options right before selecting the amount of Linked Clones to deploy, you just have to check or uncheck it (unchecked by default).
As has already been stated it is an option, the default is for the clone to remain and if none-persistant be returned to the pool or if persistant remain tied to the original user who logged on.
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points
Tom Howarth
VMware Communities User Moderator
Blog: www.planetvm.net
I have noticed with Linked Clones that when you destroy the VM after use it does not clean up the DNS entries and such...it looks like this is will create a mess in AD and DNS ??
This is correct, and has been one of my biggest complaints about VMware's product. What I would recommend is a script that runs on a weekly basis to delete old computer accounts and setup DNS scavenging.
One thing I am kind of suprised is that it seems the clones take up about 1Gb of space in my case as I set them up for 512MB of RAM and then it is also using 384MB or space for something else. The other thing I am suprised with is the amount of storage needed to deploy this linked-clone. Basically you need the Parent VM with snapshots and basically a duplicate of this a folder called something like "replica..." and then of course my clones. It does not seem like a very clean deployment or a huge space saver. I am not exactly sure how other like Citrix or doing this one-many deployments. On top of the storage requirements is the AD / DNS clean up which adds to administration time. I am sure VMware will work to clean up and streamline some of these issues (hopefully).
On another note: I am looking for find instructions on creating a bare bones XP VM with the basics required for AD, Antivirus, Office, Outlook, VMware, NAS & Netowrk shares etc. I really would like to get it down as small as I can without removing too much functionality. It has to be useful for normal user.....???
Thoughts.
One thing I am kind of suprised is that it seems the clones take up about 1Gb of space in my case as I set them up for 512MB of RAM and then it is also using 384MB or space for something else. The other thing I am suprised with is the amount of storage needed to deploy this linked-clone. Basically you need the Parent VM with snapshots and basically a duplicate of this a folder called something like "replica..." and then of course my clones.
That is for performance. by putting a replica on each LUN you are reducing he strain on the master disk. and if you are only doing a small amount of clones you will not see as much storage saving as when you are increasing the numbers
>It does not seem like a very clean deployment or a huge space saver.
That is an eronous statement, the lager numbers you do the greater saving you gain
>I am not exactly sure how other like Citrix or doing this one-many deployments.
Exactly the same way
On top of the storage requirements is the AD / DNS clean up which adds to administration time. I am sure VMware will work to clean up and streamline some of these issues (hopefully).
Short of running a remove from domain script when the machine is logged off, not much you can do really.
On another note: I am looking for find instructions on creating a bare bones XP VM with the basics required for AD, Antivirus, Office, Outlook, VMware, NAS & Netowrk shares etc. I really would like to get it down as small as I can without removing too much functionality. It has to be useful for normal user.....???
Do as search on the forums there are ateast 40 threads on this subject.
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points
Tom Howarth
VMware Communities User Moderator
Blog: www.planetvm.net