http://support.microsoft.com/kb/957006

S

-----Original Message-----
From: Ken Schaefer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 20, 2008 9:38 PM
To: NT System Admin Issues
Subject: RE: VM naming convention

Current customer has <country code><site code><machine code><type 
code><environment code><incrementing value>

e.g.
au2104vpAAAA (Australia, Particular office, virtual machine, production, 
machine code) -vs-
au2104dpAAAB (Australia, Particular office, domain controller, production, 
machine code)

Cheers
Ken

> -----Original Message-----
> From: Christopher J. Bosak [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 21 August 2008 1:23 AM
> To: NT System Admin Issues
> Subject: RE: VM naming convention
>
> As silly as it sounds. Name them from characters in the Matrix. That way we
> know they're not a "Real World" machine.
>
> Yeah, I'm weird... but it works.
>
> Christopher J. Bosak
> Vector Company
> c. 847.603.4673
> [EMAIL PROTECTED]
>
> "You need to install an RTFM Interface, due to an LBNC issue."
> - B.O.F.H. (Merged 2 into 1) - Me
>
> -----Original Message-----
> From: Dennis Melahn [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 20, 2008 08:21 hrs
> 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/>  ~
>
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to