Organizations that have multiple shifts of employees or have remote locations will find this installation method quite helpful. This Daily Drill Down will provide you with an overview of the Windows Professional unattended installation, preparing you to perform such an installation on your network.
Other Windows products will be specified, such as Windows Advanced Server. Preparing for an unattended installation As with any task, you must prepare to install Windows by ensuring that your computer hardware meets the minimum hardware requirements that have been set forth by Microsoft. You must also ensure that your hardware is compatible with Windows by verifying that the hardware components of your system are listed on the Hardware Compatibility List, or HCL.
Partitioning the hard drive is really dependent on your needs. You can create a small partition to prevent your customers from installing their own software, or you can make the entire drive one single partition.
Using this type of structure, you can easily add new device drivers without making major changes to the installation routine. This type of setup is ideal if you have multiple hardware configurations. The creation of the distribution folder is much easier when you use the Setup Manager tool.
Setup Manager is in the Deploy. To unpack the Setup Manager files, right-click on setupmgr and select extract. You will be asked to select the folder to extract the program to. You must also extract setupmgx. After extracting the files, launch Setup Manager and click Next at the initial welcome screen. As shown in Figure A , you can choose to create a new answer file or modify an existing one.
It looks like this:. Only glitch is I have to manually reboot the machine after all apps are installed. Have found a reboot.
Open to suggestions The Old Dude. I came across a procedure from ms found in the deploy. Basically it made light of using your standard win2k setup disk to boot from and then using a floppy to provide the winnt.
However I've not had much luck with this method. I keep getting the error "Line 1 invalid in INF file". The structure is the same as any other answer file MS uses in their other examples. I actually tried using the sample files they provided and the wizard as well only to get the same error.
The way I understand it. The pc boots off the win2k cd but in the first few seconds the windows installer checks the a: drive for the winnt. Mine loads but always yeilds the error. FYI My Win2k disk has been slip streamed with sp4. Is there any chance this has had any effect on the installer? You need to be a member in order to leave a comment. Sign up for a new account in our community.
It's easy! Already have an account? Sign in here. MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Unattended Setup can also be useful in situations where you need to quickly duplicate a Windows installation such as on a machine you use for beta testing.
The Web site also offers two options for downloading the service pack. This option is aimed mainly at end users who want a targeted installation and need to reduce download time. The second option is Network Download; this option downloads the service pack compressed archive, which contains all components. You can then use the archive to perform network installations on multiple computers, burn your own CDs, or simply store the file for later reinstallation if it becomes necessary. The Sp1network.
What does it fix? Service Pack 1 addresses a broad range of bugs and quirks in Windows Some of these were addressed by updates available from the Microsoft Windows Update Web site , but the service pack addresses a much larger set of issues. For a complete list of issues addressed and links to Microsoft Knowledge Base articles on each fix, check out this article on the Microsoft site.
Interface problems are addressed along with more serious problems, such as memory leaks, stop messages, hung systems, security, and corrupted data. Some performance problems with mixed-mode environments are fixed, as well. Some of the fixes address memory leaks, problems with Dynamic DNS, potential Global Catalog inconsistency, access violations, and several other areas related to the AD. Some of these fixes improve performance for indexing and searches, clear up programming problems with ASP, and fix IIS problems that can cause high CPU utilization, access violations, and potential security problems.
For example, the service pack addresses a problem with SMTP generating a mail loop when you move a mailbox from one server to another. Other: 18 miscellaneous issues related to interface problems, character sets and regional settings, logging, Terminal Services, and scripting. Issues addressed include problems displaying and sorting various character sets, security problems such as active scripting being enabled for restricted zones, date and time zone problems, and others.
Printing: Nine printing problems, including SNMP, access violations, printer installation, and miscellaneous errors. Some of the issues fixed include access violations in the print spooler, problems with Adobe FrameMaker, and installation errors where the NetBIOS name is different from the Windows domain name. Security: 23 security issues that include problems with encryption, security through Web access, memory leaks, authentication, and performance.
Some of the fixes address potential security problems with Internet Explorer, password vulnerability, lack of protection for private keys with the High Encryption Pack, memory leaks, problems connecting to SSL sites in certain situations, Kerberos password expiration and realm propagation, and others.
0コメント