SBS2003 & 2008 TS Deployment, Just want to make sure it will work

Hi

I am planning a deployment of a SBS2003 server (unfortunately needs to occur
soon so cannot wait for SBS2008 :( ). It will server files, exchange & SQL
to total of 50 local & remote users.

Also will be a Terminal Server box for 30 remote users (22 sites). I
thought 2008 would be the best option here with the added TS functionality.
Remote users will be served Outlook, an SQL Front end app & Office etc.

A 2000/2000 link for TS/RWW connections will be provisioned with 512/512
clients
ADSL 2+ for other main office traffic

While most remote sites are static, there will be use from home connections
etc so I was going to use RWW for all remote connections. With cost a big
issue saving on deploying VPN hardware etc.

However I have read that there are issues 2008 and SBS2003 through RWW.
Firstly the 2008 TS does not show up as an application server in RWW, is
there a work around for this?

I would like to take advantage of the 'easy print' also, so if there is a
work around to get the 2008 TS visible in RWW will RWW pass RDP 6.0?

I guess the alternative is to use TS Gateway straight to the TS box using
HTTPS, but that sidesteps the other RWW features.

I'm not 100% sure yet but likely full Remote Desktop will be presented to
the remote clients (restricted to only allowable apps) and will likely use
RemoteApps to serve apps to the LAN clients.

I guess I just wanted to find out what issues this config may present. I
haven't found any papers outlining 2008 TS to SBS2003, I guess its all a bit
to knew at the moment

Thanks
Dan

Charlie
Tue May 13 17:25:39 PDT 2008

There are specific steps outlined in earlier posts in this newsgroup, but
yes, you can have a Server 2k8 Terminal Server show as an application server
in RWW.

You're right, you'll not have specific RemoteApps over RWW. If you want
that, you'd need to set up a TS Gateway server.

I'm not positive, but I don't think you'll get RDP6 across RWW. I haven't
actually tested that.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Dan" <Dan@discussions.microsoft.com> wrote in message
news:3E1E16D5-D7B1-4D7A-950E-C9B02910D953@microsoft.com...
> Hi
>
> I am planning a deployment of a SBS2003 server (unfortunately needs to
> occur
> soon so cannot wait for SBS2008 :( ). It will server files, exchange &
> SQL
> to total of 50 local & remote users.
>
> Also will be a Terminal Server box for 30 remote users (22 sites). I
> thought 2008 would be the best option here with the added TS
> functionality.
> Remote users will be served Outlook, an SQL Front end app & Office etc.
>
> A 2000/2000 link for TS/RWW connections will be provisioned with 512/512
> clients
> ADSL 2+ for other main office traffic
>
> While most remote sites are static, there will be use from home
> connections
> etc so I was going to use RWW for all remote connections. With cost a big
> issue saving on deploying VPN hardware etc.
>
> However I have read that there are issues 2008 and SBS2003 through RWW.
> Firstly the 2008 TS does not show up as an application server in RWW, is
> there a work around for this?
>
> I would like to take advantage of the 'easy print' also, so if there is a
> work around to get the 2008 TS visible in RWW will RWW pass RDP 6.0?
>
> I guess the alternative is to use TS Gateway straight to the TS box using
> HTTPS, but that sidesteps the other RWW features.
>
> I'm not 100% sure yet but likely full Remote Desktop will be presented to
> the remote clients (restricted to only allowable apps) and will likely use
> RemoteApps to serve apps to the LAN clients.
>
> I guess I just wanted to find out what issues this config may present. I
> haven't found any papers outlining 2008 TS to SBS2003, I guess its all a
> bit
> to knew at the moment
>
> Thanks
> Dan
>