Print system information on top of your desktop background upon startup using BGInfo.exe (Sysinternals)

( Source/Ref.: https://technet.microsoft.com/en-us/sysinternals/bginfo )

Executable with custom template:




https://onedrive.live.com/redir?resid=C213C8B09441DCD7!48680&authkey=!AEUBtQwOZXCSUto&ithint=file%2czip

Drop the the ".exe" and the ".bgi" files in C:\Windows, and schedule task to run at user logon :

    Bginfo.exe BGInfoConf-v160205.1.bgi /nolicprompt /timer:0

Default template:

My template:

Scheduled:

RDP as a different user to Localhost on Windows 7

Concurrent sessions is a feature in server editions of Windows that lets more than one user to log on remotely and use the server at the same time. By default in desktop editions when you connect to a remote computer using Remote Desktop it will force the user who is physically sat at the computer to log off. So how to work around this?

In two steps:

• Crack termsrv.dll, remove the Concurrent Remote Desktop sessions limit, allow multi-user login in XP/Vista at the same time.

• Connect RDC to IP address 127.0.0.2

REFERENCES:

Original patcher:
TCP-Z, Best TCP/IP Patch: Universal Termsrv.dll Patch V1.0b Build 20090425 Release
http://deepxw.blogspot.fr/2009/04/universal-termsrvdll-patch.html

Article commenting on the patcher:
Enable Concurrent Sessions on Windows 7, Windows Vista and Windows XP (Termsrv.dll)
http://digiex.net/guides-reviews/guides-tutorials/windows-guides/1879-enable-concurrent-sessions-windows-7-windows-vista-windows-xp-termsrv-dll.html

Cached version of the patcher executable:
UniversalTermsrvPatch_20090425.zip (Location 4) (Click to download)
https://onedrive.live.com/redir?resid=C213C8B09441DCD7!48685&authkey=!AAdHghvpV7PZ0oM&ithint=file%2czip

Connect Remote Desktop Protocol (RDP) Client To Localhost
(see "Method 1: Connect RDC to IP address 127.0.0.2")
http://www.techbuzz.in/connect-remote-desktop-protocol-rdp-client-to-localhost.php


FURTHER READING:

TCP-Z, Best TCP/IP Patch: Say Bye To Half-open TCP Connections Limit In Vista/2008 SP2
http://deepxw.blogspot.fr/2009/05/say-bye-to-half-open-tcp-connections.html

Redirect terminal service to console (ie. Disconnect RDP and leave computer unlocked)

Usually, when you close your RDP connection the remote computer locks the computer and therefore restricts access and use of your Desktop (COMPUTER LOCKED).

The solution is either :

1/ use VNC instead of RDP

2/ or run "@tscon.exe 1 /dest:console" to transfer your session from RDP to CONSOLE, this will "virtually" kick you out, but it will leave your user session open and your Desktop active on the remote computer.

WARNING: By definition, this solution (2/) is unlikely to work for multiple remote desktop sessions on a single computer at the same time, there can be only one console session and it is already in use.


C:\Users\Administrator2>tscon 2 /dest:console
Could not connect sessionID 2 to sessionname console, Error code 7045
Error [7045]:The requested session access is denied.

TightVNC is a great Open Source alternative to Remote Desktop Connection!

In a previous post we've seen that Remote Desktop Connection (embeded with Windows XP PRO) is a great tool that allows you to work on a distant computer and to use its graphical environment.

But what do I do if I only have an XP Home Edition? You might consider using TightVNC then! Besides, even if you have the license for Remote Desktop Connection you might consider using TightVNC anyway because... it rocks!


1/ Install the VNC server

Visit http://www.tightvnc.com.

2/ Start the VNC service
3/ Update the Firewall

Authorize the server executable and open ports 5800 and 5900:

4/ Get the IP of the Target

Ping the server from your other computer (the client) and read its IP.

5/ Connect to the Target using a VNC Viewer

Connect to the remote computer using its IP:

6/ VNC Security considerations

There is one fundamental difference between TightVNC and Remote Desktop Connection: the remote computer's monitor will display an open session when you log using TightVNC (eg. you will see the mouse move, etc.) whereas it will display a "locked computer" when you use Remote Desktop Connection.
From a security point of view, you need to ask yourself if it is a problem having your session left open on the remote computer. Who are the people who have physical access to this computer?

On the other hand, having the session open is very convenient if the remote computer performs Graphical Automation: for example, AutoIT doesn't work correctly if the computer is locked! In which case TightVNC might become a life saver!

Last but not least, you can combine both behaviors by using a Virtual Machine on top of the physical one: the physical machine can then be locked and the data and processes running on the Virtual Machine will be protected from the outer world while you are using TightVNC!

Use another processor for heavy tasks... (Remote desktop connection)

Compiling can be a very annoying task: it takes ages and it uses all your CPU resources; it's especially true when your software project contains a few hundred thousands lines of code and that you have to perform a "Rebuild All" compilation.

Well, that was until today... because from now on, the "Rebuild All" doesn't run on my computer anymore... thanks to "Remote desktop connection"!

You can find this utility among the programs shipped with your Microsoft Windows XP PRO SP2 Operating System (and above):



Remote Desktop Connection allows you to connect to another computer using its address (IP or local network name):



If you want the other computer to work on your local data you may have to share your drive C:\

Warning: of course, you must trust your local network very very very much to do this! Or find another way...

Now, assuming that your computer's name is "\\MyComputer", you can make the second computer work on your data; just map the network drive using "Explorer > Tools > Map network drive":



And here you go... you can have an other processor doing the heavy tasks for you: