Microsoft KB Archive/125478

= Replicating Login Scripts from Windows NT to LAN Manager =

Article ID: 125478

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Advanced Server 3.1
 * Microsoft Windows NT Server 3.5
 * Microsoft LAN Manager 2.2c

-



This article was previously published under Q125478



SUMMARY
This article describes a procedure that ensures proper replication of login scripts from a Windows NT server to a LAN Manager server.



On The LAN Manager Server
 Check for the following entries in the LANMAN.INI file and create them if they do not exist:

In the [replicator] section:

replicate = import

importpath = 

(For example, REPL\ACCTS. This must be relative to the LANMAN directory and is needed only if your import directory is something other than repl\import)

importlist = 

(For example, SALES-PDC)

logon = 

(Must be the same as the account used on the Windows NT export server)

password = 

(must be the same as the account used on the Windows NT export server) tryuser =

(default = yes, set to "no" if you do not want the LAN Manager server to attempt to update directories while a user is logged on locally)

In the [netlogon] section:

scripts = 

(For example, REPL\IMPORT\SCRIPTS) Create the import path directory tree if it does not exist (ie. C:\LANMAN\REPL\IMPORT\SCRIPTS). Start the Replicator Service on the LAN Manager server with the command, NET START REPLICATOR. You may also want to add the Replicator Service to the list of services started automatically in the [server] section of the LANMAN.INI file, per the following example:

srvservices = alerter,netlogon,replicator



On The Windows NT Server
 Create the replication account in User Manager for Domains, making sure that the username and password match the account being used on the LAN Manager server. Also, make sure that all options requiring user intervention (such as User Must Change Password at Next Logon) are disabled.</li> Add the replication username to the Domain Users, Backup Operators, and Replicator groups and exit User Manager for Domains.</li> Start the Services option in Control Panel and from the Service list, select Directory Replicator. Then choose the Startup button.</li> Under Startup Type, select the Automatic option button.</li> Under Log On As, select the This Account option button and choose the ... button to open the Add User window and obtain the Names list.</li> Select the replicator account from the Names list, choose the Add button, and then choose the OK button.</li> Under Log On As, enter the password for the replicator account in the Password box, re-enter the password in the Confirm Password box, and choose the OK button and then the Close button to close the Services window.</li> Run the Server option in Control Panel, choose the Replication button, select the Export Directories option button, and verify that the path shown in the From Path box is correct. For example:

C:\WINNT\SYSTEM32\REPL\EXPORT

</li> From the Directory Replication window (opened in step 8 ), choose the Add button under the To List field, select the name of the LAN Manager server or the domain in which the LAN Manager server resides from the Select Domain list, and then choose the OK button to close the Select Domain window. Choose the OK button to close the Directory Replication window and choose the OK button to close the Server window.</li> Start the Services option in Control Panel again and from the Service list select Directory Replicator. Choose the Start button to start the Directory Replicator service and then choose the OK button to close the Services window.</li> Start the Servers option in Control Panel again and choose the Shares button to view replication activity when it occurs. You can view the replication session establishment in the Connected Users box by watching for a username using the REPL$ share.</li></ol>

If Replication Does Not Occur
Follow these steps if an initial replication does not occur.  Stop and restart the Directory Replicator service via the Services option in Control Panel on the Windows NT server and check for any errors in Event Viewer. If no errors regarding this service exist, proceed to step 11 above to watch for replication to occur.</li> Stop and restart the Replicator service on the LAN Manager server by issuing the following commands in succession:

NET STOP REPLICATOR NET START REPLICATOR

After issuing these commands on the LAN Manager server, you should see the file OK$ in the import directory of the LAN Manager server.</li> If replication problems persist, check Event Viewer on the Windows NT server and the error log on the LAN Manager server (using the command NET ERROR) for indications of specific error conditions related to replication.</li></ol>

For more information on replication, query on the following keywords here in the Microsoft Knowledge Base.

<pre class="fixed_text">  replication import export

Additional query words: prodnt prodlm 3.10 2.2c

Keywords: KB125478

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.