Need step by step proc. for automated SetUp


did any of you figure out the Win 95 NETSETUP and MSBATCH. I tried it, couldn't find NETSETUP and an .INF behind Setup was ignored. I wan't to run Setup from DOS-with LAN connection- without any user-prompted questions, all has to be in teh INF.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Selious: Your question is a little over simplified. Do you want to do this from a server station or another workstation with admin rights? Are the setups your doing involve installing on identical machines or do they vary in components. Are you working on a Windows NT Lan, or is it Novell, Unix or something else? These are all variables that have to be considered when doing an install to a machine without user intervention. NT is the easiest to work with while Unix is the most difficult, with Novell in the middle somewhere. Obviously, if the machines vary in component makeup, this will make life more difficult as you will have to customize an inf for each machine separately. If the machines are identical, then you could simplify things by using a push install.
Provide this information and I think I can point you in the right direction!
Hi Selious,
I've tried myself to do an installation via netsetup.
The location of the netsetup is :
X:\admin\nettools\netsetup.exe (win95 cdrom).

I had problems with installing the machine directory, so
i would be glad if you, after trying netsetup, give me
some information about your situation
Bouncer, your proposed answer is a question. Before posting answers how about you wait with the rest of us here and develop the question with the customer!
seliousAuthor Commented:
Dear Dew_Associates,

thanks for the fast reply. Was it Ok to reject, cause it ain't done yet.... Anyway, here some specifications:

I use PCDOS + DOSLAN requester for DOS (Net start, etc.) for the client PC's, wich are always IBM.

I use TokenRing 10 MB, with switches (wich don't ripple, wich isn't desired, but for an indication)

I can install from Windows NT server 4 machines, or from older OS/2 Lan Server.

I need custom installation, with hardware checking (different types), ignored network-adapters, 1024*768-256, pre-partitionised. I also need to install MS-Office 95, all options selected, and some shortcuts. The rest can be added otherwise (I hope).

I already use cloning (with JAZ), but when I go to another project, they won't have images for new IBMs...

1) Can't I do hardware-check, it's all in the CABs ???

2) The user logged in doing the installation are special Setup accounts. They can have any rights needed to the setup-server (got a special NT server for Setup-files).

3) I favore the copying of the CAB files (windows CD-Rom) to the local harddrive, for installation of network-protocols, etc. This might be used as Setup-dir, so that the computer won't ask when installing a printer or something..

Greetings and thanks so far... if you make it work (mail me a desired INF an procedure) I'll grant you the points AND I'll burn a CD-Rom with a nice game (like Carmageddon....), if you like. Though when playing alot, please buy it original, I don't like piracy (too much...)..
Selious --> or
Selious: The type of installs you want to do is not nearly as easy as writing an inf file. As an example, here are some published notes on push installs. Tell me if this fits your scenario or how yours differs.
A push installation uses Windows 95 Setup with a setup script, plus login scripts and user accounts on a NetWare or Windows NT network, to create an automated, mandatory installation scheme for installing Windows 95 on multiple computers. This allows you to install Windows 95 remotely, without actually going to the computer being upgraded.
You will probably want to create an automated push installation scheme if you are responsible for installing Windows 95 on more than 50 computers.
After you use Server-based Setup to set up the source files on one or more servers and create setup scripts, you can perform push installations in these ways:
·      Use a login script that includes a statement to run Setup with a setup script, automatically installing Windows 95 when each user logs on. Details are provided in the following sections.
·      Insert an object in an electronic mail message that will start Windows 95 Setup with a setup script when the user clicks the object.
·      Use Microsoft Systems Management Server to run Windows 95 Setup with a setup script as a mandatory job, as described in Appendix E, “Microsoft Systems Management Server.”
·      Use network management software from other vendors to install Windows 95 based on the setup scripts you create. Refer to the documentation for your network management software for information about performing remote installation of software.
Push installation example for migration of shared Windows 3.x.
Because Windows 95 installation and management methods differ significantly from Windows 3.x, it might be helpful to look at an example of how one type of corporate installation can make the move to Windows 95. The following example focuses on migrating shared installations to Windows 95.
In the corporation in this example, Windows 3.x was installed in shared directories on the network (using setup /a). Workstations each contain a hard disk, where the swap file, TEMP directory, and hardware-specific SYSTEM.INI file are stored. Windows 3.x components were installed in each user’s home directory. All workstations run NetWare real-mode networking with ODI drivers. When users log on to the network, the login script runs WINSTART.BAT, which copies the workstation’s SYSTEM.INI to the user’s home directory and starts Windows. All applications are also stored on and run from servers.
To migrate to Windows 95 using push installations that maintain similar functionality for users on shared installations, the administrator does the following:
 1.      Install Windows 95 source files and create machine directories for each computer, as described in Chapter 4, “Server-Based Setup for Windows 95.” This step includes using INF Installer to prepare any supporting software that uses Windows 95 INF files, and manually copying any additional networking or applications software to the shared Windows 95 directory on the network.
 2.      Create the setup script that specifies any custom settings, as described in Appendix D, “MSBATCH.INF Parameters.” This should include installing all protected-mode networking components, so that both the administrator and user can take advantage of Windows 95 protected-mode networking features.
 3.      Create system policies, including setting policies that enable user profiles.
      Alternately, you can enable user profiles using setup script statements, as defined in Appendix D, “MSBATCH.INF Parameters.” This is the only method for enabling group policies.
 4.      At each client computer, run a login script with statements to do the following:
·      Copy the contents of the user’s home directory to C:\WINDOWS.
      This should include copying the Windows 3.x .GRP, .INI, and REG.DAT files that define the user’s personal preferences and working environment. In this case, make sure that the Windows 3.x REG.DAT file includes registration settings for all the shared applications that users run at your site.
      Note   This process is related to the particular configuration used in the example; this is not a required process for creating shared installations or using push installation methods to install Windows 95.
·      Run Windows 95 Setup with a custom setup script.
      You can set installdir=c:\windows to define the machine directory in the setup script.
In this example, Windows 95 Setup installs the shared Windows 95 files on the local hard disk and in the machine directory for the client computer. The settings in the Windows 3.x .GRP, .INI. and REG.DAT files are migrated automatically to the Registry. Notice that in this case, where user profiles are enabled, the current version of USER.DAT file is also stored automatically in the user’s home directory when the user logs off. This copy of USER.DAT is the user profile that is then copied to the current machine directory wherever the user logs on.
To install Windows 95 on the local hard disk of client computers, the steps for the administrator are similar to those in the preceding example. However, no machine directories are created for the computers. The following section discusses specific issues related to login scripts for local installations of Windows 95.
Best regards,

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.