Advice on Terminal server setup

i am looking for advice/comments on adding a windows server 2003 (terminal server) to a small business server 2003 network.

How should i attach the terminal server box to the SBS?   set it up as a stand alone server and just join the domain ?

Can the terminal server use clients romaing profiles?

How about remote printing, do i need a third party utility?



Thank you

LVL 1
in4niAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bwalker1Commented:
How should i attach the terminal server box to the SBS?   set it up as a stand alone server and just join the domain ?

Join it to the domain.

Can the terminal server use clients romaing profiles?

Yes - you can also set the terminal services profile in the user properties in AD.

How about remote printing, do i need a third party utility?

You just need to install all of the drivers on your terminal server.

0
juanferminCommented:
50 Points, why so stingy?

1.   OK, first of all make sure you get Windows Server 2003 Standard.  If you get Enterprise, it's going to cause problems with your SBS.  
2.   Personally, I would set it up as a backup DC, in case your SBS server were to crash, you have another copy of AD that can authenticate users or at least you won't have to worry about restoring AD from a backup, which could be a pain.
3.   The Terminal Server can definitely use the Client's roaming profiles, just specify under AD the path to their romaing profiles (//servername/users/profiles/%USERNAME%/), though I would set it to turn off Wallpaper.
4.   As for Remote Printing, a utility like Net2Printer.com will eliminate the headaches associated with TS Printing, but if you would like to try with out it keep the following in mind.
          A.  You need to make sure that you install EVERY print driver for EVERY printer that the clients have.
          B.  DO NOT install the Driver from the CD's that ship with the printer, instead go to the website and DL the 2003 Server edition of the driver.
          C.  Make sure that your users LOG OFF and not just simply close the TS window, this tends to break the TS_Port Allocations, which causes the majority of TS Remote Printing problems.
          D.  Make it a policy to Administratively Log off users who's connections have been idle for say 30 Min., again to prevent TS_Port problems.
          E.  DO NOT purchase Client CALs, purchase User CAL's, they're much easier to manage than Client CALs, the exception to this is if you have a preset number of computers that access TS, by several different users.
          F.  If you do purchase user CALs make sure you change this in the Licensing Mode of the server, which by default sets up Client CALs.
0
juanferminCommented:
Oops, E & F should be 5 & 6, different subject.. hehe
0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

in4niAuthor Commented:
I dont understand the points thing howes that?



thannk you for the reply.


What problems should i expect from Server 2003 Enterprise ?



Again, Thank  you
0
juanferminCommented:
As for the points thing, if you were asking something pretty straight forward, like, "What Terminal Services are available for Linux", that's a 50 point question, someone responds with a couple of website addresses, no REAL problem solving involved.  You, however asked a multifaceted question, normally you give more points for that.

As for Win2003 Enterprise, it tries to supercede the licensing server on SBS 2003, and can cause unexpected reboots of your SBS server, so that's why you shouldn't use it.
0
in4niAuthor Commented:


>As for Win2003 Enterprise, it tries to supercede the licensing server on SBS 2003, and can cause unexpected reboots >of your SBS server, so that's why you shouldn't use it.


Very interesting, Will this happen even if the enterprise is attached as a domain member like a workstation would be?


0
juanferminCommented:
I don't think so, but if you run DC Promo on it, you're in for a world of trouble.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
juanferminCommented:
Dang, 50 Points AND a B... Not even sure if I should even say thanks for all that.
0
in4niAuthor Commented:
i thought i changed the points to 200?
0
juanferminCommented:
Oh.. you're right, sorry.. hehe ;)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.