Hi,
I use UVNC 1.0.9.6.2 on Windows 7 Prof (64 bit) to support about 40 traveling users of notebooks. The users only have restricted access rights, the admin password is known by admins only. On the notebooks UVNC-SC is installed, created with the UVNC creator. Sometimes, when the users call my PC for help, I need to do some configuration tasks to the OS. In that cases I start a shell, from that a shell with admin rights by use of runas command, and from that 2nd shell the desired admin function. My test case is:
- connect from notebook to my support PC by use of UVNC-SC as restricted user
- open a shell on the notebook from my desk
- enter the shell and call runas /user:myadminaccount cmd.exe
- enter password and from the new shell start sysdm.cpl
Now what will happen? If the OS of the notebook is Windows XP Prof (50% of all users) this will work fine. I can do to the PC what I wanted to do. But in case the OS of the notebook is Windows 7 Prof my remote control to the notebook is blocked at the time I call sysdm.cpl or other configuration tasks. Therefor I need assistance from the notebook user. I can see any thing he does but only can take control to the PC myself if there is no admin task in front. In all other cases I am only able to view what he is doing. BTW: It doesn't even matter if the user has logged in with adminstrative rights. The only solution with UVNC I found is right clicking the SC and start the program as administrator. But then the user has to know the password. From security reasons it' s clear that this is not what I want.
I have tested "Teamviewer" in non installation mode and it works fine with Windows 7 without any blocking. My favorite tool ist UVNC. So I wonder what trick they use in Teamviewer and if I can do the some thing before starting the SC? Any hints?
windspiel
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
UVNC with SC - access problems
Re: UVNC with SC - access problems
The VNC server should be pre-installed as a service to get around these issues. You can use regular UltraVNC or something like SCPrompt or ChunkVNC.