Any problem using W2008 Server Std(for Term Svc) in an SBS2003R2 environment ?

At the moment, Windows Server 2008 is compatible with an SBS environment for use as a Terminal Server. Numerous people have successfully configured it as a Terminal Server.

The only problem which has not yet been fixed is the fact that the http://sbsserver/connectcomputer wizard does not yet support adding Windows Server 2008 servers to the SBS domain. As a result, you must manually add the server to the domain, which means it doesn't show up in the Remote Web Workplace. This just means your users would need to directly login to the server using the MSTSC.EXE (Remote Desktop Client) program instead. You can easily create a pre-configured file in a shared location which users double-click and it takes them straight to the DNS name of the Terminal Server without any user-intervention required.

-tigermatt

Wouldn't that require a 2nd external IP and 2nd nic in the W2008 Term Server?

Otherwise they wouldn't have anyplace to login locally to run the mstsc from.

Bruce

No, it wouldn't. You would have to have the users create a VPN connection to the SBS server, then utilise the VPN connection to connect using the local IP address of the Server 2008 server and start Terminal Services. You could run it off a second IP if you wanted, but that wouldn't need a second NIC in the server, and it's unnecessary.

At present, this is just about the only solution which is open for you. In the future, I expect Microsoft will release an update for the connectcomputer wizard to allow it to support Server 2008, but as it stands now, you have to follow this approach until more information comes from Microsoft.

Would the router have to point 3389 to the W2008 T/S  or just create the VPN then mstsc to the loca w2008 server name?