• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Linked Cloned desktops - quickprep or sysprep?

W

WoodiE

Limp Gawd
Joined
Jan 28, 2003
Messages
231
Let me start by telling you what I have now - currently one of my pools, a linked state clone pool of 90 virtual machines. The pool is non-persistent, deletes on log off, and is created using sysprep.

I've been reading a number of things in regards to Quickprep and how much faster it is. I've also read VMware's quickprep vs sysprep KB as well.

One thing that's stuck out to me with quickprep from that KB article is that local accounts are not removed. I'm assuming that means the account users have used to log into the pool? And if so would this even matter if I change my pool setting from non-persistent, deletes on log off, and created using quickprep - wouldn't the deleting part of the VM remove all the accounts anyways?

I like the idea of quickprep as I'm all for faster and more efficient, but want to ensure the virtual machines are still going to perform as we're used to - a clean VM with each new login.

Comments? How do you manage your linked state clone pools?
 
We use quickprep with no issues, however, we are also not deleteing the VM on log off. We just don't have any environment that we can do that so we use Recompose..etc.
 
Quickprep is great as long as you dont need a unique SID.

When it says local accounts its talking about users you would have logged in as when you created the master image outside of Administrator, and other accounts created yea it wont wipe them, but if you were the one that created the master image then there should be no issue as you control those accounts.

Realistically you should make sure you have no software that is SID dependent and if not then jump to Quickprep. (softwares that use SIDs are like OLD SMS, i have heard of some antivirus' that use to use) its usually software thats managed by a central server in your environment that might require that kind of identificiation.

Deleting on Logoff also consumes a lot of IOPS and i mean A LOT as it has to rebuild the machine re-join the domain etc. i would recommend maybe a Refresh on logoff in your situation it will shut the machine down and jump the snap back to the point right after it joined the domain, and fire it back up, this causes a lot less IO load, brings up your machines faster, and saves AD from creating/deleting/creating AD accounts all the time.

Test it out with a dummy pool using the same master image see if you see any defects using it a different way and if all works find then expand to a test user set and so on... best to try it before u implement it throughout your environment.

Hope that helps.
 
WoodiE55 said:
One thing that's stuck out to me with quickprep from that KB article is that local accounts are not removed. I'm assuming that means the account users have used to log into the pool? And if so would this even matter if I change my pool setting from non-persistent, deletes on log off, and created using quickprep - wouldn't the deleting part of the VM remove all the accounts anyways?
Click to expand...

This is referring to the local accounts on your base image, ie Administrator. When quickprep creates the linked clones from the image it will retain that local Administrator account on all of the VM's.

I have been doing a lot of testing with linked clones and forcing the VM to 'refresh' after user logoff, truly presenting non-persistent machines to our end users. I am retaining important persistent data via View Persona.
 
I'm setting up a new Training Pool for our training department and will try Refresh after logoff and quick prep. If memory serves me right, I believed I had issues with refresh after logoff in the past though, I think it was due to VM's loosing connection to the domain, having the VM deleted seemed to correct that issue.

I might be thinking of something else, but I'm going to test refresh and quickprep for a week or two and see how it works out.

Thanks!
 
I think i know what you are talking about, specifically with AD computer accounts generating a new password from the account to the domain that would expire after 7 days and up to 30 days and then the account would be disabled.

thats an AD OU that controls that..
http://support.microsoft.com/kb/154501


i run my domain with default settings and dont have any issues like that... Server 08 DC with VC 5.0 View 5.0, but i did hear about it with younger versions back in the day.. Server 03 Domains.... Also my functionality level is 08R2
 
Last edited:
You would be correct, in fact I just received an error on one of the VM's now...

error.png


The VM is in a pool that's now set to Refresh on log off and using Quick Prep.

I'll have to check out the MS link and see if this is something we can deploy on the pool.
 
You must log in or register to reply here.
Back
Top