| During the Infrastructure Design you will be required to define and document any changes and or additions to the customers infrastructure, file shares added, users and or groups added or changed, any login script modifications and any infrastructure modifications required due to the Infrastructure Assessment. The Infrastructure Design deliverable consists of the following three sections: File Storage Logon Scripts Infrastructure Modifications The following is an example of an Infrastructure design: | 4. Infrastructure Design The MetaFrame Infrastructure Design defines the logical structure that will be used to deploy MetaFrame XP with Feature Release 3, MetaFrame. In the following design D & D Consulting will define any modifications to DABCC.COMs existing infrastructure. This will include such components as, file shares, users and or groups, login scripts, etc... The Infrastructure Design section of the Design Phase consists of the following sections: File Storage Logon Scripts Infrastructure Modifications |
In this section, you will want to define the file storage architecture required. In order to properly deploy the MetaFrame Access Suite, a number of network file shares are required for both application and user specific information. I highly recommend storing this data utilizing Microsofts Distributed File System (DFS). DFS gives you the ability to create a virtual file structure that always stays the same no matter the changes made to the server and data locations. Note: For more information on DFS, please refer to Distributed File System (DFS): Best Practices and Troubleshooting Guide. (http://www.dabcc.com\win2k\docs\Distributed File System - Best Practices and Troubleshooting Guide.doc) The following are the required shares needed for a MetaFrame installation: Terminal Services specific home directory (required) Terminal Services specific profile directory (required) ICA Client Update Configuration database (highly recommended) Installation Manager application packages (required for IM) System Policies (required for MetaFrame XP Server that are not part of a Windows 2000 Active Directory domain. MetaFrame Password Manager File Share Directory Service centrally stores all MetaFrame Password Managers configuration and password information.
The following is an example of a File Storage Design: | 4. 1. File Storage In keeping with the vision of achieving access, on demand, a number of file shares will be needed for the proposed MetaFrame Access Suite environment. The following file shares will be utilized. | UNC Path: | Purpose: | | \\dabcc\dfsroot\CitrixSync$ | MetaFrame Password Managers configuration and password data store | | \\dabcc\dfsroot\imapps | Installation Manager Application Share | | \\dabcc\dfsroot\tsusers | Citrix users Home Directory | | \\dabcc\dfsroot\tsprofiles | Citrix users Profiles Directory | | \\dabcc\dfsroot\icadatabase | Citrix Client Update database | | \\dabcc\dfsroot\tspolicies | Citrix specific policy share for MetaFrame XP Server who are members of Windows NT 4.0, workgroup and or Novell Netware environments | | | |
|
The section defines any changes needed to the logon scripts and the reasons why. During the Infrastructure Assessment section you would have analyzed any existing login scripts and if you think any changes are needed you will want to document here. In addition, if you will be implementing any drive mappings, environmental variables and or any other changes, you will want to document them here. The following is an example of a Logon Scripts Design: | 4. 2. Logon Scripts No modification will be made to DABCC.COM current logon scripts. |
This section defines the changes required to the existing infrastructure in order to successfully scale and support the proposed MetaFrame Assess Suite solution. This would include the following: Define any physical environment changes needed such as use of servers, hubs, switches in the proposed environment Define any network drives letters that will be utilized and their purpose. Define any user / group accounts that will need to be added and or edit and their purpose. The following is an example of an Infrastructure Modifications Design: | 4. 3. Infrastructure Modifications Keeping with the key points of the project vision, DABCC.COM will be implementing the following network modifications. Existing Infrastructure Modifications The following ports on the Cisco Catalyst 2948G-L3 switch will be utilized for the four proposed MetaFrame XP Servers. | Ports | Device | | 9 | DB2KCX1 | | 10 | DB2KCX2 | | 11 | DB2KCX3 | | 12 | DB2KCX4 | Client Drive Mapping Client drive mapping is built into the standard Citrix device redirection facilities and the client drives appear as a network type (Client Network) in Network Neighborhood. The clients disk drives are displayed as shared folders with mapped drive letters. These drives can be used by Windows Explorer and other applications like any other network drive. By default, the drives on the client system are all automatically mapped. If the MetaFrame XP Servers drives were not remapped during installation of MetaFrame then the client drives will, by default, start with V$ and continue mapping all available client disk drives and CDROMS in ascending order. If they were remapped then the client drives will start with C$. The client drive letter is a configurable setting via the servers registry. (this is a per server setting, so if you choose to change the default drive letter then you will need to make the change on all your MetaFrame XP Servers) Remember if you configure MetaFrame to automatically auto-create drive then you will need to make sure enough drive letters are available. You can configure client drive mapping farm wide or with the release of MetaFrame XP with Feature Release 3 you can configure on a user / group basis. The following networks drives will need to be created: | Drive Letter | Purpose | | Y: | Terminal Server specific user home directory (this drive will be hidden from the users view) | | V: | Client C: drive (if available) | | U: | Client D: drive (if available) | User/Group Modifications The following user / groups will need to be added to the DABCC.COM domain in order for proper functionality of the proposed MetaFrame XP farm. | User / Group Name | Purpose | | CTX Admin | MetaFrame Full task administrators | | CTX Admin (Read-Only) | MetaFrame view-only administrators | | CTX Users | All MetaFrame Users | | CTX Office XP Users | MetaFrame Office Users | | CTX Outlook Users | MetaFrame Outlook Users | | CTX Visio Users | MetaFrame Visio Users | | CTX Client Access Users | MetaFrame IBM Client Access Users | | CTX Notes Users | MetaFrame Notes Users | | CTX Users (High Bandwidth) | Used to tweak MetaFrame for high bandwidth | | CTX Users (Low Bandwidth) | Used to tweak MetaFrame for low bandwidth | | CTX Server to Client Redirection Users | Server to Client Content Redirection Users Group | | CTX IM | Installation Manager Service Account | The following will be added to the Terminal Services Profile tab of every domain account the will be logging in to the MetaFrame farm. | \\dabcc\dfsroot\tsprofiles\%username% | Added to the User Profile section | | \\dabcc\dfsroot\tsusers\%username% | Added to the Terminal Services Home Directory section | | | |
| |