How to Install Any Version of Windows from Other Network Computers

Talk about a complex thing to do: installing Windows over the network. Even installing it via a USB drive is simpler. However, this doesn’t mean it cannot be done. Using a free tool named Serva and a bit of time and attention, anyone can set up his/her network environment so that Windows installations are performed with ease, from one network computer. Here’s how the whole process works!

VERY IMPORTANT Prerequisites

There are many things you need to prepare beforehand, so that everything works smoothly. Please don’t skip any of these elements or the likelihood of failure will be high:

1. You need to download and extract a little tool named Serva. Download the appropriate version for your operating system (32-bit or 64-bit). You will notice that there are a "Non-Supporter" version and a "Supporter" version. The free one is the "Non-Supporter" version. It includes a small annoyance when you start it, plus a few limitations that won’t impact you unless you are a network admin or IT professional who needs to install lots of operating systems on many network computers. If you are such a professional, go ahead and purchase the "Supporter" version which costs a fair $29.99.
2. This software is a bit finicky. It doesn’t like long folder structures and installation folders, spaces and special characters. Therefore, extract it in a folder with a short name, directly on the root of one of your computer’s partitions. For example, I extracted it at "D:\SERVA". Choose a similar path on your computer.
   
3. You need the original installation files for the operating system(s) you want to install over the network. Have them at hand as you will need to copy them to a special folder, as they are, without modifications.
4. For the computers where you are about to install Windows over the network, identify their exact network card model(s). Then, download the appropriate drivers for the Windows version you are about to install on them. By default, Windows setup programs support a limited number of network cards. If your system is rather new, then it is very likely that it won’t support its network card and the installation procedure will fail.
5. Every time you run Serva, run it as administrator. This way it has the required permissions to create files, save the settings you make, etc.
6. When you run Serva, make sure that it is not blocked by your firewall. The application must be set as allowed on the computer where it runs, otherwise it won’t be able to transfer anything over the network.
7. The computer where the installation files are stored and the one where you want to install Windows must be part of the same network. This means that you have a router on your home network, managing network IP addresses and network traffic. If not, then you should directly connect the two computers with a crossover cable.

Step 1 - Run Serva & Make Its Initial Configuration

Run Serva as administrator. The free version will ask you to wait for 7 seconds before you can use it. Once the wait is over, click "Thanks, not today".

Its window is now open. Click Settings.

First, go to the DHCP tab. If your computers are part of the same network and the management of IP Addresses is taken care of by your router, enable these settings: proxyDHCP and BINL.

BINL is a special add-on that acts as a DHCP protocol extension and it is used by Serva during its preparation and maintenance procedures. proxyDHCP is a special setting that tells Serva that it doesn’t need to act as a DCHP server in order to provide IP addresses to the computers connecting to it.
Even though Serva’s developers don’t recommending enabling this setting, we have learned in our testing that it helps eliminate some issues. Therefore, also enable the box which says "Bind DHCP to this address" and leave the default IP address that is provided.

