Client/server systems are more scalable than shared-file systems, making client/server messaging systems suitable for the needs of small and large organizations. Clients do not poll the active messaging server and files will not be opened directly by any messaging client. Furthermore, client/server-based systems are more secure than shared-file systems because the client doesn't need read-write permission in a post office. The server services are the actual components that write messages into and read messages from the server's messaging databases.
Exchange 2000 Server is seamlessly integrated with Windows 2000 Active Directory, which allows single-seat administration because all attributes, including Exchange 2000 Server-related directory information, are maintained in a single repository.
MAPI-based clients, such as Outlook 2000, can access all messaging- related information stored on the computer running Exchange 2000 Server. IMAP4 clients can access e-mail-related information stored in Exchange 2000 mailboxes and public folders. POP3 clients have the ability to download messages from your inbox. NNTP-based newsreader programs can access public folders as newsgroups. Web browsers are able to work with mailboxes and public folders via Web Store and Outlook Web Access.
You should start with instant collaboration solutions because these solutions rely on built-in modules of Outlook 2000 and don't require any programming skills.
You integrate Exchange 2000 Server into your existing Exchange server environment and continue to use the PROFS connector running on Exchange Server 5.5 for message connectivity. With the exception of the connector server, all computers running Exchange Server 5.5 can be upgraded to Exchange 2000.
The Active Directory Users and Computers snap-in.
You have to install the management utilities of Exchange 2000 Server on the server.
No, using the Active Directory Users and Computers snap-in it is possible to easily move directory objects, such as user accounts, between OUs. It is not necessary to delete and re-create the user accounts.
Exchange 2000 Server provides a feature known as DSProxy, which forwards MAPI-based directory lookups without further processing to a Global Catalog server. DSProxy also keeps a reference of connections between clients and servers, ensuring that the response from the Global Catalog is passed back to the correct client.
To make DSProxy divert Outlook 2000 and other smart clients, set the registry parameter RFR Target Server on the server machine to the name of the desired Global Catalog server. You need to add the parameter under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ MSExchangeSA\Parameters.
No, server-to-server communication in Exchange 2000 environments relies solely on SMTP-based messages. SMTP is an asynchronous transfer protocol that doesn't require permanent network connectivity.
The essential components that need to be operational are the System Attendant, the Information Store, the IIS Admin Service, and the SMTP transport. Of course, Active Directory as an essential Windows 2000 service also needs to be available. The System Attendant controls the entire Exchange 2000 server system and is a prerequisite for the Information Store. The Information Store hosts mailboxes and public folders and relies on the SMTP service for message delivery. The SMTP transport, in turn, requires the IIS Admin Service, because this transport is implemented in the form of an IIS.
You need to stop the System Attendant, which in turn shuts down all Exchange 2000 Server-specific services. You also need to stop the IIS Admin Service, which automatically stops all related IISs, such as the SMTP service and the NNTP service.
The MTA is not required for delivery of messages to recipients on the same computer or on different computers reachable via SMTP. However, messages to X.400 systems and foreign messaging systems are not routed until you restart the Exchange MTA Stacks service.
Outlook clients cannot log on to the Exchange 2000 server and will receive an error message indicating that the Exchange Server computer is not available. Outlook users currently logged on will lose their sessions. However, Outlook is able to automatically reconnect the user when you restart the Information Store, so it is not necessary to restart Outlook.
Only the SMTP services communicate directly with each other. All other services rely on e-mail messages and use the SMTP transport as their native communication mechanism.
The two types of information store are the public store, which maintains information stored in public folders, and the mailbox store, which holds all mailboxes and messages sent to individual users.
You can manage up to 16 individual storage groups on a single Exchange 2000 server and each storage group is capable of holding up to six individual stores. This gives you the capability to create a maximum of 96 physical stores and spread them across your server's hard disk system.
Another administrator has directly or indirectly stopped the SMTP service on your Exchange 2000 server. The SMTP service hosts the advanced queuing engine, which is the central information controller in Exchange 2000 Server. Without this essential service, Exchange 2000 Server cannot deliver any messages and all messages must remain in the user's Outbox.
Exchange 2000 organizations cannot span multiple Active Directory forests. Therefore, the domain in the separate forest must be isolated and integrated into the main forest of the environment before installing Exchange 2000 Server for these users.
Because Exchange 2000 Server needs to extend the Active Directory Schema, you need to first install Exchange 2000 Server in the domain where the schema master resides.
Define an administrative group for each location and assign the appropriate user accounts Exchange Full Administrator permissions.
Routing groups describe regions of high-speed connections within a network. Messages sent between servers in the same routing group are transferred directly and immediately using the SMTP transport service. You can use a Routing Group Connector, X.400 connector, or an SMTP Connector to provide a message path between Exchange 2000 routing groups.
Administrative groups are handled similar to Exchange Server 5.5 sites. Therefore, it is impossible to move mailboxes between servers in different administrative groups. It is also impossible to move servers between administrative groups. Finally, routing groups can only contain servers from the same administrative group. Although one administrative group may contain multiple routing groups, routing groups cannot span multiple administrative groups.
The Windows 2000 administrator must prepare the forest by launching the Exchange 2000 Setup program in ForestPrep and after that in DomainPrep mode. ForestPrep extends the Active Directory Schema to add Exchange-specific classes and attributes. ForestPrep also creates the directory object for the Exchange 2000 organization and assigns the specified account Exchange Full Administrator permissions. Your Windows 2000 administrator should specify your account at this point. Your account then has the authority to install and manage Exchange 2000 Server throughout the forest and has the authority to assign further administrators Exchange Full Administrative permissions once the first server is installed. DomainPrep, on the other hand, adds further Exchange-specific configuration information to the Active Directory directory service. When Exchange 2000 Server is installed at a later time, Setup can retrieve the configuration information from Active Directory and does not need to prompt the administrator for it.
An Exchange Full Administrator can administer the Exchange organization and modify permissions on Exchange configuration objects, whereas an Exchange Administrator can only administer the Exchange organization, but does not have the ability to modify permissions on Exchange configuration objects.
You configure a front end server by activating the This Is A Front-End Server check box in the server's properties within the Exchange System Manager.
The Minimum installation type installs Exchange 2000 with the minimum number of files needed for messaging and collaboration services. Because administrative utilities are not installed when selecting this option, you cannot manage the first server. Launch the Setup program in maintenance mode to add the management utilities to the server installation or install these utilities separately on your workstation.
You need to assign these administrators the administrative role Exchange Administrator, which is available at the organization and administrative group level.
Exchange View Only Administrator.
You need to upgrade the Exchange Server to version 5.5 first because the in-place upgrade to Exchange 2000 is only supported for version 5.5. After that, update the Windows NT Server to Windows 2000, configure connection agreements in the Active Directory Connector, and then launch the Exchange 2000 Server Setup program to accomplish the upgrade.
You need to reinstall Exchange 2000 Server in maintenance mode, which replaces corrupted files and fixes problems with missing components, such as MAPI32.DLL.
You need to launch SETUP.EXE in CreateUnattand mode via the command SETUP.EXE /CreateUnattend SETUP.INI. This will launch the Exchange Installation Wizard, where you can make your choices. However, the server will not be installed, but the initialization file is generated at the specified location.
You need to install the Microsoft Exchange System Management Tools via the Setup program of Exchange 2000 Server. Launch Setup and under Action in the Microsoft Exchange 2000 category, select Custom.
The first approach is to upgrade an existing Exchange server directly, thus joining an existing site automatically using the in-place upgrade procedure. The second method involves installing a fresh server and specifying joining an existing site during Setup. Exchange 5.5 resources must then be migrated to the Exchange 2000 server.
You should rely on the move-mailbox upgrade. Join the existing site with an Exchange 2000 server, specify a server running Exchange Server 5.5 with Service Pack 3 during the installation, and move Exchange resources onto the new system afterward. Outlook clients will be redirected to the new system automatically and users are not noticeably affected. As soon as all resources are on Exchange 2000 Server you can remove the legacy Exchange Server versions.
You cannot manage resources of previous Exchange Server versions via Active Directory. You need to use the Exchange Administrator program to manage Exchange Server 5.5 Service Pack 3 and the Exchange System snap-in to administer Exchange 2000 Server.
You should use the Active Directory Users and Computers tool to manage the mailbox resources. New mailboxes should be created on the Exchange 2000 server only, which requires the Active Directory Users and Computers tool. Configuration changes on existing mailboxes can also be made using this tool because user connection agreements of an ADC in conjunction with SRS are able to replicate the information from Active Directory to the Exchange directories.
You need to remove the existing installations of earlier Exchange Server versions and their corresponding objects in the SRS database and Active Directory. The switch to native mode is only possible if no previous versions of Exchange Server exist in the organization.
A shared storage bus, and a public and private network connection connect the nodes in a cluster. The shared storage bus connects all nodes to the disks where the clustered data resides. The public network connection connects client computers to the nodes in the cluster and allows the nodes to exchange information as well. The private network connection is optional, connects only the nodes in a cluster, and ensures that the nodes will be able to communicate with each other in the event of an outage of the public network.
A minimum of three disk volumes must be connected to the Exchange cluster. One disk volume is used as the quorum resource. The remaining two volumes will each be assigned to a separate virtual Exchange 2000 server. Both virtual servers can then run on either node in the cluster.
Install Exchange 2000 Server on one node at a time, then reboot each node to complete the installation. The Setup program will do the bulk of the work automatically by detecting that it started on a cluster node and configuring the Exchange components accordingly. It is important to set up all nodes using the same directories and installation options. It is advantageous to reserve the M drive on all nodes for the Web Store of Exchange 2000 Server. After you have installed Exchange 2000 Enterprise Server on all nodes, configure the virtual servers.
Because the existing resource group already owns an IP address, network name, and disk, only the Exchange SA needs to be added manually. All other Exchange 2000 resources will be attached automatically.
Using Cluster Administrator, you can trigger a failover by right-clicking on an Exchange 2000 resource and selecting Initiate Failure. All resources in the cluster group will be taken offline and then brought back online on another available node in the cluster. The process of stopping and starting resource instances is performed automatically.
You cannot mount nonclustered information store databases in a clustered Exchange 2000 environment. Clustered information store databases contain special structures required to support access from multiple nodes, which aren't present in nonclustered counterparts. To incorporate the existing Exchange resources, install the clustered Exchange 2000 system in the organization and then move mailboxes and public folders into it. As soon as all resources reside on the cluster, you can remove the nonclustered systems.
Outlook 2000 requires at least an Intel Pentium-compliant processor and 16 MB of RAM (in addition to Windows 2000's requirements), although it is advisable to double the amount of RAM to get better performance.
You can customize the installation process by using command-line parameters, adjusting SETUP.INI settings, or creating a transform file using the Custom Installation Wizard.
You need to launch Setup with the parameter /A to set up an administrative installation point, which you then can customize using the Custom Installation Wizard. At the end of the customization process, a transform file is written, which you will save in the installation point. After that, the Custom Installation Wizard suggests a command line for an unattended installation, which you should copy into the users' login script. You should make sure that the command line is only executed once per user.
The transform file created by the Custom Installation Wizard has lowest priority, followed by SETUP.INI, which is superseded by the command-line options.
You can modify the client connection order in the Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider. The Rpc_Binding_Order value determines the connection order.
The assistant's name won't appear in messages sent on your behalf if the assistant has been granted the Send As for your account, which can be set in the Active Directory Users and Computers management tool.
A messaging profile contains configuration information about information services that will be used by the Microsoft Exchange Client to establish a session with the underlying messaging backbone. The client cannot start without an existing profile.
The Microsoft Outlook Setup Wizard (formerly known as the Microsoft Exchange Setup Wizard).
The profile of a currently logged on user can be found under: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles. Subkeys exist corresponding to each configured profile.
For users to work offline with messages, the messages need to be copied to the computer's hard disk. To do this you can configure an offline or a personal folder store. The offline store is a replica of the actual server-based content, whereas the personal folder store normally is used to download and remove messages from the server.
You can configure the message delivery on the Delivery tab of the Services dialog box, which can be displayed using the Services command on the client's Tools menu. In this tab, the primary Inbox can be specified under the Deliver New Mail To The Following Location option.
The offline folder store provides the advantage of synchronizing public folders. In other words, using an offline store you are able to work with public folders while disconnected from the server.
The profiles for Windows 2000_based Outlook Clients will be stored in the user-specific Registry keys (HKEY_CURRENT_USER). These settings can be included in server-based profiles, which will then be activated on any machine as soon as the roving user logs on to the domain.
The frame type and the internal network number.
Microsoft Directory Synchronization Services (MSDSS).
The RPC Binding Order value in the Registry under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider should be checked first. The RPC over SPX communication method (ncacn_spx) should be placed on top.
You need to install the Client for Microsoft Networks to support RPC communication between Outlook 2000 and Exchange 2000 Server.
IMAP4, POP3, NNTP, and HTTP, as well as SMTP are supported. LDAP access is available via Active Directory and Global Catalog servers.
Using Exchange System Manager, display the properties of the desired virtual server, click on the Access tab, and click Connection Control to specify the range of IP addresses that should be granted access to the virtual server.
You can use the Basic Authentication or the Integrated Windows Authentication to prompt your users for logon credentials. When using the Basic Authentication method over the Internet, make sure the communication is encrypted using SSL; otherwise passwords will be exposed because they are transferred in clear text.
You can open Internet Explorer and connect to the URL http://localhost/Exchange/ to demonstrate how to access mailbox and public folder resources from any modern Web browser. You can also launch Windows Explorer and explain how to configure a Web folder connection to access public folder resources via HTTP and WebDAV. The URL http://localhost/public/ allows you to access the entire public folders tree from within Windows Explorer just as any shared network resource. Finally, you may start an Office or any other application and access mailbox or public folder resources via drive M that corresponds to the ExIFS.
A pull feed initiates the connection to a remote USENET host and pulls the information from existing newsgroups. To pause a newsfeed, display its properties, and in the General tab, deselect the Enable Feed check box. Then click OK. This step temporarily disables the newsfeed. Now you can add more disks or move resources to another server to create more disk space, and then enable the feed again.
Exchange System Manager cannot be installed on a computer running Windows NT Workstation. Hence, you will need to use a different approach, such as Terminal Services, in which case you can use an Exchange System Manager instance running on Windows 2000 Server remotely. Theoretically, you can administer all Exchange 2000 servers that are members of administrative groups where you have Administrative permissions. Changes are written to Active Directory and replicated across the entire forest.
The Performance tool allows you to monitor performance objects on the local and remote computers. Using this tool, you can create a performance chart for processor utilization, disk and network activities, and Exchange 2000 processes. Performance charts can help to isolate bottlenecks and allow you to precisely allocate hardware upgrades.
You can define mailbox store policies and set the storage limits according to your preferences on the Limits tab. After that, place all the servers from your administrative group under this policy.
The Logon object under the Private Information Store object provides the fastest access to the desired information. As soon as you select this object, status information regarding all logged on users will be displayed in the contents pane of the Administration window.
Mail-enabled contact objects reference recipients outside the organization. They don't possess mailboxes on an Exchange 2000 server. Instead, mail-enabled contacts are wrappers around an underlying e-mail address, which points to the actual recipient somewhere outside.
You need to click on the Exchange Advanced tab of the desired mailbox in Active Directory Users and Computers and select the Hide The Account From Exchange Address Lists check box.
By designating the user as the distribution list owner.
You can designate this server for each group separately using the Expansion Server setting in the Exchange Advanced tab. If you have numerous groups to configure, consider updating them in bulk using the LDIFDE or CSVDE utility.
You need to run the Exchange 2000 Setup program in each domain in DomainPrep mode. After that, an instance of the Recipient Update service must be configured for each domain individually on the server using the Exchange System Manager utility.
You need to install the Exchange 2000 Enterprise Server edition, which is able to handle a maximum of four storage groups, each capable of holding up to five individual stores.
Configuring a dedicated public folder server means removing all existing mailbox stores, which cannot be accomplished if the mailbox stores contain user mailboxes. Hence, you need to move all existing user mailboxes from this computer to other servers in the administrative group.
You need to create a full-text index for the public store by right-clicking it and selecting the Create Full-Text Index command. Then, you need to populate the full-text catalog via the Start Full Population command. As soon as this process is complete, you can make the catalog available for full-text searches by clients on the store's Full-Text Indexing tab. You should also define update and rebuild intervals to ensure that search information is always up to date.
You cannot move servers between administrative groups. The server must be reinstalled, at which time you can specify the server's new administrative group. The administrative group must be created beforehand in Exchange System Manager.
Right-click on the Recipient Update service for your domain, and click Rebuild. A Rebuild Address Lists And Recipient Policies dialog box will appear, informing you that the settings for all recipients are recalculated on the next scheduled update interval. To overrule the update interval by triggering an immediate update, right-click the update service object again and select the Update Now command.
For incoming messages to be delivered to your host, your SMTP domain name must be registered in MX records in the Internet DNS.
You can configure a message filter and activate the filtering for your SMTP virtual server. Under Global Settings, display the properties of the Message Delivery object in Exchange System Manager. Click on the Filtering tab, and use the Add button to specify "*@Pleasegiveusyourmoney.com" as the filtered sender information. As soon as the filter is defined, activate the filtering feature on your virtual server.
It may be advantageous to not limit the number of messages per connection and let the bridgehead handle all e-mail over established links. This increases the performance because it avoids additional handshakes for further connection establishments.
You can add references to external DNS servers to your SMTP virtual server configuration. In the Delivery tab, click the Advanced button. This will display the Advanced Delivery dialog box. Under Configure External DNS Servers, click the Configure button. You can specify multiple DNS servers.
You have deselected the Allow Automatic Forward check box in the Default message format definition, which is located in the Internet Message Formats container in Exchange System Manager.
You should configure multiple routing groups if access to public folder resources must be controlled, if dedicated bridgehead servers with optimized hardware for message transfer are desired, if you need to take geographical requirements into consideration, or if you need to optimize or reduce network traffic. Unstable network links affect message transfer performance, which would benefit from the use of multiple routing groups. The same applies to WAN connections that generate costs.
At minimum, you need to specify a name in the General tab and a remote bridgehead server in the Remote Bridgehead tab.
At minimum, you need to specify a name in the General tab and define a local bridgehead server. You also need to specify a remote SMTP virtual server in the form of a smart host and a remote routing group in the Connected Routing Groups tab.
The first server in a routing group typically acts as the routing group master, maintaining the LST for all other servers in the routing group. If you shut down the routing group master for a significant period of time, as you would to replace its hardware, you should designate a different master to avoid inefficient message routing. Launch Exchange System Manager, expand the Local Routing Group, and select the Members container. In the details pane, right-click another server object, and select Set As Master.
A dedicated public server is a server that maintains folders in public stores only. All mailbox stores have been removed.
Outlook 2000 relies on RPCs in any case, whether the content is stored on the user's home server or another public server within the routing group or organization.
On the user's home server, because this server holds the default public folder store for the user.
All subfolders will be created on the server that maintains the parent folder.
The public folder hierarchy replication has not been completed yet. After a short delay, the public folder will appear in the public folder hierarchy.
Nothing. Routing group connectors allow public folder referrals by default. If public folder access is prohibited due to manual configuration changes, clear the Do Not Allow Public Folder Referrals check box on the routing group connector's General tab.
Public folder content replication permits maintenance of multiple synchronized copies of a particular public folder. Multiple replicas, in turn, can be used to distribute the workload across multiple servers. This improves the response time for all users in the organization. Furthermore, multiple replicas provide fault tolerance.
All public folders must be kept locally in all routing groups. The content of each public folder must be replicated to at least one server in each remote routing group to ensure that the content is accessible.
To add a public folder replica from another server to the public store on your server, right-click Public Folder Instances under your server's public store, point to All Tasks, and click Add Replica. This will launch the Public Store dialog box, where you can select the desired folder from the associated public folder hierarchy.
The receiving PRFA checks whether the change number of the local message is included in the predecessor list of the updated message. If it is, the information can be replaced. If the local message change number is not included, a replication conflict will be detected.
Backfill is the mechanism used to discover out-of-sync replicas based on message status information, which is included in every replication message. If no changes have to be replicated, status information is exchanged once every day automatically. If a PFRA discovers missing changes, it requests them from any Information Store that maintains a more recent replica.
You can accept the local, the updated, or both replicated items.
Design conflicts do not need to be resolved explicitly because the most recent changes overwrite all others. Public folder contacts and public folder owners are notified because they should check which design was applied.
Advanced security supports signing and sealing of messages. Signing permits a sender to add a digital signature to a message, which proves the message's origin and authenticity. Sealing is another term for message encryption. Both features can be used individually or simultaneously.
The KM Server password is used to decrypt the KM Database Master Encryption key to gain access to the KM database. It must be supplied during the KMS startup.
The KM administrator has to begin the process of enabling advanced security. During this process a 12-character security token will be generated, which must be provided to the user. It is possible to enroll multiple users concurrently.
The user needs to receive the security token from the KM administrator. In the Options dialog box of Outlook 2000, using the Security tab, the user can request a digital ID from the Exchange 2000 server. During this process, the user needs to enter the security token and specify a security password for the digital ID. A request message will be sent to the KM Server, which will forward the request to Certificate Services to obtain approved X.509 version 3 certificates. Finally, a response from the KM Server will be received, which can be opened as usual. At this point, the user will be asked for the security password as recently defined. The user must enter the password to complete the process of enabling advanced security.
After the user sends the message.
The original message is hashed and the user's private signing key is retrieved from the security store. The hash is then encrypted using the private signing key. The encrypted hash will be added to the message as well as the user's signing certificate, which contains the public signing key. The client then sends the message.
First, the client contacts Active Directory to obtain each recipient's sealing certificate, which contains the public sealing key and describes the supported encryption method. Based on this information, the encryption method for the message will be determined. Accordingly, the client generates a bulk encryption key and encrypts the message content. The bulk encryption key will then be encrypted using each recipient's public sealing key, creating a bulk encryption lockbox for each recipient. The lockbox will be attached to the encrypted message. The sender's sealing certificate will also be added to the message before it is sent.
Install the KM Server in one administrative group. After that, use the Encryption Configuration object of the second administrative group to specify the KM Server location.
You need to recover the security keys for this user. The KM Server will generate a new 12-character security token, which must be provided to the user. The user will complete the recovery by repeating the steps of enabling advanced security. A new digital ID will be created for the user.
The users' mailboxes were deleted, but deleted mailboxes are retained for 30 days by default. You can reconnect mailboxes to the new user accounts without any difficulty using Exchange System Manager. Right-click on the mailbox, select Reconnect to specify the new user account, and the user will be able to work with the reconnected mailbox immediately.
System monitoring relies on LSI, which is most efficiently propagated between the servers in the local routing group. Consequently, you should specify monitoring servers that reside in the same routing group as the monitored server.
Message tracking can be used to determine where a message was delivered. You can search for messages by the originator's e-mail address and examine the path the messages have taken from server to server in your organization. The Message Tracking Center reads tracking information from the network shares of each server that has been involved in a particular message transfer. Message tracking must be enabled to write these log files.
The databases of mailbox and public stores that belong to the Information Store, as well as the databases of the KMS and SRS can be backed up online using an Exchange 2000 Server_enabled backup program.
Transaction logs, previous logs, reserved logs, checkpoint files, patch files, and a temporary database file.
You can use ESEUTIL.EXE with the /d switch to reduce the physical size of the database files. This operation is known as offline database compaction.
The incremental backup purges transaction log files, setting the context for the next backup. The differential backup does not discard any transactions. It does not change the context for any following incremental or differential backup.
You can restore the last backup one more time with the Last Backup Set check box selected, or you can run hard recovery manually using ESEUTIL.EXE with the /CC switch from the temporary folder of the transaction log files where RESTORE.ENV file exists.
Setup /DisasterRecovery will reconfigure the local server, including program files, registry settings, and database paths based on the configuration information still available in Active Directory. The old server object must still exist in the Exchange 2000 Server configuration. When running Setup /DisasterRecovery, make sure all the components that were previously installed on the server are marked for disaster recovery on the Component Selection wizard screen. You can restore databases online after the disaster recovery.
Mailbox GUIDs associate user accounts with their mailboxes. These identifiers must be unique within the Active Directory forest. Therefore, you cannot have two copies of the same database on different servers in the same organization. Exchange 2000 Server does not allow you to reconnect a mailbox from a restored database to the same or another user as long as the mailbox from the production database is connected to a user account. To bypass this issue, recovery servers must be installed in different Active Directory forests.
It is possible to design send forms or post forms. Send forms are used to send formatted information to other users. The forms definition may be included in the message. Post forms, on the other hand, allow you to share information between users through public folders.
Organization forms library, folder forms library, and personal forms library.
In the Personal Forms Library.
It would be advantageous to create a public folder for tasks items. After that, the standard Outlook task form should be displayed and modified using the Outlook Forms Designer. To load an Outlook form into the designer you need to launch the form, open the Tools menu, point to Forms, and select the Design This Form command. This will switch the form into design mode, where you can make modifications and add custom functionality. The form also can be published in design mode.
The new approach is based on ISAPI instead of ASPs, which the former version utilized. (The ASPs were processed by another ISAPI extension called ASP.DLL using a script interpreter.) Because OWA of Exchange 2000 Server does not rely on ASPs, both OWA versions are incompatible. The direct utilization of ISAPI gives better performance and scalability.
The four virtual directories are called Exadmin, Exchange, Exchweb, and Public. Exadmin allows Exchange System Manager to work with public folder properties. Exchange provides connection to mailboxes. Public can be used to access MAPI-based public folders. Exchweb points to graphics and other files that reside in \Program Files\Exchsrvr\Exchweb.
Internet Explorer 5.0 supports advanced features, such as DHTML and XML, shortcut menus, and drag-and-drop operations between folders. Internet Explorer 5.0 can render mailbox and public folder data locally instead of sending requests to the server. This minimizes network communication and increases the scalability of the system.
It is recommended to group front end systems using Microsoft Network Load Balancing.
Round-robin DNS should not be used for load balancing across SSL- enabled hosts. The SSL bulk encryption key is maintained per host and would be lost if the client is redirected to another host by DNS. The client would have to establish a new session to generate a new bulk encryption key.
http://bluesky-srv1/Exchange/Administrator/Calendar/?Cmd=contents
The Exchange OLE DB provider (ExOLEDB) supports record-level access to messaging information based on OLE DB and ADO 2.5 interfaces.
ExIFS allows you to access message items using functions from Win32 file APIs. This allows you to access and share mailbox and public folders in much the same way as ordinary directories on the server's file system. Most important, direct file access through ExIFS allows you to store Web pages and other application elements directly in mailbox or public folders.
You should install the Web Storage System Forms SDK on your Exchange 2000 server and the FrontPage Extensions for Web Storage System Forms. Using FrontPage 2000, it is easy to design Web-based folder views and custom forms and register them with the desired public folder.
Web Storage System forms must be registered in registration items. Otherwise, the rendering engine cannot determine the location of the custom form to render the data. Various properties can be set for registration items to control how Web pages are used.
You can implement a Web Storage System event sink to intercept the asynchronous OnSave event, which is triggered when new items or item changes are committed. To register your event sink, you can use REGEVENT.VBS.
CDO is the ideal choice to implement workflow and other collaborative applications. It allows you to perform actions such as sending messages, managing contacts, scheduling appointments, handling meeting requests, creating folders, and so on. CDO simplifies working with raw data in item streams. Streams are created automatically based on Internet standard formats. Unlike ADO, CDO recreates streams when item properties are changed.
CDO.Message
You need to specify a URL of file://./BackOfficeStorage/<domain name/MBX/<user alias>/calendar/. The user alias corresponds to the left half of the sender's SMTP address, which is not necessarily the user's Windows 2000 account name.
You have to create a CDO.Person object, bind it to your account in Active Directory, and then use the GetVCardStream method to write the desired information to a specified file vCard-compliant MIME format.
You need to have Exchange Administrator permissions if you want to manage an organization or administrative group. CDOEXM applications require the same level of permissions as Exchange System Manager.
Workflow Designer for Exchange 2000 Server.
The workflow logic must be written in VBScript, but calls to CreateObject are prohibited. Restricted VBScript code cannot instantiate COM classes. The code runs in the context of a special account called EUSER_EXSTOREEVENT with guest privileges by default. The workflow system account requires the Windows 2000 Act As Part Of The Operating System permission.
Your IM home server maintains a subscriber list for your account to send notifications to registered subscribers if the status of your account changes. As soon as your state changes to Away From Computer, the server actively sends a status change notification to each subscriber, which ensures that contact lists are always up to date. IM users that have subscribed your account as a contact will see the new status right away.
The MSN Messenger client allows you to block the propagation of presence information via the Privacy command, which is available on the Tools menu.
IM clients outside a protected network can only connect to IM routers, which in turn communicate with IM home servers inside the protected network on behalf of the external clients.
You have the option to add an SRV resource record for your IM router to DNS and map the common domain name (such as bluesky-inc-10.com) to the Instant Messaging service (_rvp) and the TCP port on which the service is provided.
The permissions of an Exchange Administrator are required in the Administrative Group to which you want to add the Chat Service.
Exchange 2000 Conferencing Server requires Windows 2000 Server and IIS 5.0. Exchange 2000 Server is not required on the local computer, but Active Directory and Exchange 2000 Server must have been deployed in the Windows 2000 domain. In addition, the network must be IP multicast-enabled and must provide MADCAP services for videoconferencing. Windows 2000 Certificate Services is required to support private conferences.
The MS Mail Connector Interchange, the Connector PO, and one or many MS Mail Connector (PC) MTAs.
The Connector PO represents the MS Mail interface of Exchange 2000 Server. It is the intermediate repository for MS Mail messages between an Exchange 2000 server and MS Mail postoffices.
This is an MS Mail-related problem. You need to use the MS Mail Administrator program to check that the Connector PO has been registered as an external postoffice.
The three stages are T1, T2, and T3. At T1, requestors generate update messages, which are addressed to the Dirsync server. At T2 time, the Dirsync server incorporates address updates into the master address list. Also, update messages for requestor postoffices will be generated and sent back to the requestors. At T3, received address changes are committed to the postoffice address lists.
Running as a Windows 2000 service, the DXA is permanently active. It will commit address updates to Active Directory immediately as soon as they are received. MS Mail address information is maintained in recipient objects that are placed in an OU that was specified as the import container for the remote Dirsync requestor.
MS Mail template labels can be mapped to mailbox attributes using the Directory Synchronization configuration object in Exchange System Manager. A mapping can be defined for both incoming and outgoing information through the Incoming Templates and Outgoing Templates tabs.
A distribution group is required to contain the Adminsch accounts of the MS Mail postoffices. The Schedule+ Free/Busy Connector uses this distribution group to address the free/busy update messages.
The Connector for Lotus cc:Mail can only connect to one Lotus cc:Mail post office directly.
The Information Store maintains the connector message queues (MTS-OUT and MTS-IN). The actual Connector for Lotus cc:Mail service performs the transfer and conversion of messages. The Connector Store acts as the intermediate repository for scratch files. The Lotus cc:Mail programs Import and Export are used to access a Lotus cc:Mail post office. Address and details templates allow specifying Lotus cc:Mail recipients in Microsoft Outlook. The proxy address generator CCMPROXY.DLL allows the Recipient Update service to generate proxy CCMAIL addresses for all recipients in the organization.
Using Exchange System Manager, you need to customize the proxy address format by means of a recipient policy. Recipient policy objects can be found in the Recipients container, under Recipient Policies. Click on the E-Mail Addresses tab and select the CCMAIL check box. Double-click the Address entry to customize the proxy address generation. Specify the following format: %g%1s at <Organization Name>.
IMPORT.EXE
EXPORT.EXE
A Connector ID has to be created, which should not be included in directory synchronization. This ID requires Access permissions to the server's router mailbox, called MAIL.BOX, as well as the Connector-specific databases, by default EXCHANGE.BOX and EXCHANGE.BAD. Both can be created using Lotus Notes Administrator. If they are missing, the Connector for Lotus Notes creates them automatically. For directory synchronization, Access permissions for source and target name and address books are required, and it is advisable to add the Connector ID to the list of administrators in the server's Server document if you want the Connector to compact its databases during maintenance cycles. Do not forget to register your Exchange 2000 Server organization in a foreign domain document. To support Doclink conversion, general Reader access to Notes databases is required.
The MEXOUT process.
DXANOTES uses the Notes client API to read and write address information in Lotus Domino/Notes and DXAMEX uses ADSI to work with Active Directory. DXANOTES and DXAMEX in turn communicate with each other by means of temporary MIF files called DXANOTES.TXT and DXAMEX.TXT.
In the General tab.
You need to install and configure Novell GroupWise Patch 2 for API NLM on a NetWare server and enable it for distribution list expansion. You also need to create a gateway object for it in the GroupWise domain. The Exchange 2000 Server organization must be registered in the form of an external foreign domain, which is connected to GroupWise via API Gateway. The Connector for Novell GroupWise requires a NetWare account with membership in the NTGATEWAY group to access the API Gateway for message transfer and directory synchronization.
The Microsoft Exchange Router for Novell GroupWise, which is implemented in a separate Windows 2000 service running on the Exchange 2000 server.
This happens by design. The API Gateway only supports message bodies in plain text. Consequently, RTF information cannot be preserved in e-mail messages between Exchange and GroupWise users.
The mapping rule file for synchronization from GroupWise to Active Directory is MAPGWISE.TBL, which you can find in the connector store in the \Dxagwise subdirectory.
DXAGWISE generates an administrator message to request a list of all users in the GroupWise directory. It places this message in the form of an .api file in the \Gwrouter\Togwise directory of the connector store, where the Router for Novell GroupWise picks it up and transfers it into the API Gateway's API_IN directory. GroupWise processes the request and returns a list with all GroupWise users through the API_OUT directory of the API Gateway, which the Router for Novell GroupWise transfers into the \Gwrouter\Dirsync directory.