If NetBIOS names are unavoidable, the ideal solution to the name duplication problem is the one that preserves the greatest possible freedom in the selection of NetBIOS names. In other words, the guideline should impose only the minimum necessary constraints on possible candidate NetBIOS names. A corollary of the above is that the right to select names belongs at the lowest appropriate level of authority. Nothing in the University-wide guideline should require or recommend that divisional or departmental level administrators further deny or restrict the freedom of name choice to members of their units. Note that the guideline cannot insist on any of this-divisions and departments have a right to set their own rules.
Any guideline creates some administrative overhead.
The choices made for the NetBIOS Systems Naming Guideline impose minimal administrative demands on time and resources. Campus-wide services should not be based on environments or applications that require NetBIOS name resolution. This is not to say that all such problems will be resolved, but there is some hope that they may become more manageable over time. This means that as long as these systems are common on campus, some network services may still require NetBIOS name resolution. Problems with duplicate NetBIOS names are more serious and pervasive for NT domains and servers.