Large software network installation, very suitable for schools or units, put software discs or ISO downloaded from the Internet, on the Samba or WIN file server, each client can install directly through the network, avoid floppy disk installation The wear of the community is not afraid to read the disc due to the age of CD drive.
The situation here is Linux Samba, with MS on the server. Net2003's ISO, plus MSDN a total of seven plates, if it is engraved into the disc to get the client, you need to consider more questions:
1, CD cost
2, whether the client's optical drive is aging, whether the disc will be worn
3, the speed of the disc installation
So use the Samba shared directory, install it through the network
Simple mount -o loop hangs a few ISOs start installation, the problem has appeared, the midway installer will not find the file, because this is a reminder of the disc, but. The NET installer is not like other installers, allowing you to browse and re-determine the installation source, it recognizes you installation. The installation directory used when NET, if there is no way to find the required program, can only exit installation. Installation, you can re-Mount second ISO to the installation directory by re-mount on the server, but that is limited to the server administrator, other users can only end the installation.
I find another way, put a few ISO's files in the same directory, because comparison, the same name file, all the same files as the content, allowed to be overwritten:
MKDIR CD1
MKDIR CD2
.
.
.
MKDIR MS.NET
Mount -o loop Source1.iso CD1
Mount -o loop source2.iso cd2
CP CD1 / * MS.NET
CP CD2 / * MS.NET -RF
Re-install it again, no removal prompt, but when you put it in half, there was "20 ???" what is wrong, it is not too clear, the installation is forcibly stop, and gives an error log, But that thing didn't understand what to say.
No way, turn it back. Net installation instructions are mentioned. NET is allowed to allow network installation and skip the changing prompts or even serial numbers input:
Create a network image
In addition to running the Visual Studio .NET 2003 installer from the CD or DVD, you can share this installer from the web. The following procedure explains how to prepare to install Visual Studio .NET 2003 from the network.
The example process of the installation file in the shared CD creates a folder (for example, VS2003) on the server. Create three subfolders in the top folder and named Pre, VS, and MSDN, respectively. For example, VS2003 / Prevs2003 / VSVS2003 / MSDN copies the contents of the CD necessary to Visual Studio .NET 2003 system to a subfolder named Pre. Copy the contents of all CDs marked with Visual Studio .NET 2003 to the subfolders named VS folders. If prompted, please override an existing file. Copy the contents of all CDs marked with MSDN Library for Visual Studio .NET 2003 to a subfolder named MSDN. If prompted, please override an existing file. Use a text editor (such as "Notepad" to open the file setup.ini in the VS subfolder. In the [Baseline] section, the rows starting with "DIR =" will be changed as follows:
[Baseline]
DIR = .. / pre
Filename = setup.exe
In the [Documentation] section, the rows starting with "DIR =" will be changed to "DIR = .. / MSDN". E.g:
[Documentation]
DIR = .. / MSDN
Save the changes made and turn off the file. Note that this step prevents the case where the CD is required during the installation process, and the Visual Studio .NET 2003 system must notify the installer for the correct path of the MSDN Library CD. Open the Setup folder in the VS subfolder. Use the text editor (such as "Notepad" to open setup.sdb and add the following line to the end of the file:
[Product Key]
Xxxxxxxxxxxxxxxxxxxxxxxx
Note xxxxxxxxxxxxxxxxxxxxxxxx is 25-bit product key, you can't bring a short line when entering, you can find the product key on the CD package. Save the changes made and turn off the file. Note Complete this step to fill in the user's product key. Share the VS2003 folder on the network and set the appropriate security settings. The path to the Visual Studio .NET 2003 installer on the web is as follows: //[servername]/vs2003/vs/setup.exe. Pay attention to the installation, if any path and file names exceed 260 characters, the installation will fail. The maximum length of the path in Visual Studio is 221 characters; therefore, the file should be copied to the path with less than 70 characters. If the created network share is to be a network image, the character of the UNC path in the root installation location should be less than 39 characters. Note If the space in the folder name in this path is embedded, if "// [ServerName] / VS 2003 / MSDN /" or "// [ServerName] / VS2003 / Visual Studio /" may fail. Note that Visual SourceSafe and Visio are not part of the Visual Studio .Net 2003 installer, but you can still copy the contents of the Visual SourceSafe and Visio CDs to other folders on the server, so you can easily install these products separately in your network. .
