Configuration changes to RDP require that the RDP service be restarted. Assuming single session RDP mode, try this: restart the server machine: don't log on (headless mode!). From the client machine, initiate an RDP session to the server; iniitiate a second RDP session (with the same credentials as the first) to the server; the first RDP session should terminate, the second session should have connected to the first. This behaviour is consistent with single session RDP. If you try to initiate an RDP session with a local session on the server (that is, one where someone has physically logged onto the server) a new RDP session will be initiated: a remote user should never be able to terminate an existing local session. But (assuming single-user mode) a subsequent RDP session will relinquish control of the existing session. RDPWrap is working the way that I "designed" and want it to: that under no cirumstance where the server is being administered locally that administrative control is lost. The conventional offsets for RDPWrap might give you the behaviour that you desire.