add shortcut to users desktop for RDP on local system.

You can use script or group policy preference to create shortcut.

Group Policy Preferences - Creating Desktop Shortcut
http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/02a7bfbb-180f-40eb-82e3-2343b2bf31eb
http://community.spiceworks.com/topic/289722-deploy-rdp-file-to-user-desktop-using-group-policy

How to Create a "Remote Desktop Connection" Shortcut to a Specific Computer
http://www.sevenforums.com/tutorials/149790-remote-desktop-connection-shortcut-create-specific-computer.html

Check this simple steps

http://blogs.utexas.edu/waj288/archives/16

ok...i seen where i can do that and have created shortcuts before but confused as to how i can create a RDP shortcut on all users desktops with remote setting already in the RDP Session...so when users doubleclick on RDP Desktop shortcut they will be presented with a username and password box....


So i go to create a desktop shortcut....under

action i choose create...
Name...is name of shortcut...
target type....is file system object....
Location....is desktop...

Target path ....is  %windir%\system32\mstsc.exe
arguments.....none
Start in....%windir%\system32\mstsc.exe
 
I Chose  %windir%\system32\mstsc.exe in target path and start in path for i want the users to user their own RDP client locally......will this work the way i have it????

The only thing i need to do is add RDP location but where would i do that?????

I seem a little lost????

P.S....was just looking in the edit GP...and seen where it say icon file path....if i put %windir%\system32\mstsc.exe in there and get rid of the other two places...target path and start in would this mean that the desktop shortcut would run on the local users computer and it would look in directory %windir%\system32\mstsc.exe????? Thanks again for everyones help.....

Why not configure a connection, save it as .rdp file and distribute that?

sounds good mcknife but i am trying to put this on 350 desktops. is there a way to do that without physically touching each machine??? Thanks for help!!!

Of course. You can distribute the file using a logon script or via group policy preferences. Logonscript would use robocopy, GPPs just like you did before with the shortcut, this time no shortcut but a file.

how would you go about doing it through GP by file...confused as to what it would look like....using 2008 R2...Thanks for your help

It's the same place where you configured the distribution of a shorcut before, but this time it's a file. So the section is "file", not "shortcut".

yes, i get that but confused with wanting to add shortcut to rdp..but i want it to put to users local system and i want to add the rdp connection ip address configured already in it...how would you go about that...thanks for your help...

The rdp file holds all that. As described before: configure a connection at the rdp client. Save the connection as rdp file and distribute it afterwards.

okay..So if i configure rdp and save then i can distribute that through group policy but i would have to place that file on our server for users to access....but would that not create alot of more network traffic??? if i do it that way then i am assuming i would just fill out target path and point to location under GP...correct???

My issue is i want users to user their RDP Client locally and not travel across network and use the one on server....so under GP under Icon File path i can input %windir%\system32\mstsc.exe and this will let user use their local RDP...correct??? if so how can i add ip address to that file or cant i?????? Thanks again for all your help...

P.S..Okay so i think i figured how to create shortcut to local client RDP on all desktop...through gp...target type..file...location...desktop...target path..%windir%\system32\mstsc.exe...then name the shortcut whatever i want...i believe this will place a shortcut on all users desktop for the rdp client using their local RDP client and not on network...does this seem right....Sorry for confusion...just has my head spinning .....thanks again....

okay...got it thanks...