Anybody had any success in getting an Aloha Remote Back Office installation to run on Win7?We have a server running 2003 and an XP remote bo. We're replacing the remote bo and would like to upgrade to Win7. The remote bo installs OK on Win7 and I can run the app but 'File' - 'Login' doesn't give me a username/password prompt. It doesn't do anything, no errors logged.This is a domain environment. Aloha is 6.7 (controlled deployment) but same issue in 6.2.22. RE: Aloha Remote Back Office on Win 7 (TechnicalUser) 17 Nov 10 20:26. Windows 7 on a domain might be a little tricky, haven't done it, but most important with Aloha you need to make sure you have full rights to that server to read and write files.
If you have that, it should work. Remote manager does not have a lot of criteria.Here are the steps to make it happen. These steps are pre Windows 7 but I don't see how that would matter.1. Ensure the network and Aloha BOOTDRV share on the file server enable the remote user fullaccess to the file server.2. Install the Aloha application software on the remote workstation.
Do not enter any keynumbers or select any optional components. With the exception of the Aloha application softwarefolder location, leave the setup parameters at their default settings since they will be erased later andhave no bearing on the final result. You can leave the Aloha application software folder location atthe default location or move it to a different location on the remote workstation hard drive. Restartthe computer when the installation is complete.3. On the remote workstation, open a command prompt, navigate to the BIN folder, and use thefollowing command line to unregister CTLSVR.EXE (Control Server):CTLSVR.EXE /UNREGSERVER4.
Remove the BOOTDRV share from the remote workstation that was created by the installationprocess.5. Delete the entire contents of the Aloha application software folder on the remote workstation,leaving only the Aloha application software folder, the BIN folder, and the BIN folder's contents.6.
Remove the Aloha application software environment variables from either the IBERCFG.BATor the system environment variables (depending on the operating system).7. Create a shortcut to Aloha Manager on the desktop:A. Right-click any unused portion of the remote computer desktop and select New/Shortcut.B. Enter the following command in the 'Command Line' text box being sure to insert thecorrect server name and Aloha application software folder:ALOHABOHBOOTDRVALOHABINALOHAMGR.EXE /IBERDIRALOHABOHBOOTDRVALOHA /REMOTEC. Click Next and enter 'Aloha Aloha Manager' as the shortcut name.D.
Click Finish.BoRemember,If the women don't find you handsome,they should at least find you handy.(Red Green)RE: Aloha Remote Back Office on Win 7 (TechnicalUser). Just installed Remote Aloha Manager on a Win 7 box today.No issue other than error on install but the install continued after the error and worked fine.Not on a domain though.Here some info about win7.Aloha POS supports 32-bit Windows 7 (W7) and 32-bit Server 2008 using Aloha versions 6.4 and higher.
There are a handful of extra steps for W7 and Server 2008 (similar to Vista) that are required to install. The goal will be to eliminate most of these steps through image releases (for Radiant Servers) as well as updates to the Aloha install.MSI.1. HASP drivers need to be updated to the version supported for Windows 7 first.
The HASP drivers on the current install CD will not work, options are:a. Put the HASP key in the USB port, if using USB key, Windows 7 will update the drivers.b.
Go to and install the HASP drivers for use with Server 2008.2. Disable IPv6 on all NIC's. If installing from the Aloha CD:a. Explore to the CD and right click on Advanced.exe then select Properties.b. Select Compatibility Mode and select Windows XP from the dropdown box.c.
How To Make File Server
If installed with a non-administrator user account, then also select the Run As Administrator check box.4. If using Radiant Kitchen Videoa. Disable the NIC not being used for Aloha (WAN), before running Radvidsetup.exe. This assumes a BOH PC with dual NIC's,b. Once setup is complete re-enable the NIC.5. User Account Control (UAC) and Data Execution Protection (DEP) should not be disabled.a. For DEP add each application to the exception list that requires the use of the HASP key.
(CTRLSvr, EDC, Grind(q), Aloha Manager, etc.b. UAC typically does not have an effect, but may require the application to be installed using an administrator account.c. Please refer to DOC 8774 concerning some issues with DEP: /radiantKS/documentview.cfm?documentId=8774.