Technical article 109880

File replication from AFPS 3.5.2 to Windows NT 4.0.

OpenServer 5.0.4

Written · Last revised

Problem

How do I set up file replication from SCO AFPS 3.5.2 to a Microsoft Windows NT 4.0 system?

Solution

As an example only, two systems are set up as follows:

BDC                             PDC
NTDOM domain                    NTDOM domain
+-------------+                 +------------+
|             |                 |            |
|             |                 |            |
|   SCOTEST   | - - - - > - - - |   SCORE    |
|             |                 |            |
|             |                 |            |
+-------------+                 +------------+
OpenServer 5.0.4                NT Server 4.0
AFPS 3.5.2n                     NT Service Pack 3

The AFPS system is configured to be a Backup Domain Controller (BDC) to the Windows NT Primary Domain Controller (PDC) in the domain "NTDOM". The AFPS system is then configured to be an "export" server and replicate its files to the NT system acting as the "import" server. Make sure you are familiar with the systems' UNIX "root" and AFPS and NT systems' "administrator" passwords.

(1) A special user account is created so that the import systems
can use it to log on (as in domain rather than UNIX logon) to the
export server. This user account can ONLY be created using the NT
Server Tools "User Manager for Domains" utility, as the option for
setting a non-expiring password is not available with the UNIX
command line "net user" command. The account can be created on the
NT system. The account details will be replicated across to the
AFPS BDC, or from an additional Windows PC configured with the
Windows NT Server Tools, which are supplied in the "ASTOOLS" share
on the AFPS server.

Choose "Start", "Programs", "Administrative Tools", "User Manager" and set:

User, New User;
Username:       scorep

NOTE: You can choose any name, so it might be good to have "rep" as part of it.

Full Name:      Replication User
Description:    same
Password:       scorep
Confirm:        scorep

Note: Now click the "Password Never Expires" check box AND clear all the other check boxes. Leave the other settings as default.

(2) Next, the NT import server is set up to receive the files from the export server. Choose the "Server Manager" from the Windows NT Server Tools utilities and double-click on "SCORE", which appears listed as the Windows NT 4.0 Primary server on the screen.

Choose "Replication" and set the "Import Directories" by clicking the check box. This should set the default Path to:

"C:\WINNT\System32\Repl\Import"
At the bottom of the screen you will see the "Logon Script Path"
set to "C:\WINNT\System32\repl\import\scripts".
Click "OK" and exit.

In this case the system "SCORE" is configured only to receive files, whereas it can be configured to both receive and send out files.

The services running on the server may be examined using the Server Manager by choosing "Computer" and "Services". The "Directory Replicator" status is listed as Started and Manual. Alter this by double-clicking on the entry and setting it to "Automatic". In the bottom box of this screen, click on the square button to the right of the "This Account" line. Add the user that was created earlier, "scorep". This adds "NTDOM\scorep". Confirm the user password again and click "OK". You should see the message:

The account NTDOM\scorep has been granted the Log On As A service right and added to the Replicator local group

(3) Next, configure the AFPS export server. Create a few test files in the export directory that should appear in the import directory as mentioned in part (2). The default export directory already has some files there:

$ pwd
/var/opt/K/SCO/asusrv/3.5.2n/usr/net/servers/lanman/shares
                /asu/repl/export/scripts
                $ ls
                netlogon.bat
                netlogon.cmd

The "netlogon.bat" file can, for example, be altered to be replicated throughout your servers so that a standard logon script can be presented to your PC clients upon logon to the domain.

Create or place some test files into this directory to confirm replication to the import server. In this case, the files "test1.txt" and "test2.txt" are created.

The default import and export directories are used in this example but you can specify any replication directory you may require.

Next configure the export replicator service.

Assign the "scorep" logon account to the replicator service. From the NT-based Server Manager utility, highlight the export server and choose "Computer", "Services", "Directory Replicator", "Startup". Set startup type to Automatic and the "Log on As:" account name under "This Account" as (again by clicking on the square button option) "NTDOM\scorep". Confirm the password again and click "OK". Start the export replicator service via the Server Manager.

The settings of the AFPS Replicator service can be seen in the AFPS "/usr/net/servers/lanman/lanman.ini" file. For example:

...
[ netlogon ]
scripts=/usr/net/servers/lanman/shares/asu/repl/import/scripts
                [ replicator ]
                replicate=export
                exportlist=NTDOM
                logon=scorep
exportpath=/usr/net/servers/lanman/shares/asu/repl/export
importpath=/usr/net/servers/lanman/shares/asu/repl/import
                interval=5
                pulse=3
                guardtime=2
                random=60
                importlist=SCORE

(4) The replicator services on both systems should now wait until stabilized and then transfer the files. Check the import server import directory "C:\WINNT\System32\Repl\Import\Scripts" for the appearance of test files. Unlike the UNIX-based system, no replication flag files appear on the NT side. If, after a period of time, no replication has taken place, stop and restart the services on both systems with the NT Server Manager and try again. If no transfer occurs, recheck/reset the password settings for the "scorep" user.

See also

SCO Advanced File and Print Server System Guide, P124-137.

ta109852, "File replication from AFPS 3.5.2 to 3.5.2 systems".

From the Xinuos technical article database, record 109880. Reproduced with permission. The original is at www.sco.com/ta/109880, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.