Can PocketCloud companion accept incoming requests when running as a non-admin?
I see that one logged in as a "user" (non-admin account) is not able to modify settings. This is fine and relatively understandable. But, there ought to be some sort of UAC call to remedy this, no? I haven't come across such an app that is completely unusable when logged in as a user in a while.
But, what I'm really here for is to find out and confirm that Companion cannot accept incoming connections whatsoever when logged in as a user. If this is this case, this is really bad. Could there be something amiss with my install? FWIW, I have uninstalled/re-installed, and the behavior persists. I simply cannot imagine pocketcloud would restrict this software in such a heavy-handed manner.
Just to add a bit of info: The client on the android device reports that the PC is offline when logged on as a user, while online logged on as an admin. Is there a way to modify the preferences/settings so that the user account can report that it is indeed in online? I simply cannot believe that anno 2012, user account virtualization and the proper use of UAC by devs is not fully materialized.
So what you will need to do to run the application on the limited account would be to do the following:
-Launch start menu
-Right click on PocketCloud
-Select run as administrator
-Enter admin credentials
From here you should be able to log on successfully. Please let me know if this does not help.
Visit our Knowledge Base and Manuals web site at pocketcloudsupport.wyse.com
Hi, yes this does work. But, as you well know, it's a clunky workaround having to specifically log on manually as an admin and sort of defeats the purpose of remote administration. Shouldn't there be a way simply to modify an INI or preferences file as an admin, and only then, have the app work properly in the limited user environment? Or, better yet, have a button which calls for a UAC prompt for admin credentials? How about running the app as a service?
OK, after I fully logged off the user account and logged onto the admin account, perhaps the install became "finalized" with additional write access that perhaps wasn't allowed for whatever reason when the installer was run with admin credentials within the user environment. So, now things seem to work and the service seems to be doing its job. Thanks...