Re: thin clients on SBS2003 ?

WOW do you need some help?
I'd be glad to come and help sounds like a challenge

Russ

--
Russ Grover
Small Business IT Support
Portland\Beaverton OR USA
Email: Sales at SmallBusinessITSupport.com
Website: www.SmallBusinessITSupport.com


"Steven" <steven@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Om9Y%23V8hFHA.2424@xxxxxxxxxxxxxxxxxxxxxxx
> Hi again thanks for your comments
>
> just to clear things up, the thin clients are not your normal users - no
> email no data access etc. Would only be used for accessing 2 custom
> software applications.
>
> This rollout has a very large budget -alot more then you have listed
> below.
>
> Have added comments to below;
>
>
>
>
> "John Vollman" <nospam@xxxxxxxxxxx> wrote in message
> news:OQ%23YMJ8hFHA.572@xxxxxxxxxxxxxxxxxxxxxxx
>> Steven,
>> While your initial thought is certainly possible I think you are headed
>> in the wrong direction. Trying to manage 523 stand alone SBS networks
>> would take an army of techs. Even with the ease of SBS features.
> Yes, i was mainly asking if it was possible to run on SBS2003 - however we
> did not expect to run 523 sbs networks.
> i have received alot of help on this newsgroup and it has all been very
> helpful, just wanted some comments from people who make sense :)
>
> You have
>> massive amounts of things working against you. Lets do some math:
>> 523 Sites
>> 1 Internet connection per site = 523 connections
>> 1 SBS Server per site = 523 servers
>> 1 Terminal Server per site = 523 Terminal Servers = 1046 total servers
>> 6 Clients per site = 3138 clients
>>
>> I would estimate that the cost of a very basic box with software (Virus,
>> SBS, Backup, Citrix, Windows 2003 for the terminal server) will run you
>> in the neighborhood of $4,000.00 - Is this for each thin client. or you
>> mean sbs server.
>>
>> Just the cost of purchasing 1046 servers will cost you over 4 million. -
>> not a problem.
>> Now some hard questions:
>> How are you going to manage 3000 plus user accounts scattered across 523
>> sites? Remote Desktop? No way. Not enough hours in the day. - we will
>> have the tech team for this (actually it will be outsource)
>>
>> Do they all want email? How are you going to redirect email sent to
>> yourdomain.com to 523 individual independant sites running exchange? The
>> DNS would be a nightmare. -- No - no email at all they do not require
>> it.
>>
>> What if someone moves from one office to another? Do you set up a
>> duplicate account in the new location? No - users are not your normall
>> office user - will not be moving from office to office. It is for people
>> to
>>
>> The facts:
>> If 523 sites is even a remote possiblity you have entered the world of
>> enterprise level systems. ok
>>
>> Off the cuff the quick and simple way to make this happen would be to
>> install a broadband connection in each site, connect it to a LAN that is
>> managed by a router (DHCP, VPN, Switch, Print Server, etc) and have the
>> thin clients all connect back to a Terminal Server (Citrix) farm in the
>> HQ data center. Even with this you will need some big iron to host 3000
>> plus sessions. - Yes, info like this is very helpful.
>>
>>
>> Time to hire an enterprise level consultant. You are in deep my
>> friend. - thanks for your comment but you do not know my history or my
>> team
> we are just fact finding at the moment but again thank you for your
> comments.
> We also have microsoft helping with this but i wanted some background
> info.
>>
>> John Vollman
>>
>>
>>
>> "Javier Gomez [SBS MVP]" <javier_gomez@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:uU$bAk6hFHA.1460@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Is it possible to run thin clients on a SBS2003 network.
>>>> I have a client would would like to run a server and 6 thin clients
>>>
>>> Its possible... but you need a 2nd server for running the thin client
>>> sessions. SBS doesn't support Terminal Services in Application Sharing
>>> Mode.
>>>
>>>> From my understanding of thin client, it does not include hard drives
>>>> etc, so how would they connect to the server.
>>>
>>> In most cases yes... Thin Clients have minimal software integtated in
>>> order to run an RDP session (or ICA if you are runiing Citrix). So, you
>>> connect to a Terminal Server and only the input/outputs are transmitted
>>> but the processing is done at the server. You might want to read more
>>> here:
>>> http://www.microsoft.com/windowsserver2003/technologies/terminalservices/default.mspx
>>>
>>>> we would be rolling out 523 of these networks (1 server and 6 thin
>>>> clients) (523 seperate locations)
>>>> Can you suggest a good way to manage all the servers (ie patches,
>>>> updates etc)
>>>
>>> I really don't know your scenario, so I can't tell you if you are on the
>>> right track or not. However, if I may be so bold... you don't seem very
>>> experienced with Terminal Services, so I suggest you make sure you know
>>> what you are getting into before rolling this out.
>>>
>>> For example-> One of the main benefits of Terminal Services is that you
>>> can run sessions with minimal bandwidth... so you could have a couple of
>>> servers on a central location and run all the sessions from that server
>>> farm (whithout having to buy 523 servers!). This is definitely outside
>>> the scope of this group... but we would be glad to point you out where
>>> you can get more info if you decide to.
>>>
>>> In any event... to answer your question: if you can put all the servers
>>> on the same AD domain (which you couldn't do with SBS) then you could
>>> use WSUS for patching them. I don't have networks this big... so I might
>>> be out of my league recommending this to you.
>>>
>>> --
>>> Javier [SBS MVP]
>>> www.msmvps.com/javier
>>> << SBS ROCKS !!! >>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: SBS Network Design Inquiry
    ... application sharing mode and thin clients. ... So $1,500 for a starter second server, $1,000 for the operating ... SBS is to serve files and email. ... computers on a wireless LAN. ...
    (microsoft.public.windows.server.sbs)
  • Re: thin clients on SBS2003 ?
    ... Even with the ease of SBS features. ... SBS Server per site = 523 servers ... clients all connect back to a Terminal Server farm in the HQ data ... >> Is it possible to run thin clients on a SBS2003 network. ...
    (microsoft.public.windows.server.sbs)
  • Re: thin clients on SBS2003 ?
    ... Even with the ease of SBS features. ... > sbs server. ... > thin clients all connect back to a Terminal Server farm in the HQ ... >> sessions. ...
    (microsoft.public.windows.server.sbs)
  • Re: RDP, RWW and VPN difference
    ... And a big feature coming to big server land in Longhorn. ... It's great to see a security expert installing SBS, ... restrict those VPN sessions to specific ports/IP in the network. ...
    (microsoft.public.windows.server.sbs)
  • Re: accessing the system TEMP environment variable
    ... You'd probably better ask in the sbs newsgroup, ... MCSE, CCEA, Microsoft MVP - Terminal Server ... "Do not use temp folders per session" ... If users need to access the same files from their sessions, ...
    (microsoft.public.windows.terminal_services)