  ------------------------------------------------------------------

              Microsoft Exchange Server Migration Tools README      
                      Digital ALL-IN-1 Source Extractor
   Copyright(c) 1986-1997 Microsoft Corporation. All Rights Reserved 

   ------------------------------------------------------------------

This document describes the steps necessary to install the Microsoft Exchange
Migration Tool on an ALL-IN-1(tm) system.  It also includes usage notes and
requirements.


PREREQUISITES:
--------------
You need the following software and hardware:

1. Digital ALL-IN-1, version 2.3 or later (local language version). This source 
   extractor runs within ALL-IN-1, which runs under the VMS (or Open VMS) 
   operating system. The source extractor supports VAX and Alpha platforms. 
   Any version of VMS that is supported by ALL-IN-1 is supported (typically 
   version 5.4 of greater).

2. Enough free disk space to create a migration account and build the intermediate 
   migration files. These files require an amount of disk space roughly equal 
   to the combined sizes of all documents to be migrated in a given session. 
   These files could require hundreds of megabytes of disk space, depending on 
   your system and users.

3. The EX_MIGRATE account myst have the XOWN (ALL-IN-1) privilege in order to 
   execute the migration scripts and accesss the forms library.

Note that the tools can be used to migrate most customized Digital ALL-IN-1 systems 
unless standard Digital ALL-IN-1 functions have been altered.


INSTALLATION STEPS:
-------------------

1. Create an ALL-IN-1 account called EX_MIGRATE with very high, or no disk
   quota and no ALL-IN-1 document quota.

2. Using SYS$SYSTEM:AUTHORIZE.EXE, give this account READALL and SYSPRIV
   privileges (both Authorized and Default).

3. In the ALL-IN-1 profile for EX_MIGRATE, specify EDT as the default
   editor and include EXFORMS as a default form library.  Insure that
   the profile includes XOWN privilege (for V3.x systems).

4. Copy all files from the Migration Tools directory into the ALL-IN-1
   directory of the EX_MIGRATE account (typically [EX_MIGRATE.A1] OR
   [EX_MIGRATE.OA]).  This can be accomplished with Kermit, PATHWORKS(tm), or
   any number of other techniques. 

   From the EX_MIGRATE ALL-IN-1 directory (at the $ prompt), enter:
   @EX_INST

   This should run for just a few seconds and display a completion message.
   Assuming no error messages from the above, you have completed the
   installation.  If there were errors, correct the condition suggested by the
   error message and re-enter @EX_INST.


USAGE NOTES:
------------

1. Due to a well-known problem with the way that ALL-IN-1 interacts with
   VMS(tm) it is necessary to use the MIG option in small batches.  If you
   stick to the following limits on batch size you should not experience
   problems:

   ALL-IN-1 Version		Max. # accounts in a batch
   ----------------		--------------------------

	2.3				 50
	2.4				100
	3.0				100
	3.1				100

2. To avoid file-locking problems, it's a good idea to run the MIG option
   at a time when the affected users are NOT using ALL-IN-1.  This is less
   of an issue in V3.0 and later, but still worth noting.

3. If your organization uses the document archiving facility of ALL-IN-1,
   it will be necessary for users to retrieve any archived documents for
   for inclusion in the migratation prior to running the MIG option.

4. Depending upon the number of accounts selected and the size of the
   affected file cabinets, the MIG option could take several hours to
   complete.  As indicated above, it's a good idea to select several small
   groups (batches) of accounts for MIG processing.  Additionally, the users
   should delete any documents that don't absolutely have to be migrated.
   This can save several hours of processing time.  (see item 5 below)

5. The contents, if any, of users' Wastebasket folders will be migrated.
   To save time (potentially a great deal of time), an Empty Wastebasket
   operation can be performed by/for the affected users.  This will prevent
   documents marked for deletion from being migrated.  The only caution is
   that users may not have their normal amount of time to change their minds
   and undelete (refile) these documents.  If users count on Wastebasket
   contents being "safe" until a published date, then it may be a good
   idea to notify them prior to a non-scheduled Empty Wastebasket operation.


HELP TEXT:
----------
			  Migration Tools Instructions

OVERVIEW:
---------

Welcome to the Microsoft Exchange Server(tm) Migration Tools Menu!  This
subsystem is provided to assist in migrating users from an ALL-IN-1(tm)
system to a Microsoft Exchange Server system.

This system is designed to be used from a single ALL-IN-1 account named
EX_MIGRATE.  Usage from another account may not produce correct results.

Migration typically occurs in three stages:

1. A users to be migrated are identified and grouped into batches for
   processing.

