[Install]

The [Install] section sets parameters for copying additional files as part of Windows 95 installation. The format for this section is identical to the format for the [Install] section in general INF files, as defined in Appendix C, "Windows 95 INF Files."

The following sections provide these examples for using the [Install] section for custom installations:

[Install] Example: Copying Custom Files

This section describes MSBATCH.INF entries for copying custom files while installing Windows 95. In the following example, custom files are copied for a bitmap file containing a corporate logo plus a shortcut to be placed in the Network Neighborhood. These custom files must be created by the administrator and placed with the Windows 95 source files on the network.


[install]
CopyFiles=newfiles.Copy

[NEWFILES.Copy]   
my_corp.bmp      ; bitmap file
my_link.lnk      ; file that contains the shortcut

[DestinationDirs]
newfiles.copy=25   ; shared Windows directory

The statement in [DestinationDirs] specifies where files are to be copied. Common values include the following for shared installations:

Notice that the most flexible means of providing custom links for multiple users is to use system policies. For information about using system policies to create a custom Network Neighborhood or a custom desktop, see Chapter 15, "User Profiles and System Policies."

[Install] Example: Enabling User Profiles and Remote Administration

If you plan to take advantage of user profiles and to allow administration of remote computers, you can enable these capabilities using setup scripts. The following entries are required in MSBATCH.INF to enable these features.


[Install]
AddReg=User.Profiles,Remote.Admin

[User.Profiles]
HKLM,"Network\Logon","UserProfiles",1,1

[Remote.Admin]
HKLM,"Security\Access\Admin\Remote",%Server_Domain_Username%,1,ff,00

[Network]
Security=domain_or_server   ;enables user-level security
PassThroughAgent=provider_name
services=remotereg   ;installs the Microsoft Remote Registry agent

[strings]
; specifies the server containing the group or individual account 
; to be allowed remote administration capabilities 
Server_Domain_Username = "server_or_domain\account"

To define the custom values required for enabling remote administration

  1. To enable user-level security, set the appropriate values in the [Network] section for Security= and PassThroughAgent=.

    For example, on a NetWare network, if the security provider is a server named NWSVR1:

  2. In the [Strings] key, define the value for %server_domain_username% to specify the location for the list of user accounts, plus the names of accounts for users who will be allowed remote administration capabilities for this particular computer.

    For example, for a NetWare network, the following specifies the server containing the group or individual account, plus the account name to be given remote administration capabilities:

Important You must also make sure that the related files supporting Microsoft Remote Registry services are installed with the Windows 95 source files. To do this, use INF Installer, as described in Chapter 5, "Custom, Automated, and Push Installations."

When you enable remote administration in this way, Setup automatically adds the appropriate Administrators account (including Supervisor and Domain Administrators under Windows NT) to the list of persons or groups allowed to administer the computer remotely, and sets the permissions required for remote administration.

Enabling user profiles in a setup script is the equivalent of selecting the items in the Passwords option in Control Panel named Users Can Customize Their Preferences And Desktop Settings and Include Desktop Icons And Network Neighborhood Settings.

To enable group policies

For information about user profiles and group policies, see Chapter 15, "User Profiles and System Policies." For information about remote administration of a computer's Registry, see Chapter 16, "Remote Administration."

[Install] Example: Replacing Configuration Entries

This section presents some sample entries for replacing entries in configuration files as part of Windows 95 Setup.

Depending on the common network configuration at your site, you may determine that you need to remove a line from one or more configuration files as a global procedure before starting Windows 95 Setup. For example, you may want to use a protected-mode protocol such as Microsoft TCP/IP instead of the real-mode version of TCP/IP currently being using on the target computers. The following kinds of entries can be used to make these changes during the installation process.

Note If you want to remove TSRs when installing Windows 95 on a NetWare network, you should modify the NETDET.INI file rather than making modifications using MSBATCH.INF. For information, see Chapter 9, "Windows 95 on NetWare Networks."


[Install]
UpdateInis=update_prot.Ini   
UpdateCfgSys=Update_config.sys   
UpdateAutoBat=Update_autoexec.bat

[Update_prot.Ini]
system.ini,386enh,"device=mytcp.386"

[Update_config.sys]

[Update_autoexec.bat]