Kbase 19244: How To configure windows to Start A Broker Under a Windows User?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/15/2009 |
|
Status: Verified
GOAL:
How To configure windows to Start A Broker Under a Windows User?
GOAL:
How to configure windows to start admin server under a windows user?
GOAL:
How to define a Windows user account to start a Unified broker?
GOAL:
How to define a Windows user account to start admin server?
GOAL:
How do I start a Ubroker Process in Windows under a different user account?
GOAL:
How do I start admin server Process in Windows under a different user account?
GOAL:
Account permissions needed to start Appserver or Webspeed broker
GOAL:
Account permissions needed to start admin server
GOAL:
How To Start A (webspeed) Broker with Domain Account?
GOAL:
How To Start admin server with Domain Account?
GOAL:
How to configure a Windows 2000 DC policy rights when starting AdminServer as an account.
GOAL:
What are the additional privileges required for starting Services on Windows 2000.
GOAL:
How to start Adminserver using another user other than system
FACT(s) (Environment):
Progress 9.x
WebSpeed 3.x
OpenEdge 10.x
Windows
FIX:
In order to start a unified broker under a windows user account, the windows user needs to be granted appropriate privileges.
You can set a user to be the owner of the process of any unified broker: WebSpeed, AppServer, ORACLE DataServer, ODBC DataServer and MSS DataServer.
You can define it in Progress Explorer. For more details on how to define a user in ubroker.properties file or through progress explorer to start a unified broker, please reference Progress Solutions:
P6373, How do I start a Ubroker Process in Windows under a different user account?
Extra privileges are required for the specified user before you start the broker using that specific account:
- Administrator.
- Log on as a service.
- Log on as batch job.
- Act as part of the operating system.
- Increase quotas.
- Create a token object.
- Replace a process level token.
If the user does not have all the rights specified above, the broker will not start.
These are the steps to set rights for a user :
For Windows NT :
1) From Start - Administration - User Manager, select Policies -
select User Rights menu
2) Check the option "Show Advanced User Rights"
3) From "Right" option, Select the option : "Log on as a batch
job"
4) Click on "Add" button
5) Select your NT DOMAIN from "List Names From "
6) Click on "Show Users"
7) Select the USER and click on Add button
8) From "Right" option, select "Log on as a service"
9) Re-do steps from 4 to 7 to add the other rights
For Windows 2000 and windows 2003 that is not Primary Domain Controller:
1) add the user as a local Administrator:
Start->Programs->Administrative Tools->Computer Management,
expand System Tools,
expand Local Users and Groups,
select Groups,
right-click on Administrators,
select Properties and add your user to the local Administrator group.
2) Go to Start -> Programs -> Administrative Tools -> Local
Security Policy
From left pane choose Local Policy -> User Rights Assignment
In the right pane you have to find following Policies:
- Log on as a service.
- Log on as batch job.
- Act as part of the operating system.
- Increase quotas.
- Create a token object.
- Replace a process level token.
Double-click on each one of the policies stated in the previous step and add the user account that you wish to use to start the broker.
For Windows 2000 primary domain controller
1) Go to Start -> Programs -> Administrative Tools -> Domain Controller
Security Policy
2) Add following rights
- Administrator.
- Log on as a service.
- Log on as batch job.
- Act as part of the operating system.
- Increase quotas.
- Create a token object.
- Replace a process level token.
The "Increase quotas" has been replaced by "Adjust memory quotas for a process" on XP and 2003