
Introduction
============

ARCserve* allows you to backup, copy or restore files to and from Windows NT*
workstations with Client Agent for Windows NT loaded on the network. The Client
Agent for Windows NT is a Windows application (.exe) that you start like any 
Windows application. The Client Agent for Windows NT has a screen where you
can view information about the agent and the workstation on which it is running.



Installing Client Agent for Windows NT
======================================

Because Client Agent for Windows NT uses the IPX protocol, the NetWare* Link 
(NWLink) transport must be installed before you can run Client Agent for 
Windows NT. For more information about the transport and its parameters, 
refer to the Windows NT User's Guide.

NOTE:
If your Windows NT Version 3.1 is running NWCS (NetWare Workstation Compatible 
Service) or CSNW (Client Service for NetWare) , please see Section Notes issue 
#1 before running Client Agent for Windows NT.

NOTE:
If you are running Windows NT Version 3.5, please see Section Notes issue #2 
before running Client Agent for Windows NT.

1. To install the Client Agent for Windows NT, copy the following files from 
diskette to the appropriate Windows NT workstation:

	*  A:\NTAGENT.EXE  and
	*  A:\NTAGENT.HLP

2. You need to have ARCserve Version 501E installed on a NetWare server.

3. Copy WSTAPE.NLM and ARCOPY.NLM from diskette to the ARCSERVE's NLM directory on the
ARCserve server (eg. SYS:ARCSERVE\NLM). 

4. Copy ASDB.DLL from diskette to the ARCserve manager directory (eg. c:\AS50 or 
SYS:ARCSERVE\MANAGER).



Loading Client Agent for Windows NT
===================================

Suppose you installed NTAGENT.EXE and NTAGENT.HLP to C:\AGENT directory.
To load Client Agent for Windows NT, enter the following command at the NT 
command line:

	C:\AGENT\NTAGENT

To load Client Agent for Windows NT with a password, enter the following 
command at the NT command line:

	C:\AGENT\NTAGENT  <password>

If you want the Client Agent for Windows NT be started automatically whenever 
you log on Windows NT, create a program item for Client Agent for Windows NT 
in the Startup group.




Client Agent for Windows NT Options Menu
========================================

1. Password

This option specifies the password you want associated with Client Agent for 
Windows NT on your machine. Any input here will overwrite the previous 
passwords including the one specified in command line when Client Agent for 
Windows NT was started.

2. Status Log File

This option specifies the Status Log File which records information for each 
session performed by Client Agent for Windows NT. Default status log file 
is C:\AGENTERR.LOG.   You can change the path and filename  here.

3. Registry restore

This option specifies whether  the restore operation needs to restore the NT 
Registry or not if the session been restored includes NT Registry files. This 
option is set OFF by default. Turn on this option only if you want to restore 
previous registry. This option can be turned on from command line by entering 
the following command at NT command line:

	ARCSERVE\AGENT\NTAGENT  -R



Excluding directories with Client Agent for Windows NT
======================================================

You can exclude directories or drives on a Windows NT workstation with Client 
Agent for Windows NT, so ARCserve will not be able to back them up or browse 
them from the ARCserve Manager.

To exclude any directories or drives, use a text editor, create a file named
ARCAGENT.LOG similar to the one below, containing the names of directories 
and/or drives to be excluded from the backup. This file must be in the root 
directory of the C: drive.


C:\letters
D:\mydir
E:


The Client Agent for Windows NT will automatically search for ARCAGENT.LOG 
before a backup job or browsing.




Client Agent for Windows NT Features
====================================

Client Agent for Windows NT provides the following workstation data management
functions:

1. Query

From ARCserve manager, users can browse drives, directories and files on a 
Windows NT machine with Client Agent for Windows NT. File names are displayed 
in Long Name format if the file system being queried is HPFS or NTFS.


2. Backup

Windows NT supports FAT, HPFS and NTFS file systems. Client Agent for 
Windows NT is capable of backing up long filenames, file data, security data, 
extended attributes and alternate data streams supported under these file 
systems.


3. Copy

ARCserve Manager can copy files and directories from a Windows NT workstation 
to a server volume or to the local PC client drive.


4. Restore

Client Agent for Windows NT allows restoring files to a file system different 
from the one they were backed up from.
Note:  Restoring files backed up from NTFS file system to a FAT file system may
result in the loss of security data and extended attributes. Restoring files 
backed up from FAT to an NTFS file system will generate system default security
data for these files.


5. Compare

Client Agent for Windows NT provides a compare function so ARCserve can verify 
the data written to tape with the data on the local NT machines.


6. NT Registry Backup/Restore

Client Agent for Windows NT allows users to backup/restore the Register 
information which is stored in the NT system config directory , 
C:\WINNT\SYSTEM32\CONFIG. Any attempt to backup files in this directory will 
trigger the checking and backup of Registry files.

Restoration of the Registry occurs if the Registry_Restore option is turned on 
and the session which is going to be restored includes the current NT 
workstation's system config path,  C:\WINNT\SYSTEM32\CONFIG. Client Agent for 
Windows NT restores (swaps) the Registry files in directory \TEMP under Windows
NT boot drive.

