|
| In my opinion, the analysis phase is the most important phase in the process. When you complete it successfully, you will be well on your way to a successful deployment. The goal for the analysis phase is twofold: First is to prepare yourself with all of the information you will need to successfully plan, implement and rollout MetaFrame in the proposed environment. Second is to present this to your customer in the form of a Project Plan and Infrastructure Assessment. The analysis phase is usually broken down into the following four segments: Vision / Project Scope (Statement of Work) Project Plan Infrastructure Assessment Proof of Concept Deliverables are created for each of the above segments upon completion of that segment. I have also been known to call the Analysis phase the setting expectations phase. What I mean is that during the process of completing each of the segments, you will be spending the bulk of your time in meetings with your customer asking questions and setting the rules for the project. Being a big fan of analogies, I like to explain it like this: If two parties are playing a game and have a small wager on the outcome and one set the rules and draws the playbook, which one would you bet on? Obviously, the one who makes the rules and draws the plays! With a little experience and the right know how, you will be able to set the rules to your advantage and guide your projects towards successful completions. The following is an example of an Analysis Phase Overview: | 1. Analysis Overview This Analysis Phase document is the first deliverable of the MetaFrame XP project and will explain the projects high-level Vision/Scope. This document is as follows: Project Vision (Statement of Work) Project Scope Estimated Project Plan Infrastructure Assessment Findings Proof of Concept Findings | The first section you will address is performed prior to any obligation from the customer. In this section, you will create the vision and define the Project scope in the form of a Statement of Work (SOW). To define the vision is to define the project. It is the business reason you are deploying MetaFrame, i.e. the benefits that your customer is expecting to receive from a successful deployment. All decisions made throughout the lifespan of a project will be verified against the vision. A vision is derived from your customers goals and business case for the project. You will need to set up a meeting with the customer to identify and quantify this. You will need to discuss what they see as the goals of the project are and you will need to make sure that you are setting the proper expectations. In most cases, the customer might not understand completely what they want to accomplish. If this is the case, you will need to sit down with the customer and explain what MetaFrame can and cannot do for them. Then and only then will you be able to create a high-level list of goals that the deployment will address. Once documented, make sure that your customer reviews the Vision and signs off on it. Only then will you be ready to start on the project scope. I like to break the project scope down to what I call in scope, out of scope. This is probably the second most important element of the project, so be very careful in creating it. You do this by creating a table that lists the vision and then break the project into five project management phases in which you will list the tasks that will need to be performed in order to achieve the vision. In the scope you need to list what you are responsible for, what you are NOT responsible for, what the customer is responsible for and the resources that you will be utilizing throughout the project. For example, if you are deploying MetaFrame for both LAN and WAN access, you will need modifications to the firewall that requires you to document who is responsible for those changes. In some cases, this may be you, but more often, you will need to work with the party who is responsible for the routers/firewalls. In this case, you will document the changes required and more importantly, who in the router/firewall group is responsible for what tasks and by what date. Scoping of the project is something you will get better with over time, it is important for you to understand that the project scope. Also note that Methodology in a Box is just a starting point to turn you on to project management. In future versions I will be explaining more on this subject but in the mean time please refer to numerous project management site around the web and Citrix Consulting Services documentation for more information on this and other subjects found throughout this document. You will also create a list of applications that will be deployed. This will assist in defining the Project Plan and Proof of Concept and help you determine the time it will take to deploy in completing the project. You will want to make the SOW as comprehensive as possible and then present it to your customer in the form of a formal document during a formal meeting setting. It is important to get the individual or group(s) responsible involved, as it gives them a stake in the project. Your customer will now have the opportunity to engage your services and continue with the MetaFrame project as documented in the SOW. Throughout the lifespan of a project, it will probably be necessary to modify the project scope to meet the goals of the vision based on new information found, decisions made or applications added. If this is necessary, you will need to have the customer sign off on a change request, modify the scope and the estimated time for completion. A successful project is one that not only achieves the vision but one that comes in on time. From my experience, scope additions can and will cause a project to come in over the estimated time and dollars amount. If you present your customer with the knowledge that an addition to the scope will result to a change in the time estimate, then you will have set the proper expectations. Remember that in creating the scope, you are creating the rules and plays of the game and need to be as thorough as possible.
The following is an example of a basic Statement of Work. |  Statement of Work
November 5, 2002 Executive Sponsor: Douglas Brown, Owner Project: MetaFrame XP application server deployment DABCC.COM would like to have centralized management of their Citrix MetaFrame Extended Platform (XP) based application servers. The ability for rapid deployment is one of the primary goals for implementing MetaFrame XP. DABCC.COM currently has a network infrastructure in place to electronically communicate with remote sites. DABCC.COM would like to make it easier for the end-user to securely connect to remote applications from any location at any time. This vision includes the following key objectives: Enhance application availability for end-users both locally and remotely by providing a secure, reliable, stable, and efficient application deployment system. Reduce administration, support and operational costs of supporting front-end workstations. Provide value added services now and in the future including portal services that will provide for team collaboration, document management, conferencing services and other web and MetaFrame applications Increase productivity of employees by providing them with a comprehensive application system. Provide reliable printing from any application to both local and remote devices. Take advantage of the newly implemented corporate wide Windows 2000 Active Directory. Project Scope | | | | Project Plan | Prepare and document detailed project plan. | | Infrastructure Assessment | Prepare for assessment questions and inquiry. Schedule times and meetings with DABCC.COM personnel for questions and inquiries. Document and present assessment. | | Analysis Phase Checkpoint | Prepare for and schedule meeting with DABCC.COM for a formal presentation of the Analysis Phase deliverable. | | | | | | | | Server Requirements | | | MetaFrame Design | | | Network Design | |
Design Phase Checkpoint | Prepare for and schedule meeting with DABCC.COM for a formal presentation of the Design Phase deliverable. | | | | | Develop installation procedures & Build initial MetaFrame environment | | | Implementation Phase Checkpoint | | | | | | | | | | | | | | | Test, Test, Test | | | Production Pilot | | | Rollout Additional Servers | | | Change Management | | | Readiness Phase Checkpoint | | | | | |
| | | | End-User Training | | | Administrator Training | | | Go Live | | | Rollout Phase Checkpoint | | | | | Out of Scope | Proof of Concept | | | Router Configuration | | | VPN Configuration | | Proposed Applications | Microsoft Office XP (Access, Excel, Outlook, PowerPoint, Word) Microsoft Visio 2002 Symantec Corporate Edition Antivirus 8.0 Adobe Acrobat Reader 5.0 Microsoft Exchange 2000 Admin Tool Microsoft Active Directory Administration Tools WinZip 8.0 |
Analysis Phase estimated 40 hours starting 11/8/02 Design Phase estimated 40 hours starting 11/15/02 Implementation Phase estimated 40 hours starting 11/22/02 Readiness Phase estimated 40 hours starting 11/29/02 Rollout Phase estimated 40 hours starting 11/5/02
Estimated time to project completion: 200 hours Estimated project labor cost at $ 25,000
| Accepted by: D&D Consulting | | | Accepted by: DABCC.COM | | | | | | | Authors Signature | | | Signature | | | | | | | Title | | | Title | | | | | | | | Date | | | Date | | | | | | | | | | | | Managers Signature | | | Street Address | | | | | | | | | | Phone number for Key Contact | | | | | | | | | | | | | | | | | | | | | |
| Important! The above example an example of a specific deployment and it is important to remember that every deployment is different and you will need to adjust your project vision / scope on a project-by-project basis. In other words time and effort are listed here for illustration purposes only. 3. Project Plan Now that you have finalized the Vision / Scope, you need to expand the scope and develop a detailed list of the tasks to be completed. The desired audience for this document is the LAN/WAN Engineer who is not a project manager. Therefore, I will provide two options for creating a comprehensive project plan; by hand or with Microsoft Project. I know that not everybody is a MS Project expert, but I highly recommend spending the time necessary to learn how to use it, as it is not that difficult. When I first started creating projects for my jobs, I did everything by hand (Microsoft Word). Then I went out, picked up a Dummies guide to Microsoft Project, and was blown away by how much easier it made my job. Please peek at it; I think you will be impressed with what you find. Your project plan should consist of a list of every task that needs to be completed. Each task should consist of the name and phone number of the individual responsible, any other parties that are needed to assist and an estimated timeframe for completion. You should do this for each task in your project and with as much detail as possible. Remember, it is necessary to go into as much detail as possible in order to set the proper expectations and to provide the necessary framework required to complete the project. When estimating the time allotted for each phase, be very careful not to underestimate. Time estimation is far from an exact science. Remember to leave time for application tuning and troubleshooting. In case you underestimate this, you will need to discuss with the customer any additional time needed to complete the project and why. At the end of the Analysis phase, you will have a completed project plan. Next, you need to setup a meeting with your customer and have them sign off on the overall plan. It is also important to make sure that your customer knows the project plan is not set in stone. You will probably need to add or subtract items or go into greater detail as you move through the Design and the Implementation Phases. Each time you make a change you will need to inform all parties and supply them with an updated copy of the plan.
The following is a basic project plan for a small to medium size MetaFrame deployment: | 3. Project Plan The following is an estimated Project Plan: | Task | Owner | Estimated Time | | | | Analysis Phase | 1 Week | | Create Vision | D&D Consulting | .5 days (pre project) | | Create Scope (in scope / out of scope) | D&D Consulting | .5 days (pre project) | | Infrastructure Assessment. Prepare for assessment questions and inquiry. Schedule times and meetings with your customer for questions and inquiry. Review the following areas: o Network Environment. o Hardware o Operating Systems o Printing Environment. o Client Environment Document and present assessment. | D&D Consulting | 4 days | | Proof of Concept (if applicable) Schedule meeting to define goals and tests for the Proof of Concept (POC). Setup and document the POC environment. Conduct tests to achieve the goals of the POC. Make any changes necessary to achieve the goals. Document and present findings | D&D Consulting | 1 day | | Analysis Phase Checkpoint | D&D Consulting, Net Admin, Management | .25 day | | Design Phase | 1 Week | | | D&D Consulting | 1 day | | | D&D Consulting | 2 day | | | | | | | | |
| D&D Consulting | 2 day | | Design Phase Checkpoint | D&D Consulting, Net Admin, Management | 2 hours | | Implementation Phase | 1 Week | | Create network shares | D&D Consulting, Net Admin | 1 hour | | Firewall modifications | Dan Morrow | 1 hour | | Configure switch port settings | D&D Consulting, Net Admin | 1 hours | | Add / configure users for a Terminal Services environment. | D&D Consulting, Net Admin | 1 hours | | Create Data Store | D&D Consulting, Net Admin | 1.5 days | | Unpack and prepare hardware | D&D Consulting, Net Admin | 5 hours | | Install and Configure base operating system | D&D Consulting, Net Admin | 2 hours | | Install and Configure MetaFrame XP | D&D Consulting, Net Admin | 3 hours | | Create Image | D&D Consulting, Net Admin | 2 hours | | Deploy Image on second test server | D&D Consulting, Net Admin | 3 hours | | Install Applications | D&D Consulting, Net Admin | 1 day | | Configure ICA Client update configuration utility | D&D Consulting, Net Admin | 1 hour | | Configure Printing Environment Configure print compatibility mappings Configure network print server assignments Configure Universal Print Driver | D&D Consulting, Net Admin | 2 hours | | Implement Policies | D&D Consulting, Net Admin | 3 hours | | | | | | | | | | Install Terminal Services licenses | D&D Consulting, Net Admin | 1 hour | | Install and Configure and secure IIS web server | D&D Consulting, Net Admin | 4 hours | | Install NFuse Classic 1.71 Web Extensions | D&D Consulting, Net Admin | 3 hour | | Implementation Phase Checkpoint | D&D Consulting, Net Admin, Management | 2 hours |
Readiness Phase | 1 Week | | Pilot and Test Develop Test Procedures Determine and train test users Launch Pilot and run test procedures Obtain Pilot Users feedback (forms, surveys, reports and observations) Evaluate Pilot Results and change design or processes if needed and then repeat the previous two steps. | D&D Consulting, Net Admin | 2 days | | Rollout Any Additional Servers | D&D Consulting, Net Admin | 7 hours | | Implement Change Management Policies and procedures | D&D Consulting, Net Admin | 1 hour | | Pilot and Test entire network as documented about | D&D Consulting, Net Admin | 2 day | | Readiness Phase Checkpoint | D&D Consulting, Net Admin, Management | 2 hours |
Rollout Phase | 1 Week | | Train Admin Staff | D&D Consulting, Net Admin | 1 day | | Train End-Users | D&D Consulting, Net Admin | 1 day | | Go Live | D&D Consulting, Net Admin | 1 day | | Gather Feedback | D&D Consulting, Net Admin | 1 day | | | | | | | Estimated Time to Completion: | 160 hours | | IMPORTANT! The above times are just an example and in no way reflect any baseline for deploying an application. Time and effort will vary. 4. Infrastructure Assessment The infrastructure assessment section of the Analysis phase is one of the most overlooked sections of a successful project but is one of the most important to the perception of performance. From my experience, a MetaFrame deployment will augment the environment you deploy it to. What I mean by this is that if you place a MetaFrame farm in a poorly laid out network you will most likely experience 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 a rollout of MetaFrame and identify the ones where more attention is needed. 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 let you achieve the vision. 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. Citrix 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: Window 2000 - 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. q 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. q 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 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 liked 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 5, 2002 Client: DABCC.COM Executive Sponsor: Douglas Brown, Owner Project: MetaFrame XP Application Server 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. 1. What network topology do you currently have in place (Ethernet, Token Ring, etc.)? Ethernet 2. 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. 3. 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). |
4. 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 | 5. 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 Andy Klopf 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 Sara Smith Dan Morrow Andrea Kimmel 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. | In a Proof of Concept, (POC) you will want to create a small MetaFrame test environment to prove to your customer and yourself that a MetaFrame rollout is able to meet the vision set forth, i.e., if your vision is to deploy home grown application to doctors while adhering to HIPPA complicacy, then you will want to verify that the home grown application is compatible. A common attitude towards a POC is one of Why I already have those applications working? Unfortunately, this attitude misses the intention of a POC. Simply focusing on applications is only part of what a POC is intended to accomplish. Additionally, a POC can be used to evaluate almost any open question or risk uncovered through the infrastructure assessment, including: New methods for deploying applications Evaluate load/scalability Evaluate new software/application combinations Evaluate new configurations and server build procedures New users / user groups New client devices or methods of deploying applications Evaluate security configurations It is critical that you clearly understand the objective and intention of a POC, and not focus on strictly your existing deployment. The POC focuses on what is new, even if old elements must be integrated to ensure a complete evaluation. If you will be conducting a POC, you will want to break it down into the following four phases: 1. Develop Tests: Call a meeting with your customer to define the tests and acceptable results thresholds. 2. Create Test Environment Start with a clean server, build a MetaFrame server, install any applications that are in question and run the tests that you defined in step 1. Note: You should document all of the steps taken during the creation of the test environment. It will be used later and added to the disaster recovery documentation. 3. Make adjustments as necessary Once you have run your first round of tests you will want to take a step back and determine where tuning is needed in order to meet the vision. 4. Document findings You will want to take the documents you created during step 2 and formalize them in form of OS and application installation procedures. You will also want to document any issues you may have found and your recommendations for resolving them. This is the last item in the Analysis phase, you are now ready to take your Proof of Concept document and present it as part of the Analysis Phase deliverable. Important! Please note that the Proof of Concept section of this document is still a work in progress and that I will be adding to it in great detail in the next release of MIAB! In the mean time please refer to POC documentation found freely throughout the Internet and also to any Citrix Consulting Services documentation on this subject. Now that you have completed the Statement of Work, created a project plan, infrastructure assessment, started to design a project plan and finished the proof of concept, it is time to present your findings to your customer. You will deliver documentation that will be presented to your customer during a formal meeting. In addition, you thought that we where never going to have any fun. The Analysis Checkpoint document should contain the following sections: Preface Vision / Scope (Statement of Work) Infrastructure Assessment findings Proof of Concept assumptions and findings Statement of Work that defines scope, deliverables, estimated duration and costs for the design, Implementation, Readiness and Rollout phases. You should assemble all the key players in the project, along with any of the money people and present the project and estimated times for completion. At this point, your customer can choose to continue with the project or bow out gracefully with the knowledge they have learned about their environment for use in a future MetaFrame deployment. In the second case, you will walk away with a slew of service dollars and a significant amount of additional knowledge and experience. You will also leave with the knowledge that you are now a true consultant and not just a break/fix engineer. You will find the following examples and templates located in Methodology in a Box 2.1. (MIAB2.1.ZIP) | Path \ Filename | Description | | \Examples\EXAMPLE Statement of Work.doc | Example of a Statement of Work. | | \Examples\EXAMPLE - Infrastructure Assessment.doc | Example of a basic Infrastructure Assessment | | \Examples\EXAMPLE Analysis Phase Deliverable.doc | Example of an Analysis Phase Deliverable. | | | | | Templates\TEMPLATE Statement of Work.dot | Microsoft Word Template file for a Statement of Work deliverable. | | TEMPLATE - Infrastructure Assessment.dot | Microsoft Word Template file for an Infrastructure Assessment | | Templates\TEMPLATE Analysis Phase Deliverable.dot | Microsoft Word template file for an Analysis Phase deliverable. | |