Running Afaria Remote Control from within AppCenter

// Expert user has replied.
A Andrea Sada 3 years 6 months ago
2 3 0

Hi All SAB Miller in South Africa have a large install base of MC9000 and MC70's running SAB apps which are run from within AppCenter Ver1.10(Build1499) They now want to manage these devices using Afaria Remote Control. The problem is thay cannot get Afaria to function properly once it is registered as a valid application in Appcenter. Appcenter continuouslt pushes Afaria into the background. The following are the setting being used. HKEY_CURRENT_USER\SOFTWARE\Symbol\AppCenter\Afaria Remote Control] "Description"="Afaria Remote Control" "Execute"=\\Program Files\\Afaria Remote Control\\netophostd.exe "ExeName"="netophostd.exe" "Arguments"="" "IconFile"=\\Program Files\\Afaria Remote Control\\netophostd.exe "Window1"="*|*" "ReadOnly"=dword:00000000 "HideFromUser"=dword:00000000 "HideMenuBar"=dword:00000000 "HideDoneButton"=dword:00000000 "HideStartMenu"=dword:00000000 "HideSip"=dword:00000000 "AutoStop"=dword:00000000 "AutoStart"=dword:00000000 "StartupDelay"=dword:00000000 "RelaunchInterval"=dword:00000000 Has anyone successfully run Afaria Remote Control from within AppCenter. If so are there any settings which we need to know about? Regards

Please Register or Login to post a reply

3 Replies

L Larry Dykes

once you know the name of the executable that was closed, you can allow all windows by using *|* as an approved window specification - but sometimes that can also produce security "holes", depending on what functions are allowed by the windows. Also, if you want to be able to Launch an application from the AppCenter UI, you will need to know not only the executable name but perhaps also the command line arguments used to run the program.

L Larry Dykes

once you know the name of the executable that was closed, you can allow all windows by using *|* as an approved window specification - but sometimes that can also produce security "holes", depending on what functions are allowed by the windows. Also, if you want to be able to Launch an application from the AppCenter UI, you will need to know not only the executable name but perhaps also the command line arguments used to run the program.

J Justin Walther

Andrea Within the application folder there should be AppCenter.log. This can be opened using Note/WordPad and this should tell you which class, window or executable has been closed or blocked. I have not used AppCenter with Afaria, however on another application after I approved one window, another unapproved window was then blocked, so it could be a lengthy process. Regards Justin

CONTACT
Can’t find what you’re looking for?