PC DirSync: Removing Users from Directory Synchronization

 Last reviewed: May 28, 1996
Article ID: Q131151
The information in this article applies to:
  • Microsoft Mail for PC Networks, versions 3.0, 3.2, 3.2a, and 3.5

SUMMARY

When you create a user, there is an option to include the user in Directory Synchronization (Dir-Sync). If the user is included in Dir-Sync, but the requirement to keep the user in the Postoffice Address List but remove the user from Dir-Sync is needed, you can Modify the user; select N to not include the user in Dir-Sync. This will create a Delete transaction in the REQTRANS.GLB that will delete the user from all Requestors participating in Dir-Sync.

MORE INFORMATION

An alternative method is to use Import. Use a text editor to create a file with the following format: 

   D in Col 1   Alias name in  3 - 33 ,  in col 34 address
   type:network/po/username
For example: 

   D  User1 alias                  PCM:NET1/PO1/USER1
Use the following command to import the file into a Requestor (preferably the Dir-Sync server): 

   Import Admin -ppassword   -E  -ffilename.txt  -ddrive
The deletion will be sent to all the participating Requestors for deletion from their .USR files without effecting the address in the Postoffice Address List.

Additional reference words: 3.00 3.20 3.20a 3.50 import dirsync delete usr
KBCategory: kbenv
KBSubcategory: MailPCDirSync

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 28, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.