As with most modern Windows programs, you install Citrix MetaFrame XP on your Windows 2000 server using a setup wizard. Although Citrix did a good job of designing MetaFrame XP’s installation program, there are some things you need to watch for. In this Daily Feature, I’ll show you what you need to do to install MetaFrame XP on your Windows 2000 server.

Starting the installation
The installation process is straightforward, with only a few places that can trip you up. When you place the MetaFrame XP CD-ROM in your server, you’ll see the Citrix MetaFrame XP CD-ROM splash screen. Click the MetaFrame XP Setup button to begin the setup.

The first thing you’ll see is the MetaFrame XP License Agreement screen. Read the license agreement to make sure you can abide by its terms. You must click I Agree to continue the installation.

Next you’ll see a Welcome screen. As with most Welcome screens, this screen just gives you basic information about the program, so you can bypass it by clicking Next.

Down on the farm
You’ll then see the Server Farm Selection screen. Here you can select whether you’re starting a new server farm or joining an existing one. You’ll only select Create A New Server Farm for the first MetaFrame XP server you install in your organization. For subsequent MetaFrame servers, select Join An Existing Server Farm. For the purposes of this Daily Feature, we’ll assume you’re creating a new server farm. Make your selection and click Next.

Setup then displays the Data Store Type screen. As mentioned in the Daily Drill Down “Lay the groundwork for a successful MetaFrame XP installation,” you must choose a database to store MetaFrame’s information. If you’re going to use Microsoft Access and the data store will reside on the MetaFrame server, select the first option, Direct Data Store Connection. If you choose Microsoft SQL or Oracle, you should select the second option, Connect To A Data Store Set Up Locally On Another Server. Click Next to continue.

The Zone Name screen allows you to specify a name for your MetaFrame Zone. Zones group servers together in one unit. Every 100 MetaFrame XP servers need one data collector server to replace the ICA Master browser in gathering and storing information about the different servers. On the Zone Name screen, you can create a custom name for the Zone. To do so, deselect the Use Default Zone Name checkbox and enter a custom name in the Zone Name field. Click Next after you’ve entered the name.

You’ll then see the Interoperability Mode screen. You can choose between two operating modes for MetaFrame XP, Native Mode and Mixed Mode. If you plan to have an all-XP farm with no servers running MetaFrame 1.8, select Native Mode. Native Mode will also let you leverage all the new features in MetaFrame XP. If you’re in the middle of a migration and want to run XP and earlier versions of MetaFrame, such as MetaFrame 1.8, then select Mixed Mode. Citrix recommends Mixed Mode only as a staging point in a migration to a full Native Mode server farm. Click Next to continue.

The next screen you’ll see is the Farm Administrator screen. On this screen, you’ll specify a domain account to be the farm administrator. Select the username and the domain and click Next.

The Network ICA Connections screen appears next. This screen allows you to specify the protocols that your clients use to connect to your MetaFrame server. Selections on this screen are based on which protocols you have running on your network. You can only select protocols that are installed on your server and clients. Select your protocols and click Next.

The TAPI Modem Setup screen then appears. On this screen you can add modems in order to grant users direct dial-in access to the Citrix MetaFrame XP server. To add a modem, click Add Modems and configure your modem appropriately. You can also configure a modem for dial-up access later in Control Panel. Click Next to continue.

The shadow knows
You’ll then see the ICA Session Shadowing screen. Shadowing allows you to view and monitor client connections to your MetaFrame server. You can see exactly what’s going on at the workstation as the client works, which can be very helpful for training and troubleshooting purposes. The first screen is informational, so click Next to continue.

You’ll then see the Shadowing Setup screen shown in Figure A. Take some time when considering your shadowing options. Options you select here can’t be reversed later on. The only way to change these settings is by reinstalling MetaFrame.

Figure A
You can monitor client sessions by enabling shadowing.

If you don’t want to shadow clients, select Do Not Allow Shadowing. If you select Allow Shadowing, you have the following additional choices to make:

  • Prohibit Remote Control Of ICA Sessions—This choice allows you to view, but not control, the remote sessions.
  • Prohibit Shadow Connections Without Notification—This option notifies the user when you want to view the connection. The user then has the option to accept or refuse your monitoring.
  • Prohibit Shadow Connections Without Logging—This option ensures that every session being shadowed has to be logged.

Be careful when deploying shadowing in your organization. Shadowing gives a lot of the power to the user doing the shadowing. If improperly configured and used, a user can spy on someone else without that person even knowing it. Once you have selected the options you want, click Next.

Pack a map and a sandwich
Drive Mapping is the screen you’ll see next. This screen is purely informational and shows the default drive maps that MetaFrame XP’s ICA client assigns to users when they log in. When a user logs in to a Citrix MetaFrame server, local drives on the workstation like C and D are mapped and made available for the ICA session. If drive mappings needed by the workstation conflict with drive mappings needed by the ICA session, MetaFrame’s Drive Mapping option remaps the server drives to drive letters that don’t conflict.

Click Next to bypass the Drive Mapping information screen. You’ll then see the Server Drive Reassignment screen shown in  Figure B. Here you can tell MetaFrame that you do want to remap drive letters. Select Remap The Server Drives and then select the default drive letter for remapping to begin. By default, drive mapping begins at drive M, but you can select a new starting letter from the drop-down list box.

Figure B
You can remap server drives for your ICA session.

You’ll then see the Perform Installation screen. Unlike most Setup programs, MetaFrame XP’s Setup doesn’t give you a summary screen to review your settings. Click Next to begin installation or Back to review your selections. When you click Next, you’ll see the second Perform Installation screen, which displays a bar graph showing Setup’s progress.

After the MetaFrame XP copies files to your server, you’ll see the Citrix ICA Client Distribution Wizard screen. Insert the ICA Clients CD into your server and click Next. You’ll then see the MetaFrame XP 1.0 Licensing screen. Enter your license number in the License Serial Number field. You may choose to do so later and simply leave this field blank for now by clicking Next. You’ll then see the MetaFrame XP Product Code screen. Enter the product code for your installation in the Product Code field and click Next. Setup finalizes MetaFrame XP’s installation and displays the System Restart screen. Click Restart to reboot your server and you’re done!

That’s all there is to it
Now that you’ve installed your first Citrix MetaFrame XP server and selected your appropriate database and method of accessing it, you can start using it in your organization. You can also add additional servers to lighten your server’s workload. As you can see, MetaFrame XP’s installation is similar to most Windows Setup programs, but it has a few gotchas along the way. Once you work your way around them, installing MetaFrame XP is fairly straightforward.