Mirror Driver and User rights on Windows

[aftertaf]

Hi,
I have a question/problem.....

I have uvnc 1.02 installed as a service on Windows 2000.
When I connect to the PC, i can login as administrator or as a regular user, via VNC (service mode, i presume...)....

My problem is this:
-When administrator I can open the properties option on the taskbar icon and I can see if the mirror driver is running... When I click the 'check hook' button it shows me: driver present, comm service present, driver active.
All is good.

-When I login as regular user, I can't access the Current User Properties in this manner (option on taskbar icon is greyed out)... So i go to VNC Menu in start Menu. When I open current user properties, and click the 'check hook' button it shows me: driver present, comm service NOT present, driver active.

OK.
So, my questions are....:
-Is there a rights issue that means VNC is giving me bad information on the Driver Test window?
-Is the non admin rights of this account actually stopping some of the mirror driver from functioning (and thus degrading performance)?
-Is there a way of making this run with full rights (i.e. running service as a different account than localservice....) and so letting the driver run correctly?

for info:
-When I look in 'System Information'/Software Environment/Drivers i can see both vnccom and vncsys as Kernel Drivers that are running, for both admin and non admin accounts...
-If i make my normal account a member of the administrators group then I reboot, the driver test says comm service present...

Can someone give me some light on this? Is it working ok, but windows is just stopping vnc from giving me the right info??

[aftertaf]

Bump...

Anyone?

I have the same issue with Windows XP, when running as a non admin account.
I dont know whether it works or not!

[bevtech]

might need to have admin rights to have it function properly..

[aftertaf]

oh, i hope not.....
can someone on the dev team test this and say one way or another if the mirror driver and comm service are correctly engaged if the user account is not a local admin on the PC?


On the other hand, could be one more selling point to migrate to linux ...

[Eugene Sukhodolin]

You don't need admin rights provided that you adjusted special permissions on certain registy keys beforehand.

I'm not sure about UltraVNC driver, but for DFMirage the reg path is:

HKLM\SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Services\dfmirage

Just grant r/w rights to the INTERACTIVE pseudo user.

[aftertaf]

Thanks for that info.... I'll test like, right now, and let you know what's going on
thanks again....
David

[bevtech]

David let me know if it works i will make it a faq and see if the information can be added to the documents

[aftertaf]

OK.

I used regedt32 to change the rights.....
As I use Sysprep on the PC i decided to put All Users with Full Access on those 2 keys:
HKLM\SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Services\dfmirage
&
HKLM\SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Services\vncdrv
All Users had just Read rights beforehand...

I have rebooted the PC and I still have the message saying Comm. service not present.
I have also rerun Sysprep to see if my modifications remain in the registry, they do...

But the same problem remains.....

My other question is, does this mean the mirror driver isn't active?

[Rudi De Vos]

v1.02 had a seperate communication service, v103RC don't use it anymore.

The service is system started, and not started and stopped by winvnc.
If the communication service run for admin it also run for the user, but the mechanism to detect could fail because of the lack of rights.

But we use the check, so driver is not working for a standard user.
check permissions on, user need to be able to get the dll version of that file. version should be 1.00.17
\system32Drivers\vnccom.SYS

[aftertaf]

OK Great... Thanks for that Rudi...

Any news on when 1.03 final is released? That way I can upgrade the ghost with this.

What do you mean by this??

But we use the check, so driver is not working for a standard user.
check permissions on, user need to be able to get the dll version of that file. version should be 1.00.17
\system32Drivers\vnccom.SYS

both vnccom.sys and vncdrv.sys are version 1.00.17
NTFS rights are USers, read & execute, admin Full control.

Should I change the NTFS rights?
David

[aftertaf]

I Have another question, concerning the settings & default settings.....


Is there a way I can give rights to the normal non admin user to change or even be able to open these settings windows?

The text is greyed out on the tray icon, and when I open the menu items in the start menu, I cannot run the default settings, even via runas...

[aftertaf]

Hello again............

I have one more question concerning v1.04.RC3

I understand a lot of the changes you are making to the software concern Vista compatibility, along with the registry thing.....

Is v1.04 stable enough to use on XP/2000 (I mean by this, do you have enough feedback to say, yeah go for it...?). It seems a lot more stable than 1.03RC5 I tried this summer....

Because the newer mirror driver is also available and it seems to be more accurate and good on performance too.