nope.....
 
My first name is rl-mbames, my second machine is rl-mbames-1, the third
machine is rl-mbames-2 and so forth.
 
If there was a second "Matthew B Ames" in the company, their logon name
would mbames1, thus their machines would be rl-mbames1, rl-mbames1-1,
rl-mbames1-2, and so on.  A third "Matthew B Ames" would have a logon
name of mbames2.
 
I didn't design it, it is just what we use.... :-)

________________________________

From: Micheal Espinola Jr [mailto:[email protected]] 
Sent: 16 November 2010 02:47
To: NT System Admin Issues
Subject: Re: Workstation names and who it belongs to


You must have lots of duplicate name issues.

--
ME2





On Mon, Nov 15, 2010 at 8:58 AM, Ames Matthew B <[email protected]>
wrote:


        We do:
         
        <letter1><letter2>-<username>
         
        Where:
        letter1 = domain the machine sits in
        letter2 = d for desktop, l for laptop
        username = my logon name.
         
        Each machine is assigned to a member of staff and when they
leave the machine is rebuild before assigning to someone else.  If I had
multiple machines, we add a -1, -2, -3, etc onto the end of the string.

________________________________

        From: David Lum [mailto:[email protected]] 
        Sent: 15 November 2010 16:53
        To: NT System Admin Issues
        Subject: Workstation names and who it belongs to
        
        

        How do you guys handle matching users to machines? We currently
have a PC naming standard of <firstinitial><lastname>-<model> but this
obviously doesn't scale. One possibility is putting the user name in the
description field in AD (I do this for %sidejob%), but I was wondering
if there was a better way to automatically get a machine <->user lookup.

         

        How do you guys handle it? 

        David Lum // SYSTEMS ENGINEER 
        NORTHWEST EVALUATION ASSOCIATION
        (Desk) 971.222.1025 // (Cell) 503.267.9764

         

        ~ Finally, powerful endpoint security that ISN'T a resource hog!
~
        ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
        
        ---
        To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
        or send an email to [email protected]
        with the body: unsubscribe ntsysadmin

        This email and any attachments to it may be confidential and are
intended solely for the use of the individual to whom it is addressed.
If you are not the intended recipient of this email, you must neither
take any action based upon its contents, nor copy or show it to anyone.
Please contact the sender if you believe you have received this email in
error. QinetiQ may monitor email traffic data and also the content of
email for the purposes of security. QinetiQ Limited (Registered in
England & Wales: Company Number: 3796233) Registered office: 85
Buckingham Gate, London SW1E 6PD http://www.qinetiq.com
<http://www.QinetiQ.com>  <http://www.QinetiQ.com> 

        ~ Finally, powerful endpoint security that ISN'T a resource hog!
~
        ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
        
        ---
        To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
        or send an email to [email protected]
        with the body: unsubscribe ntsysadmin


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

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin


The QinetiQ e-mail privacy policy and company information is detailed elsewhere 
in the body of this email.

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

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to