| The design phase is where you utilize the information obtained during the analysis phase to design the layout of your MetaFrame network. In designing the network, you should stick to the basic principals of Simplicity and Future Growth. A good project is a simple and straightforward one that anticipates future changes in the environment. A shortcoming I have found in analyzing networks is that, networks are designed for today and not tomorrow. Even if you consider todays deployment as a small one, you will still want to design for tomorrow. This gives you the ability to anticipate future growth. The Design Phase document will document the architecture that will be implemented during the Implementation phase. The key sections of these documents are outlined below: Design Overview Server Design q Hardware Requirements q Operating Systems Requirements MetaFrame Design q Farm Design q Zone Design q Data Collector Design q Data Store Design q Load Management Design q Applications q Applications Delivery q Printing Architecture Network Design q File Storage q Logon Scripts q Network Modifications Note: It is important to remember that the following examples are just examples and every design is going to very depending on the project vision on client environment.
The following is an example of a Design Overview: | 1. Design Overview D&D Consulting has been engaged to design and assist in deploying Citrix MetaFrame XP Application Servers for DABCC.COM. The main technology areas covered in this document includes: q Server Requirements q MetaFrame Design q Network Design D & D Consulting will utilize a Project Management approach in order to achieve an optimum network design. Simplicity is the best investment. Simple structures are easier to explain, maintain and debug than complex ones. Every network created will require some maintenance over its lifetime. When you create a structure without well-defined reasons, it will end up costing than any value it may add. Therefore, it is important to carefully analyze and justify the structure required before beginning. Your business and your organization will always change. There are normal changes that occur within any organization such as changing applications requirements or enterprise-wide reorganizations that will affect DABCC.COMs MetaFrame XP architecture. When designing the architecture, consider how these potential changes will affect end user and administrators interaction with the farm. Make sure your design is general and flexible enough to accommodate constant and significant change. Aim for the ideal design. In your design and planning, you should aim for the ideal structure even if it does not reflect the current architecture plan. It is useful and practical to understand what would be ideal, even if it were not currently attainable. Below is a diagram of the planned native MetaFrame XP architecture: 
| The Server Design section consists of the following sections: Hardware Recommendations Operating System Requirements The following is an example of a Server Design Overview: | 2. Server Requirements The Server Design section consists of the following sections: Hardware Recommendations Operating System Requirements | The question that is asked for every project is What kind and/or how many Citrix servers do I need? This is a touchy subject and it all depends on a number of factors. It is not the purpose of this document to examine cost analysis and scalability testing, For the most part, a customer for this sized project will probably not want to incur the associated expense. However, it is important to make a determination from the information we have gathered and our experience in past installations. All MetaFrame environments are different and based on the data you collected from the Proof of Concept; you should be able to give your recommendations on server hardware. The following are my recommendations; anything more would be like shooting arrows in the dark. What type of and how many processors do I need? There are numerous processors to choose from in deciding what server hardware to purchase. A minimum of a single Pentium is required, but I recommend dual Pentium III or IV processor boxes for maximum performance in a cost effective manner. How much memory per server? From my experiences, I recommend 1GB RAM per CPU. This gives you the best bang for your buck and is ultimately more cost effective in the long run. How many servers do I need? This all depends on how many users you will be supporting, the amount of RAM each application requires, the type of applications you are running and how heavy the end users utilize the applications and numerous other factors. What I have always recommended is as follows: A MetaFrame server is an application server and the only data that needs to reside on it should be the applications executables. With this in mind, I believe in scaling out vs. scaling up and having N+1 instead of RAID controllers and redundant fans and power supplies. The money you save is best spent on an additional server for load balancing purposes. In other words if you have 40 concurrent users on two boxes and one drops off, you would want to make sure that the other server would be able to handle the additional 20 users load. If the remaining server(s) cannot hold the load then you will need to add another server to the farm. This guarantees your customer high availability. N+1 solves this perception issue. The following is an example of Hardware Requirements: | 2. 1 Hardware Recommendations Keeping to the vision of achieving high availability while achieving a very high user perception of performance, D&D Consulting specked the following hardware price quotation. | Hardware Price Quotation | | | | Quantity | Part Number | Product | Unit Cost | Total Cost | | | | HARDWARE | | | | | | | | | | 4 | 218789981 | Proliant DL360 PIII933/256k | $4,650.00 | $18,600.00 | | | | Pentium III 933MHz processor, a 256KB L2 ECC cache, an integrated Smart Array controller and 128MB PC133 Registered ECC SDRAM, expandable to 4GB. In addition to the 133MHz front bus speed, this server contains a 3.5" 1.44MB floppy disk drive, a 24X (max. speed) Slimline CD-ROM drive and two open PCI slots (one 64-bit/33MHz and one 32-bit/33MHz). Because there is no pre-installed hard drive, you are free to configure storage to fit your needs. The standard Wide Ultra2/Ultra3 SCSI drive cage supports up to two 1" Wide Ultra2/Ultra3 hot-plug hard drives, for a maximum Internal hot-plug capacity up to 72.8GB (2 x 36.4GB). | | | | | | | | | | 4 | 265447-B21 | P3-933 SECOND PROCESSOR KIT FOR DL360 | $1,298.00 | $5,192.00 | | 4 | 155646-001 | REMOTE INSIGHT LIGHTS-OUT EDITION | $486.00 | $1,944.00 | | | | | | | | 8 | 125669-B21 | 512MB REG SDRAM DIMM 133MHZ | $1,357.00 | $10,856.00 | | | | (STD MEMORY IS 128MB AND THERE ARE (3) EMPTY SLOTS) | | | | | | | | | | 8 | 142654652 | 9.1 PLUGGABLE WIDE ULTRA SCSI 3INT UNIVERSAL 10K | $453.00 | $3,624.00 | | | | | | | | | | Sub Total minus tax / Freight | | $40,216.00 | | | | | | |
| Note: Citrix does not recommend any particular hardware vendor. This would be driving by the customers preference and or corporate standard.
In this section, you will want to document the Operating System and MetaFrame version recommended with a preliminary price quote for the proposed operating system(s) and MetaFrame version and any additional client access licenses. The following is an example of the Operating System Requirements: | 2. 2 Operating System Requirements In keeping with the vision of achieving high availability while achieving a very high user perception of performance and stability, D&D Consulting, recommends Microsoft Windows 2000 Server and Citrix MetaFrame XPe. The following is a software quote for Microsoft Windows 2000, the appropriate client access licenses and Citrix MetaFrame XPe with the required amount of additional connection licenses. | | Citrix MetaFrame v1.0 XPe | | | | | | | | | | | | | 1 | EW22XPE0020 | XPe Starter Kit, includes 20 users w/ 1 yr subscription | $4,085.00
| $4,085.00 | | | | | | | | | | | | | Microsoft Windows 2000 Server | | | | | | | | | | | | | | | | | 1 | C11-00821 | Windows 2000 Server | | | | $710.00 | $710.00 | | |