Citrix MetaFrame XP
Feature Release 2
MetaFrame
Project in a Box
Version 2.5 Draft - October 12, 2002
Prepared by: Douglas A. Brown, MCSE, CCEA
Field Systems Engineer, Northern California
Citrix Systems, Inc.
NOTICE
The information in this publication is subject to change without notice.
This document represents a professional approach to successfully completing an IT project based on personal and professional experiences. This document is not officially endorsed, nor is it currently supported by Citrix Systems, Inc. I have written and compiled MetaFrame Project in a Box (MPIAB) in my spare time from many different sources found freely throughout the Server Based Computing World. MPIAB is intended to serve as one of many available resources that can be leveraged by small and medium businesses. The focus of this document, in addition to the process recommendations, is provide details on methods that can be used to deploy Citrix MetaFrame XP with Feature Release 2.
The high-level framework presented throughout this document is intended as a starting point, no more. The template is not intended as a replacement for professional services and experienced consultants. Enterprise clients embarking on large Citrix implementations should contact CCS, a CCCP or a CSN with proven Enterprise deployment skills.
THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. DABCC.COM SYSTEMS, INC.
(“DABCC.COM”), SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR DIRECT, INCIDENTAL, CONSEQUENTIAL OR ANY OTHER DAMAGES RESULTING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS PUBLICATION, EVEN IF DABCC.COM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES IN ADVANCE.
This publication contains information protected by copyright. Except for internal distribution, no part of this publication may be photocopied or reproduced in any form without prior written consent from DABCC.COM.
The exclusive warranty for any Citrix products discussed in this publication, if any, is stated in the product documentation accompanying such products. DABCC.COM does not warrant products other than its own. Product names mentioned herein may be trademarks and/or registered trademarks of their respective companies.
© 2002 DABCC.COM
All rights reserved. Printed in the good ole U.S.A!
Special Thanks!
This project is a by-product of everyone that I have had the pleasure of knowing and working with and a slew of awesome resources found by letting your fingers do the walking around the Internet. I must admit that one of the most important things I have learned throughout my life is that I am not to proud to learn from people. Someone once taught me to listen to anyone that wants to tell me their experiences, never to fear asking questions and to read every overview I can get my hands on and this document is made up of just that. I really hope you like it and find some knowledge in it.
I must also say thanks to the following awesome minds that sacrificed their time and gave of their knowledge to help create what you see before you. Without them, this project would not exist.
Rob Beekmans Matt Paler Tiwan A. Nicholson
Robin J. Brandl Greg Pontrelli Mark Verhagen
Barry Brown Tahir Saleem Rob Voss
Phu Hong David Lacote Frank Chen
John Nelson Stephane Lalonde Albert J. Hernandez
Roddy Rodstein Paul.B.Tisl Norm Erlendson
Deryck A Bodnarchuk Barry Flannigan Andrew Wilmot
Lori Hardtke Matt General
When I first started working on this document, I had a goal to create something that could have a
possibility of becoming bigger than the sum of its parts. Now that we are in version 2.5, I am seeing that this goal is coming true and it is because of the people found on this and the following page. This document would just not be possible without them. If I missed, someone then please let me know and I will make sure I give you the credit you deserve. Thanks!
Special thanks to Robert Voss. Rob has been a pivotal part of the creation of this project. He is only the second person to see this doc and in the last few months and days before the first release, he was the first person I would send copies too. Without his tireless contributions, this document would not be the same. Rob also continues to thank me for “letting him help” but really we all should thank him, so to Rob, I say, “quit thanking me… because I need to thank you.”
Special thanks to Tahir Saleem. Tahir contributed tons to this document. When I asked him if he would be interested in going over this document and what I had to date, I never imagined he would cause the creation of another fifty pages. Make sure you check out his awesome Administrative Template (MPIAB.ADM). Therefore, it goes without saying that Tahir has been crucial in the creation of this project.
Special thanks to Barry Brown. This project would not have been possible without his selfless
contribution in cleaning up my poor grammar and giving this document a sense of professionalism, not to mention putting up with my annoying phone calls.
Special thanks to Tiwan A. Nicholson. Tiwan supplied some awesome feedback and he provided the Infrastructure Analysis template. Needless to say, thank you!
Special thanks to Mark Verhagen. In version 2.0, I did not give Mark the credit he deserved. This guy helped me shape this document it to what became 2.0 and something that I’m very proud to have my name on. I don’t think that would have been possible if it was not for one, Mark Verhagen. Thank you, Mark! Special thanks to Robin J. Brandl. This is another correction to my thank you page, Robin contacted me very early in the development of this project and offered his awesome services in the form of the
Special thanks to Matt General. Matt has been giving me feedback on MPIAB from the get go and now he extended his awesome services to all of us in form of the Macintosh ICA Client sections. Even more than that, Matt is a great person, an exceptional asset to the Citrix extended family and has been more than a pleasure to work with for over the past year and a half. Thank you very much, Matt! The next one is on me…
Special thanks to Norm Erlendson. Norm is a colleague of mine and I am very proud to be able to say that. Norm has been given me some great feedback and even gave of his limited time to write up the Linux section of this document but then what do you except from a Canadian Citrix SE? Northern but perfection is par for that course.
Special thanks to Stephane Lalonde. Stephane is another one of my colleagues and just another reason why the SE team is the best team there is period. Stephane contributed the Office 2000 integration section and already I have had positive feedback on how it has overcome technical issues resulting in happier end users. Now that is what a Citrix SE does and does well. Thanks Stephane.
Special, Special thanks to Douglas M. Shreve, Jr. There is not a day that goes by that I do not use something that this man taught me. Doug is the real brain behind the concept of this document and the reason I am the SE and person I am today. Thanks Slice, I am forever in your debt.
I must say a bit of thanks to Rick Dehlinger. About two years ago, Rick started an eGroup for Citrix enthusiasts (CitrixNW), he spearheaded the development of Project Columbia and then he created his MetaFrame Tuning Tips document and in early April 2002, he released Project Willamette and www.TweakCitrix.com. Rick has made a huge difference in the world of Citrix integration and he has taught us all what we know and from the looks of it he is just getting started. When I came to Citrix, I wanted to do things like Rick so I guess this document is my feeble attempt to begin to attempt to follow in his footsteps. For all of you that know exactly what I am talking about, I challenge you to do the same!
Document Revision History
The third revision of MPIAB is a minor revision packed with a few new additions and a lot of fixes and suggestions from all of you.
Please stay tuned to http://www.dabcc.com/projectinabox for the latest version of this project and to this page for the latest editions to this document.
Please send all suggestions and or comments to [email protected].
Date Version Updated By Description of Changes 5/01/02 1.0 - Beta Douglas Brown &
Friends First Version
7/2/02 2.0 Douglas Brown &
Friends Added / changed the following: • Misc. grammar / typos corrections
• Infrastructure Assessment additions / corrections • Printing Architecture section
• I cleaned up the design phase to change it to reflect the addition of CSG and added a printer architecture section.
• SQL Server 2000 installation procedures
• MetaFrame XP with Feature Release 2 installation procedures for both new server builds and upgrades • Policies
• Citrix Web Console for FR2 • Cloning a FR2 server • Printing Section • NFuse 1.7
• Citrix Management Console
• AND a slew of other changes through the document. This release is really a total change.
11/1/02 2.5 Douglas Brown & Friends
Added / changed the following: • Installation Manager 2.2 • Recourse Manager 2.2
• How to Install & Configure Office 2000 and Office XP
• Changed the NFuse section to reflect the changes to NFC 1.7
How to Use MetaFrame Project in a Box 2.5
MetaFrame Project in a Box is a living document. This document was written for the Citrix integrator’s deploying MetaFrame in to small businesses and it is only a starting point. When I originally starting writing MPIAB I geared it toward integrators who are just starting out with project management but from the feedback I have received I’ve realized that it can help administrator’s and integrators of all skill-sets. Throughout this document, I have added links to more information that will assist in giving you more knowledge on the subject but if you are a customer or will be performing large-scale MetaFrame installation then sometimes there is no substitute for professional experienced services. MPIAB is not meant to be a replacement for professional services and or experienced consultants but it is aimed at giving everyone a bit more information and at opening your minds to Project Management, the way mine was. To use this document, I highly recommend taking the templates and examples and customizing them in to your own. Add on to the Pilot schema, and create your own implementation polices and procedures and best practices for your company to use in the future. I believe this will help take you from a "brake/fix" engineer in to a consultant.
I have written this document to be a starting point. If followed, it will help change the way you deploy MetaFrame. It will guarantee a successful outcome and at the same time help make a few more dollars in the process. However, remember that every project and environment is different and there is no simple broiler plate for all deployments; you will need to adjust the supplied documentation for every environment and fine tune as necessary.
Table of Contents
TABLE OF CONTENTS ...8
PREFACE...15
PROJECT MANAGEMENT...17
1. Project Management Overview... 18
2. Project Management Methodology... 19
3. What Makes an Effective Meeting? ... 20
ANALYSIS...21
1. Analysis Overview ... 22
2. Vision / Project Scope (Statement of Work)... 23
3. Project Plan... 28
4. Infrastructure Assessment ... 32
5. Proof of Concept ... 43
6. In Analysis - Checkpoint... 44
DESIGN ...45
1. Design Overview ... 46
2. Server Design ... 48
2. 1. Hardware Recommendations... 48
2. 2. Operating System Requirements ... 50
3. MetaFrame Design ... 51
3. 1. Farm Design ... 53
3. 2. Zone Design... 54
3. 3. Data Collector Design ... 56
3. 4. Data Store Design... 57
3. 5. Load Management Design... 60
3. 6. Applications... 61
3. 8. Printing Architecture ... 66
4. Network Design... 69
4. 1. File Storage... 69
4. 2. Logon Scripts... 70
4. 3. Network Modifications... 71
5. Design - Checkpoint ... 73
IMPLEMENTATION...75
1. Implementation Overview ... 76
2. Prepare the Network Environment... 77
2. 1. Create Required Network Shares... 78
2. 2. Firewall Modifications ... 79
2. 3. Throttling Port Speed and Duplex Settings ... 80
2. 4. Add Users to a Terminal Services Environment... 81
2. 4. 1 Terminal Server Home Directory ... 81
2. 4. 2 Terminal Server Profile Path ... 82
2. 5. Create Required Citrix Specific User Groups... 83
3. 3rd Party IMA Data Store Installation & Maintenance... 84
3. 1. How to Install & Configure Microsoft SQL Server 2000 Enterprise Edition... 85
3. 1. 1 How to Install Service Pack 2 for Microsoft SQL Server 2000... 91
3. 1. 2 How to Change the Default Login Authentication Mode ... 94
3. 1. 3 How to create the MetaFrame XP Data Store with SQL Server 2000... 97
4. Install Operating System... 101
4. 1. Installing Microsoft Windows 2000 ... 101
4. 1. 1 How to Install Microsoft Data Access Components... 105
4. 1. 2 How to Install the Windows 2000 Recovery Console ... 107
5. Install MetaFrame XP with Feature Release 2 ... 108
5. 1. How to Install Microsoft Windows Installer Service 2.0... 109
5. 2. How to Remap MetaFrame XP Server Driver Letters... 110
5. 2. 1 Reversing Remapped Drives ... 112
5. 2. 2 Known Issues with Drive Remapping ... 113
5. 3. How to Install MetaFrame XP with Feature Release 2 (Clean Install)... 114
5. 4. How to Upgrade to MetaFrame XP with Feature Release 2... 128
5. 5. How to Install Additional MetaFrame XP with Feature Release 2 Servers to a Farm... 133
5. 6. How to Add / Remove MetaFrame XP Components (IM, RM & NM) ... 136
5. 7. How to Add Licenses through the Citrix Management Console (CMC)... 138
6. Tweak Windows 2000 / MetaFrame XP ... 140
7. How to Install and Configure Microsoft Office 2000 ... 147
7. 1. How to Install Microsoft Office 2000 Resource Kit... 148
7. 2. How to Create a Custom Office 2000 Terminal Services Transform (MST) File... 150
7. 3. How to Execute the Microsoft Office 2000 Installation Program ... 162
8. Install “Image” Applications ... 163
9. Rapid Server Deployment... 164
9. 1. 1 Steps required to clone a MetaFrame XP Server ... 166
9. 1. 2 Workarounds for Cloning MetaFrame Servers with Remapped Drives ... 168
9. 2. Windows 2000 Unattended Install For Thin Client Servers ... 169
9. 2. 1 Hardware Configuration ... 169
9. 2. 2 Unattended Windows 2000 Setup and Configuration... 169
9. 3. How to Create a Network Boot Disk... 181
10. Install “Manual” Applications ... 186
11. Installation Manager 2.2 ... 187
11. 1. Installer Service ... 187
11. 2. Packager ... 188
11. 3. How to Install the Citrix Installer Service on a Target Server... 189
11. 4. How to Install the Citrix Packager Service on the Packaging Server ... 191
11. 5. How to Set the Root Build Location... 193
11. 6. How to Package an Application with Installation Manager... 195
11. 7. Restoring Packager to its Original State ... 200
11. 8. How to install a Package to a Citrix Server ... 201
11. 9. How to Add a MSI Package Through the CMC ... 203
11. 10. How to install a Service Pack with Installation Manager ... 205
12. Resource Manager 2.2... 206
13. How to Setup Automatic Reboot for MetaFrame Servers... 209
14. MetaFrame Delegated Administration... 213
14. 1. How to Add a New MetaFrame Administrator... 214
15. How to Set the MetaFrame Server Preference for Data Collector Elections... 216
16. How to Create a Zone & Move MetaFrame Servers to it ... 219
17. Citrix User Policies ... 223
17. 1. How to Create a New Citrix Policy ... 225
17. 2. How to Configure a Citrix Policy ... 226
17. 3. How to Assign a Citrix Policy to User(s) and or Group(s)... 227
18. How to Implement Automatic ICA Client Updates... 228
18. 1. How to Update the ICA Client Database with a ICA Client Images ... 229
18. 2. How to Update a Single ICA Client ... 231
18. 3. How to Configure the ICA Client Update Configuration Database ... 233
18. 4. How to Move the ICA Client Update Configuration Database ... 235
18. 5. How to Set ICA Client Updates on a User / Group Basis... 239
19. Client Drive Mapping... 241
19. 1. How to Configure Client Drive Mapping on a User / Group Basis ... 242
19. 2. How to Manually Map Client Drives ... 243
19. 3. How to Change the Default Client Drive Letter ... 245
20. How to Implement Client to Server Content Redirection... 247
21. How to Implement Server to Client Content Redirection... 249
21. 1. How to Implement Server to Client Content Redirection Farm Wide... 250
21. 2. How to Implement Server to Client Content Redirection per Server ... 251
22. Publishing through the Citrix Management Console... 253
22. 1. How to Publish an Application... 255
22. 2. How to Publish Content... 260
22. 3. How to Publish Application from a Shortcut... 262
22. 4. How to Publish the Printer Folder ... 263
23. How to Build a Stable Printing Environment ... 264
23. 1. Gather a List of Printers to be Supported ... 264
23. 2. Setup the Print Environment... 264
23. 2. 1 Configure the Printer Management Properties ... 265
23. 2. 2 Configure Network Print Servers and Assign Printers ... 269
23. 2. 3 How to Configure Autocreation of Client Printers on a User / Group basis... 272
23. 2. 4 How to Create a Network Printer for All Users... 273
23. 3. Create Printer Compatibility Driver Mappings... 277
23. 3. 1 How to Setup Printer Compatibility Driver Mappings ... 278
23. 3. 2 How to Import Printer Compatibility Mappings... 280
23. 4. Set Printer Bandwidth Limits for Client Auto-Created Printers ... 281
23. 5. How to be Proactive in Maintaining Driver Compatibility Mappings... 282
23. 6. How to use Project Compatibility to be proactive in Driver Mapping ... 284
23. 7. How to Manually Connect a Client Printer within an ICA Session... 286
24. NFuse Integration... 287
24. 1. How to Install NFuse Classic 1.7 Web Extensions (Clean Install)... 288
24. 2. How to Upgrade an Existing NFuse Server to NFuse Classic 1.7 ... 293
24. 3. How to Configure NFuse 1.7 through the Web Administration Tool... 294
24. 3. 1 MetaFrame Servers... 295
24. 3. 2 Authentication ... 298
24. 3. 3 Server-Side Firewall ... 302
24. 3. 4 Client-Side Firewall... 306
24. 3. 5 ICA Client Deployment... 309
24. 3. 6 ICA Customization ... 314
24. 4. How to Customize the Text and Graphics on the NFuse Web Site ... 315
24. 4. 1 How to Customize the Text Found on the NFuse Classic Default Web Site... 316
24. 4. 2 How to Customize the Graphics Found on the NFuse Classic Default Web Site... 317
24. 5. How to Repair NFuse Classic 1.7... 318
25. How to Secure an Internet Information Services (IIS) Server ... 319
25. 1. How to install and configure the IIS Lockdown Tool (version 2.1) ... 320
25. 2. How to Enable SSL on the NFuse IIS Web Server... 326
25. 2. 1 How to Create and Install a SSL Certificate with a Public Certificate Authority... 327
25. 2. 2 How to Create and Install a Certificate with Microsoft Certificate Server... 336
25. 2. 3 How to Add the Certificates MMC Snap-in ... 345
25. 2. 4 How to backup your SSL Certificate... 347
25. 2. 5 How to Restore a SSL Certificate... 351
25. 3. How to Force the use of SSL Encryption on the NFuse Web Site ... 357
26. How to Secure ICA Session Traffic with Citrix Secure Gateway (CSG) 1.1... 359
26. 1. How to Install and Configure the STA Component... 360
26. 2. How to Install and Configure the CSG Component ... 365
26. 3. How to Configure NFuse to Utilize Citrix Secure Gateway (CSG) ... 372
26. 4. Common Issues Encountered During Installation ... 375
27. MetaFrame XP Remote Administration Tools ... 376
27. 1. Citrix Management Console (CMC)... 377
27. 1. 1 How to Install the Citrix Management Console (CMC) ... 378
27. 2. Citrix Web Console (CWC)... 382
27. 2. 2 How to install the Citrix Web Console on a Standalone IIS Server ... 385
28. ICA Clients... 386
28. 1. How to Install the ICA Win32 Program Neighborhood Agent... 387
28. 2. How to Install the ICA Win32 Web Client... 392
28. 3. How to Configure the ICA Java Client... 393
28. 3. 1 How to Use a Private SSL Certificate with the ICA Java Client and NFC 1.7... 394
28. 3. 2 Troubleshooting the Java Client on machines running the Sun Java VM... 395
28. 4. How to Utilize the ICA Program Neighborhood Pass-Through Client ... 397
28. 5. How to Install the ICA Client on Redhat Linux 7.1 ... 398
28. 5. 1 Starting the ICA UNIX Client ... 401
28. 5. 2 Troubleshooting the Netscape UNIX Client Plug-in ... 404
28. 5. 3 Using Certificates for Connecting to CSG - SSL support... 405
28. 5. 4 Private Certificate Authorities ... 406
28. 6. Citrix ICA Client 6.20 for OS 9.X... 412
28. 6. 1 Installing the Citrix ICA Client 6.20 ... 412
28. 6. 2 Creating a Server or Published Application Connection ... 417
28. 7. Citrix ICA Client 6.30 for OS 10.x... 421
28. 7. 1 Installing the Citrix ICA Client 6.30 for OS 10.x... 421
28. 7. 2 Configuring the Citrix ICA Client 6.30 ... 423
29. Microsoft Terminal Services License Server ... 428
29. 1. How to Install and Activate a Terminal Services License Server... 429
29. 2. How to Hardcode a Preferred Terminal Services License Server... 432
30. Implement Windows System Policies ... 433
30. 1. MPIAB Administrative Template Overview ... 434
30. 2. How to Create an Administrative Template to Hide Drives... 444
30. 3. Implementing Windows 2000 Active Directory Group Policies ... 446
30. 3. 1 Prepare the Active Directory Environment... 447
30. 3. 2 How to Add / Edit Group Policies ... 452
30. 4. Implementing Windows NT, Terminal Server 4.0 System Policies ... 459
30. 4. 1 How to add Administrative Templates to the System Policy Editor... 462
30. 4. 2 How to create a System Policy with the System Policy Editor... 464
31. Implementation - Checkpoint... 469
READINESS...470
1. Readiness Overview... 471
2. Testing your New MetaFrame Environment ... 472
3. Pilot Implementation... 473
3. 1. Test Schema for pilot user / test user... 473
4. Rollout Any Remaining Servers... 480
4. 1. How to Activate Licenses through the Citrix Management Console... 481
5. Implement Change Management Policies and Procedures... 485
6. Readiness Phase - Checkpoint ... 486
1. Rollout Overview ... 489
2. End-User Training... 490
2. 1. Sample End-User Training Document... 490
3. Administrator Training ... 496
4. Go Live! ... 497
5. Rollout - Checkpoint ... 498
APPENDIX ...500
1. Additional Resources... 501
Preface
Welcome to what I call, “MetaFrame Project in a Box 2.5”. Version 2.5 is a minor revision packed with a few new sections and a lot of fixes and suggestion / clarification from all of you
Over my years implementing and supporting networks, I have been fortunate enough to learn that deploying a solution is much more than just installing the systems and configuring the clients. It is and needs to be seen as a project and a project needs a plan and someone to manage that plan. My goal for this document is to explain, as best I can, how to plan, implement, rollout and manage a successful Citrix MetaFrame XP deployment.
I have geared this guide toward small size deployments. It is meant to be a starting point to help the technicians and engineers who find themselves working in the trenches with no tangible plan for success. I know that I cannot possibly cover everything, but will try to touch on the points that I feel are the most important and have the biggest impact on the completion of a successful project. My intention is to pass on the base knowledge that is required while guaranteeing a successful outcome.
I have also tried to write this document in the same framework that your project will follow and throughout this document, I have presented real world examples from my personal experiences in deploying
MetaFrame and other software packages. To accomplish this I have created a fictitious consulting firm (D&D Consulting) and a customer called DABCC.COM to add a sense of realism to the examples. I have also documented systematic instructions on everything needed for a successful MetaFrame / NFuse deployment. My intentions are to make this a blueprint for a successful deployment!
This is also a living document. In this project, you will find a lot of information but it is far from
everything one would need and not even meant to be. It is meant to be a starting point, a process change to get you excited about the art of Project Management the way I am. I truly believe it can take you and your organization to the next level.
Finally, this guide is my attempt to give back a little to the community that had taught me so much. When I try to thank everybody who has helped over the years, I was asked to carry the word to others, the way they did for me. Therefore, to all you who have been a help and given so much to my growth, this document is for the next question boy, coming from you, through me…
Thank you and enjoy,
Douglas A. Brown, MCSE, CCEA
Field Systems Engineer, Northern California Citrix Systems, Inc.
1. Project Management Overview
One night while sitting in a bar in a small town in northwest Iowa, I was kicking back having a beer with a Senior Systems Engineer who was more than willing to share the knowledge he had learned over the past twenty plus years. This does not always happen, as some people want to horde their knowledge.
Fortunately, this gentleman wanted to teach and I was more than willing to learn. In between sips he looked at me and said something that I will never forget, he said, “Doug, you are a good engineer and can build a great network, but if the end-users don’t perceive it is a great network, then you will NEVER become a great engineer.”
I looked back at him, with a questionable look, took a sip and asked, “What the hell are you talking about?” He just looked back at me and in a firm voice said, “Doug, let me teach you a bit about customer perception and Project Management.”
That night, he changed my professional life, changed the way I did business and made me in to the engineer I am now. When I asked how I could thank him, he would only accept a promise from me to carry on the words that he that he shared. This document is me fulfilling that promise; it is the gospel of a successful engineer along with my personal experiences, my opinions and some awesome contributions by some awesome people thrown in the middle.
2. Project Management Methodology
The Project Management methodology that we will follow throughout this document is made up of the following five phases:
1. Analysis 2. Design
3. Implementation 4. Readiness 5. Rollout
I have tried to write this guide in plain everyday language and to explain things in a simplified approach with examples from my days as a MetaFrame consultant. I have broken this document down in to the above five phases. If you follow it through to the last phase, you will be ready start reaping the rewards of a successfully managed project-oriented deployment.
At the end of each phase, you will be presented with a checkpoint, where you can present your customer with a deliverable that signifies the completion of the phase. The checkpoints will also act as an
opportunity for you to compare your plan against what you have completed and to verify that you are still on track with the original project plan. At this point, you might need to add or subtract items, as it is important to measure your progress and not just blow through each of the checkpoints. It is important to emphasize that if you make a change to the plan, you will need to present the change and the revised plan to the customer for “Sign Off”.
3. What Makes an Effective Meeting?
Throughout a project-oriented deployment, you will be required to conduct numerous meetings with your customer. If you plan them properly, you will be able to steer the project in the right direction. It also gives you the ability to gather all the key players in one room, put them on the same page, work through any issues that might have arisen and make any decisions that need to be made.
When I first started running my own projects, I was given some great tips on what makes an effective meeting and felt that it might be helpful if I pass them on.
1. Set Objectives – The art of setting objectives is something you will get better at with experience. You will want to give the attendees as much information as possible on why you have called the meeting and what you expect to accomplish. You will also want to set a clear timeline.
2. Establish an agenda and distribute inadvance – Send your attendees an agenda and a copy of the documentation you will be presenting to them. This gives them the opportunity to become prepared for the meeting and the oportunity to truly participate. Your results will fall short of your objectives if you give a customer a fifty page document and then turn around and ask if he or she has any questions. Send it out a few days in advance and let them know that you are willing to answer any questions they may have. Ask the attendees if they have talking points for the agenda and have them email those thoughts back to you before the meeting so you too will be better prepared. People love to participate. This shows them you are interested in what they have to say and also shows them that you like to be prepared in advance so as to not waste anyones time.
3. Start and end the meeting on time (Don’t allow interruptions or sidetracking from the meetings agenda) – It is important for you to utilize your time as efficiently as possible. It is a good ideal to set tentative times for each item and then stick to them. You do this by the art of “on table / off table”. If you find the meeting getting off subject, you will want to take the subject “off table”. Then when you are documenting and assigning the next steps you will be able to schedule time for those questions / comments, if they are truly important.
4. Work through each agenda item (Assign and document action items) – In your agenda you will have documented a list of action items you want to discuss. You will want to address each item and if additional follow-up is needed, assign a party to be responsible for the task and a timeline for
completion.
5. Document and assign next steps – If you are not able to finalize all the action items, you will need to document the steps required for completion and the individual responsible. You can also take this time to take action on items that you had tabbed “off table” and make assignments and schedule follow-up.
6. Summarize Meeting – To close the meeting, you will want to leave yourself a few minutes to summarize what has been completed and summarize what follow-up is required. You should schedule follow-up meetings for sign-off on any action items that you have scheduled.
1. Analysis Overview
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 project’s high-level Vision/Scope.
This document is as follows:
• Project Vision (Statement of Work) • Project Scope
• Estimated Project Plan
2. Vision / Project Scope (Statement of Work)
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 customer’s 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 MetaFrame Project 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.
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
Analysis Phase Estimated Time: 5 Days
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
Design Phase Estimated Time: 5 Days Server Requirements Define and document the following sections:
o Hardware Requirements
o Operating Systems Requirements
MetaFrame Design Define and document the following sections: o Farm Design
o Data Collector Design o Zone Design
o Data Store Design o Load Management Design o Applications
o Application Delivery o Printing Architecture
Network Design Define and document the following sections: o File Storage
o Login Scripts
o Network Modifications
Design Phase
Checkpoint Prepare for and schedule meeting with DABCC.COM for a formal presentation of the Design Phase deliverable.
Implementation Phase Estimated Time: 5 Days
Develop installation procedures & Build initial MetaFrame environment
Prepare the Network Environment.
Install MetaFrame Data Store
Install Windows 2000
Install MetaFrame XP with Feature Release 2
Tune MetaFrame XP with Feature Release 2
Install Image Applications
Image Server
Deploy Image
Install Remaining Application
Configure ICA Client Updates
Configure Server Reboots
Configure MetaFrame Administrators
Configure Citrix Policies
Configure Drive Mapping
Configure Content Redirection
Publish Applications
Configure Printing Architecture
Install and Configure and Secure Web Server
Install and Configure NFuse 1.7
Install and Configure Citrix Secure Gateway (CSG)
Install and Configure Remote Administration
Install and Configure ICA Clients
Install and Configure Microsoft Terminal Services Licensing
Install and Configure Windows System Policies Implementation Phase
Readiness Phase Estimated Time: 5 Days Test, Test, Test Develop and document test procedures.
Perform test on both scalability and functionality. Production Pilot Determine pilot goals and objectives.
Determine pilot users.
Train pilot users.
Conduct pilot.
Conduct interviews with pilot users and documents responses.
Document pilot results. Rollout Additional
Servers Install any additional servers via the installation policies and procedures documented in the above phases. Change Management Implement Change Management Policies and Procedures
Readiness Phase
Checkpoint Prepare for and schedule meeting with DABCC.COM for formal presentation of the findings throughout the Readiness phase.
Rollout Estimated Time: 5 Days
End-User Training Create End-User training documentation
Gather user’s for formal training Administrator Training Create Administration documentation
Meet users that will be empowered with Citrix MetaFrame administrator privileges and provide formal, admin training.
Go Live Obtain sign off for live rollout
Distribute end user documentation
Configure rollout users
Go Live Rollout Phase
Checkpoint Prepare for and schedule meeting with DABCC.COM for formal presentation of the findings throughout the Rollout phase.
Out of Scope
Proof of Concept Based on the applications that will be deployed, DABCC.COM has opted out of the Proof of Concept section of the Analysis Phase.
Router Configuration Network Address Translation changes – Dan Morrow, 555-351-3268
Firewall Change (TCP 1494) – Dan Morrow, 555-351-3268 VPN Configuration Client installs – Help Desk Staff, 555-351-HELP
VPN Hardware changes – Fred Klopf, 555-351-5235
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
Author’s Signature Signature
Title Title
Date Date
Managers Signature Street Address
Phone number for Key Contact
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.
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
SeverRequirements - Define and document the following sections
o Hardware requirements
o Operating Systems Requirements
D&D Consulting 1 day
MetaFrameDesign - Define and document the following sections:
o Farm Design
o Data Collector Design o Zone Design
o Data Store Design o Load Management Design o Applications
o Application Delivery o Printing Architecture
Network Design - Define and document the following sections:
o File Storage o Login Scripts
o Network Modifications
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.7 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
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 a 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
¾ 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 customer’s 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 customer’s 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 (OU’s, 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 customer’s 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.
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
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
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)
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.
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.COM’s 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
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
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.
5. Proof of Concept
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
