Setting the seeadmin User Privileges

You may need to configure the new seeadmin user account to function in the Windows environment.

The following guidelines should be used when determining if the seeadmin user has sufficient privileges:

  • Verify that the seeadmin user is a member of the Administrators group as described in Creating the seeadmin User. This group assignment is necessary to administer DB2, WebSphere, and the SIMULIA Execution Engine database.

  • If the seeadmin user installs DB2, the seeadmin user will automatically be granted all permissions needed to administer DB2. In this case you must log in as this seeadmin user to install DB2. Changing the security context to this user via the runas utility is not sufficient. If DB2 was installed by a different user, the seeadmin user must be added to the local group DB2ADMNS, created by the DB2 installation, to be able to create and administer the SIMULIA Execution Engine database.

  • If the seeadmin user is going to be used to start a SIMULIA Execution Engine station when the SIMULIA Execution Engine database has Run-As security enabled, the seeadmin user must be granted the privilege Replace a process level token. For more information, see Configuring Station (Run-As) Security.

  • If you add a user to a new group or grant it a privilege, the change does not take effect until you log out and log in again as that user. Groups assignments and privileges are checked only during the logon process.