We are in a situation where we have a conflict between ease of use and what is practical for the enterprise. Particulalry computer naming conventions. We have inheritted a non standardized mess and are taked with implementing and designing a Windows2000 rollout globally for approximately 20,000 users. We currentlly have several goals that are unattainable in our envirnment.
Our most common sstandard is to name the computer the same as the users logon ID. OR that and increment it with a 01,02, 03 ….. lik bob smith would be smitbob01
We can not selectively deploy software by business unit.
We can not accurately bill back to the Business Units fopr support because we have no idea what business unit the machine belongs to. (We have multiple business units in single locations all over the world).
We use Tivoli and the maintenance is rather cumbersom everytime we have to change a computer name we have to involve a member from our tivoli team to update the tivoli databasebefore a ticket can be closed.
our new recommendation is to use a 3 character code for business unit and the service/asset tag for the computer name since that will never change.
We have a large user base that currently uses peer to peer sharing (mostly non work related) that we feel should stop and be done through the servers.
We are getting a lot of resistance regarding our proposal because people just don’t like the change. We can easliy identify the machine by computer name for the user using tivoli resource of http://loopback:9495 which displays the current computers IP# and machine name and status in tivoli.
Any ideas or recommendations?