Exchange 2010 and Terminal Services Configuration

I want to confirm that Exchange 2010 Standard edition will allow for the setup of 5 different Email groups.  

I would like to setup 1 exchange Server to handle mail for and through to, all being independent.

I also would like to make a Domain Controller a Terminal Server as well (Separate of the Exchange Server).

I should be able to accomplish this should I not?  I would also just use AVG for Exchange Email to handle spam and virus detection.

Let me know if this is feasible.

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.

A comment on using a DC as a Terminal Server - that is the opposite of Best Practice.  By using a DC as a Terminal Server, you are in effect allowing normal user accounts to log in to a domain controller.  You could do that, but you really shouldn't.

Exchange can handle email for mulitple email domains - no problem.  (Don't know what you mean by independent, though)

I haven't looked lately, but AVG does have a server version, which I know for sure works with Exchange 2007 and Windows 2003.  Check their website to see if their product supports Windows 2K8 and Exchange 2010.  Virus protection might work okay, but I don't know if their antispam protection is good or not (it might be, I've never tried it on a server).


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
2ndFloorAuthor Commented:
Thanks for the reply Kaffiend, I was thinking I should just use Hyper V for the Terminal Server running on the Domain Controller.....Since Hyper V uses lots of RAM it may not be the best solution, but it should be better than logging directly on the Domain Controller.
Well, if you have the budget for an additional server license, a separate server for Terminal Services would be the way to go.

Hyper-V will work fine.  Like you said, give it lots of RAM.  If you have a new-ish server, it should have enough free slots for you to add more.  RAM is a great investment, if you're going to run virtual machines.
2ndFloorAuthor Commented:
I'm just ordering the Servers now, so I'll include lots of RAM.  Since I'm ordering the Standard Edition of 2008 64 bit Server, I think it comes with a free Standard License for use in Hyper V.
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
Microsoft Server OS

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.