Please follow the steps below to unistall Punchh on Aloha:
1. The Installer on the Back Office will uninstall the Punchh services when used from the Control Panel > Programs function. Before running uninstall, please read below:
NOTE: Uninstalling the Foh apps will depend upon what your business has deployed on the Back office computer, as some applications (e.g. Take Out and various on-line ordering platforms) will cause iber.exe or iberqs.exe to run and may load the punchhInter.dll and punchhPrt.dll.
In order to remove them:
a. If Iber.exe or iberqs.exe is running on the back office computer, then you can issue a STOP front of house. Beware, if this occurs during business hours, then it will stop the POS terminals, so it's suggested you plan the uninstall after close of business.
b. After the instance of iber or iberqs has been stopped on the Back office, you can uninstall punchh from the Control panel and the punchh apps found in Aloha's bin folder will be removed too.
2. Unregistering punchh on Front of house. While not necessary, you can unregister the dll's used by punchh with these 2 commands on the terminals: %windir%\Microsoft.NET\framework\v2.0.50727\regasm.exe/unregister%localdir%\bin\PunchhPrt.dll
3. The Punchh apps may still reside on the terminals due to aloha copying them prior to running the control panel's uninstall.
To remove them from the POS Terminals you have a couple of options:
a. If the FOH is still stopped (see item 2), you should be able to delete them manually. Due to network policies, you may not have access to the Front of House bin folder where these apps are stored (I.e. Aloha's bin folder). Once removed, you can restart the terminals and "START" the front of house if you've performed a "STOP Foh" operation.
b. If your site uses a SyncInclusionList.cfgfile, then remove or remark out the punchh files listed in this file and refresh terminals. This will purge the terminal's bin folder and copy just the files listed in this file.
c. If punchh needs to be removed during business hours, using the Syncinclusionlist.cfg may be the easiest option to employ. Once the punchh entries are remarked out, just refresh the terminals or wait until End of Day to run.