Microsoft Outlook is currently the preferred messaging and collaboration client in Microsoft Exchange Server environments. Outlook
It is a good idea to deploy Outlook 2000 to best utilize the capabilities of your messaging and collaboration system. Outlook 2000 is more powerful and more reliable than any of its predecessors, it operates faster, it supports exciting new technologies, and it provides administrators with
With Exchange 2000 Server in mind, this chapter focuses on the installation and configuration of Outlook 2000. The first lesson covers the various installation types and
To complete this chapter:
Microsoft Office 2000 includes Outlook 2000, but this application is also available as a separate product for Exchange 2000 Server, so you are not forced to fully deploy Office to benefit from Outlook's messaging and information management capabilities. Nevertheless, users can benefit from Outlook's tight integration with Microsoft Office, which often leads organizations to the decision to fully deploy Microsoft Office at a later stage. You can deploy Outlook 2000 before, with, or after other Office 2000 applications.
This lesson only covers the installation of Outlook 2000 for Exchange 2000 Server, but the installation strategies and tools
At the end of this lesson, you will be able to:
Estimated time to complete this lesson: 90 minutes
You can install Outlook 2000 with no e-mail support, with only Internet support, or with support for corporate and workgroup environments. No e-mail support is useful for users without a messaging platform who still want to be able to manage personal contacts,
Outlook 2000 requires at least an Intel Pentium-compliant processor and 8 MB of RAM on Microsoft Windows 95/98,
If you are planning to deploy Outlook 2000 on workstations running Windows NT 4.0, make sure at least Service Pack 3 is installed on these computers. You should also take into consideration that Outlook 2000 requires Microsoft Internet Explorer 5.0, which will be installed automatically during setup if it wasn't deployed beforehand. In fact, you cannot install Outlook 2000 without Internet Explorer on the workstation.
Unlike previous versions of Outlook that required procedural scripts to control the setup process, Outlook 2000 takes full advantage of Windows Installer technology. This new technology relies primarily on .msi package files, which are databases that describe the relationships between the features and components for a given product, such as Outlook 2000. Features are components or groups of components that you can choose to install.
Windows Installer is part of the Windows 2000 operating system, where it runs as a system service using the LocalSystem account. On systems running Microsoft Windows 95/98 and Windows NT Workstation, it will be added to the operating system during the first installation. You can find detailed information about Windows Installer in the Microsoft Office 2000 Resource Kit.
Windows Installer facilitates the deployment and maintenance of Windows-based software and is available to independent software
vendors(ISVs) as a universal installation technology.
By specifying command-line options, you can control the way Setup
Command-line properties can lead to huge and puzzling commands, such as setup /qn TRANSFORMS="c:\Blue Sky.MST" COMPANYNAME="Blue Sky Airlines", which are difficult to handle. An easier option is to specify the required properties in a SETUP.INI file. A sample SETUP.INI file containing helpful comments is available on Outlook's installation CD in the root directory. Every command-line option has a corresponding .ini setting. Of course, you cannot edit the file on the installation CD directly, but you can save a modified version on your hard disk and specify this file through the /Settings command-line option (for instance, SETUP.EXE /Settings c:\MYSETUP.INI).
Alternatively, you can copy the installation files to a network installation share point and edit SETUP.INI in this location. SETUP.INI is the default initialization file in an installation directory, used when no other file was specified in the command line.
You have the option to use the Custom Installation Wizard to further customize the Outlook installation process. As mentioned in the beginning of this chapter, this wizard is part of the Office 2000 Resource Kit. It helps you create .mst transform files, which Windows Installer can apply during the setup process. Transform files allow you to override the settings in the .msi database of Windows Installer. You can read more about the Custom Installation Wizard later in this lesson.
If you are running Microsoft Windows 2000 Professional on your client computers, deployment of Outlook 2000 becomes remarkably easy. Take advantage of the software installation and maintenance feature provided by Active Directory group policies. You can manage group policies for all or a subset of your Windows 2000 users, which includes central management of software settings. Either assign Outlook 2000 to your users (or computers) or publish the application.
If you assign Outlook 2000, users will be able to launch Outlook from the Programs group in the Start menu without prior installation. Outlook 2000 will then be installed automatically on first use. When you publish the software, on the other hand, you provide users with a dedicated installation option in the Add/Remove Programs applet of the Control Panel. Users then need to install Outlook 2000
A local installation refers to the method of installing all client files on the computer's local hard disk. Outlook offers two different local installation options for this purpose—Install Now and Customize. The Install Now option installs all the components that are required by the average user. However, if you need complete control over the setup process and the selection of Outlook features, choose Customize. The local installation method was used in the "Getting Started" section of "About This Book" to prepare BLUESKY-WKSTA for Chapters 1 through 4.
To perform a local installation, you need to start SETUP.EXE from the installation CD or from a network share. At startup, Setup checks whether Windows Installer is available on the local computer and installs it if not found.
You need the permissions of a local administrator if you want to install Windows Installer on Windows NT 4.0.
After making sure Windows Installer is available, Setup checks whether Outlook is already installed. If it is, Setup switches into maintenance mode to allow you to add or remove Outlook features. Maintenance mode is signified by the presence of the following Setup options: Repair Outlook, Add Or Remove Features, and Remove Outlook.
To perform the actual Outlook installation, Setup launches MSIEXEC.EXE, a component of Windows Installer. MSIEXEC.EXE utilizes a DLL called MSI.DLL to retrieve information about available components and selections from the .msi database. If you have specified a transform file to customize the installation process, this .mst file is applied on top of the .msi database. Further command-line properties specified for Setup via SETUP.INI or command line are taken in last (see Figure 8.1).
Figure 8.1 Launching the Outlook 2000 setup process
A shared client installation refers to a configuration where the majority of the client files are kept on a file server within the network (see Figure 8.2).
Figure 8.2 Running Outlook from a network share
When running Setup from a network share instead of a local CD, there is a difference in the installation options that are available for individual features. After accepting the licensing agreement, select the Customize option, specify where to install Outlook, and then, on the screen allowing you to select the individual Outlook features, click on the node for Microsoft Outlook For Windows, for example. In the shortcut menu, the Run From CD option changes to Run From Network; Run All From CD becomes Run All From Network (see Figure 8.2). You can specify these options to run the entire client or selected components directly from the installation point. Because the files are not
The advantages of a shared installation, such as saved local disk space, can also become disadvantages. For instance, most of the files must be loaded from the file server during client startup, which
increasesnetwork traffic and typically slows down the startup process. Likewise, if the network server is temporarily down or not available for any reason, you won't be able to start Outlook at all.
The administrative installation point is the shared access point for a customized network installation, which must be created explicitly by running the Setup program with the /A option. Within the installation point, you can edit SETUP.INI or create a transform file and then deploy Outlook over the network. Alternatively, you can burn customized CDs for users who cannot install or run Outlook over the network but want to benefit from a preconfigured installation. Preparing custom Outlook CDs does not infringe the license agreement as long as you make sure these copies are not installed without a client license from Microsoft.
In this exercise you will prepare an administrative installation point on a computer running Exchange 2000 Server. In
To view a multimedia demonstration that displays how to perform this procedure, run the EX1CH8.AVI files from the \Exercise_Information\Chapter8 folder on the Supplemental Course Materials CD.
To prepare an administrative installation point
At this point, you are creating an administrative installation point on the Exchange 2000 server (see Figure 8.3).
Figure 8.3 Creating an administrative installation point
Use the command line SETUP.EXE /A DATA1.MSI to copy the Outlook files to an installation point on a network server. You need to provide the CD key and company name that you want to assign to all Outlook installations from this location and accept the licensing agreement.
Setup /A will modify the package file DATA1.MSI to identify the network share as an administrative installation point.
The administrative installation point is an ideal place to preconfigure client settings and specify the components to install. As mentioned earlier in this lesson, you have various options for customizing the setup process.
Do not alter any folders or files in the installation point other than SETUP.INI and transform files to guarantee a properly functioning Setup procedure.
The Custom Installation Wizard allows you to modify the setup process extensively, including modifications that you cannot specify in the command line or SETUP.INI. You can specify where to install Outlook and with what features, and you can detail to a large extent the client configuration parameters. You can also add your own files to the installation process, such as advanced business applications or company forms, and set custom registry entries.
Furthermore, it is possible to suppress the display of arbitrary Outlook features by selecting the Hide option for the corresponding item in the Set Feature Installation States screen of the Custom Installation Wizard. Hidden features may still be installed in the background if you have specified the installation state
If you hide a feature in the Custom Installation Wizard, all subordinate features
belongingto the feature will be hidden as well.
For some options, you can specify a value in SETUP.INI, while a different value may be listed in the transform file, and yet another value could be used in the command line. This clearly leads to a conflict, which Windows Installer handles according to the following rule: The transform file has
The unattended Setup mode, which is launched using the /Q command-line parameter, is the basis for installing Outlook on
In this exercise you will finalize the preparation of the installation point using the Custom Installation Wizard. After that, you will deploy Outlook 2000 using the unattended installation method.
To view a multimedia demonstration that displays how to perform this procedure, run the EX2CH8*.AVI files from the \Exercise_Information\Chapter8 folder on the Supplemental Course Materials CD.
To deploy Outlook 2000
At this point, you have specified your installation directory as the location of the transform file (see Figure 8.4). This
Figure 8.4 Starting the Custom Installation Wizard
At this point, you have specified to install Outlook with the most important features and hide the document converters and filters (see Figure 8.5). This feature will still be installed, but users will be unable to change converter settings when running Setup interactively.
Figure 8.5 Selecting Outlook features
|Value Data||Not Set|
At this point, you have preconfigured the users' default messaging profile (see Figure 8.6).
Figure 8.6 Specifying a default messaging profile
At this point, you have successfully created a transform file, which you can specify in the Setup command line to customize the installation process (see Figure 8.7).
Figure 8.7 Completing the Custom Installation Wizard
At this point, you are installing Outlook 2000 unattended on BLUESKY-WKSTA with the option to display a reduced user interface (see Figure 8.8). Alternatively, you may suppress all progress information and dialogs by specifying the /qn option. Either way, Outlook will take several minutes to install.
You can facilitate the deployment of Outlook 2000 when preparing an administrative installation point and configuring the Setup environment using the Custom Installation Wizard. A prepared installation point in the network allows you to run the Outlook 2000 Setup program unattended or via group policy assignments. Windows 2000 group policies, however, require Windows 2000 Professional to be installed on all workstation PCs.
Figure 8.8 Running Setup unattended with a reduced user interface
A messaging profile, sometimes also called a MAPI profile, describes the set of those information services that should be activated during a particular session. At least one must exist to successfully start Outlook 2000 (see Figure 8.9). You can read more about MAPI profiles in Chapter 9, "MAPI-Based Clients."
Immediately after the installation of Outlook on a new computer, no messaging profile exists. However, the client is unable to
When you have installed Outlook 2000 without any customization of Setup files, upon startup you need to configure the client with support for corporate and workgroup environments. In the Microsoft Outlook Setup Wizard dialog box, you have to select the Microsoft Exchange Server check box. When you click Next, you must specify the name of your server and ensure the correctness of the mailbox name to successfully start Outlook.
Figure 8.9 A messaging profile for Outlook 2000
The configuration of a messaging profile may overwhelm your end users. Consequently, it is preferable to configure the important settings prior to the client installation. One option is to create a file called OUTLOOK.PRF and place it in the administrative installation point. This file will then be copied to the Windows directory (\Winnt) during the installation. When Outlook starts for the very first time on a new computer, it looks for OUTLOOK.PRF in the Windows directory. If it finds the file, Outlook uses it to generate a default profile. You can read more about the generation of messaging profiles using .PRF files in Chapter 9, "MAPI-Based Clients."
To conveniently create messaging profiles, most organizations use the Custom Installation Wizard. After launching the Custom Installation Wizard, on the Customize Outlook Installation Options wizard screen, select the Customize Outlook Profile And Account Information option, and then make your choices as required (see Exercise 2). The Custom Installation Wizard saves your changes in the transform file. During Outlook installation, the settings will be transferred into the client's Registry. You will thus not end up with an OUTLOOK.PRF file in the Windows directory through this approach. You have the option of overriding an existing profile, which would be
In this exercise you will verify the automatic generation of messaging profiles when starting Outlook 2000 for the first time on a new workstation.
To view a multimedia demonstration that displays how to perform this procedure, run the EX3CH8.AVI files from the \Exercise_Information\Chapter8 folder on the Supplemental Course Materials CD.
To verify the profile generation
At this point, Outlook has created the default profile named CIW Generated Profile for you. The environment variable <username>, specified in Exercise 2 for the mailbox name, was substituted with your account information (see Figure 8.10).
Figure 8.10 An automatically generated default profile
The automatic generation of a default messaging profile is a very helpful feature when deploying Outlook 2000 to end users with limited knowledge about MAPI-based information services. Individual default profiles are possible because the user variable <username> is supported in the context of the mailbox name. The user only needs to start Outlook to connect to the correct mailbox that was configured for his or her user account.
Users who are new to Outlook 2000 may be overwhelmed by the set of features that this client application offers. In fact, this is one good reason why many organizations decide to split the deployment into stages, loading only the essential Outlook features first, then the advanced features, and finally the full Microsoft Office 2000 suite. As indicated earlier, you can suppress various features by using the Custom Installation Wizard and a transform file.
To add features to an installation at a later time, you may run the Outlook Setup in maintenance mode, which is launched automatically when an Outlook installation is
Alternatively, you could also use the Custom Maintenance Wizard to completely reconfigure your Outlook installations. This wizard is downloadable from the Microsoft Office Resource Kit Web site mentioned in the beginning of this chapter. The Custom Maintenance Wizard allows you to create a .cmw file that you can then use to modify an existing installation.
Files, custom registry keys, and any programs you have added to a transform file to include in your Outlook deployment will not be reinstalled during a repeated installation. This is
HKEY_CURRENT_USER \Software \Microsoft \OfficeCustomizeWizard .0 \RegKeyPaths
Delete the keys that