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

Posted on 2008-06-13
Last Modified: 2010-04-19
We have an existing SBS2003R2 environment.  Single server.  Need to add a Terminal server for an application for remote users.  New server would be running Windows 2008 Std.

All compatible ?  Any gotcha's ?


Question by:BBrayton
  • 3
  • 2
LVL 58

Expert Comment

ID: 21780158
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.


Author Comment

ID: 21780872
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.

LVL 58

Expert Comment

ID: 21780903
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.

Author Comment

ID: 21780998
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?
LVL 58

Accepted Solution

tigermatt earned 125 total points
ID: 21781007
Once the VPN is set up all the traffic is sent to the SBS and then passed off locally, so it would just need to have the VPN port forwarded to the SBS. You would then use the local server 2008 address or IP to connect to TS.

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

Redirected folders in a windows domain can be quite useful for a number of reasons, one of them being that with redirected application data, you can give users more seamless experience when logging into different workstations.  For example, if a use…
You may have discovered the 'Compatibility View Settings' workaround for making your SBS 2008 Remote Web Workplace 'connect to a computer' section stops 'working around' after a Windows 10 client upgrade.  That can be fixed so it 'works around' agai…
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now