An RDP Session issue

Question

Post reply

An RDP Session issue

jayoub

SSCertifiable

Points: 6991
More actions
June 12, 2015 at 7:08 pm

#297818

Sorry for posting an RDP session issue, but this is the only forum that i use. I am hoping someone can help.
Does anybody know how to use the mstsc -v:servername /F –admin and get it to map the local drives of the PC
Any help is appreciated.
Jeff

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Alan Burstein SSC Guru Points: 61141 More actions · Answer 1

Take a look at this article:

http://blogs.msdn.com/b/brendangrant/archive/2009/02/17/most-useful-feature-of-remote-desktop-i-never-knew-about.aspx

It's a bad idea to use RDP to manage a DB server. MS Windows and SQL Server offer a variety of tools for administering SQL Server instances without needing to open up an RDP session.

"I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

-- Itzik Ben-Gan 2001

jayoub SSCertifiable Points: 6991 More actions · Answer 2

jayoub

SSCertifiable

Points: 6991

June 13, 2015 at 6:39 am

#1805296

Thank you very much. I will check it out

Jeff

jayoub SSCertifiable Points: 6991 More actions · Answer 3

The article is great, but what I am look for is to be able to map drives while using console or admin connection and not the regular RDP Connection.

I tried to use \\tsclient\c\ to map the drive once connected, but got an error message said the drive does not exist…

I thank you for helping I will keep trying and if you find something please let me know

Jeff

Joie Andrew One Orange Chip Points: 27360 More actions · Answer 4

Why not configure your RDP session and then save it to a file? Then you can use mstsc pointing to the configuration option and still specify /admin.

Joie Andrew
"Since 1982"

Jeff Moden SSC Guru Points: 1004312 More actions · Answer 5

Alan.B (6/12/2015)
It's a bad idea to use RDP to manage a DB server.

If you're going to say something like that, you need to explain why. To be sure, I'll say "It Depends".

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

jayoub SSCertifiable Points: 6991 More actions · Answer 6

The post from Joie Andrew is interesting and sound like the solution to my problem. I would like to know how to do this if you have a chance.

The reason we need to do this is that we have different networks and we often need to copy large db backups from one network to another. The only way to connect is via RDP so it takes hours to copy the files over. Well when you use the regular RDP session the it times out and you loose the copy. We are having to nurse these session while the copy is happening.

When we connect with the /admin the session does not time out and close. I will lock and continue to copy the files. The problem is that when i connected using /admin my drive were not mapped.

Please if you have a way that i can use the RDP file setting with the /admin connection it would be great.

Your help is appreciated.

Thank you very much

Jeff

Joie Andrew One Orange Chip Points: 27360 More actions · Answer 7

Try something like the following.

Joie Andrew
"Since 1982"

jayoub SSCertifiable Points: 6991 More actions · Answer 8

Thank you very much for the help. You saved me from having to sit in front of the computer for hours while the files copy over.

I marked your post as solution.

Jeff

Alan Burstein SSC Guru Points: 61141 More actions · Answer 9

Jeff Moden (6/13/2015)
Alan.B (6/12/2015)
It's a bad idea to use RDP to manage a DB server.
If you're going to say something like that, you need to explain why. To be sure, I'll say "It Depends".

I discourage it because RDP sessions use up memory and are not very friendly about returning that memory to "Available Memory" even after you end (not just disconnect from) your Terminal Services session.

Brent Ozar had a session back in 2012, at Redgate's "SQL in the City", called "Six Scary SQL Surprises". I attended it in Chicago and he demo'd why he discourages using Remote Desktop to manage your SQL Servers. He did some basic tasks such as copying files and opening SSMS and showed the impact it had on Available Memory. He did the same session in Seattle before SQL PASS 2012. The discussion is available on Youtube - he begins talking about it 12 minutes in where he talks begins talking about "Surprise #2: The cannibal that eats all your memory." He does not exclusively blame RDP but mentions it repeatedly as one of the culprits. Those presentations were compelling enough to scare me away from RDP as a tool for managing SQL Servers unless there is no other way and you understand the consequences of doing so.

Again, if there is something that you must do and RDP is your only option then I guess it's okay provided you don't copy files (or use XCopy with parameters that prevent caching), don't open an internet browser or other memory intensive application and close your session when you are done.

"I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

-- Itzik Ben-Gan 2001

Joie Andrew One Orange Chip Points: 27360 More actions · Answer 10

Glad to know it worked for you!

Joie Andrew
"Since 1982"