telecom network inventory

It’s possible to adapt and implement a lifecycle model without a massive migration project. The first thing you need to do (if you haven’t already done so) is gain a high degree of familiarity with your existing network—what services it already delivers; what components it includes; which servers may be able to host the new service and so on. For this, you need inventories. Few organizations have comprehensive inventories and documentation on their network. Yet, how can anyone manage or administer a network if they don’t know what it contains? Unfortunately, many administrators do just that every single day.

Taking telecom network inventory doesn’t have to be difficult. In many cases, it doesn’t even require a commercial inventory product. One of the best ways to perform a comprehensive inventory is to use a logon or startup script. This can be as simple as a batch or command file that verifies specific items found on each system. If you’re already running Windows 2000, Windows XP or Windows Server 2003, you can assign a startup script to every machine in your network, including both servers and workstations, through the use of Group Policy Objects. If you’re still on NT, then you’ll need to focus on the user logon script since it doesn’t support startup scripts.