|
|
|
|
Group: Administrators
Last Login: Yesterday @ 7:33 PM
Posts: 1,687,
Visits: 3,177
|
In this post I would like to describe an issue we are currently having with the v2.0 implementation. I’m also seeking your feedback.
- Service mode is started as a windows service; setting it to run in Service mode requires administrator privileges on the system.
This mode is compatible with Vista’s UAC prompts. - User mode is started manually by a user after logging in. It can be done by launching winvnc.exe. Controlling VNC server in User mode doesn’t require administrative privileges.
This mode is not compatible with Vista’s UAC prompts.
ServerX 1.0 executes in a mode similar to the User mode. On the plus side, administrative privileges are not required when hosting application needs to change a ServerX instance settings. The downside is that ServerX doesn’t support UAC prompts. And this is a huge problem for users with Vista/Windows 7.
To work around this problem ServerX 2.0 is being designed to run as a Windows service. The service would be installed when the ActiveX is registered on the computer and uninstalled upon un-registration.
Installation / uninstallation of a service require administrative privileges, but this is not an issue because registering/unregistering an ActiveX requires the same privileges anyway.
The issue that we are facing is that controlling ServerX 2.0 settings would require administrative privileges. There is no other way around it. So my question to the current and potential ServerX users is how the administrative requirement would affect your applications? Would you still be able to use ServerX?
Basically the above mentioned issue is the only one that preventing us from finish the 2.0 release.
Please post your feedback here or you can email it directly to me at yury (at) s-code.com.
Kindest Regards,
SmartCode Solutions Support
|
|
|
|
|
Group: Forum Members
Last Login: Tuesday, March 08, 2011
Posts: 3,
Visits: 8
|
A service always needs UAC priviledges to run.
So, your vnc server.
But in most enterprise environments, administrator priviledges are not allowed for simple users.
The concept is that whoever has admin priveledges is a possible superuser for all other apps.
SO, making an activex require the user to be an admin, is not very wise.
At the other side, to really run an activex (apart from user mode) is usually
a UAC trust action.
I would propose to start the activex in user mode and use a menu to elevate the
user trust and then, you may also ask the user to run the service installer.
If the system denies it, you will have to get stuck with the NO TRUST priviledges.
Please take a look at how we handle the vnc server as a dll in our app
When we ask for priviledged access, we can also temporarilly turn uac prompts
OFF for Admins only, since you already have the privs.
Regards
Netgotiator
Edited: Sunday, October 24, 2010 by
Support (s-code)
|
|
|
|
|
Group: Administrators
Last Login: Yesterday @ 7:33 PM
Posts: 1,687,
Visits: 3,177
|
Thanks for your feedback. The very important difference is that you use VNC server as an application. This is very different use case from when a VNC server is implemented as a COM component (an ActiveX), which has control a windows service. From what we know many of the ServerX v1 customers use it as part of their Web-based applications. So they instantiate ServerX and use it on a web page. With UAC in place and ServerX running in a server mode, they will be able to instantiate the ActiveX, but they won't be able to control the service. Because UAC won't let them.
And that’s where we got stuck.
Kindest Regards,
SmartCode Solutions Support
|
|
|
|
|
Group: Forum Members
Last Login: Tuesday, March 08, 2011
Posts: 3,
Visits: 8
|
Any news on that? Is there enough requests to justify the project ?
|
|
|
|
|
Group: Forum Members
Last Login: Monday, May 09, 2011
Posts: 8,
Visits: 31
|
I really really want to know when will the ServerX 2.0 be available to customers.Please let me know. Thank you.
|