Re: RWW - log off after timeout?

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'm not sure where I saw this yesterday... I did so much googling my fingers
ached <grin>
If I can find this I'll post it back...

SusanV

"Steve" <newsgroup@xxxxxxxxxx> wrote in message
news:%23psnFAO4HHA.5424@xxxxxxxxxxxxxxxxxxxxxxx
Susan that's interesting about Vista-do you have any references to
official MS documentation that discusses it? Or is it another type of
hack?

"SusanV" <svanallen@xxxxxxxxxxxxxxx> wrote in message
news:O29n0uM4HHA.5852@xxxxxxxxxxxxxxxxxxxxxxx
Hi Larry,

Thanks for the suggestion, but although we have another server running
W2003, we do not have the TS licensing. And while this may sound like a
good "solution" to the problem, in our case I'm not sure it would be
worth the price. The workstations were not bought for the purpose of
RWW - they were purchased some time back, prior to our move from NT to
SBS 2003 in order for users from the office to be able to jump on a
vacant machine to check email or whatever when they are at the shop
location (and vice versa). Therefore, the purchase of TS licensing is
simply an additional cost, not a trade-off.

Perhaps upgrading to Vista is the way to go, as from what 'I've read,
Vista will allow multiple sessions... Something to think about...
--
SusanV

"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in
message news:%23TTnZoM4HHA.5844@xxxxxxxxxxxxxxxxxxxxxxx
"SusanV" <svanallen@xxxxxxxxxxxxxxx> wrote in message
news:%23C4TMQM4HHA.3400@xxxxxxxxxxxxxxxxxxxxxxx

Well, actually we have 27 XP Pro workstations, these 2 are unassigned,

Exactly my point... had you opted for 1 Terminal Server, instead of 2 XP
Pro Unassigned Workstations you would not be having this problem. As
you already know, RWW to desktops is a one to one relationship. RWW to
a TS is a many to one relationship. For the price of a copy of Server
2003, and using one of your XP Pro workstations if they are relatively
beefy, and (probably) more RAM, plus $90 or so per user for the TS
license, you can have as many folks logged on at a time as you wish.

Even now , if you were to turn one of the workstation into a TS, you
could leave the other one as a dedicated one for the one or two users
you can acutally train to log off, and put the rest on the TS, where is
does not matter if they do or don't.

Larry











.

Relevant Pages

  • Re: RWW - log off after timeout?
    ... It's another hack. ... we do not have the TS licensing. ... XP Pro Unassigned Workstations you would not be having this problem. ... RWW to desktops is a one to one relationship. ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW - log off after timeout?
    ... we do not have the TS licensing. ... XP Pro Unassigned Workstations you would not be having this problem. ... RWW to desktops is a one to one relationship. ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW - log off after timeout?
    ... we do not have the TS licensing. ... XP Pro Unassigned Workstations you would not be having this problem. ... RWW to desktops is a one to one relationship. ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW - log off after timeout?
    ... we do not have the TS licensing. ... The workstations were not bought for the purpose of RWW - they ... Pro Unassigned Workstations you would not be having this problem. ...
    (microsoft.public.windows.server.sbs)
  • Re: Can I limit User RWW?
    ... Every time I see discussions of limiting user's rights, I am reminded that it's a personnel problem. ... In this case, the technology problem is trivial to solve, as Les has pointed out. ... And I can think of other ways to solve it as well, by not giving the user in question rights to RWW, but still allowing them to do OWA or RPCover HTTP, plus the 444 trick for company web. ... Les you said they see the workstations by default but what is stopping them from logging on the desktop? ...
    (microsoft.public.windows.server.sbs)