Some of the big issues to tackle include:
* Determine hardware costs per TS session (how much ram, disk, etc)
is necessary to support a user.
* How much print spooling will be done
* TS Failover making sure you have 50% free resources
* Sufficient Bandwidth and QoS
* ISP failover
* Perimeter network (router class, firewall, etc)
* Internal vlans, networks, routes, filters, etc
Sounds like a fun project.
Klint
Art DeKneef wrote:
>
> A client has asked me what it would take to set this up. The current
> plan is to allow access to Exchange 2003, the internal web site
> (Windows SharePoint Services 3) and a line of business app. There are
> talking about a small group to start, 25 people, but have big
> expectations. Like a 1000 virtual employees.
>
>
>
> The idea is to start small and see what happens and proceed from
> there. I can figure out pricing and the server cost. What I am looking
> for are any tips or things to look out for while still in the planning
> stages from those that have done or are doing something similar.
>
>
>
> I have been reading up on Terminal Services in Server 2008 right now
> and looking at the guidelines but was hoping for some insight.
>
>
>
> Thanks.
>
>
>
> Art DeKneef
>
> Avanti Computers
>
> Mesa, AZ
>
> 480-649-4430
>
>
>
>
~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