There is no need to modify other settings in this tab. Next, go to the TFTP tab.
TFTP comes from Trivial File Transfer Protocol and it is the protocol used by Serva to transfer files over the network. This protocol needs a bit of configuration as well.
First, check the box near TFTP Server. Then, you need to specify the so called "root" directory. This is the directory where you plan to store the Windows installation files. This folder can be the same folder where you extracted Serva or a new one. Keep in mind that you should use short paths and avoid using spaces and special characters (*, &, ", etc) in the directory name or its path.

To help eliminate problems in some networking environments, you might want to also check the box near "Bind TFTP to this address" and leave the default IP address unchanged.

Press OK to save your settings. Then close Serva and start it again (as administrator). During the restart, it will create a special folder structure in the root folder you specified.

Amongst those folders, you must find one named WIA_WDS and another named WIA_RIS. If they are not found inside the root folder you specified, something went wrong with Serva’s configuration. If all is well, go ahead and read the next section in this article.

Step 2 - Copy the Windows Installation Files

Go to the root folder you specified. Here, you need to copy the Windows installation files, as they are, without any modifications from your side.
If you want to install older versions of Windows like Windows XP or Windows 2000, you need to copy those files in the WIA_RIS folder. Since these operating systems are very old and we don’t recommend using them, we won’t provide specific instructions for them.
If you plan to install Windows Vista, Windows 7 or Windows 8, then open the WIA_WDS folder. There, create a new folder named according to the Windows version you want to copy. Use simple folder names, with no spaces or special characters. For example, I used Windows_7.

Create separate folders, with different names for all the Windows versions you plan to install over the network, using Serva.
Inside that folder, copy and paste all the installation files for the Windows version you want to install over the network. Simply go to the root of the installation disc, and copy its entire file and folder structure.

Step 3 - Start Serva

Start Serva again, as administrator and wait for it to detect the installation files you added. It will create its special folder structure, required to distribute the installation files over the network.
Then, close Serva and go to the next step.

Step 4 - Copy the Network Card Driver(s)

Next, you need to copy the network card drivers for the computer(s) on which you want to install Windows.
Go the folder where you copied the installation files. In my case it was "D:\serva" (both the root and Serva installation folder), followed by "WIA_WDS\Windows_7".

There, go to "$OEM$\$1\Drivers\NIC". If you can’t find these folders, create them yourself.
Then, extract the network card drivers and place them inside. If your drivers come as a setup.exe or as a self-extractable archive, extract it first. Make sure the driver’s ".inf" and ".cat" files are stored directly in the NIC folder.

Step 5 - Share WIA_WDS Folder with the Network

In order for Serva to distribute the Windows installation files over the network, they need to be shared with the network, so that other computers can access them. Unfortunately, Serva requires you to share the WIA_WDS folder (and not its subfolders or other folders) using a very specific share name: WIA_WDS_SHARE. Using any other share name means that the installation procedure is likely to fail.

To share this folder with the name we mentioned, you first need to enable advanced sharing in Windows and then share it. Here’s how advanced sharing works in Windows: Share Libraries or Folders Using Advanced Sharing.
You must give the user Everyone read-only permissions. You can also share this folder with specific user accounts, whose login details you will use later on, during the network installation process. Again, read-only permissions are enough.

Step 6 - Start Serva

Start Serva again, using administrator permissions. It will detect the network drivers you added and make a few changes, so that the drivers are distributed correctly when you launch the installation process on other computers. You can now leave it open and waiting for network connections.
Next, go to the computer(s) where you want to install Windows.

Step 7 - On the Target PC - Enable Lan Booting & Boot from the Network

Go to the computer where you want to install Windows and enter its BIOS. Make sure networking booting is enabled. This setting can be named "Boot from the network" or "Boot from PXE".
Then, start the computer and press the required key to bring up the Boot Menu. On most computers, you need to press F12 or F8, depending on the BIOS version. Select Network or PXE (again, this depends on your computer’s BIOS), to boot from the network, using Serva.

If all is well, you should see a screen similar to the one below, where the computer’s MAC is displayed and the network card requests an IP address via DHCP.

When the computer is connected to the network, Serva loads and displays a screen with the operating systems available for installation. Pick the one you want and press ENTER.

The installation files are loaded and a small window named ServaPENet is shown. At this step, Serva installs the network driver you added earlier, loads network resources and connects to the Windows installation folder. Depending on how you shared the WIA_WDS folder, it will ask you to provide a username and password to access it. Type the details of the user account you shared it with and connect.
If all went well, the Windows installation process is now started.

Step 8 - Install Windows Over the Network

Next, continue with the Windows installation, as usual. If you plan to install Windows 8, check this installation guide: How to Install Windows 8 RTM on Your Computer.
If you plan to instal Windows 7, check this article: How to Install Windows 7 - Complete Round of Installation Guides.

Troubleshooting Problems with Serva

If you don’t pay attention to all the steps in this procedure, some things are likely to fail. Here are some things we learned while experimenting with this tool:

• If ServaPENet returns this error: "Failed No NIC/Driver, Aborting!", it means that you forgot to copy the network card drivers as instructed at Step 4. If you copied them and you still get the error, double check that you have the correct driver for the network card of the computer where you want to install Windows, for the Windows version you are about to install. Also, double check that you copied it to the correct folder. Then, restart Serva to make sure it detects the driver before the network installation procedure starts.
• If, on the target computer, Serva is not able to load at all over the network, consider enabling the "Bind DHCP to this address" and "Bind TFTP to this address" settings in the DHCP and TFTP tabs.
• If you connected two computers directly, with a crossover cable, you need to set Serva as DHCP server, in order for everything to work. This means setting the 1st address available in the IP pool, the pool size, and the subnet mask to be used when Serva assigns IP addresses.
• One last piece of advice is to check the Serva logs. The messages shown there can help you troubleshoot different problems.

Another good tip is to restart Serva every time you change any of its settings and every time you add something to its root folder.
Since we are not the developers of this software, we cannot provide support for it and help you with all the issues you might encounter. If our guide does not help you, then double check Serva’s documentation - Serva PXE/BINL - AN01: Windows Install and advanced configuration guide - Advanced Topics on TFTP.

Conclusion

As you can see from this guide, setting things up with Serva requires quite a bit of time and attention. However, it is the simplest way of installing any modern version of Windows over the network. It works great both for home networks and small or medium sized business networks.
If you know other useful tools for installing Windows over the network, don’t hesitate to share them using the comments form below.

How to Manually Repair Windows 7 Boot Loader Problems

If you’re having boot problems on your Windows PC, it’s often helpful to repair the MBR (Master Boot Record) to restore the Windows 7 boot loader—and you can do it easily from the Windows installation disc.
This is generally most useful if you’ve broken something and there’s a boot loader error, or if you have made the mistake of installing an older version of Windows on the same PC that already has Windows 7 which wipes out the boot loader.
Note: If your PC starts booting into Windows but fails, you should probably try using Safe Mode instead.

Boot From the Windows Install Disc

The first thing you’ll need to do is boot off the install disc, and then click through until you see the “Repair your computer” link in the lower left-hand corner.

[surveycode]
You’ll need to choose the correct installation of Windows and then click the Next button.

And then you’ll get to the System Recovery Options screen, where you can get to the Command Prompt.

Repairing the Master Boot Record

If you want to restore the master boot record, you can simply type in the following command:

bootrec /fixmbr

You can also write a new boot sector onto the system partition with this command (which is often more useful):

bootrec /fixboot

And of course, if you just use bootrec /? you’ll be able to see all the options.

This is the same way that we fixed the “BOOTMGR is missing” error when trying to boot up Windows 7 or Vista.

Replacing the Windows XP Bootloader with Windows 7

If you’ve managed to install XP on the same PC that you already had Windows 7 on, you’ll noticed that you can’t boot into Windows 7 anymore. You can use this command to fix that and restore the Windows 7 bootloader:

bootsect /nt60 all

Depending on the partition that you’ve installed, you might need to substitute the drive letter instead of “all”.

Note: if you want to restore Windows XP back to the menu, you can open up a command prompt in Windows 7 and run this command:

bcdedit /create {ntldr} -d “Windows XP”

Using the Automated Startup Repair

Of course, all this command-line stuff is probably not necessary in most cases. You can usually just use the Startup Repair option from the Recovery menu…

It’ll check for problems and probably fix them. If not, then you can always use the command prompt.

Have you ever needed to restore your boot loader to get Windows working again?

How to Create a Password Protected Folder without any Extra Software

There are a lot of methods that you can use to create a password protected folder, most of which require the use of some third party software. Using this neat method you can hide your folders with a quick batch script.
It’s important to note that this will not actually conceal your data from somebody that knows what they are doing.
Note: if you are a beginner you should be careful with this script.

Create Your Password Protected Folder

Before you get started you need to create a folder that will house your password protected folder, this is just an ordinary folder and can be located anywhere and named anything.

Navigate into your newly created folder and create a new Text Document. This can easily be done from the context menu.

Open the document, now paste the following code into the contents of the document:

cls 
@ECHO OFF 
title Folder Private 
if EXIST "HTG Locker" goto UNLOCK 
if NOT EXIST Private goto MDLOCKER 
:CONFIRM 
echo Are you sure you want to lock the folder(Y/N) 
set/p "cho=>" 
if %cho%==Y goto LOCK 
if %cho%==y goto LOCK 
if %cho%==n goto END 
if %cho%==N goto END 
echo Invalid choice. 
goto CONFIRM 
:LOCK 
ren Private "HTG Locker" 
attrib +h +s "HTG Locker" 
echo Folder locked 
goto End 
:UNLOCK 
echo Enter password to unlock folder 
set/p "pass=>" 
if NOT %pass%== PASSWORD_GOES_HERE goto FAIL 
attrib -h -s "HTG Locker" 
ren "HTG Locker" Private 
echo Folder Unlocked successfully 
goto End 
:FAIL 
echo Invalid password 
goto end 
:MDLOCKER 
md Private 
echo Private created successfully 
goto End 
:End

Change the PASSWORD_GOES_HERE text to the password you want to set. Now go ahead and save the file as locker.bat.

Once the file is saved as a batch file you can delete the original text file.

Now run your batch file by double clicking on it–the first time you run it, it will create a folder called Private. This is where you can store all your secret things. When you have finished adding all your stuff to the Private folder, run locker.bat again.

This time you will be asked if you sure that you want to lock the folder, press the “Y” key and hit enter to lock your folder.

You will see that your Private folder quickly disappears.

If you run the script yet again, you will prompted for a password.

If you enter the same password as you set in the script the Private folder will reappear if you enter the incorrect password the script will just Terminate.

Warning

Most people don’t know how to show system files, but anybody who has some experience will probably be able to quickly figure it out in the Folder Options.

Also, any ordinary user who unchecks the box will most probably be scared off by the warning message that appears.

The second way someone could comprise the folder is to open the batch file and read your password. It’s definitely not a really secure way to hide your files, but it is fun.
Attribution note: We found this script on dozens of different web sites going back many years. We have no idea who first created the script, so we’ve omitted any sort of attribution link. If you do have proof that you first created the script, contact us and we’ll adjust the article accordingly.

How to Add Google Documents to the Windows Explorer “New” Menu

We’ve already shown you how to create shortcuts to create new Google Docs easily, but what if you want total Windows integration? Here’s how to add them to the Windows Explorer “New” menu for easier access.
This should work for all versions of Windows, and you can modify it to work with Google Apps for your Domain as well. Keep reading for the full instructions.

Import the Registry Hack

The first step is to download and extract the package we’ve provided at the end of the article. Once you’ve done that, you’ll want to import the registry hack file, since there are just way too many keys to manually create them all.
Just double-click on the AddGoogleDocsToNewMenu.reg file, provided in the zip file at the bottom of the article, and you’ll see a message saying it was successful.

You aren’t done yet! Keep reading…

Copy the Icons and Runner Application

I’ve created a set of icons and a tiny runner application, which does nothing more than launch whatever your default browser is. In fact, it’s created in AutoHotkey and consists of nothing more than the following line:

Run, %1%

You’ll need to copy the 4 icons and the googledocsrunner.exe and put them all into your Windows directory. There should be 5 total files, and it’ll look something like this once you copy them in:

If you’re using regular Google Apps, you should be done. You may need to use the Refresh option from the context menu, like this:

Go ahead, test it out! Open up your New menu, and select one of them.

If the icons aren’t showing up yet, you might have to log out and back in, or restart Explorer.exe.

Editing the Keys for Google Apps for Domains

If you’re using Google Apps for your Domain, unfortunately you’re going to need to modify a few keys. You can do this in the registry, or you can modify the .reg file that we imported earlier. If you choose to go the registry route, here’s what you need to do.
Open up regedit.exe through the Start Menu search or run box, and then browse down to one of the following keys, one for each type of document:

• HKEY_CLASSES_ROOT\.googledoc\ShellNew
• HKEY_CLASSES_ROOT\.googledrawing\ShellNew
• HKEY_CLASSES_ROOT\.googlepresentation\ShellNew
• HKEY_CLASSES_ROOT\.googlespreadsheet\ShellNew

For each one, you’ll want to open up the “command” key on the right-hand side, which points to the runner application, and the only parameter is the URL.

You’ll need to modify each of the URLs so that it matches your domain, in the format below:

• https://docs.google.com/a/YOURDOMAIN.com/?action=newdoc
• https://spreadsheets.google.com/a/YOURDOMAIN.com/ccc?new
• https://docs.google.com/a/YOURDOMAIN.com/?action=new_presentation
• https://docs.google.com/a/YOURDOMAIN.com/drawings/create?hl=en

Once you’ve done that, you should be done, and the shortcuts should work now.

Removing the Registry Hack

To remove the registry hack, use the provided UninstallGoogleNewMenu.reg file, and then delete the 5 files you copied into the Windows directory.

The 8 best Windows 8 devices

Windows 8's unique blend of desktop compatibility and the finger-friendly modern interface means it fits right in on a wide swathe of devices. Here's the cream of the touchscreen crop, no matter whether you're looking for an all-in-one, laptop, tablet, or a multi-purpose hybrid that falls somewhere in between.

Microsoft Surface Pro 2 (256GB storage, 8GB RAM)
Lenovo ThinkPad Helix prices from $1,911.00
Asus Transformer Book T100 (64GB)
Lenovo IdeaPad Yoga 11S
Dell XPS 12 Ultrabook Convertible
Acer Aspire V7 (Model 482PG-9884)
Sony VAIO Pro 13 $1,098.00
Lenovo IdeaPad U430 Touch

  Sony VAIO Pro 13

$1,098.00
Lenovo IdeaPad U430 Touch