They always seem to open maximized, glued to the upper left-hand corner of my monitor. I hate that. After much googling, I found:

http://www.simmonsconsulting.com/2005/09/26/remote-desktop-rdp-window-state/

http://msdn.microsoft.com/en-us/library/ms632612(VS.85).aspx

and

http://blogs.msdn.com/rds/archive/2008/09/02/specifying-the-ts-client-start-location-on-the-virtual-desktop.aspx

These settings work for me:

desktopwidth:i:1600
desktopheight:i:1200
session bpp:i:32

I have a 2560x1600 display, so I like my sessions to be 1600x1200.

winposstr:s:0,1,500,200,2560,1600

1st is always set to zero according to the MS Blog post.
2nd is 1 because I like my remote sessions windowed. Often I have multiple connections open at once.
3rd is 500 because I want my window offset 500 pixels from the left of my primary monitor.
4th is 200 because I want my window offset 200 pixels from the top of my primary monitor.
5th and 6th are kinda funny. They are supposed to represent the bottom right coordinate of the window, so I would expect them to be the top left offset plus the window size. Setting them to 2100 and 1400 should make the window fully sized given my window size and offsets, but I guess it doesn't work that way. Maybe you have to compensate for the frame of the window itself. I found that there is no harm at all in simply setting the size to something larger than the window to assure that it is fully sized. So, I set these values to the size of my largest display.

As the author of the first article mentions, you need to use a text editor that won't corrupt the header of the RDP file. Notepad2 did NOT corrupt it, nor did BeyondCompare 3. TextPad 5.2 did corrupt it.

BeyondCompare 3 was a great way to fix the rest of my RDP files. I just pasted most of the contents of my new, working file over to the files that needed to be fixed, letting only the fulladdress and username fields remain.

When I bought my new Dell Studio XPS 16 laptop, the first thing I did was take out the HD and put in a new SSD. Now I've put that original HD into an external eSATA enclosure and I'd like to use all of its space, but there was a parition on it called OEM Partition that was protected, and I could not delete it from the Disk Management utility.

To delete it, I simply ran diskpart.exe, which comes as a part of Windows 7 and I think Windows Vista.

With diskpart running, I first typed:

select disk 1

then:

list partitions

(to make sure I was on the right disk), then:

select partition 1

and finally:

delete partition override

...and that nuked it! In fact, I had the disk manager open while I did this, and it vanished before my eyes. Now I can make a new partition utilizing all of the space on the drive!