To use RUM with an alternate user database:

1. You must be using verion 3.3.b.20011213 or later. If you have an earlier version, upgrade before proceeding.

2. Install/upgrade normally onto your webserver. When prompted for the service's username, be sure to pick an account that has admin privs on the alternate database (i.e., administrative privileges on the domain if picking a domain, or on the particular standalone server if picking a server).

   Don't try to configure any helpers or other options at this point. Just click through until the install is finished.

3. Use regedt32 or regedit to add this value on the webserver:

      HKEY_LOCAL_MACHINE
         Software
            Greyware
               Remote User Manager
                  Parameters
   

   SAM Source: REG_SZ: nameofyourpdc

   example: OUR_PDC

   Use the NetBIOS machine name of your PDC, without the two leading backslashes. Note the space between "SAM" and "Source." To verify that you have picked the right name, log on to the webserver using the username/password you specified for the service, and run the command (from a command prompt):

   net use \\OUR_PDC\ipc$

   If you get an error message, either the account you chose does not have sufficient privileges or you are not using the NetBIOS name of the remote machine. (Don't forget to substitute the real machine name for OUR_PDC in the registry and the example command line command above.)

4. Reboot the webserver. (You can just stop and restart the affected services if you prefer -- RUM and all IIS-related services. It's usually faster to just reboot.)

5. Pull up the RUM control panel applet. You should see the groups and users from your selected database. If you had already configured RUM on this machine with the default settings, remove any helpers that are present (they will no longer be meaningful and will just confuse your users).

6. The [sync domain] and [sync machine] options (if enabled) will be replaced by a single [sync database] option. This option will only work on NT4 domains or Win2K domains running in compatibility mode. Win2K domains in native mode (with full AD enabled) will either ignore the sync signal or return error 50 to the RUM web screen. (You may ignore the error message.) Win2K domains sync themselves according to the schedule set up by the Enterprise Administrator.

 Back to Previous Page