I followed this approach at my old job. It was distinctive, but it ended up being a problem with such an odd set of numerals. It was Difficult to determine whose machine was whose (always using WINS), and even though they are different, sometimes they were very similar. (a1b2c3 and a1b2c2) I found myself making simple human error mistakes and trying to fix something remotely, on the wrong computer. In my office now, we don't have roaming profiles, so every users computer stays with that user. So we follow a format of username-extension. Sometimes it is too long for NetBIOS, but all in all it works really well.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Masthanaiah Cheekavolu Sent: Thursday, March 13, 2003 8:57 AM To: NT 2000 Discussions Subject: OFF TOPIC: Desktop naming conventions > Hi, > We have close to 350 desktops running with Windows NT 4.0 SP6 in our > Windows NT 4.0 domain . We are planning to upgrade (clean install) all > of them with Windows XP. We currently use animal, flower and bird > names to name the desktops. But, we have some difficulties going ahead > with this approach. Since we are reinstalling all the desktops in the > domain, we are planning to use service tags as the machine names. > > All the machines we use are from DELL. In future, we might have some > COMPAQ desktops as well. We also use SMS in our environment. We use > unattended PXE based automated installation method to install the > desktops. > > 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). > > I will be very happy to hear from all of you on the industry best > practice (at least widely followed) used in assigning machine names, > in a typical Windows network. > > Thanks, > Masthanaiah Ch. > ADP Wilco International Systems. This message is confidential and may also be legally privileged. If you are not the intended recipient, please notify [EMAIL PROTECTED] immediately. You should not copy it or use it for any purpose, nor disclose its contents to any other person. The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of ADP Wilco. ------ 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 PROTECTED]
