Hi sanfranqsr,
The easiest way to do this is to configure a separate manager account with the security privileges you need, change the password to your admin account, and register the aloha services to start with admin permissions.
--Goto start->run->services.msc
--Right click on ctlsvr, goto the logon tab, and have the service logon with the admin account information.
--Repeat for edcsvr
This will allow your core Aloha services to run with administrator privileges, but allow you to lock down anything else through normal windows security management.
If you have any issues with this configuration, here is more detailed info from the Aloha knowledgebase on how to setup core services with alternate credentials:
Summary
The ALOHA® application software Back-of-House (BOH) CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) applications are capable of running as a Microsoft® Windows® service, but you must register them as such. Besides Control Server and EDC Server, several other Aloha software application files also require registration. All of these applications are automatically registered when you install or upgrade the Aloha application software using the Aloha Installation CD, but some situations may require you to manually un-register and register applications.
Information
If you are using Windows 95 on the file server, you must install and configure DCOM before performing the procedures in this document. DCOM is included with all other approved operating systems, so you do not need to install it on them. Refer to document ID 6019 for more information on installing DCOM.
If manually installing a new version of the Aloha application software on a file server already using it, you must unregister the previous version before installing and registering the new version. Always restart the system after uninstalling previous versions of the Aloha application software.
If you install the Aloha application software versions 5.2x and higher using the installation CD, the setup application leaves copies of the batch files that it uses to un-register and register BOH applications in the root folder of the drive or partition in which the Aloha application software was installed. You can use these batch files to manually un-register and register BOH applications, or you can also use the information in this document to build your own customer batch files for versions 4.2x and higher.
Refer to document ID 6132 for more information on the benefits of running the Aloha application software components as a service.
Un-register Control Server Versions 4.2x through 4.4x
To un-register Control Server, open a command prompt and navigate to the BIN folder. Type the following commands:
CTLSVR.EXE /UNREGSERVER
REGSVR32.EXE /U CTLSVRPS.DLL
REGSVR32.EXE /U CALCEDIT.OCX (Version 4.4x only)
REGSVR32.EXE /U QWERTY.OCX (Version 4.4x only)
Register Control Server Versions 4.2x through 4.4x as a Service
To register Control Server as a service, open a command prompt and navigate to the BIN folder. Type the following commands:
CTLSVR.EXE /SERVICE
REGSVR32.EXE CTLSVRPS.DLL
REGSVR32.EXE CALCEDIT.OCX (Version 4.4x only)
REGSVR32.EXE QWERTY.OCX (Version 4.4x only)
Register Control Server Versions 4.2x through 4.4x not as a Service
To register Control Server to not run as a service, open a command prompt and navigate to the BIN folder. Type the following commands:
CTLSVR.EXE /REGSERVER
REGSVR32.EXE CTLSVRPS.DLL
REGSVR32.EXE CALCEDIT.OCX (Version 4.4x only)
REGSVR32.EXE QWERTY.OCX (Version 4.4x only)
Un-register EDC Server Versions 4.2x through 4.4x
To un-register EDC Server, open a command prompt and navigate to the BIN folder. Type the following commands:
EDCSVR.EXE /UNREGSERVER
REGSVR32.EXE /U EDCSVRPS .DLL
Register EDC Server Versions 4.2x through 4.4x as a Service
To register EDC Server as a service, open a command prompt and navigate to the BIN folder. Type the following commands:
EDCSVR.EXE /SERVICE
REGSVR32.EXE EDCSVRPS.DLL
Register EDC Server Versions 4.2x through 4.4x not as a Service
To register EDC Server to not run as a service, open a command prompt and navigate to the BIN folder. Type the following commands:
EDCSVR.EXE /REGSERVER
REGSVR32.EXE EDCSVRPS.DLL
Un-register Aloha Manager and Control Server Versions 5.0x through 6.2x
To un-register Aloha Manager and Control Server, open a command prompt and navigate to the BIN folder. Type the following commands:
ALOHAMGR.EXE /UNREGSERVER
CTLSVR.EXE /UNREGSERVER
REGSVR32.EXE /U AMGRPS.DLL
REGSVR32.EXE /U AMGRSHIM.DLL (Version 5.0x only)
REGSVR32.EXE /U CTL4X.DLL
REGSVR32.EXE /U EDTPUNCH.DLL
REGSVR32.EXE /U MNT4X.DLL
REGSVR32.EXE /U USERTOOL.DLL
REGSVR32.EXE /U ASECPS.DLL
REGSVR32.EXE /U ARSEC.DLL
REGSVR32.EXE /U ARSECPS.DLL
ALOHASEC.EXE /UNREGSERVER
REGSVR32.EXE /U ALOHALAB.DLL
REGSVR32.EXE /U CTLSVRPS.DLL
REGSVR32.EXE /U CALCEDIT.OCX
REGSVR32.EXE /U QWERTY.OCX
REGSVR32.EXE /U CRYSTL32.OCX (Versions 5.2x and higher)
Register Aloha Manager and Control Server Versions 5.0x through 6.2x as a Service
To register Aloha Manager with Control Server running as a service, open a command prompt and navigate to the BIN folder. Type the following commands:
ALOHAMGR.EXE /REGSERVER
ALOHASEC.EXE /REGSERVER
CTLSVR.EXE /SERVICE
REGSVR32.EXE AMGRPS.DLL
REGSVR32.EXE AMGRSHIM.DLL (Version 5.0x only)
REGSVR32.EXE ASECPS.DLL
REGSVR32.EXE ARSEC.DLL
REGSVR32.EXE ARSECPS.DLL
REGSVR32.EXE MNT4X.DLL
REGSVR32.EXE EDTPUNCH.DLL
REGSVR32.EXE CTL4X.DLL
REGSVR32.EXE USERTOOL.DLL
REGSVR32.EXE CTLSVRPS.DLL
REGSVR32.EXE ALOHALAB.DLL
REGSVR32.EXE CALCEDIT.OCX
REGSVR32.EXE QWERTY.OCX
REGSVR32.EXE CRYSTL32.OCX (Version 5.2x and higher)
If you are using Control Server versions 5.230 and higher and you are using the Microsoft Windows NT®, Windows 2000, or Windows XP operating system, Control Server prompts you for the user configuration. This is the user with which Control Server will log in. You can instruct Control Server to use the Windows local system account (the default configuration in versions 5.229 and lower), or you can configure a specific user name and password. You must configure a specific login in instances where the operating system on the Front-of-House (FOH) terminals does not enable network access by the Windows local system account or if you are using Windows 2000 on the file server (refer to document ID 6167).
Configuring Control Server to login using the local system account on a file server using Windows 2000 can result in memory leaks. You must use a specific user name and password. Refer to document ID 6167 for more information.
You can use the /LOCALACCOUNT command line variable to instruct Control Server to register using the Windows local system account without prompting the user. For example:
CTLSVR.EXE /SERVICE /LOCALACCOUNT
You can use the /ACCOUNTNAME and /PASSWORD command line variables to instruct Control Server to register using a specific user name and password. For example:
CTLSVR.EXE /SERVICE /ACCOUNTNAME .\[user name] /PASSWORD [password]
If you are using a domain account, you can specify the domain name using the following command line:
CTLSVR.EXE /SERVICE /ACCOUNTNAME [domain name]\[user name] /PASSWORD [password]
The batch file automatically created by the Aloha application software setup application (as explained previously in this document) uses the /SNAME and /SPWD command line variables instead of the /ACCOUNTNAME and /PASSWORD variables to designate that the user name and password in the batch file are encrypted. For example:
CTLSVR.EXE /SERVICE /SNAME /SPWD
Register Aloha Manager Control Server Versions 5.0x through 6.2x not as a Service
To register Aloha Manager with Control Server not running as a service, open a command prompt and navigate to the BIN folder. Type the following commands:
ALOHAMGR.EXE /REGSERVER
ALOHASEC.EXE /REGSERVER
CTLSVR.EXE /REGSERVER
REGSVR32.EXE AMGRPS.DLL
REGSVR32.EXE AMGRSHIM.DLL (Version 5.0x only)
REGSVR32.EXE ASECPS.DLL
REGSVR32.EXE ARSEC.DLL
REGSVR32.EXE ARSECPS.DLL
REGSVR32.EXE MNT4X.DLL
REGSVR32.EXE EDTPUNCH.DLL
REGSVR32.EXE CTL4X.DLL
REGSVR32.EXE USERTOOL.DLL
REGSVR32.EXE CTLSVRPS.DLL
REGSVR32.EXE ALOHALAB.DLL
REGSVR32.EXE CALCEDIT.OCX
REGSVR32.EXE QWERTY.OCX
REGSVR32.EXE CRYSTL32.OCX (Version 5.2x and higher)
Un-register EDC Server Versions 5.0x through 6.2x
To un-register EDC Server, open a command prompt and navigate to the BIN folder. Type the following commands:
EDCSVR.EXE /UNREGSERVER
REGSVR32.EXE /U EDCSVRPS.DLL
REGSVR32.EXE /U EDCSEC.DLL
Register EDC Server Versions 5.0x through 6.2x as a Service
To register EDC Server to run as a service, open a command prompt and navigate to the BIN folder. Type the following commands:
EDCSVR.EXE /SERVICE
REGSVR32.EXE EDCSVRPS.DLL
REGSVR32.EXE EDCSEC.DLL
If you are using EDC Server versions 5.230 and higher and you are using the Windows NT, Windows 2000, or Windows XP operating system, EDC Server prompts you for the user configuration. This is the user with which EDC Server will log in. You can instruct EDC Server to use the Windows local system account (the default configuration in versions 5.229 and lower), or you can configure a specific user name and password. You must configure a specific login in instances where the operating system on the FOH terminals does not enable network access by the Windows local system account or if you are using Windows 2000 on the file server (refer to document ID 6167).
Configuring EDC Server to login using the local system account on a file server using Windows 2000 can result in memory leaks. You must use a specific user name and password. Refer to document ID 6167 for more information.
You can use the /LOCALACCOUNT command line variable to instruct EDC Server to register using the Windows local system account without prompting the user. For example:
EDCSVR.EXE /SERVICE /LOCALACCOUNT
You can use the /ACCOUNTNAME and /PASSWORD command line variables to instruct EDC Server to register using a specific user name and password. For example:
EDCSVR.EXE /SERVICE /ACCOUNTNAME .\[user name] /PASSWORD [password]
If you are using a domain account, you can specify the domain name using the following command line:
EDCSVR.EXE /SERVICE /ACCOUNTNAME [domain name]\[user name] /PASSWORD [password]
The batch file automatically created by the Aloha application software setup application (as explained previously in this document) uses the /SNAME and /SPWD command line variables instead of the /ACCOUNTNAME and /PASSWORD variables to designate that the user name and password in the batch file are encrypted. For example:
EDCSVR.EXE /SERVICE /SNAME [encrypted user name] /SPWD [encrypted password]
Register EDC Server Versions 5.0x through 6.2x not as a Service
To register EDC Server to not run as a service, open a command prompt and navigate to the BIN folder. Type the following commands:
EDCSVR.EXE /REGSERVER
REGSVR32.EXE EDCSVRPS.DLL
REGSVR32.EXE EDCSEC.DLL
Register RFS Server Versions 6.0x and above as a Service
RFSSVR is run as a service on all versions of Windows that supports services (NT-based OSes). On versions of Windows that do not support services, it must be run as a server (Windows 95, 98, and ME). To register RFS Server (RFSSVR.EXE) to run as a service, open a command prompt and navigate to the BIN folder. Type the following commands:
REGSVR32.EXE COMMSGST.DLL
REGSVR32.EXE RFSSVRPS.DLL
RFSSVR.EXE /SERVICE
You can use the /LOCALACCOUNT command line variable to instruct RFS Server to register using the Windows local system account without prompting the user. For example:
RFSSVR.EXE /SERVICE /LOCALACCOUNT
You can use the /ACCOUNTNAME and /PASSWORD command line variables to instruct EDC Server to register using a specific user name and password. For example:
RFSSVR.EXE /SERVICE /ACCOUNTNAME .\[user name] /PASSWORD [password]
If you are using a domain account, you can specify the domain name using the following command line:
RFSSVR.EXE /SERVICE /ACCOUNTNAME [domain name]\[user name] /PASSWORD [password]
The batch file automatically created by the Aloha application software setup application (as explained previously in this document) uses the /SNAME and /SPWD command line variables instead of the /ACCOUNTNAME and /PASSWORD variables to designate that the user name and password in the batch file are encrypted. For example:
RFSSVR.EXE /SERVICE /SNAME [encrypted user name] /SPWD [encrypted password]
Register RFS Server Versions 6.0x and above not as a Service
To register RFS Server to not run as a service (only allowed on Windows 9x/ME), open a command prompt and navigate to the BIN folder. Type the following commands:
REGSVR32.EXE COMMSGST.DLL
REGSVR32.EXE RFSSVRPS.DLL
RFSSVR.EXE /SERVICE
The application detects the local operating system version and registers the application as a server when the platform does not support Windows services.
Un-register RFS Server Versions 6.0 and above
To un-register RFS Server, whether it is registered as a server or a service, open a command prompt and navigate to the BIN folder. Type the following commands:
REGSVR32.EXE /U COMMSGST.DLL
REGSVR32.EXE /U RFSSVRPS.DLL
RFSSVR.EXE /UNREGSERVER
Silent Registration Options
All registered Aloha software applications and REGSVR32.EXE support silent registration which disables the confirmation prompts (and error prompts) following file registration. The following switches are used for silent operation:
Silent operation disables error prompts, but you will not be informed of errors that may inhibit the application or .DLL registration process.
CTLSVR.EXE and REGSVR32.EXE use '/S' to enable silent operation. For example:
CTLSVR.EXE /REGSERVER /NONET /S
C:\WINDOWS\SYSTEM\REGSVR32.EXE /S CTLSVRPS.DLL
EDVSVR.EXE uses '/S ' to enable silent operation. EDCSVR.EXE does not recognize the '/S ' variable unless there is a space after the 'S' (use '/S ', not '/S'.) For example:
EDCSVR.EXE /REGSERVER /NONET /S
ALOHAMGR.EXE and ALOHASEC.EXE use 'QUIET' to enable silent operation. For example:
ALOHAMGR.EXE /REGSERVERQUIET
ALOHASEC.EXE /REGSERVERQUIET
ALOHAMGR.EXE /SERVICEQUIET
ALOHASEC.EXE /SERVICEQUIET
Extended Information
ATL.DLL
Aloha Manager requires you to register ATL.DLL. This file has already been registered and does not need to be registered again if the Aloha application software was originally installed using the versions 5.0x or higher Aloha Installation CD.
The ATL.DLL file differs between Windows 95, Windows 98, and Windows Millennium Edition (Me) operating systems, and the Windows NT, Windows 2000, and Windows XP operating systems. You can find ATL.DLL for Windows 95, Windows 98, and Windows Me in the W95DLL.ZIP file in the ALOHATS folder on the installation CD. You can find ATL.DLL for Windows NT, Windows 2000, and Windows XP can be found in the WNTDLL.ZIP file in the ALOHATS folder on the installation CD.
Do not overwrite newer versions of ATL.DLL.
If you need to manually register the file, you must copy ATL.DLL to the Windows System folder. If you are using Windows NT, Windows 2000, or Windows XP, place it in the Windows SYSTEM32 folder. If you are using Windows 95, Windows 98, or Windows Me, place it in the Windows SYSTEM folder. If the file already exists in the folder, replace it only if the existing file is older.
Navigate to the Windows System folder containing the file, and use the following command line to register the file:
REGSVR32.EXE ATL.DLL
Caveats
If the Aloha application software variables are not defined properly on the system, they need to be added to the command lines described in this document. Refer to document ID 6613 for more information on the Aloha application software variables.
Silent operation disables error prompts, but you will not be informed of errors that may inhibit the application or .DLL registration process.
Configuring Control Server to login using the local system account on a file server using Windows 2000 can result in memory leaks. You must use a specific user name and password. Refer to document ID 6167 for more information.
Configuring EDC Server to login using the local system account on a file server using Windows 2000 can result in memory leaks. You must use a specific user name and password. Refer to document ID 6167 for more information.
