Client Computer Naming Convention

Hi,

You question sounds very challenging! I am not really sure what you want to do now. You talked about Tivoli (which I have to find out what it is) but are you going to continue using Tivoli?

You also did not give info about how your domain are setup now and if you are using a complete win2k environment of mixed-mode environment.

Also, you need to consider geographical contrain for designing your Active Directory.

For client computer naming, that is easier compared to setting-up AD. First, if you put the computer the name of a person, how sure are you that the person using the computer is actually the same person? Why don't you put them according to Department 01,02,03...? The reason for this is so that you know what specs (software and hardware) is used on that department. If you are afraid that users get confuse, try labelling the computer name on the monitor or something.

Or you can use a centralize location for file sharing. That way, you can make a folder for each user and they can share files from there.

OR you can use DFS (distributed file system) to create logical sharing that is easy for users to see.

What I am saying that, there are a few approach to this problem. Setting everything dead on PC naming is not the only way to solving you problems.

Setting computername dead, is bad idea. What if a user change department or leave the company?

Since you user is located miles away, you need to send someone to go there and change the computername? You need a method that is dynamic and logical that do not need you to leave your chair.

Oh yeah, you could check out Microsoft Metadirectory to see if it could solve some of your problems.

I am just giving suggestions, I am no expert yet. But through discussion, we can obtain more knowledge. Email me at abubin@yahoo.com for further discussion.

To help eliminate confusion here is what we have identified as valid business requirements for a naming convention in our envirnment.

Our primary criteria:
minimize interuptions to clients.
achieve ROI by getting savings in IT support related cost.
get there within or below our budget.

1. Can only use valid Characters (A ? Z) and (1 ? 0).
2. Windows 2000 can not use numeric only computer names.
3. Can not start with a numeric character ? 1st Character needs to be Alpha.
4. Avoid using Hexadecimal digits. They can be misinterpreted.
5. Names need to be no longer than 15 characters.
6. Computer Name needs to consist of Unique and Static information that is not subject to change.

About our envirnoment:
We are performing an in place upgrad of our single domain to Win2k. We will be going to native mode ASAP. We will begin implementing Exchange 2000 and deploying Windows 2000 to the desktop and implementing group policy to lock down the desktops. Tivoli is our framework enterprise solution for helpdesk, asset managment and change management.

What I am saying is, your approach is not a good way for administration. In the first place, with this problem, you should not let users share their data from THEIR computer. Let them share through a centralized server. This way you do not need to concern about computer naming. This is the main gist of windows 2000 and Active Directory. You can have folder redirection too if you want. With that centralize server, you only need to manage the fileserver. And you can name them according to user account name. Simple and easy. If the server is located remotely, just use Terminal Services to manage it. And it comes free with win2k (oh..boy, I like TS in winXP. Each workstation is TS ready!!!).

You should not adopt your old methods that you are using with winNT. It's time you explore the advantages of win2k. Just name those PCs like Account01, Account02...or Finance01, Finance02...And since you have Tivoli, you can just refer to Tivoli and knows who is using which computer. The users doesnot need to know. Their concern of filesharing has been handled by DFS or fileserver.

Naming Convention Technical requirements as we have defined them based on Technical specification of technologies to be deployed and to capitalize on metodologies we have defined as well:

BHI Computer Naming Convention Technical Requirements:

1. Will Identify Business Unit.
2. Will not be subject to change.
3. Is defined by business need.
4. Will be consistent globally.
5. Does take into consideration other adopted ?industry standards.?
6. Will try to not exceed 15 characters in length.
7. Will only consist of valid characters (A thru Z, 1thru 0)
8. Will be alpha numeric.
9. Will not start with a number.
10. If machine is to not be Tivolized it will start with ?XXX?

Exactly What I am looking for:

A recommended naming convention that you have seen or that your company uses. I will give tech points to those that can supply me with a sound naming convention that I can quote as an example.

Use Win2k Remote installation Service (RIS)to upgrade all PCs to win2k.
In Active Directory, select the Desired RIS server (with a right click)
Click Properties, and choose the Remote Install tab, then click the Advanced Settings button.
Click "Generate client computer names using list", choose the custom option...
then in that window, enter the string
%5Last%5first%#
this makes the names
first five letters of Last name
First five letters of First name
an incremental yet unique number assigned by the RIS server

for example, if you were user number 12,568
your computerID would be
SMALLPRESC12568
even 20,000 users would not exceed 15 characters, and short names are just shorter, eg
DOEJOHN11567

If you use wisdom in modelling your physical business layout as Organizational Units in Active Directory, it won't be confusing at all, AND can be remotely administered.

I say, send Tivoli back to their Ferraris and staff your IT department with clever admins who are capable of exploiting all of the Win2kServer features.....somebody like....oh...Me ;-)

It sounds as though you're seeking some general guidance on establishing your enterprise IT standards. Of course, this can include a wide range of issues. It might be helpful to review the enterprise IT standards of others, and apply relevant areas to your particular situation.

The following links will take you to some such documents:

(REMOVE SPACES from the pasted URLs.)

http://www.state.ia.us/itd/ITStandards/enterprise_it/index.html

http://www.state.ky.us/kirm/arcstand.htm

http://techupdate.zdnet.com/techupdate/stories/main/0,14179,2837626,00.html

Good luck,

Maxwell