For all our dev guys that have local VM's we name then jdoeVM001 jdoeVM002 etc... since we join them to the domain this lets us know that theyre virtual and who they belong to, that way if we give them a new desktop naming still works
-----Original Message----- From: Dennis Melahn [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 20, 2008 9:21 AM To: NT System Admin Issues Subject: VM naming convention Quick question to you vmware workstation guys. We have decided to use workstation for a few of our engineering "power users". We've always used the machine asset number in the naming convention to maintain uniqueness. If we do that with the VMs (ie - 12345vm1) then the number will be wrong when the vm is transported into then next host. On my setup I use the OS description (ie - S2K3x32Stnd_VM1), but these aren't joined to the domain either. What do you guys do? Thanks, Dennis ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ _________________________________________________________ This e-mail, including attachments, contains information that is confidential and may be protected by attorney/client or other privileges. This e-mail, including attachments, constitutes non-public information intended to be conveyed only to the designated recipient(s). If you are not an intended recipient, you are hereby notified that any unauthorized use, dissemination, distribution or reproduction of this e-mail, including attachments, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify me by e-mail reply and delete the original message and any attachments from your system. _________________________________________________________ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
