VMware Horizon Community
bihiett
Contributor
Contributor

non-persistent active directory workstation objects

I am trying to create a fully automated Non-Persistent pool of workstations. The idea is to replace a lot of our kiosk-style desktops with non-persistent vm's which are set to delete after logoff.

I have the configuration set and I am hung up on one small item that I hope you all have a fix for.

I have the OS customization set to use the name of the vm and join the domain automatically using a domain admin account. In VDM admin I have the pool configured to "Power off and delete virtual machine after first use". The pool is set for a pool size of 3 (while testing, this will become 25-30). I prepopulated 3 computers (computer1, computer2, computer3) in a new Active Directory OU (VMDesktops). I applied a number of GPO settingss to this OU to automate the process, which include;

Domain users added to security policy "Allow log on through terminal services"

Holes opened in firewall for remote desktop

Additional security settings specific to our environment

Additional security settings specific to the role of the desktops (shared kiosks)

My problem is that each time a user logs off and VDM creates a new desktop the computer name increments (computer4, computer5, computer6, etc...) instead of reusing unused computer names. While these new computers join the domain sucessfully, their computers are joined in the wrong OU and therefore do not get the correct GPO settings. Not to mention that as time goes on, I will have hundreds of unused workstation objects.

I can think of a few ways to fix this but they are pretty difficult (dedicated trusted domain for vm machines, writing custom scripts to run at first login which will move the account to the correct OU). And none of them fix the aged computer objects problem.

Any help or guidance is greatly appreciated!

Bill

0 Kudos
3 Replies
Jasemccarty
Immortal
Immortal

Lot of posts about this lately.

Check out these posts:

http://communities.vmware.com/thread/174693 and http://communities.vmware.com/thread/145711

Jase McCarty

http://www.jasemccarty.com

Co-Author of VMware ESX Essentials in the Virtual Data Center

(ISBN:1420070274) from Auerbach

Jase McCarty - @jasemccarty
0 Kudos
bihiett
Contributor
Contributor

I figured this was the case. Just couldn't find anything definitive.

My biggest problem with this solution is the leftover unused workstation accounts. We have 25 kiosks that are asked by as many as 20 students in a day. So we will end up with 500 computer accounts each day!

There needs to be a setting to recycle computer names...

Thanks for the input.

Bill

0 Kudos
Jasemccarty
Immortal
Immortal

I would agree.

If you have a Windows 2003 backend, the following might help:

dsquery computer "ou=student workstations,dc=domain,dc=com" -inactive 1 -limit 0 | dsrm computer

That command would look for, and delete, all systems in the "student workstations" OU that haven't logged in for 1 week.

A vbs that could delete by the day would be even more efficient.

Jase McCarty

http://www.jasemccarty.com

Co-Author of VMware ESX Essentials in the Virtual Data Center

(ISBN:1420070274) from Auerbach

Jase McCarty - @jasemccarty
0 Kudos