Release Notes: MultiView 2007 Central Administration Sample Release Version: 7.0.00 Release Date: May 31, 2007 ================================================================================ Please review this document carefully before installing or using any of the files discussed in this document. These notes contain last-minute information that may affect your use of the files. ================================================================================ Contents 1.0 Introduction 2.0 Instructions for Use 3.0 Technical Support ================================================================================ 1.0 Introduction This procedure is for Windows NT 4.0 Servers and Workstations participating in a domain. ================================================================================ 2.0 Instructions for Use The NT4 Server Resource Kit Must be installed on the server. A response file must have been produced which is specific to the site to be installed. a) Create a directory on the server (which is either a PDC/BDC or member server for the domain that contains the workstation) where the MultiView 2000 central administration scripts will be stored. b) Create subdirectories in the directory created in (a) to hold the MultiView 2007 installation files and logs files generated by the installs. c) Copy the central admin scripts to the directory created in (a). d) Copy the MultiView 2007 installations files from the distribution CD to the directory created in (b). e) Copy the m2kinst.cmd file from the scripts directory to the installation files directory. f) Copy your silent install response file to the installation files directory, and rename it m2k.iss. g) Edit the siteinst.cmd script and change the following parameters to suit your site: SRCDIR - Source directory for MultiView 2000 installation files created in (b) LOGDIR - Install logs directory created in (b) ADMINACCOUNT - fully qualified name of administrators account, i.e., domain\accountname MACHINELIST - list of machine to be installed to, separated by spaces h) Open a command prompt on the server console. i) Change to the script directory, created in (a). j) Run the siteinst.cmd script using this syntax: siteinst.cmd