Preparing Windows

The installation program uses Windows APIs that require additional user rights to function properly. If these user rights are not granted, the installation program fails.

Before you begin

You must ensure that you are using a supported version of the Windows operating system. For information, see the requirements for Watson Explorer Content Analytics.

If you install the product as a non-root user, you must install the product on a single server and some functional limitations occur. See the topic about administrative IDs and passwords for more information about using a non-root user as the administrative user.

About this task

If the user ID that you use to install the product belongs to a domain, the domain policies override the local user settings. Before you assign user rights to a user ID, ensure that the domain does not deny any of the required rights. For example, if the domain denies the right to act as part of the operating system, then the user is denied that right.

If an attempt to install the product fails because these user rights are not correctly assigned, you must remove the software, assign the correct user rights to the user ID that you use to install the product, and run the installation program again.

Procedure

To grant administrative user rights:

  1. In Windows, click Control Panel > User Accounts.
  2. Ensure that the user ID that you want to use has administrator privileges.
  3. In Windows, open Control Panel > Administrative tools > Local Security Policy > Local Policies > User Rights Assignment.
  4. Ensure that the user ID has the following user rights:
    • Act as part of the operating system
    • Lock pages in memory
    • Create a token object
    • Replace a process level token
    • Impersonate a client after authentication
    • Increase quotas (In Windows 2008, this option is labeled Adjust memory quotas for a process.)
    • Log on as a service

What to do next

If you use WebSphere® Application Server and set up WebSphere Application Server as a service, you must ensure that the WebSphere Application Server user ID that is associated with the Windows service has the appropriate administrative privileges and user rights. The WebSphere Application Server user ID must be an administrator ID with the following user rights:
  • Act as part of the operating system
  • Log on as a service

If WebSphere Application Server does not run as a service, you do not need to set up or verify user rights for the WebSphere Application Server user ID.