2. This tool is used to process a batch of users (which creates
   intermediate files that contain documents, calendar events and migration
   information.

3. The intemediate files are transferred to a Microsoft Exchange Server
   system where they are processed by the Microsoft Exchange Server Migration
   Wizard.

The Migration menu contains 3 choices which are selected by entering the
corresponding 3-character mnemonic and hitting the return key.  Like most of
this subsystem, usage follows normal ALL-IN-1 conventions and should be
familiar to an experienced ALL-IN-1 user.  While formal ALL-IN-1 help is not
available for this subsystem, this document is provided as a replacement.

MENU CHOICES:
-------------

The 3 menu choices perform the following tasks:

MIG	Migrate user's documents and schedules.  This option displays the
	parameter form and accepts migration parameters.  If an Accounts or
	Control file are specified, then the migration process starts with
	the first user listed in the input file.  Othewise a list of users
	is displayed to allow for the selection of a migration batch.

	Processing continues until each user specified has been processed.
	At this point a completion message will be displayed and the
	intermediate files will be ready to be transferred.  The
	intermediate files are named as follows:

	mmddhhmm.PKL			Packing list file
	mmddhhmm.PRI			Primary migration file
	mmddhhmm.nnn			Secondary migration file

	Where mmddhhmm is the unique numeric month, day, hour, and minute
	that the migration process began; and nnn is a sequential number,
	001 for the first user, 002 for the second...

	There should be one secondary migration file for each user in a
	migration batch, one packing list file, and one primary migration
	file per migration batch.  So, if 50 users are processed, 52
	intermediate files would be created.

	It's a good idea to limit the number of users processed during any
	given migration batch due to a problem in VMS.  If you keep the number
	under 100 (50 if you are using ALL-IN-1 Version 2.3), you should not
	experience problems.

LOG	Prints a log file.  Each migration produces a log file named
	mmddhhmm.LOG (where mmddhhmm correspond to the .PKL file and .PRI
	files noted in MIG description.  This option displays a list of all
	.LOG files.  Select the desired file by entering the sequence
	number that appears to the left of the log name.

	To view the log file on the screen, choose TERMINAL when prompted
	for a printer destination.  Otherwise select a printer and the log
	file will be printed.

HLP	Displays this file.  Normal ALL-IN-1 navigation is available while
	reading this.  Should you need to print these instructions, you can
	copy them to your ALL-IN-1 Scratchpad. To do so, enter the scratchpad
	from the scatchpad menu (SP or GOLD *), and choose the Delete option
	to remove any old information from the scratchpad. Then choose the
	Edit option. Once you are in the editor press GOLD G, to get a
 	document. Then choose the VMS file option. When asked for the file
	name, enter "OAUSER:EX_HELP.TXT" and press return. You will be
	returned to the editor with the contents of this file. Next press
	GOLD F, to save this to the scratchpad. You may then use the
	Print option to print the file from the scratchpad.

	Alternatively, if you are comfortable with DCL commands, you can
	simply print the file EX_HELP.TXT which is in the ALL-IN-1
	subdirectory of the EX_MIGRATE account.


ALL-IN-1 and VMS are trademarks of Digital Equipment Corporation
Microsoft Exchange Server is a trademark of Microsoft Corporation


KIT CONTENTS:
-------------

README.TXT		Installation instructions (This document)
EX_ATMSG.TXT		Text for body of message to host binary attachments
EX_HELP.TXT		Help text
EX_INDEX.FLG		ASCII version of user index form
EX_INDM.FLG		ASCII version of user index menu form
EX_MENU.FLG		ASCII version of Migration menu form
EX_MORE.FLG		ASCII version of MORE$SCROLL$KEYS$INDEX form
EX_PST.FLG		ASCII version of Migration parameter form
EX_SEL.FLG		ASCII version of log selection form
EX_STAT.FLG		ASCII version of the migration status form
EX_FC.BLP		Template for creating drawer access document
EX_ATTS.SCP		Script to process all attachments for a given doc
EX_BUILD.SCP		Script to start the build document and schedule data
EX_CAL.SCP		Script to process calendar information
EX_DOCS.SCP		Script to process all docs for a given user
EX_PARSE.SCP		Script to parse for special characters & fix them
EX_FILER.MAR		Assembler language program for building secondary files
EX_CVT.FDL		File Definition for converting seq. files to stream
EX_INST.COM		Installation procedure (VMS command procedure)
EX_SNIFF.COM		Procedure to test for halt command during processing

Note: ALL-IN-1, PATHWORKS, and VMS are trademarks of Digital Equipment
Corporation.


Copyright(c) 1994-1996 Microsoft Corporation.  All Rights Reserved
