UVNC and server 2008

[fsidegrind]

Is UVNC server supported on Server 2008? If so are there any instructions on setting it up? I have rad through all the posts on the uvnc website as well as several of the posts returned via searches on google. See below for details:

I have installed UVNC and can get connected, put in my password and it is accepted. This is the point i get stuck, all I see at this point is a black screen. If I log in to this server via RDC, I then can go back to my uvnc viewer window and I see the desktop of the server but cannot click on anything. It seems as this issue is similar to the "vista" issues but non of those solutions are working. Please help.

[mod=494,1240236150]moved from vnc related product to general help[/mod]

[JDaus]

all I see at this point is a black screen. If I log in to this server via RDC, I then can go back to my uvnc viewer window and I see the desktop of the server but cannot click on anything.

first, this is wrong place to be posting this.

but regardless, it sounds like your running uvnc as a non console user ... I ran into problems with installing uvnc on server 2003, and had similar problems ... did you install when physically standing in front of the machine ??? or over rdp ???

if over rdp, then that maybe your problem.

[fsidegrind]

Yes, I installed UVNC over RDC as this is a server in a closet and does not have a monitor/keyboard/mouse hooked up to it.

[JDaus]

Yes, I installed UVNC over RDC as this is a server in a closet and does not have a monitor/keyboard/mouse hooked up to it.

therin lies your problem

you need to start mstsc with the /console arugement

EG
Click start > run
type "mstsc /console" (minus comma's) and click OK

now you will need to uninstall the software, and install again ... if this still fails, try connecting a monitor and mouse to the server ... mstsc is a hard thing to get uvnc working over (i had to actually travel 3 hours, just to install UVNC on a clients server ... so yeh it SUX)

[JDaus]

let me elaborate my last post further, by explaining (the way i think) how terminal service sessions work (or rather pause)

when you connect to the terminal server, a new (or existing) session is opened (or resumed).
when you disconnect, this session is paused (something like standby / hibernation on a workstation) so whatever you where doing, now has no more memory to work with, and whatever processes it was using may no longer respond (my reasoning for only getting a black screen when connecting to uvnc - the session it is attached to has paused ...).


of course, this could all be the ravings of a mad-man (me) ... but its what i'm guessing is happening
(even the most researched experiment is nothing but a guess without proof)

[fsidegrind]

I tried these suggestions both with mstsc /console and with a monitor, mouse and keyboard plugged into the server. (uninstalled, rebooted and reinstalled under both scenarios all to no avail. any other suggestions? has anyone been able to get this to work with server 2008 (and not just on vista)? Does anything special need to be enabled on my server?

another interesting note is that I never see an icon for uvnc in the system tray running as a service or as an application. should I?

just for more info, I connect to the machine and get prompted for the password, my password gets accepted and I can see the desktop I just cannot do anything. this is the same behavior with uvnc running as a service as admin or running uvnc server as admin. please help...

thanks,
jed

[CAOgdin]

Is this all due to the fact that, when you configure the uvnc_service, and select "Allow service to interact with desktop", it never works, because Vista and Server 2008 prohibit any service from interacting with the desktop (per notes at http://social.msdn.microsoft.com/Forums ... 147946e114)

Has anyone found a way 'round this?

Is there a policy that will re-enable this functionality?

In the meantime, I'm using RDC with no problem.

[redge]

CAOgdin wrote
> Has anyone found a way 'round this?

[topic=15993][/topic]

[CAOgdin]

Thanks, Redge...but it seems more complex than I am willing to commit to. Perhaps, someday, when I have more such systems under management, but for this sole server, I'll just stick with RDC.