Title: Controlling RightFax USER Creation/Modification During Active Directory Synchronization Technote #: 0201729016

of 7 Title: Controlling RightFax USER Creation/Modification During Active Directory Synchronization Technote #: 0201729016 Date: 01/22/2002 Product: Release - RightFAX 8.00 Category: Info windows 2000 users groups kb2000 schema rfxch2k adsynch Issue/Question: By default, EVERY Domain User in the Active Directory Domain I configure to synchronize is created as a RightFax user during Active Directory Synchronization. Answer: Captaris Technical Support will not support VB Script code. This article is for informational/example purposes only. The information in this article allows you to execute custom VB script. DO NOT CREATE OR MODIFY THE CODE IN THIS ARTICLE UNLESS YOU KNOW WHAT YOU ARE DOING! Examples in this article assume that you are familiar with Active Directory terminology as well as the tools used to manage and edit Active Directory. Copies of all of the XML files used to update the Active Directory Schema and Configuration can be found at http://www.rightfax.com/schemas. Scenario #1: Controlling RightFax USER creation based on Windows 2000 Domain USER Name. To accomplish this, VB code is required as Custom Code in the CaptarisSynchConfig setup. #1. Open the CaptarisSynchConfig console tool from the RightFax WorkServer Configuration tool. This is done by clicking on "Configure Profiles" from the Active Directory synch cfg in the WorkServer Configuration.

of 7 #2. Create a new profile. From the Action menu of the CaptarisSynchConfig console select New > Profile. #3. Supply a Profile Name (required) and a Parent Profile (if needed - we DO recommended) then press OK to save the new profile.

of 7 #4. Select the new profile on the left side of the console, then from the Action menu of the CaptarisSynchConfig console select New > Item. #5. Select samaccountname as the Windows Attribute and rfaxid as the RightFax Attribute.

of 7 #6. On the Custom Code tab of New Item Properties enter the VB Script code (example below, case sensitive) that aborts RightFax user creation for the Domain Users of your choice.

of 7 #7. Apply and save everything at this point and the configuration is complete. The Domain Users you setup up to be excluded from the synchronization should successfully be aborted during the synchronization process. The RightFax WorkServer Service performing the Active Directory synchronization will report the following when in verbose debug mode during the synchronization, validating what we've just created/configured: ADsynch: About to load the RightFax COM API Library. ADsynch: Successfully created an instance of the RightFax COM library. ADsynch: Successfully opened the fax server 'RHOADS'. ADsynch: User (ADMINISTRATOR) successfully added/update. ADsynch: User (Guest) successfully added/update. ADsynch: User (TsInternetUser) successfully added/update. ADsynch: A custom action has been processed for the user 'IUSR_CLAPTON.' This act ion has caused the user to be aborted. Mapping Field = CN=sAMAccountName-rfaxID, Reason = Special Users are not synchhed.. ADsynch: A custom action has been processed for the user 'IWAM_CLAPTON.' This act ion has caused the user to be aborted. Mapping Field = CN=sAMAccountName-rfaxID, Reason = Special Users are not synchhed..

of 7 ADsynch: User (krbtgt) successfully added/update. ADsynch: User (WOODSTOCK$) successfully added/update. ADsynch: User (suu) successfully added/update. ADsynch: User (mkk) successfully added/update. ADsynch: User (sac) successfully added/update. ADsynch: User (edp) successfully added/update. ADsynch: User (82FD1F1E-6E4B-48A3-B) successfully added/update. ADsynch: User (broke) successfully added/update. ADsynch: Active Directory synch succeeded. Scenario #2: Controlling RightFax USER creation based on Windows 2000 Organizational Unit Enrollment. To accomplish this, VB Code could be used like the example above, however, a workaround to supplying the code could be to create an Organizational Unit in Active Directory and DENY access to the service acct. the RightFax WorkServer performing Active Directory synchronization uses. The Organizational Unit will be "invisible" to the service account and will not generate any errors during the synchronization, as if the Organizational Unit does not exist. So, you can effectively NOT synchronize certain users by making them members of the Organizational Unit you've created. The new Organizational Unit in Active Directory (called No_Synch in this example): Deny access to the WorkServer Service Account to this Organizational Unit:

of 7 Entered by: Eric Phillips/Olympus Approved by: Alex Cooper/Olympus 01/23/2002 02:42:20 PM