|
| In a Proof of Concept, (POC) you will verify the assumptions to prove to your customer and yourself that the MetaFrame Access Suite rollout is able to meet the vision set forth. You will do this by creating a small test environment. i.e., if your vision is to deploy home grown applications to doctors while adhering to HIPPA complicacy, then you will want to verify that the home grown application is compatible in a MetaFrame XP environment. It is very common for one to confuse a Proof of Concept with the Pilot. Please dont as they are very different in both vision and scope. A Proof of Concepts goal is to prove any assumptions in a non production environment with no end-user involved. Where a Pilots goal is to verify, on the production network with live data and real end-users, that the vision of the project in being addressed. 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 XP 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 during the implementation phase. 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, when completed you will be ready to take your Proof of Concept document and compile it in with the rest of the documentation you created earlier to create the finial Analysis Phase deliverable.
The following is an example of a basic Proof of Concept document:
 Proof of Concept
November 7, 2003 Client: DABCC.COM Executive Sponsor: Douglas Brown, Owner Project: Citrix MetaFrame Access Suite Deployment The Proof of Concept (POC) phase of the project is designed to determine the capabilities of the proposed MetaFrame Access Suite deployment to achieve the vision of the project. During the POC, a prototype MetaFrame Access Suite environment is built, complete with all necessary applications, printers, etc. The applications are then exhaustively tested to evaluate their functionality in a MetaFrame XP/Terminal Server environment. For each item, results are documented and necessary adjustments are made. This document is a summary report of the POC procedures. This Proof of Concept document is divided into the following sections: Environment Specifications Environment Setup Procedures Test Cases Test Case Adjustments Conclusion
1. Environment Specifications 1. 2. Hardware Environment | Name: DB2KCTX1 Model: Compaq ML 530 Role: Citrix MetaFrame XP 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 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: DB2KWEB1 Model: Compaq ML 530 Role: Web Interface Web 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 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.
|
1. 3. Operating Systems 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.7 | | DB2KWEB1 | 192.168.1.8 | | DB2KCTX1 | 192.168.1.9 | | 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. | | Domain User/Group Information |
Group Name | Group Type | Members | | Domain Admins | Security Group - Global | Administrator Douglas Brown Jim Worthington | | Proof of Concept 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 | | Group Policy Information (if applicable) | | Using WinNT 4.0 or Win2000 policies? | Win2000 | | Policy File(s) Location (for WinNT 4.0 policy): | N/A | | Groups/Users affected by policies: | Administrators, Users |
1. 4. Login Scripts Logon_users.cmd 
Logon_admins.cmd 
1. 5. 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 | 1. 6. Client 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 |
2. 0. Environment Setup Procedures 2. 1. Server Build Procedures The Citrix MetaFrame Access Suite Server and all other servers used in the Proof of Concept will be configured to production standards according to D&D Consulting methodology, including server security and optimization. This is done so that if the Proof of Concept is successful, the server environment will become the foundation for the production MetaFrame Access Suite deployment. For details regarding the design of the MetaFrame XP, MetaFrame Secure Access Manager, Web Interface, or the Secure Gateway for MetaFrame, refer to the MetaFrame Access Suite Design document provided by D&D Consulting. The following is a basic checklist for a MetaFrame XP server: q Install Server Operating System with latest Service Pack and necessary Hotfixes | |