วันพฤหัสบดีที่ 15 ธันวาคม พ.ศ. 2554

Complete guide to the Windows network

Do you want to reinstall Windows on the netbook lacks an optical reader, or you need to prepare the operating system on a wide range of vehicles? In these scenarios, the network installation is the ideal solution: we propose the step by step guide, including a semi-automatic scripts to simplify the preparation of the necessary files, and all indications to operate even in the absence of Windows Server.

Complete guide to the Windows network

Until recently, the ability to install the operating system via network was one interesting feature only for the larger corporate network administrators: prepare a PC using a shared folder on a server it is a big step simplifies deployment (avoids having to use it to engineer the optical media to install on each workstation), and the maintenance of the installation files themselves, which can be upgraded or changed in a centralized manner.

But today the situation has changed dramatically: with the advent of netbooks, often physically without a drive for CD / DVD, proceed installing Windows network can be an attractive option for geeks, who can thus sparing the purchase of an external player.

Are you sufficiently prepared?

I state that the procedure is not straightforward to implement. Although the hardest part has been significantly streamlined thanks to a semi-automatic script that will be presented later, there are still some difficulties inherent in this transaction.

Necessity of exposition, I'll assume that you know the basics of a local network TCP / IP and its related technologies, such as sharing folders in LAN and assigning addresses via DHCP.

Anyone of these notions on an empty stomach, can find more information about the article "Setting up a computer network (LAN)."

Client and server

We will use the client-server terminology: in particular, we call the "client" does not have a PC operating system on which you wish to install Windows, but the "server" is the machine that delivers the installation files.

You will also need a PC on which to prepare some essential files, which are then distributed from the server. It is essential that the server PC and used to prepare the necessary files are the same: it is possible to prepare the files necessary to boot on a certain system, then move on the network server and run them from this second computer.

To avoid burdening further discussion, however, I will proceed assuming that the two machines in one match, which we call generically "server".

What you need

No special technology required. The requirement is more squeeze on the availability of a machine equipped with at least Windows Vista on the PC on which you prepare files.

Other pre-REQUIREMENTS HAVE BEEN:

Clients must support booting over the network any computer within the last 5-6 years should still have that functionality

You must have the appropriate LAN connections: either a cross cable to connect directly affected machines, a switch a hub, or (as probably most common in homes), an ADSL router with Ethernet ports built-in connection the client will use the wired network: in fact, to date, you still can not boot via a wireless network.

We're going to also use the following tools:

Windows Automated Installation Kit (WAIK), to be installed on the server: The setup file is downloaded from the card attached to this article by MegaLab.it PXEBuilder Automatic, a script that will automatically prepare the files offered by Tftpd32 WAIK, which we will always install on the server: it is also annexed to Article

The phases of deployment

The steps I describe will follow the following steps:

Create files needed to boot via network boot Provision of the appropriate service on the server of the client network connection and start the setup on the client

Manual IP and no DHCP

First, make sure that the network configuration server is set manually: IP 192.168.0.4 and subnet 255.255.255.0 , to be included in the dialog box the TCP / IP

Sinceratevi so that no DHCP server is running: if you have clients and servers connected through a hub, a switch or a cross cable, you should be quiet. But if you are using a home router, you must act on its configuration.

As usual, the signs vary from model to model, but will probably have to search for a similarly named option Enable DHCP server and disable it

See Pictures and Read more : Complete guide to the Windows network

ไม่มีความคิดเห็น:

แสดงความคิดเห็น