Wednesday, March 27, 2013

Customize an RDP file for a Specific RDWeb user

Do you have some rdweb users who would like to rdp to their desktop from the rdweb portal, but are uncomfortable with the method used in the rdweb portal? It's kind of a long process to login to rdweb, mouse over to 'remote desktop' then plug in the desktop information, etc. What if the user had an rdp file that looked and acted like an app in the remoteapps list? That would be great you say? Then let's do it.

*There might be an easier way than this and if there is please let me know about it*

First, launch remote desktop connection.
Input the user specific information in the fields.

Second, save it as an rdp file.

Third, (only do this if your user's desktop has dual-monitors) open the rdp file in notepad to add some information.
If you user's desktop has dual monitors and the system is Windows 7 ultimate or enterprise then add the following to the end of the rdp file that is opened in notepad: use multimon:i:1

If the users' desktop has dual monitors and running pre-Windows 7 ultimate or enterprise (e.g., windows 7 pro or Windows Vista) then add the following to the end of the rdp file: span monitors:i:1

What is the difference between span and multimon?

From MSDN blog

"Span mode, introduced in Vista, allows the remote desktop to span across all monitors on the client as long as the monitors are arranged to form a rectangle. The remote session created when using span mode is still a single-monitor session. With multimon support, each monitor on the client machine is viewed as a distinct monitor in the remote session. Due to this fundamental difference, span mode has some restrictions that true multimon does not:
1. The primary monitor must be leftmost.
2. The set of monitors must form a rectangle (i.e. identical vertical resolution, and lined up in exact straight line).
3. The total of the resolutions must be below 4096x2048 (ex. 1600x1200+1600x1200 = 3200x1200)."

Multimon "...for Remote Desktop Services allows users to open a Remote Desktop connection expanded across all the monitors on the client computer regardless of the client monitor configuration. With this feature, the user can fully utilize all the monitors connected to the client computer for the Remote Desktop connection thereby providing extra desktop space and an almost seamless experience with the client desktop that is much improved over “Span mode”. "

Fourth, add the rdp file to the remoteapp programs list in your rdweb server.
Go to "remoteapp manger."
Click "add remoteapp programs."
Make sure "all files (*.*)" is selected in the dropdown box. After you've found your custom rdp file select Open.
Next and finish.

Fifth, customize view permissions for the rdp file.
Under remoteapp programs in remoteapp manger, right click the rdp file then select properties. Select user assignment then select "specified domain users and domain groups." Click add. Since this is a specific user rdp file select the appropriate user profile for the rdp file.
OK it.
Then OK in remoteapp properties.

Now, say all of this was for Jane Austen. She will login to the RDWeb portal, see the file you've added to remoteapp programs for her profile, run it then have access to her work desktop. This is much easier compared to the default route.

1 comment:

  1. Interesting topic for a blog. I have been searching the Internet for fun and came upon your website. Fabulous post. Thanks a ton for sharing your knowledge! It is great to see that some people still put in an effort into managing their websites. I'll be sure to check back again real soon.modem router combo reviews


Life in IT appreciates and encourages your comments, but we do have guidelines for posting comments:

1. Avoid profanities or foul language unless it is contained in a necessary quote.

2. Stay on topic.

3. Disagree, but avoid ad hominem attacks.

4. Threats are treated seriously and reported to law enforcement.

5. Spam and advertising are not permitted in the comments area.