3.1 Creating Accounts for Authentication

If the GroupWise driver is on the same server as the GroupWise domain database, skip this section. No authentication accounts are required.

When the GroupWise driver is installed on a Windows server and the GroupWise domain database resides on a remote Windows/NetWare server, you need to create accounts on both servers to enable the driver to authenticate to the domain database server and access the database. This is the only remote database scenario (Windows server with the driver and remote Windows/NetWare server with the database) that is supported. For more information, see Section 2.1, Where to Install the GroupWise Driver.

When you create the user account for the Windows server that is running the driver:

  • Add the user account to the Administrators group.

  • Deselect any options that force the account password to be changed or that cause it to expire.

  • In Administrative Tools, access Local Security Policy > Local Policies > User Rights Assignment and add the account to the Log On as a Service policy.

When you create the user account for the Windows/NetWare server where the GroupWise domain database resides:

  • Use the same username and password you used for the account on the driver’s server.

  • For a Windows server, create a new share for the drive where the GroupWise domain database resides. Remove the Everyone group from the share’s Permissions list. Add the driver’s user account to the Permissions list and give it Full Control.

  • For a NetWare server, use iManager or ConsoleOne to give the user account Read, Write, Create, Erase, Modify, and File Scan access to the GroupWise domain directory and subdirectories.