Forums > NComputing Community > Feature/Product Requests
Subject: Don't touch Windows preferences
Prev Next
You are not authorized to post a reply.

Author Messages
romsUser is Offline

Posts:52
06/19/2008 1:20 PM  

NComputing software touch a lot of Windows personnal parameters like

  • "Display window while moving"
  • Remove visual style 
  • Don't  turn off monitor
  • Lock Energy parameters to "Presentation"
  • And many more i think ....

Why doing this ? Why don't let the users choose what they want ?

Even if we have to disable visual style or turn off energy parameter to get NComputing software work better, why locking them ?

If i want my host-monitor to turn off after 20 minutes, how can i do ? it's to be a little more green ... like are the L-series ....

You can say : turn off the monitor's power switch .... yes but it is the principe .... you can even say "use a software that power-off the monitor", yes but windows can do it alone ...

I have even many more question to this globally quetion ... but i'm better a french writer than a english one ...

My point of view of the NComputing software would be to "only enable a multi-user windows access" with audio service and many more thing, a little like Windows RDP do .... but don't touch personnal parameters or custom parameters ...

On a Terminal Server, even if RDP is activate, we can change Visual Style / Energy parameters / etc ...
JohnBUser is Offline

Posts:44
08/14/2008 11:58 AM  
First of all think of the legististic of what you want.
You have 10 user terminals all with different monitors, now how is Windows or any other OS to know which one to power down.
I mean, if I was one of your users and you had the unit to power down my monitor after 20. The OS would have to power down all the monitors.
Remember this is not the same as Terminal Server or RDP. Under normal Windows os the parameters set in the admin account make it so others cannot change some of these settings.
I personally think if your users are too lazy or forget ful to turn off thier Monitor when done, you have bigger issues.
Most errors occur between the ears
romsUser is Offline

Posts:52
08/14/2008 12:10 PM  

But the situation with the monitor to turn off and any other parameters is on the Host computer not on remote terminal.
JohnBUser is Offline

Posts:44
08/14/2008 3:23 PM  
That was my point. Windows OS does cannot control each user/Terminal indivually. It is all or none. You have to remember you are accessing the os as a user. Each terminal connects and logs in as a user. If you start changing these parameters for one, windows will have problems. I believe that is why they did what they did. I tell my users to "log out" and turn off the monitor and box. Thus saving the power on both units.
Some just forget to do either. When I come in. I do it for them, for security reasons....
Most errors occur between the ears
romsUser is Offline

Posts:52
08/14/2008 4:17 PM  

I understand your point of view. And you said  I tell my users to "log out" and turn off the monitor and box : I do the same.
But where I am not agree with you is that Windows can differentiate each session and each parameters of each user connected.

For example, NComputing disable the "show window contents while dragging" option, but we can re-enable it manually, at every new session.
This setting doesn't affect other session connected to the host, this is the same for some other effect like "show shadows under menus" or any other visual effects. This, even, doesn't consume a lot of bandwidth in a 100Mb/s network (even with 30 users), on the contrary, this add, the so called expression, "a better user experience".

For the monitor to switch off, this is only at the host side, not terminal side, and that, Windows can differentiate the user which is connected to the console or the user which is connected remotely, so he can turn-off the monitor on the console.

Another example too, NComputing software make Windows skip "the search for a driver in a specific path" option when we connect a device that he does not recognize (yes, we can add/change a reg key to put the specific path). But Why ? Does this really affect the software ? I don't think.

What I would like is that NComputing should make a recommendation list and let the sysadmin do what he wants, if he does not want to follow the recommendation, it is his problem. NComputing should not block features that the OS has.
You are not authorized to post a reply.
Forums > NComputing Community > Feature/Product Requests > Don't touch Windows preferences