I have been burned to many times by adding in the Username to the Machine. I have gone with for all of my clients <OS>+<Network Location> and add username into the AD description. for example I have a laptop that is named xploc18 in the AD it's Dave's Laptop. It's much easier to change the AD description then it is to change the machine name. Especially in a small office environment were people don't move from desk-to-desk. they usually just quit or get fired then you have to either A) change the machine name for the new user or B) change the AD description. I would rather change the AD description.
David Rolling - President www.Infovue.net On the Plains of Hesitation, Bleach the Bones of Countless Millions Who, at the Dawn of Victory, Sat Down to Wait and Waiting Died ========================================================= -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Lum, David Sent: Thursday, March 13, 2003 4:18 PM To: NT 2000 Discussions Subject: RE: Desktop naming conventions For my small shop I use <OS><USERID> (using only 3 chars for the OS. For example, W2KJFRANKLIN). The OS thing seems silly but for a long time I had four Win OS's on just a few dozen different machines. I have a folder (%windir%\pcdata) that has a file in it named <servicetag>, as well as another PCNOTES.TXT file in there that has any unique configuration (software or otherwise) for that PC. This way I know who has what by browsing, and I can merge the .TXT files on a script if I need to and simply match/merge the two files to know what user has what service tag at any given time. For passing machines to different users as upgrades happen, a number is added for the new machine (W2KJFRANKLIN1) as it's built before the old one is moved and then renamed. I'm not expecting one user to get too many machines before an OS change, and the .TXT lets me know the "path" it has followed. Dave Lum - [EMAIL PROTECTED] Sr. Network Specialist - Textron Financial 503-675-5510 -----Original Message----- From: Angus Scott-Fleming [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2003 12:54 PM To: NT 2000 Discussions Subject: Re: Desktop naming conventions On 13 Mar 2003 at 6:11, pavan wrote: > Question is, do you folks see any issues in using service tags as the > machine names? One major advantage that we gain here is that the machine > name is unique at any given time. We can read this from the BIOS and > assign to the system (using a script). Yes, I have that at several small clients and it is a PITA trying to remember which of several identical Dells is DG7W7B11. I wish I had named them for the desk of the common user. Downside to doing that is that when you move a machine to another person, which typically happens when a new machine is purchased for someone who needs more power. The oldest, slowest machine in the shop is not usually theirs, so their machine is passed to someone else and the name must be changed. A -- Angus Scott-Fleming GeoApps, Tucson, Arizona 1-520-290-5038 / fax 1-208-248-3124 http://www.geoapps.com/ AIM: AngusWSF ICQ: 165646506 --------------------------------------------------------- -- Angus Scott-Fleming GeoApps, Tucson, Arizona 1-520-290-5038 / fax 1-208-248-3124 http://www.geoapps.com/ AIM: AngusWSF ICQ: 165646506 --------------------------------------------------------- ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.461 / Virus Database: 260 - Release Date: 3/10/2003 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.461 / Virus Database: 260 - Release Date: 3/10/2003 ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
