The following explains how to change the startup account of Systemwalker Operation Manager. If you are using the startup account as the Systemwalker Operation Manager user, you must change the user information of Systemwalker Operation Manager, too.
The "Systemwalker Operation Manager user" is:
A owner of a Jobscheduler project
A job owner
A user registered in the password management book for Task Link.
Procedure
Change the startup account of Systemwalker Operation Manager's services.
Change the user information of Systemwalker Operation Manager. (If the information change is required)
These steps are detailed below.
1) Shut down Systemwalker Operation Manager's services.
Shut down all services of Systemwalker Operation Manager.
For details of service shutdown, see the section "Shutting Down the Systemwalker Operation Manager Servers [Windows version]" of the Systemwalker Operation Manager User's Guide. You cannot shut down all services of Systemwalker Operation Manager from the Service Control of the Systemwalker Operation Manager Environment Setup window.
2) Rename the startup account name.
Rename the user of the startup account using the OS's user renaming function.
To use a new or existing user as the startup account rather than changing the user name (while still keeping the old user), the new account must meet all of the following conditions.
The user must belong to the Administrators group on the local computer.
The following privileges must have been assigned to the user:
The Log on as a service privilege
The Act as part of the operating system privilege
The Increase quotas privilege (for Windows Server 2008 or later, this is Adjust memory quotas for a process)
The Replace a process level token privilege
The password for the user must not expire.
The user name and password must not include spaces.
A local system account must not be selected.
If these conditions are not met, the following issues will occur:
The Systemwalker Operation Manager service will fail to start.
This is caused by conditions b and c above.
A user authentication error will occur when the client starts and an attempt is made to connect by specifying the user name and password.
This is caused by conditions a and b above.
To use the server function of this software on a computer that belongs to a Windows Server 2008 or later domain, specify the following kind of user as the startup account for the "Systemwalker ACL Manager" service.
A user that meets all of the conditions above and that has been registered with the domain that the computer belongs to.
3) Change the startup account of Systemwalker Operation Manager's services.
Select Control Panel >> Administrative Tools >> Services of Windows Server 2008, and check and change the following items for each of the Systemwalker Operation Manager's services.
Make sure that the startup account has been set in the service logon account.
Enter the changed account name in the Account field, and enter the changed password in the Password and Password Confirmation fields.
No action is required.
4) Restart Systemwalker Operation Manager's services.
Restart Systemwalker Operation Manager's services you have shut down in Step 1.
For details of service startup, see the section "Starting Up the Systemwalker Operation Manager Servers [Windows version]" of the Systemwalker Operation Manager User's Guide.
5) Reset the shutdown job nets.
You must set the shutdown job nets again if the "Shutdown job nets" have been defined in the Jobscheduler. For the details of shutdown job nets, see the section "Shutting Down the System at Optional Time [Windows version]" of the Systemwalker Operation Manager User's Guide.
To execute them as shutdown job nets, each account must satisfy the following requirements
The job nets have been registered in the project having the same name as the startup account of "Systemwalker MpJobsch" services.
The job net name is either "JSHEND" or "JSHFORCE."
Therefore, if you have changed the service startup account, you must create a project having the same name as the new startup account on the Jobscheduler and you must copy the shutdown job net ("JSHEND" or "JSHFORCE") in a location under the new project. (Also, you must delete the old project information after this copy.)
Reset the system if necessary.
6) Change the user information of Systemwalker Operation Manager.
You must change the specified information if the startup account has been defined as the job owner or if it has been defined in the password management book for Task Link.
The following explains how to change the user information of Systemwalker Operation Manager in the following steps.
These steps are detailed below.
Change the security information of job projects.
You must change the project owner if the startup account of a Jobscheduler project has been set as the owner. Also, you must change the access privilege information of the project if the access privileges of the startup account has been set for the project.
For the procedure to change the project owner, see the section "Changing Projects" of the Systemwalker Operation Manager User's Guide.
Refer to "Setting up Access Permissions for Projects" in the Systemwalker Operation Manager User's Guide for details on how to change the access privileges for projects.
Change the job owner information
You must change the information of job owner if you have specified the Execute jobs under the respective job owner's authority option in the Job Execution Control definition and if there is a job whose startup account has been defined as the owner.
Procedure
Check whether or not the Execute jobs under the respective job owner's authority has been enabled in the Job Execution Control definition.
If enabled, go to Step 2.
For the checkout method, see "2.9.1 Defining the System Operating Information".
If this option is disabled, you need not change the job owner information.
Check whether or not the startup account is registered after you have changed the definition of job owner information.
If the startup account has been registered after the change, you must set the password information again. If not registered, you must register the startup account.
For details to check the definition of job owner information and to set the password, see "2.9.3 Defining the Job Owner Information [Windows]".
If the Previous Load Distribution function is used:
If you are using the Previous Load Distribution function, you must rename the startup account of the distributed server.
The Job Execution Control startup account of the server and the job execution service startup account of the load distribution server must be the same. You must change the startup account name of the distributed load server.
For details of Distributed Execution function and Previous Load Distribution function, see "2.9.1 Defining the System Operating Information".
Change the definition information of password management book for Task Link
You must add the startup account after its change if the Task Link function is used and if the startup account has been defined in the password management book for Task link.
For the definition of password management book, see "2.11.1 Defining a Password Management Book".
