| Migrating file and print services requires attention to the physical design. Of course, the first step is to take an inventory of the application and file servers as well as of the printers. The Reed Elsevier Company, whose case study information is profiled in Appendix A, used the criteria shown in Table 6.2 for its inventories. Table 6.2. Server Inventory Table | Characteristic | File Server 1 | File Server 2 | File Server 3 | File Server 4 | | Make and model | | | | | | Memory | | | | | | Disk capacity | | | | | | Storage Adapter Model | | | | | | Type/make/model of storage array | | | | | | MAC address | | | | | | IP address | | | | | | Current user storage and growth requirements | | | | | | Backup storage requirements and growth estimates | | | | | | Redundant file shares | | | | | | Hardware, drivers, peripherals on Microsoft HCL | | | | | | Replace or upgrade suitability | | | | |
Print services, like file services, should be assessed for the migration as part of the physical design. Table 6.3 is the printer inventory used by Reed Elsevier. Using a printer inventory permits the examination of printers just as you would servers to determine whether they are suitable to keep and upgrade, or retire. Note that some of the information collected here includes an evaluation of the volume, sizing requirements, network impact, and footprint to see whether the printer is going to meet future needs. There is no sense in upgrading a printer that won't meet future needs. In addition, you must evaluate whether the characteristics of the printer (duplex printing, color , and so on) match the need of the users and determine whether the users have complaints about it, such as reliability, accessibility, features needed, and so on. Printers are an important part of any computing infrastructure. Table 6.3. Printer Inventory | Printer Characteristic | Printer 1 (provide name /location here) | Printer 2 (provide name/location here) | | Printer make, model | | | | Memory | | | | Network or host attached | | | | MAC/IP address | | | | Printer driver version | | | | Current printer volume requirements | | | | Printer availability and accessibility requirements | | | | Specialized printing requirements (large format, collating, binding, and so on) | | | | Existing server suitability for upgrade and remaining book value | | | | File and printer driver and support availability | | | | Current versus future server and printer sizing estimates | | | | Current versus future power and floor space requirements | | | | Network impact of proposed changes | | | | Current versus future maintenance and service contract expenses | | |
|
