Re: [ros-dev] Terminal Server Clone

[Love Nystrom]

"Jan Blomqvist Kinander" <jan.blomqvist(a)reactos.org> wrote:
>   Opening many sessions in windows is really bad idea
> ... for kernel stuff and another csrss, smss problems ... terminal server blue screen,
> black screen, printers, etc ... so i have an idea for a workaround ...
>
>  Is open a session using createwinstation api ... in that session, create multiples
> desktops, using createdesktop api, in each desktop will be secure shell replacement,
> ejecuted using x user credentials (runas) ... the printing is gonna be universal virtual
> printers that receive the buffer from the win32, and send the emf or pdf to the client
> ...
>     
Hi Jan & Gonzalo,

I'm no expert in this particular area, but don't You think it would be 
more logical
to give each remote a winstation, and not just a desktop on a shared 
winstation ?

Best Regards
// Love

[Enrico Weigelt]

* Love Nystrom <love.nystrom(a)gmail.com> schrieb:

Hi folks,

>   "Jan Blomqvist Kinander"
> <jan.blomqvist(a)reactos.org> wrote:
> >  Opening many sessions in windows is really bad
> > idea ... for kernel stuff 
> > and another csrss, smss problems ... terminal server blue screen, black 
> > screen, printers, etc ... so i have an idea for a workaround ...
> >
> > Is open a session using createwinstation api ... in that session, create 
> > multiples desktops, using createdesktop api, in each desktop will be 
> > secure shell replacement, ejecuted using x user credentials (runas) ... 
> > the printing is gonna be universal virtual printers that receive the 
> > buffer from the win32, and send the emf or pdf to the client ...
> >    
>  
>  Hi Jan & Gonzalo,
>  
>  I'm no expert in this particular area, but don't You think it would be 
>  more logical
>  to give each remote a winstation, and not just a desktop on a shared 
>  winstation ? 
I'm not a win32 expert (just a GNU guy lurking on this list ;-)),
but my approach would be simply putting the windows workloads into
VMs and giving each user its own VM.

This probably would require more iron, but - assuming we're talking
about an professional/production environment - this should be more
cost-efficient than spending too much manpower into some solution
w/ less iron.

BTW: my current customer (1+1) provides shared win32 hosting as 
well as win32 VMs. Maybe you could have a look at it.


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------