Configuration Item - Network Client Devices DRAFT

This class includes network client devices that do not have a separate class of their own. This includes laptops, workstations, thin clients, kiosks, and others. Only network-based devices that require a host name are covered in this topic.

CI Naming Convention

All network-based client devices have unique host names that are assigned at the time the device is configured for the client. Host names for client devices are divided into three or four segments with the segments separated by hyphens. The total length of a device name cannot exceed 15 characters. (See Technical Notes on Device Hostnames, below.) Since host names are unique to the device to which they are assigned, the host name is also used as the CI name for the device. Device host names follow the form of:

      {division}[-{subdivision}]-{type}-{sequence_number}

Where:

{division}	A mandatory two- to four-character code representing the major unit that owns the device.
{subdivision}	If the primary unit is a large one this segment is used to define the subdivision of the larger unit. The subdivision is optional and is separated from the rest of the CI name by a hyphen.
{type}	A mandatory code indicating the type of device. See Device Type Codes, below for a list of device type codes.
{sequence_number}	A three-digit sequence number beginning at 001. The sequence number has no relation to the device's IP address. Occasionally, sequence numbers may be reissued as devices are retired but the same sequence number will not be issued to more than one device within a particular division, subdivision, and type combination.

NOTE

When a network device is retired, the CI name must be modified in the CMDB to include a prefix of RETIRED to make it obvious in listings and searches that the device is no longer being used.

Device Type Codes

Only the following device type codes may be used in a device name:

Code	Represents
D	Windows Desktop
MD	Mac OS Desktop
L	Windows Laptop
ML	Mac OS Laptops
V	Virtual Machines
TC	Thin Clients
PRSN	DEDICATED Presentation Systems, including projectors, interactive whiteboards, digital AV systems, etc.
K	Kiosks

Examples

The following are examples of CI names that conform to this standard:

Device Name	Description
OIT-WSG-D-001	The first desktop workstation deployed in the Windows Service Group within OIT.
OR-ORA-L-023	The 23rd laptop installed in the Office of Research Administration department within the overall Office of Research.
DTS-K-002	The second kiosk system installed for Distribution & Transportation Services.
RETIRED - OIT-PRSN-003	The third presentation system installed for OIT which has been retired.

Technical Notes on Device Hostnames

NetBios names are limited to a maximum of 15 characters as described in the following articles:

- http://support.microsoft.com/kb/163409
- http://support.microsoft.com/kb/909264

Typical Life Cycle for Network Client Devices

Phase	CI Activity
Phase 1: Device Requested & Approved During this phase, a need for the device is determined and a decision is made to acquire new equipment. Specifications are determined, quotes are obtained, approvals are collected from appropriate stakeholders, and a supplier is selected. In some cases, the "supplier" may be internal if, for example, an existing device can be repurposed or one is located in another department. This phase ends when all internal documentation is complete and a PO (or transfer documentation) is being prepared.	No CI required. A CI does not need to be added to the CMDB until the device is acquired (or developed) and work is ready to begin.
Phase 2: Order Placed & Device Acquired If the device is being acquired from a third party, an order is placed. If the device is being transferred internally within OIT or from another department, the required documentation is prepared and executed. This phase ends at the point where the device has been delivered and is ready for installation or configuration.	Submit a ServiceNow Configuration Item Update Request and a new CI representing the device will be added by the CMDB Administration Team. The Status field should be set to On Order or Installed, depending on the physical status of the device. Once the CI has been added to the CMDB, the Status and State fields are adjusted by the device owner to indicate the actual current state of the device.
Phase 3: Device Installed & Tested The device must be compared to the original specifications and acquisition documents to confirm that it matches the original requirements. Any required assembly and configuration is done during this phase. This includes network connections, security rules, disaster recovery, and any other arrangements required for the specific device. When all configuration steps are complete, a final system test is performed on the device in place to ensure it meets all client requirements. This phase ends when the device is ready to be used for its intended purpose.	Once the device is installed, the Status field should be set to Installed. This should be the status throughout the configuration and testing phase.
Phase 4: Device in Service & Maintained This phase represents the useful production life of the device. Throughout this phase, the device will undergo periodic maintenance, upgrades, failures, and fixes. At some point, its usefulness will come to an end and plans need to be made to take it out of service. This phase ends when the device is deactivated, is no longer being used, and is ready to be deinstalled.	The Status, State, and other fields are maintained by the asset owner throughout the service life of the device.
Phase 5: Device Retired When the device is no longer needed, either because it is being replaced by something newer or it no longer serves any useful function, it is retired.	The Status and State are updated by the device owner to reflect the fact that the device is no longer operational and has been retired. *Under no circumstances should a CI ever be deleted* from the CMDB. Deleting a CI record will make it impossible to trace the history of the server and any activity documented by incidents and change requests. When there is no longer a need for the device, the device name in the CI is modified to include a prefix of RETIRED** to make it obvious in listings and searches that the device is no longer in use.