|
| The infrastructure assessment section of the Analysis phase is one of the most overlooked sections of a project but is one of the most important. Without it we make a lot of assumptions and increase our chances of risk, not to mention the possibility end-user perception might be skewed due to issues beyond the scope of the project. From my experience, a MetaFrame XP deployment will amplify the environment you deploy in to. What I mean by this is that if you place a MetaFrame XP farm in a poorly performing network you will most likely experience user perception problems. However, if you prepare your environment and deploy in to a network that meets the necessary requirements, your customer will love the outcome and you will make more money with less hassles. During the Infrastructure Assessment, you will be tasked to document the readiness, requirements and considerations for each of the following sections. This information will allow you and your customer to understand which areas of their current environment are ready for the MetaFrame Access Suite rollout and identify the ones where more attention is required. Professional Services organizations will often focus on other items that may represent a risk, but are not directly associated with technology users, project management practices, etc. These are important areas to explore, and should be assessed to some degree when you perform your own assessment. Upon completion of the infrastructure assessment, you will be able to spot problem areas and make recommendations for changes that will help you in your quest to achieve the vision of the project. An Infrastructure Assessment is broken down into the following sections though others may be added/subtracted based on the specific IT environment: Network Architecture: The Network Architecture segment is very important but sometimes is completely overlooked. Please give it the attention it deserves. The MetaFrame Access Suite is great if you have a good network, but can turn ugly very quick if the network infrastructure you are installing into is not properly designed. You will want to document what network protocols are on the wire, if they are using switches / hubs and how they are configured. You should document how they are segmenting the network (VLANS, subnets), what topologies are in play (Ethernet, Token Ring, ATM) and any bandwidth management software they may be running. You will also need to look for and document any duplex mismatch that might be found. In order to make sure that you are not responsible for any possible security holes, you will want to discuss with your customer what security precautions they have in place I.E. (firewalls, access controls, and two-factor authentication). You will also want to determine and document who has access to the physical presence of the hardware Hardware Environment: You will want to document the vendor, the amount of memory, processors, disk drives, NIC(s) required and any additional hardware for devices pertinent to the MetaFrame deployment.
Operating Systems Environment: Windows Server 2003 (Active Directory) - you will need to document how the Active Directory is designed. Document information such as name resolution, pertinent IP addresses, OU structure and file/print structure. Parse through the login scripts for any possible issues, group membership, any users/groups that will have administrator access and any additional information that might be specific to your customers AD design. Windows 2000 (Active Directory) - you will need to document how the Active Directory is designed. Document information such as name resolution, pertinent IP addresses, OU structure and file/print structure. Parse through the login scripts for any possible issues, group membership, any users/groups that will have administrator access and any additional information that might be specific to your customers AD design. NT Server 4.0 - you will need to document how the NT domain is designed. You will want to gather such information as the Domain model (Single Domain, Multiple Domains, Multiple Master, etc), name resolution (WINS, DNS), file/print structure. Parse through the login scripts for any possible issues, group membership, any users/groups that will have administrator access and any additional information that might be specific to your customers domain design. Novell Netware - you will need to document how the Novell network is designed. You will want to gather such information as the type of Novell directory services running, i.e. NDS, Bindery. If they are running NDS, you will want to document the NDS design (OUs, trees, etc.), name resolution, all the protocols running and their respective addresses. Parse through the login scripts for any possible issues, group membership, any users/groups that have administrator access, and any additional information that might be specific to your customers Netware design. MetaFrame Environment: If you will be deploying into a network with an existing MetaFrame / WinFrame installation, you will need to verify the following: Farm Architecture, ICA Browser, Servers, Load Balancing, Network Structure, Users, Applications, Application Delivery Architecture and Licensing. Printing Environment: If you have been around the Citrix world for a while, you will know that the print subsystem is one of the most finicky problem spots and requires proper configuration for optimum performance. With this in mind you will want to make sure you do your best in analyzing your customers print environment. You will need to document all the print servers for such things as what OS it is running, how the printers are attached and how many printers are on each print server. You will also need to document as many of the home / off-site printers as possible. I like to throw this task in to the hands of my customer and task them with the responsibility of supplying me with a list of all the printers that need to be supported. I also make sure that they are aware that any additional printers might require additional changes. Client Environment: In a server-based computing environment, you spend 99% of your time on the back-end but it is still important to know what type of client workstations you will be deploying into so that you can account and support them as needed. You will want to document the operating systems you will need to support, if they are desktops or laptops, how the users will be connecting to the server and from what type of connection. (RAS, ICA dial-in and or TCP/IP via the Internet)
Change Control Environment: The goal of any deployment is not only to successfully deploy the product, but also to leave an environment that will not fall when you leave. This is done by creating policies and procedures on how future changes will be orchestrated. This is what we call change management. In most cases, you will not find any change control mechanism in place, but this does not mean that you want to leave it that way. Document any change procedures that might be in place, which is able/responsible for making changes and inform your customer that you will be creating basic change control procedures for their new MetaFrame environment.
The following is an example of a basic Infrastructure Assessment finding: |  Infrastructure Assessment
November 7, 2003 Client: DABCC.COM Executive Sponsor: Douglas Brown, Owner Project: Citrix MetaFrame Access Suite Deployment Instructions: Complete the following survey. Answer all questions that apply to your environment. The assessment is divided into 6 parts: Network Architecture Hardware Environment Operating Systems Environment Printing Environment Client Environment Change Control Environment 1. Network Architecture Fill in all applicable sections regarding your network architecture. What network topology do you currently have in place (Ethernet, Token Ring, etc.)? Ethernet Are all servers located in the server room? If not, please indicate location. All servers are located in the computer room located in the southwest corner of the office. Fill out the following information for each hub/switch: | Hub/Switch 1: | | Hub/Switch Model: | Cisco Catalyst 2948G-L3 switch | | Cable type: | CAT 5 | | SNMP Name: | Dbswitch1 | | IP Address: | 192.168.1.2 | | Subnet Mask: | 255.255.255.0 | | Manageable? | Yes | | Duplex capable? | Yes | | VLAN definition(s): | Default VLAN | | Broadcast controls? | No | | Filters? | No | | Any non-default settings? | Ports 9-45 are presently set to auto detect speed and half/full duplex operations. These ports are populated with workstations and printers. Ports 5- 8 are set to full duplex / 100Mb for connections to the repeaters (repeaters only capable of half duplex operations) in other parts of the complex, (Closet(s) B, C, D). |
List all port assignments for each hub/switch: | Hub/Switch 1: Cisco Catalyst 2948G-L3 | | 1 | Router | 25 | Workstation | | 2 | None | 26 | Workstation | | 3 | None | 27 | Workstation | | 4 | None | 28 | Workstation | | 5 | DB2KAD1 | 29 | Workstation | | 6 | DB2KAD2 | 30 | Workstation | | 7 | DB2KFS1 | 31 | Workstation | | 8 | DB2KWEB1 | 32 | Workstation | | 9 | None | 33 | Workstation | | 10 | None | 34 | Workstation | | 11 | None | 35 | Workstation | | 12 | None | 36 | Workstation | | 13 | None | 37 | Workstation | | 14 | None | 38 | Workstation | | 15 | HP LaserJet 4M | 39 | Workstation | | 16 | HP LaserJet 4000 | 40 | Workstation | | 17 | HP LaserJet 4000 | 41 | Workstation | | 18 | HP LaserJet Color 4050 | 42 | None | | 19 | HP OfficeJet 720 | 43 | None | | 20 | Workstation | 44 | None | | 21 | Workstation | 45 | None | | 22 | Workstation | 46 | None | | 23 | Workstation | 47 | None | | 24 | Workstation | 48 | None | Complete the following information about your firewall: | Router/Firewall Model: | | | IP Address | Subnet Mask | | Fast Ethernet 0/0: | 203.72.26.21 | 255.255.255.248 | | Fast Ethernet 0/1: | 192.168.1.254 | 255.255.255.0 | | | | | Password: | R5y3ds7f3Z | | | | | NAT Translation | | IP Address | Assignment | | 203.72.26.17 | NAT Translation | | 203.72.26.18 | NAT Translation | | 203.72.26.19 | (Open) | | 203.72.26.20 | 192.168.1.4 | | 203.72.26.21 | Router External Interface | | 203.72.26.22 | DSL Interface | | | | | Ports Open: | | IP Address | Port(s) | | 203.72.26.20 | SMTP, POP3, WWW, FTP, DNS, 3389 | | | |
2. Hardware Environment Complete the following information regarding all existing server hardware, which will interact with the Citrix MetaFrame environment. | Name: DB2KAD1 Model: Compaq ML 530 Role: Active Directory Domain Controller | | Form Factor Rack Mount Processor 2 933MHz, Pentium III Xeon processors with 256KB level 2-Advanced Transfer Cache. Memory 1 GB 133 MHz ECC SDRAM expandable to 4GB using 512 MB modules Network Controller - NC3123 Fast Ethernet NIC PCI 10/100 controller Drive Bays Four total 5.25" removable media bays (1) 1.44 MB floppy drive. One, is used for a 48x CDROM drive and another for a Compaq Internal DLT 20/40 Internal Storage -218.4 GB Maximum Internal Hot Plug Storage Ultra2 and Ultra3 ready. Three 18.2 GB Hot Plug Ultra 3 hard drives are installed. Drive Controller - One Smart Array 4200 4-channel array controller configured for RAID 5 data protection. - Interfaces - One RJ-45 Ethernet port, two serial, one parallel, keyboard, mouse, and one graphics port, and external SCSI through knockout.
| | Name: DB2KAD2 Model: Compaq ML 530 Role: Active Directory Domain Controller | | Form Factor Rack Mount Processor Two 933MHz, Pentium III Xeon processors with 256KB level 2 Advanced Transfer Cache. Memory 1 GB 133 MHz ECC SDRAM expandable to 4GB using 512 MB modules Network Controller - NC3123 Fast Ethernet NIC PCI 10/100 controller Drive Bays Four total 5.25" removable media bays (1) 1.44 MB floppy drive. One, is used for a 48x CDROM drive and the other for a Compaq Internal DLT 20/40 Internal Storage -218.4 GB Maximum Internal Hot Plug Storage Ultra2 and Ultra3 ready. Three 18.2 GB Hot Plug Ultra 3 hard drives are installed The Smart Array 5300 128 Cache Module with RAID ADG is configured for RAID 5. - Interfaces - One RJ-45 Ethernet port, two serial, one parallel, keyboard, mouse, and one graphics port, and external SCSI through knockout.
| | Name: DB2KFS1 Model: Compa1 ML 530 Role: File Server | | Form Factor Rack Mount Processor Two 933MHz, Pentium III Xeon processors with 256KB level 2 Advanced Transfer Cache. Memory 1 GB 133 MHz ECC SDRAM expandable to 4GB using 512 MB modules Network Controller - NC3123 Fast Ethernet NIC PCI 10/100 controller Drive Bays Four total 5.25" removable media bays (1) 1.44 MB floppy drive. One, is used for a 48x CDROM drive and another for a Compaq Internal DLT 20/40 Internal Storage -218.4 GB Maximum Internal Hot Plug Storage Ultra2 and Ultra3 ready. Three 18.2 GB Hot Plug Ultra 2 hard drives are installed Drive Controller - The Smart Array 5300 128 Cache Module with RAID ADG is configured for RAID 5. - Interfaces - One RJ-45 Ethernet port, two serial, one parallel, keyboard, mouse, one graphics port, and external SCSI through knockout.
| | | | Name: DB2KWEB1 Model: Compaq ML 360 Role: Web Server | - Form Factor Rack Mount
- Processor Pentium III 1.40GHz with 512k cache FC-PGA 1
- Memory 1 GB 133 MHz ECC SDRAM expandable to 4GB
- Network Controller - NC3123 Fast Ethernet NIC PCI 10/100 controller
- Drive Bays Four total 5.25" removable media bays (1) 1.44 MB floppy drive. One, is used for a 48x CDROM drive and another is used for a Compaq Internal DLT 20/40
- Internal Storage - 2 x 1" Ultra3 Hot-Plug available. Two 18.2 GB Hot Plug Ultra 3 hard drives are installed.
- Drive Controller - Integrated Smart Array 5i Controller, with 32MB memory
- Interfaces - two serial, one parallel, keyboard, mouse, one graphics port and external SCSI through knockout.
- Network Interfaces: 2 Compaq NC7780 Gigabit Ethernet NIC Embedded 10/100/1000
|
3. Operating Systems Environment Complete all information regarding your OS environment. | Domain Configuration | | Active Directory or NT Domain? | Active Directory | | (NT Domains) Domain Model (Single domain, Master domain, Multiple-master, etc.): | N/A | | (Active Directory) What Mode (native or mixed)? | Native | | (Active Directory) Forest Name(s): | DABCC.COM | | (Active Directory) Domain Name(s): | DABCC.COM | | (Active Directory) DNS Namespace(s): | DABCC.COM | | (Active Directory) Internal Namespace(s): | DABCC | | DNS Server Name(s): | DB2KAD1, DB2KAD2 | | WINS Server Name(s): | DB2KAD2 | | DHCP Server Name(s): | DB2KAD2 | | TCP/IP Addresses | | Enter the IP Address information for your network: | | Network Address: | 192.168.1.0 | | Subnet Mask: | 255.255.255.0 | | Gateway: | 192.168.1.254 | | Primary WINS: | 192.168.1.1 | | Secondary WINS: | None | | Primary DNS: | 192.168.1.1 | | Secondary DNS: | 192.168.1.2 | | Enter the IP Addresses for the servers you specified in the Hardware Environment section: | | DB2KAD1 | 192.168.1.5 | | DB2KAD2 | 192.168.1.6 | | DB2KFS1 | 192.168.1.71 | | DB2KWEB1 | 192.168.1.8 | | Enter the IP Addresses for all applicable networked printers: | | HP 4M | 192.168.1.15 | | HP 4000 | 192.168.1.16 | | HP 4000 | 192.168.1.17 | | HP LaserJet 4050 Color | 192.168.1.18 | | HP OfficeJet 720 | 192.168.1.19 | | Enter the DHCP Range: | | DHCP Range: | 192.168.1.100 through 192.168.1.200 |
| Active Directory Organizational Units (if applicable) | | Name of OU | Description | | Built-in | Default OU | | Computers | OU for end-user devices | | DABCC Users | OU for DABCC.COMs Microsoft Windows 2000 Active Directory Users and groups. | | Domain Controllers | OU for Windows 2000 Active Directory Domain Controllers. Includes: DB2KAD1 and DB2KAD2. | | Foreign Security/Principles | Default OU | | Servers | OU for Windows NT/2000 servers. Includes: DB2KFS1 and DB2KWEB1 | | Users | OU default Active Directory Users and groups. |
| Group Policy Information (if applicable) | | Using WinNT or Win2000 policies? | Win2000 | | Policy File(s) Location: | \\DB2KAD1\Policies\w2kconfig.pol | | Groups/Users affected by policies: | Administrators, Users | Attach the code for all login scripts here: Logon_users.cmd 
Logon_admins.cmd 
Enter all pertinent Domain users and groups here: | Domain User/Group Information |
Group Name | Group Type | Members | | Domain Admins | Security Group - Global | Administrator Douglas Brown Jim Worthington | | Enterprise Admins | Security Group - Global | Administrator Douglas Brown | | Schema Admins | Security Group - Global | Administrator | | Web Site Users | Security Group - Global | Douglas Brown Jim Worthington Lonnie Huffaker Andy Klopf Troy Gentry Helen Tamasi Chad McGrath Dan Morrow Scott Houseman Mark Nall Douglas Shreve Rob Voss Scott Duer Chad Kunz | | FTP Users | Security Group - Global | Douglas Brown Barry Brown Jim Worthington Lonnie Huffaker Chad Kunz Troy Gentry Helen Tamasi Andrea Madsen Chad McGrath Dan Morrow Scott Houseman Mark Nall Douglas Shreve Rob Voss | | Domain Users | Security Group Global | Douglas Brown Jim Worthington Lonnie Huffaker Chad Kunz Troy Gentry Chad McGrath Andrea Madsen Dan Morrow Scott Duer Scott Houseman Mark Nall Douglas Shreve Rob Voss GuestFTP GuestWEB | | | | | 4. Printing Environment Complete all information regarding your printing environment: | Printer Name | Print Server Name | Driver | | HP4M | DB2KFS1 | HP 4M | | HP4000West | DB2KFS1 | HP 4000 | | HP4000East | DB2KFS1 | HP 4000 | | HPColor | DB2KFS1 | HP LaserJet 4050 Color | | HPOfficeJet | DB2KFS1 | HP OfficeJet 720 | 5. Client Environment Complete all information regarding your client workstation environment: | Group Policy Information (if applicable) | | Internal Workstation Operating System(s): | Windows 2000 Professional (office standard) Windows 98 (legacy apps and device support) | | Remote Workstation Operating System(s): | Windows 2000, Windows ME, 98 and 95, Apple Macintosh, other personal devices | | Remote connectivity methods available: | Wireless, dial-in, DSL, cable, and TCP over the Internet | 6. Change Control Environment Complete all information regarding your change control procedures and environment. DABCC.COM currently does not have any changes control mechanism is in place. D&D Consulting will implement basic change control policies and procedures, which are part of the MetaFrame XP rollout. | |
|