Solved

New to Remote Desktop Services

Posted on 2013-05-12
4
562 Views
Last Modified: 2013-05-20
I have a 2008 SBS & currently have a Win2k3 server set up as a terminal server, that's soon to be replaced with a 2008 server, running the new & improved (?) Remote Desktop Services.

I want a drive to be mapped when a user logs on & want them to either only have the ability to log off, or have them logged off automatically when they quit their session - no shut down option, but don't see where I can set up a profile for that!

Has printing improved with Remote Desktop Services? On the the win2k3 server, I was using a program called Net2Printer, which allowed users to print to their own printers. Will I still need a 3rd party app like that?

FYI, only programs that will be used are Quickbooks, Word & Outlook.

I was planning on upgrading Win2k3 to 2008, to be a BDC, as well, assuming it's still taboo to have terminal services running on a DC.

Any advice appreciated!
0
Comment
Question by:gromack
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 15

Accepted Solution

by:
ZabagaR earned 500 total points
ID: 39159677
I definitely wouldn't run remote desktop services / terminal services on a DC. It is a bad idea. You don't need a 3rd party print application. Go to Remote Desktop Host Configuration. In the properties of your rdp-tcp connection, just allow printer redirection. It's on the Client Settings tab. W2K8 uses easy printing where the print jobs are rendered on the term server then sent back to the client where their own printer driver does the printing. See here: http://blogs.technet.com/b/askperf/archive/2008/02/17/ws2008-terminal-services-printing.aspx

Under the sessions tab, still in properties of rdp-tcp, you can control what happens when a user loses their connection or quits. Disconnect & Log off are set here.

If your users aren't admins, they won't be able to shut down the server. Default policy dictates that. Even if its just local policy on your terminal server, you can check the "shut down the system" under user rights assignment. In group policy, thats under Computer Configuration,  Windows Settings, Security Settings, Local Policies.
0
 

Author Comment

by:gromack
ID: 39160308
Thanks for the advice - been a long weekend, so I'll give that a try tomorrow & get back to you.
Thanks, again!
0
 

Author Comment

by:gromack
ID: 39165728
Ok, printing works great & I'm even using a wireless printer, which I thought could add another fly to the ointment!
As far as the session settings, I'm gonna try override on both, with end disconnected session in 5 minutes(?) - my thinking is that if they get disconnected they may try to reconnect immediatley, which should put them right back where they were (right?), or if they don't try, it will disconnect in 5 minutes, or should that be something else.
I set idle session limit at 10 min, & when limit reached or connection broken, end session, hoping that this will keep users from being in limbo & someone having to go to server & disconnect their session.
Any advice?
0
 
LVL 15

Expert Comment

by:ZabagaR
ID: 39166479
I usually set my disconnected sessions to end in 5 minutes. Sometimes you accidentally lose your connection, or want to move to another desktop PC - so reconnecting is nice. But after 5 minutes, for me, it means a user didn't exit properly...meaning they clicked the X in their RDP session instead of logging out....in which case I want them logged off.

In my job, we leave idle alone - no limit. People may not be active with keyboard & mouse for a while and don't want to have to log in all over again.

"When session limit is reached or connection is broken" is really whatever works best for you. I usually set that to "disconnect"...then my 5 minute 'disconnected' setting goes into effect.

We also use a script to log off all users at the end of the night
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

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

Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

729 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