Note: Under Windows NT, only users with administrator privilege can do a 
complete registry backup/restore. Otherwise, an error message will be generated
in Client Agent for Windows NT's status log file.


7. NT Event Logs

Event Log files are also located under the NT system config directory.  Client 
Agent for Windows NT retrieves the contents of event log files and generates 
files with the same file names as the event log files except that the extensions
of the filenames are changed to .BAK. For example, Event Log file  SYSEVENT.EVT
will be backed up as SYSEVENT.BAK file by Client Agent for Windows NT.



Notes
=====

1. If you are using Windows NT Version 3.1 and have

 * Microsoft NWCS, NetWare Workstation Compatible Service, Dec. 93 Beta version 
or
 * Microsoft NWCS, NetWare Workstation Compatible Service, Jan. 94 Beta version
or
 * Microsoft CSNW, Client Service for NetWare, Jun. 94 release version

installed on NT,  a communication time-out (E5042) might occur between Client 
Agent for Windows NT and ARCserve during a backup operation.
This is possibly caused by a fragmentation problem in NWCS. To work around this
problem, you can use the NT registry editor to change NWLINKIPX parameters by
following the instructions below. For more information on NWCS fragmentation 
problem, please contact Microsoft technical support. If you do not need NWCS 
services, removing NWCS from NT will also solve this problem.

To change the NWLINKIPX parameter:

     (1) From a Command Prompt under Windows NT, type regedt32 then press
	 Enter key. This should bring up Windows NT's registry editor.

     (2) Focus on the HKEY_LOCAL_MACHINE window inside the registry editor.
	 You should be able to see several subkeys, including HARDWARE, SAM...
	 etc., under HKEY_LOCAL_MACHINE key.

     (3) Double click on SYSTEM subkey under HKEY_LOCAL_MACHINE key.

     (4) Double click on CurrentControlSet subkey under SYSTEM key.

     (5) Double click on SERVICES subkey under CurrentControlSet key.

     (6) Double click on NWLINKIPX subkey under SERVICES key.

     (7) Double click on PARAMETERS subkey under NWLINKIPX key.

     (8) With PARAMETERS key hi lighted, select 'Add Value' under 'Edit' pull
	 down menu. Type in RouterMtu in the Value Name input field. Select
	 REG_DWORD in the Data Type selection. Click on OK.
	 Note: RouterMtu is a case sensitive value name.

     (9) A DWORD Editor should popup. From Radix group, select Decimal button.
	 Type in 2000 in the Data entry field. Then, click on OK.

     (10) You can verify these values on the right-hand side of the window.
	  Select Close under Registry pull down menu to close the registry file.
	  Close Registry Editor.

     (11) These update will take effect after a REBOOT.



2. A similar problem (mentioned in 1.) may occur when running Client Agent for
Windows NT under Windows NT Version 3.5 with or without CSNW installed.
To work around this problem:

 (a) If your Windows NT is running under Ethernet network,

     you can use the NT registry editor to change NwlnkSpx
     parameters by following the instructions below:

     To change the NwlnkSpx parameter:

     (1) From a Command Prompt under Windows NT, type regedt32 then press
	 Enter key. This should bring up Windows NT's registry editor.

     (2) Focus on the HKEY_LOCAL_MACHINE window inside the registry editor.
	 You should be able to see several subkeys, including HARDWARE, SAM...
	 etc., under HKEY_LOCAL_MACHINE key.

     (3) Double click on SYSTEM subkey under HKEY_LOCAL_MACHINE key.

     (4) Double click on CurrentControlSet subkey under SYSTEM key.

     (5) Double click on SERVICES subkey under CurrentControlSet key.

     (6) Double click on NwlnkSpx subkey under SERVICES key.

     (7) Double click on PARAMETERS subkey under NwlnkSpx key.

     (8) With PARAMETERS key hi lighted, select 'Add Value' under 'Edit' pull
	 down menu. Type in RouterMtu in the Value Name input field. Select
	 REG_DWORD in the Data Type selection. Click on OK.
	 Note: RouterMtu is a case sensitive value name.

     (9) A DWORD Editor should popup. From Radix group, select Decimal button.
	 Type in 2000 in the Data entry field. Then, click on OK.

     (10) You can verify these values on the right-hand side of the window.
	  Select Close under Registry pull down menu to close the registry file.
	  Close Registry Editor.

     (11) These update will take effect after a REBOOT.


 (b) If your Windows NT is running under Token Ring network,

     Run Client Agent for Windows NT with -! option. This option forces the 
     agent to use 512 byte packet size.

     For example:  NTAGENT -!


3. Presently, a Windows NT node can not be automatically tracked with ARCserve's
Client Tracker NLM. In order to display a Windows NT node address in Managers,
such as Backup or Database,  you will need to add a record in the Client 
database for each Windows NT running Client Agent for Windows NT. Please refer 
to ARCserve User Guide, Chapter 11 Managing Databases, Client database section.



Trademarks
==========

* ARCserve is a registered trademark of Cheyenne Software, Inc.
* Windows NT is a registered trademark of Microsoft Corporation.
* NetWare is a registered trademark of Novell, Inc.
