Boot a PC to Remote Desktop

Boot a PC to Remote Desktop - Concept / Reasoning

There are many reasons why you may wish to boot a PC to a remote desktop, you can share resources and software, make better use of you high spec PC from a low spec PC, or access you PC from remote locations. All of these are good reasons, but for me the main reason is to make use of old PCs which would otherwise go in the bin.

Step 1 - Build a Stripped down version of windows XP service pack 2 or 3.

You can skip this step if you want it is not necessary is you are using a fairly good PC as a client, but if you are using an old PC may be you should / might want to do it.

Use "n-lite" to strip down you copy of windows XP service pack 2 or 3, there are guides of how to do this on the n lite site.

Step 2 - Install your OS.

Install you OS on the PC you intend to use as a client. If you already have XP service pack 2 or 3 on there already save some time and maybe use that.

Step 3 - Learn your user and network setting.

You need to know your user name and passwords for your PC you intend to log on to (your "server" and the computers name.

Step 4 - Tinkering with the Registry.

Step 4.1 - mstsc.exe instead of explorer.exe

If you have got this far you probably know and accept the fact that messing about with the registry in windows can mess it up to the point where you have to reinstall . . . . .

First off we have to change the windows shell so it looks for mstsc.exe in stead of explorer.exe

type regedit in the run box and navigate to the following bit:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

Find this key () and right click > modify.

Change explorer.exe to mstsc.exe.

Step 4.2 - Change / Set Default User

You don't have to do this bit, but if you don't you will have to log in twice, once top the local client, and then again to the remote desktop.

In regedit:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon.

Edit Value : "DefaultUserName"

If this isn't present then create the value, put in the user name that you specified during installing you OS or "administrator". To create a value right click on empty window space in regedit, "new" will appear select "string value" and rename to "DefaultUserName"

Edit Value "DefaultPassword"

If this isn't present then create the value.

Step 5 - Reboot Client

With your fingers crossed reboot your client, make sure your server is on.

You should be presented with:


Type in the computers name you are using as a server. For a guide of home to find you server / computers name.

Click More Options and select features you would like to be available during you session, for a home network you should be able to switch on all of the "experience" features.


Click Connect and away you go.

Desktop Study

Sustainability Consultants

Sun Ray 1 and Windows

Sun Ray 1 - Overview

The sun ray is a thin client which you can buy on ebay for £10 / $20 and this made it a tempting buy for someone like me who enjoys experimenting with networking etc. It is dated nowadays and rather large. . but there we are.



Sun Ray 1 - Server 2008 R2

My end goal is to use a copy of server 2008 R2 to run three worksations using 2 x remote desktops (allowed under admin), and one user on the server itself. It would appear that the Sun Ray 1 WILL NOT WORK.

In order to boot the sun ray 1 to a windows desktop you need a server running a Solaris operating system, which then will direct the user to another server or virtual server running windows. I am not a pro and this I suppose will be obvious to some, but it was so obvious no one had written it down on the net, so I have.

Sun Ray 1 - Other Obstacles

Another obstacle is that you need a special kind of keyboard to go with you sun ray even to access the on client menu, "press shift +ops" to enter the config menu . . . . I DON'T have a OPS button.

Sun Ray 1 - Alternatives



If you are trying to boot to windows desktop you might try a HP T5530, with windows CE 5.0, or for that matter any thin client running Windows CE. This will enable you to get on to a remote desktop session on the server fairly easily without advanced tinkering.

If you are feeling brave there are some tweaks you can do to an old / legacy desktop PC get it is boot to a remote desktop which I will explain in my next post.

Desktop Study

Sustainability Consultants

Why are Servers so Powerful?

In a previous article I was explaining how to set up an old PC as a network file / media server, and being that I used an ancient PC for the task and it worked well, I began to wonder why servers have to have soooo much processing power.

Well the answer is that servers don't only store files, they do other things too. The file server I mentioned that I made, just sits there and stores files, and doesn't really do anything. However there are different types of server that do lots more stuff.

A terminal server or a remote desktop server, may provide all of the processing power for the equivalent 10 PCs, because ten people are using it at once. How?

When people in an office log on to windows they are often working at a thin client terminal, a thin client terminal does not have much processing power, just enough to access the terminal / remote desktop server. All of the hard work is done by the sever, whilst the box on the desk (thin client) just communicates the keyboard and mouse info to the sever, and gives you a box to plug your monitor in to.

Servers can also run "virtual machines" which is like a computer within a computer, whilst say using MS Sever 2008 R2 you can install a 2nd 3rd or 4th (or more) operating system to run in its own little area of the sever OS.

So that is why sevres have to be so powerful, they are in effect running 10, 20 30 . . 100 "PCs" all at the same time, allowing lots and lots of users to all share the same processing power.

Environmental Consultants

Environmental Permitting

Desktop Study