Aloha System Redundancy exceeded after upgrade to Win 7

[snackattack]

I recently migrated a site from XP to Win 7. After a few days I see the message "System Redundancy will be exceeded in X days", although the site clearly isn't in redundant mode. I am able to fix the issue by doing 2 things. I add "everyone" to the bootdrv share (security concern) and I enable RFSSVR which isn't being used. I am currently lab testing to determine which was truly the fix, but figured I'd ask for input.

The RFSSVR being enabled doesn't seem likely to be the fix as the site doesn't use RFSSVR.

Adding Everyone shouldn't be the fix either as all terminal accounts are explicitly added already.

Win 7 SP1, POS QS 6.7.32

 

[snackattack]

I should clarify that enabling RFSSVR means I am enabling the service, which I set to disabled. Not fully turning on the feature.

 

[dauphin2]

Aloha needs admin rights to update the registry on the FOH. First the FOH contacts CTLSVR on the server to determine redundancy info, it then attempts to update the value in the registry on the terminal. Any issues with contacting CTLSVR or being able to update the local registry (Are you logging in as an administrator on the terminal or THE administrator?) will result in redundancy issues even though it is not in redundant mode. I've seen this issue on many Win7 terminals and sometimes for whatever reason even though I'm logging onto Windows as an Administrator, I have to log on as the actual local admin. Look at the debout files on the terminal for anything related to permissions.