| The initial installation of MetaFrame Secure Access Manager on the primary server must successfully complete before additional servers can be added to the server farm. Upon the conclusion of a successful installation the Setup wizard will prompt to restart the server. After you restart the server, the Administrator must log in and allow the State server configuration to be completed before the addition of additional MetaFrame Secure Access Manager servers. Otherwise, the State server may not be configured correctly. Do not install MetaFrame Secure Access Manager over a previously installed version, including the Technology Preview version. Various files and Registry keys are not removed upon the completion of a un-install. During a multi-server installation it's necessary that the user account in which the MetaFrame Secure Access Manager services are installed has Administrator rights on each MetaFrame Secure Access Manager server in the farm. All machines in the portal server farm should be in the same domain. All machines should meet the recommended minimum hardware and software requirements. All other programs and applications should be closed before the installation is started. When MetaFrame Secure Access Manager is installed, the Guide to MetaFrame Secure Access Manager and online help files are installed in the following location: install_directory\ Citrix\MetaFrame Secure Access Manager\Help See the following documentation for more information: Software requirements: - Windows 2000 Server or Advanced Server
- IIS 5.0 or later with the latest service pack
- One of the following database applications:
- Microsoft SQL Server 7.0 with service pack 3
- Microsoft SQL Server 2000 with service pack 2
- MSDE (Installed with MetaFrame Secure Access Manager)
- MSI 2.0
- Hardware Minimum Requirements
- Pentium III with 600MHz or greater
- 256 MB of RAM or greater
- 10GB of hard disk space with 1GB of free space or greater
- .NET v 1.0 Framework
There are two installation methods, a single server or multi server. Single Server Setup: - The State Server, Agent Server, Web Server and Index Server components are all installed on the same machine
Multi Server Setup: - The State Server, Agent Server, Web Server. Index Server and SG components are installed on different machines
Note: You can add more Agent and Web servers at any time. During a MetaFrame Secure Access Manager installation you will be prompted for an account to use for communicating with MetaFrame Secure Access Manager services and other servers in the access server farm. You must specify an existing account to be this service account. If you have not created a service account, create one before you start your MetaFrame Secure Access Manager installation. The account should be a domain account with read access to any shared directories or file services that you will be providing access to via an Access Center. MetaFrame Secure Access Managers installation process will set the correct privileges on the service account to be able to run all the services. Installation Gotyas: MetaFrame Secure Access Manager does not install correctly through a remote terminal server session if the MSDE option for the server farm database is selected. If you have the Access Management Console on a box and try to install CDS components, you will get a message indicating that MetaFrame Secure Access Manager is already installed. You will need to uninstall the Access Management Console and to be able to proceed with the installation. If youre single server MetaFrame Secure Access Manager machine is also a domain controller, refer to the following Microsoft Knowledge Base Article 315158 to resolve .NET related issues that you will experience. FIX: ASP.NET Does Not Work with the Default ASPNET Account on a Domain Controller Access Management Console & SQL Performance Issues. In my lab environment Ive noticed a performance increase when switching from Windows authentication to SQL authentication. SQL authentication seems to dramatically improve Access Management Console response times. Follow these steps to install MetaFrame Secure Access Manager and create a fully functional MetaFrame Secure Access Manager Access Center server farm on a single server. MetaFrame Secure Access Manager requires you to update Windows 2000 to Windows Installer version 2.0.
Citrix recommends that you use the latest version (v2.7 or higher) of MDAC with MetaFrame Secure Access Manager for optimal performance and stability. The following versions of MDAC are supported for MetaFrame Secure Access Manager: MDAC 2.52 (included with Windows 2000 SP2) MDAC 2.61 (included with SQL Server 2000 SP1) MDAC 2.62 (included with SQL Server 2000 SP2) MDAC 2.7 (included with Windows XP) Note: Should you have MetaFrame running on this machine be sure to stop the MS Terminal Services Licensing service. Restart the server before beginning MetaFrame XP installation. Please refer to section 3.1.1 How to install the Microsoft Data Access Components (MDAC 2.8) section above for installation instructions.
MetaFrame Secure Access Manger 2.0 requires Microsoft Installer Service 2.0. Please refer to section 3.1.3 How to Microsoft Windows Installer Service 2.0 section above for installation instructions.
The following defines the installation of .NET Framework, which is located on the MetaFrame Secure Access Manager CD. This is one of the required prerequisites. 1. Locate the Microsoft DotNetFramework.exe, which is available on the MetaFrame Secure Access Manager CD at \Support\ DotNetFramework.exe. Double click the DotNetFramework.exe. 2. Select Yes to accept the term of the license agreement. 
3. Unpackaged the files to your desired location 
4. Click yes to create new folder. 
5. From the installation directory double click the dotnetfix.exe to stat the installation. 6. Select Yes to continue. 
7. Select Next to continue. 
8. The .NET Framework was successfully installed. Now we need to patch it! 
9. Locate the Microsoft DotNetFramework_SP2.exe, which is available on the MetaFrame Secure Access Manager CD at \Support\ DotNetFramework_SP2.exe. Double click the DotNetFramework_SP2.exe to start the installation. 
10. Select Yes to accept the term of the license agreement. 
11. You have successfully installed SP2! 
We are now ready to install MetaFrame Secure Access Manager 2.0 (MSAM). In the design phase you would have defined if you will be using additional State or Web servers. If this is the case you will follow the following steps and when you come to step 6 you will select the appropriate services to run. The following defines how to install MetaFrame Secure Access Manager 2.0 on a Windows 2000 Server. 1. Insert the MetaFrame Secure Access Manager CD ROM. Click Citrix MetaFrame Secure Access Manager to start the install. 
2. Click Next to continue. 
3. Select I agree to the terms and conditions of the license agreement and click Next to continue. 
4. Select Server and management components and click Next to continue. 
5. Enter the serial number that appears on the MetaFrame Secure Access Manager packaging and click Next to Continue. 
6. You are prompted to select the services to install in the server. In this example install all services by clicking Next. Note: If in the design phase you documented to use multiple Agent or Web servers then you will want to select the desired service and possibly unselect the other. Important! If you will be installing any additional MetaFrame Secure Access Manager with SP1 in to the farm then you will be required to uncheck both checkboxes and enable the correct services in the Access Center Properties of the desired Access Center. 
7. Select the destination folder for the MetaFrame Secure Access Manager application files and click Next. 
8. Select the destination folder for the MetaFrame Secure Access Manager configuration date and click Next. 
9. Enter a User name, Password and Domain for the MetaFrame Secure Access Manager service account and click Next. Note: The service account must be created in advance.  10. You are prompted to select the data store type that will be used for the MetaFrame Secure Access Manager infrastructure. This example uses a stand-alone Microsoft SQL Server which should be detected by default. Click Next to continue. 
11. Select the authentication type of the SQL Server. In this example we have configured the SQL Server to use SQL authentication. Select the authentication method and click Next to continue. Note: Access Management Console & SQL Performance Issues. In my lab environment Ive noticed a performance increase when switching from Windows authentication to SQL authentication. SQL authentication seems to dramatically improve Access Management Console response times. 
12. Review the installation settings and Click Next to accept the settings and continue to install MetaFrame Secure Access Manager. 
13. Click Finish. 
You have successfully installed MetaFrame Secure Access Manager. No re-boot is required!
|