That's what we do.
-----Original Message----- From: Malcolm Reitz [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2003 6:18 AM To: NT 2000 Discussions We assign a unique asset tag number to each PC we purchase and then we use that asset tag number as the computer name. -----Original Message----- From: pavan [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2003 8:12 AM To: NT 2000 Discussions Subject: 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. ------ 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%% ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
