Solved

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

Posted on 2008-06-13
5
342 Views
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 ?

Thanks

Bruce
0
Comment
Question by:BBrayton
  • 3
  • 2
5 Comments
 
LVL 58

Expert Comment

by:tigermatt
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.

-tigermatt
0
 

Author Comment

by:BBrayton
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.

Bruce
0
 
LVL 58

Expert Comment

by:tigermatt
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.
0
 

Author Comment

by:BBrayton
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?
0
 
LVL 58

Accepted Solution

by:
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.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

803 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