That's what we do too - physical boxes get the asset tag in the name and VMs are just sequentially numbered per user if they have more than 1.
- Andy O. >-----Original Message----- >From: Garcia-Moran, Carlos [mailto:[EMAIL PROTECTED] >Sent: Wednesday, August 20, 2008 8:41 AM >To: NT System Admin Issues >Subject: RE: VM naming convention > >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? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
