Setup Script Parameters

This section summarizes the parameters that can be used in setup scripts.

Setup-related parameters

Network-related parameters

The setup script parameters are not case-sensitive. They are also not required; if they do not appear in a setup script, Windows 98 Setup just uses default values.

The display of most Setup dialog boxes can be disabled in the setup script so that users cannot change any setting. If the dialog boxes are not disabled, sources of information for parameters are given the following priority:

• Information specified in the setup script
• User input
• Detection information

In this section, the descriptions for an option can contain any of six possible entries, as described in the following table. For an example of the resulting file, see "Msbatch.inf Sample File" later in this appendix.

[Setup]

The [Setup] section sets parameters for controlling the Setup process.

Change Installation Directory

This parameter allows you to change the installation directory from the default. For clean installations and upgrades from Windows 3.x, the default installation directory is C:\Windows.

Clean Installation

This parameter forces a new Windows 98 installation (on a new computer or a computer with a reformatted hard disk) instead of an upgrade from either Windows 95 or Windows 3.1x. For more information on clean installations, see "Running Setup on a New Installation" in Chapter 2, "Setting Up Windows 98."

Device Path

This parameter specifies whether Windows 98 should check a source installation path to find INF files, rather than looking only in the Windows INF directory when installing devices. If this parameter is set to 1, network administrators can later add INF files to a single source location to ensure that up-to-date drivers are installed any time a new device is installed on computers running Windows 98. However, set this value to 1 only if the installation source files are in a network directory (not floppy disks or compact disk).

Note that Devicepath=1 causes the entire INF database to be rebuilt each time a user changes a network component or changes drivers for any device.

Windows 98 Startup Disk

This parameter specifies whether to create the emergency Startup Disk during Setup (the command-line override for this is /ie). For a setup script intended for hands-free installation, you might want to specify ebd=0 so that the user is not prompted to insert or remove the floppy disk. If you need to specify ebd=1, you can also add a reboot=0 entry, so that Setup will not attempt to restart the computer while the floppy disk is in the drive.

Express

This parameter specifies whether the user can provide input during Setup. If Express=1, then Windows 98 Setup uses only the settings specified in Msbatch.inf or built-in defaults and does not ask the user to confirm or enter input. This setting disables most of the user interface for Setup.

Caution

If Express=1, you cannot add parameters to override safe detection for network adapters, SCSI controllers, or sound cards — which, in some cases, requires installing support after Setup is complete. If you need to force installation of certain hardware when Express=1, add specific entries in the [System] section.

Installation Directory

This parameter specifies the directory where Windows 98 is to be installed.

Installation Directory Warning

This parameter allows you to install Windows 98 over an existing Windows installation directory without warning you.

Install Type

This parameter specifies the type of installation for Windows 98 Setup.

Optional Components

This parameter specifies whether or not to display the Select Components dialog box during installation. You must specify InstallType=3 with this setting.

Pen Windows Warning

This parameter specifies whether to display a warning if an unknown version of Pen Windows is installed.

Reboot Prompt

This parameter specifies whether the user should be prompted before rebooting the computer.

Time Zone

This parameter specifies the time zone to set on the computer.

Uninstall

This parameter is used to specify whether Setup should create a compressed backup version of the existing Windows and MS-DOS directories to be used for automatically uninstalling Windows 98. If you specify Uninstall=5, you also must add a value for BackupDir=path that specifies the directory where Setup should place the compressed backup files.

[System]

This section sets parameters for modifying the system settings.

Tip

The correct entries for Msbatch.inf can be copied from similarly named entries in Setuplog.txt for a computer on which Windows 98 has been installed with devices identical to those that you want to install from a setup script.

The following entries are based on INF section names:

Table D.1 [System] parameters based on INF section names

The following entries use INF descriptions. The choice must be in the list of compatible devices for that class.

Table D.2 [System] parameters based on INF descriptions

Keyboard

This parameter specifies the keyboard layout.

MultiLanguage

This parameter sets the type of multilanguage support installed for Windows 98.

[NameAndOrg]

This section defines the name and organization for Windows 98 Setup, and specifies whether the user is to be shown the Name And Organization dialog box.

Name

This parameter specifies the full user name for this installation.

Organization

This parameter specifies the registered organization for this installation.

Display

This parameter specifies whether the Name And Organization dialog box appears during Windows 98 Setup.

[InstallLocationsMRU]

This section specifies the paths to add to the list of directories that the user can choose when Windows 98 Setup prompts for a path. For example, this section could appear as follows to specify local and network file locations:

[InstallLocationsMRU]
\\server\share\folder=mru1
c:\win98=mru2
\\winserver\source=mru3

To force the path for files from which to copy, use CopyFile= and related statements in an [Install] section and specify the complete path for the component files.

[OptionalComponents]

This section contains the descriptions that appear in the Optional Components dialog box in Windows 98 Setup.

To create entries for this section, type the description enclosed in quotation marks. Each description is followed by 1 (install) or 0 (do not install). The strings that specify the optional components to install are defined in INF files.

Another way to define entries for this section is to copy the [OptionalComponents] section in Setuplog.txt from a computer that already has all the optional components installed that you want defined in the setup script. For an example, the entries to install Briefcase and Net Watcher are as follows:

[OptionalComponents]
"Briefcase"=1
"Net Watcher"=1

The following tables show the strings for the optional components defined in the Windows 98 standard INF files, grouped by the following component sets:

• Accessibility
• Accessories
• Communications
• Desktop Themes
• Internet Tools
• Microsoft Outlook Express
• Multilanguage Support
• Multimedia
• Online Services
• System Tools
• Web TV for Windows

Additional strings can be defined by other application developers.

Table D.3 Optional component strings

Optional Component Dependencies

The following table lists optional component strings that are no longer valid in Windows 98. The left column lists the obsolete component; the right column the new string that replaces it.

Obsolete Component Strings

[Network]

This section specifies the parameters and options for installing networking components. The categories for these parameters include the following:

• Installation parameters
• Computer identification parameters
• Security parameters
• User interface options

Installation Parameters in [Network]

Clients

This parameter specifies the network clients to be installed. It is a list of the device IDs used in the INF files. These IDs are not limited to those in the Windows 98 INF files (Netcli.inf and Netcli3.inf). A site that has an INF file from another vendor can use any device IDs listed in it.

Note

If you are installing a network client other than those listed in the INF files provided with Windows 98, you need to obtain an updated Windows 98 INF file from your vendor. You can use INF Installer (Infinst.exe) to add network clients to your Windows 98 installation. For more information on how to use INF Installer, see "Adding Custom Drivers with INF Installer (Infinst.exe)" in Chapter 3, "Custom Installations."

If you are installing multiple clients, the first client in this list will start first whenever the computer is started.

Specify multiple networks in a comma-separated list. If the list contains two network clients, or lists multiple networks with a primary-only network (such as IBM OS/2 LAN Server), Windows 98 Setup presents an error message and displays the Network Configuration properties for changing the selection. The verification process that occurs in Setup still takes place.

The following table shows the device IDs for network clients included with the Windows 98 files (as specified in Netcli.inf and Netcli3.inf).

The following table shows other valid device IDs for third-party network clients.

Network Card Drivers

This parameter specifies the drivers to be installed for network adapters as a list of the device IDs used in the INF files. These IDs are not limited to those included in the Windows 98 INF files. A site that has an INF file from another vendor can use any device IDs listed in that file.

Note

In general, it is recommended that you rely on detection in Windows 98 Setup to install the correct driver and define the correct configuration settings.

If you are installing drivers for network adapters other than those listed in the INF files provided with Windows 98, you need to obtain an updated Windows 98 INF file from your vendor. You can use INF Installer (Infinst.exe) to add drivers for network adapters to your Windows 98 installation. For more information on how to use INF Installer, see "Adding Custom Drivers with INF Installer (Infinst.exe)" in Chapter 3, "Custom Installations."

When a network adapter is listed, the usual verification takes place. Windows 98 Setup chooses an NDIS 3.1 or later driver, if available; otherwise, it uses an NDIS 2.x driver. Do not specify a Plug and Play or PCI card with the NetCards parameter if that device is enumerated by Windows 98.

For example, the following entries would install drivers for Intel EtherExpress 16 or 16TP plus 3Com EtherLink II or IITP:

Netcards=*PNP812D,*PNP80F3

Caution

The virtual private networking (VPN) and Web TV for Windows dial-up adapters should not be specified with the Netcards parameter.

Protocols

This parameter specifies the protocols to be installed as a list of the device IDs used in the INF files. These IDs are not limited to those in the Windows 98 INF files. A site that has an INF file from another vendor can use any device IDs listed in that file.

Note

If you are installing network protocols other than those listed in the INF files provided with Windows 98, you need to obtain an updated Windows 98 INF file from your vendor. You can use INF Installer (Infinst.exe) to add network protocols to your Windows 98 installation. For more information on how to use INF Installer, see "Adding Custom Drivers with INF Installer (Infinst.exe)" in Chapter 3, "Custom Installations."

For example, the following entry installs the Microsoft TCP/IP protocol:

Protocols=mstcp

The following table shows the valid device IDs for network protocols included with the Windows 98 files (as specified in Nettrans.inf).

The following table shows examples of other valid device IDs for third-party network protocols. These are not included with the Windows 98 files.

Setup verifies these settings, so it is possible to specify only the network clients and let Windows 98 Setup choose the protocols. For example, if you specify Clients=Novell32, then Windows 98 Setup adds Novellipx32.

Default Protocol

This parameter sets the default protocol (which is assigned LANA 0), which is the specified protocol bound to the specified network adapter (if the computer has more than one network adapter). If no adapter is specified, the default is the first instance of the specified protocol. Set this value if, for example, the computer will run software that requires a protocol to be bound to LAN adapter (LANA) 0, which can only be defined by setting that protocol as the default protocol. For more information about LAN adapter numbers, see Chapter 15, "Network Adapters and Protocols."

If netbios=1, you must set defaultprotocol=nwnblink if you want to specify the IPX/SPX-compatible protocol as the default.

The following example sets the default protocol as an instance of NetBEUI bound to a particular adapter:

DefaultProtocol=netbeui,*pnp812d

Remove Binding

This parameter removes the binding between the two devices. This parameter is used to tune bindings in a setup script.

Services

This parameter specifies the network services to be installed as a list of the device IDs used in the INF files. These IDs are not limited to those in the Windows 98 INF files. A site that has an INF file from another vendor can use any device IDs listed in that file. When a service is listed in a setup script, the usual verification still takes place.

Note

If you are installing network services other than those listed in the INF files provided with Windows 98, you need to obtain an updated Windows 98 INF file from your vendor. You can use INF Installer (Infinst.exe) to add network services to your Windows 98 installation. For more information on how to use INF Installer, see "Adding Custom Drivers with INF Installer (Infinst.exe)" in Chapter 3, "Custom Installations."

The only service installed by default is VSERVER (File and Printer Sharing for Microsoft Networks) if peer sharing services were enabled for Windows for Workgroups.

The following shows the valid device IDs defined in several different INF files.

Computer Identification Parameters in [Network]

Computer Name

This parameter sets the computer’s network name.

Description

This parameter is the description for the computer (mainly used by peer servers, such as File and Printer Sharing for Microsoft Networks).

Workgroup

This parameter sets the workgroup for the computer.

Security Parameters in [Network]

User Security

This parameter specifies the security model to be used and, for user-level security, the type of pass-through agent (that is, server or domain). A client with a security provider must be installed for these values to have an effect.

Pass-Through Agent

This parameter specifies the pass-through agent for user-level security. This value is ignored for share-level security.

User Interface Options for [Network] Parameters

Display

This parameter controls whether any of the Network Configuration dialog boxes appear in Custom Setup.

Validate NetCard Resources

This parameter specifies whether to display a dialog box to resolve resource conflicts if a partial configuration is detected or if there is an IRQ conflict for a network adapter.

[netcard_ID]

The actual name for this section is the identifier for the network adapter, as defined in the related INF file. This section sets parameters for a specific network adapter, as defined in the [netcard.NDI] sections of the network device INF files provided with Windows 98.

Important

In general, it is recommended that you rely on detection in Windows 98 Setup to install the correct driver and define the correct configuration settings.

All entries for a [netcard_ID] section depend on the specific adapter. The actual parameters and settings for a specific network adapter can be found in that adapter’s INF file in the Windows INF directory.

To locate settings for a network adapter, check Net.inf for entries, such as the following:

CardBrand=brand of network adapter
INFFile=file where these settings can be found

In the related INF file for the specific network adapter, search for the adapter’s name. For example, you might find the following entry for an Intel EtherExpress 16 network adapter:

;*********************************************************************
; *PNP812D  Intel Etherexpress 16 or 16TP
;*********************************************************************

The information in the netcard.INF file is followed by the specific settings, using this format:

;netcard model name
[<adapter>.NDI]
actual settings for adapter 

For example, for the adapter in the previous example, the following entry appears in the Netee16.inf file:

[*PNP812D.ndi]
AddReg=*pnp812d.ndi.reg,EXP16.ndi.reg

Based on the AddReg= entry in this statement, you need to search for the [*pnp812d.ndi.reg] or [EXP16.ndi.reg] sections in the INF file to find the parameters required for a particular adapter. For example, for the related Intel EtherExpress adapter, the following sections appear in Netee16.inf:

[*PNP812D.ndi.reg]
.
.
.
HKR,NDI\params\Interrupt,resc,1,04,00,00,00
HKR,NDI\params\IOAddress,resc,1,02,00,00,0
HKR,NDI\params\DMAChannel,ParamDesc,,"DMA Channel"

These entries describe the parameters that can be specified for the adapter in a setup script. Furthermore, in this same part of the netcard.INF file, the statements also indicate the kinds and ranges of values that can be specified for a particular parameter. For example, in Netee16.inf, the following statements indicate that for DMAChannel= you must specify an integer in the range of 1 – 3, where the default value is 1:

HKR,NDI\params\DMAChannel,type,,int
HKR,NDI\params\DMAChannel,default,,1
HKR,NDI\params\DMAChannel,min,,1
HKR,NDI\params\DMAChannel,max,,3

The following entry in Netee16.inf indicates that for Transceiver= you can specify the values external or onboard (based on the first string that appears after the enum item):

HKR,NDI\params\Transceiver,default,,onboard
HKR,NDI\params\Transceiver,type,,enum
HKR,NDI\params\Transceiver,enum,external,,external
HKR,NDI\params\Transceiver,enum,onboard,,onboard

Based on the previous examples, the following shows an example of the [netcard] section you would add to Msbatch.inf to set parameters for an Intel EtherExpress 16 or 16TP network adapter:

[*PNP812D]
Interrupt=
IOAddress=
DMAChannel=2
Transceiver=external

Notice that you only need to set values for the parameters where you do not want to use the defaults. For a list of possible parameters for some common network adapters, see "Windows 98 Network Adapter INF Summary" later in this appendix.

[MSTCP]

This section sets parameters for Microsoft TCP/IP. For more information about TCP/IP, see Chapter 15, "Network Adapters and Protocols."

DHCP

This parameter specifies whether TCP/IP is configured to use DHCP for dynamic TCP/IP configuration.

DNS

This parameter enables DNS name resolution. You must also set DNS=1 if you plan to use LMHOSTS for name resolution.

DNS Servers

This parameter is a list of the DNS servers to use in the order to try them.

Domain

This parameter sets the DNS domain that this computer is in.

Domain Order

This parameter sets a list of DNS domains for host name resolution in the order to try them.

Gateways

This parameter lists the IP gateways (sometimes called IP routers) in the order they are to be used.

Hostname

This parameter sets the DNS hostname for this computer (usually the same value as ComputerName).

IP Address

This parameter sets the computer’s IP address if DHCP is not enabled.

LMHosts

This parameter enables or disables LMHOSTS for name resolution.

LMHOST File Path

This parameter sets the path and file name of the LMHOST file.

Primary WINS Server

This parameter sets the primary WINS name server.

Secondary WINS Server

This parameter sets the secondary WINS name server.

Additional WINS name servers can be specified using parameters WINSServer3 through WINSServer12.

Scope ID

This parameter sets the scope ID.

Subnet Mask

This parameter sets the IP subnet mask for TCP/IP if DHCP is not enabled.

WINS

This parameter enables WINS for NetBIOS computer name resolution.

[NWLink]

The parameters in this section specify settings for the IPX/SPX-compatible protocol and are valid only if protocols=nwlink is also specified in the setup script. For more information about these parameters as defined using the Network option in Control Panel, see Chapter 15, "Network Adapters and Protocols."

Frame Type

This parameter specifies the default frame type for IPX.

NetBIOS

This parameter specifies whether NetBIOS support for IPX/SPX should be installed.

[NWRedir]

This section sets parameters for Microsoft Client for NetWare Networks. For more information about these values, see Chapter 17, "Windows 98 on Third-Party Networks."

First Network Drive

This parameter specifies the first network drive to which to attach in login scripts for Client for NetWare Networks. This parameter overrides the equivalent setting in Net.cfg.

Preferred Server

This parameter specifies the NetWare preferred server. This parameter does not override the equivalent setting in Net.cfg.

Process Login Script

This parameter specifies whether login script processing is enabled when running Microsoft Client for NetWare Networks.

[NWRedir4]

This section sets parameters for Microsoft Service for NetWare Directory Services. For more information about these values, see Chapter 17, "Windows 98 on Third-Party Networks" and Chapter 18, "Logon, Browsing, and Resource Sharing."

Preferred Tree

This parameter specifies the NetWare preferred tree.

Name Context

This parameter specifies the preferred context for the user to log on to.

[NWServer]

This section sets parameters for Microsoft File and Printer Sharing for NetWare Networks. For more information about these values, see Chapter 18, "Logon, Browsing, and Resource Sharing."

Browse Master

This parameter specifies whether a computer configured with File and Printer Sharing for NetWare Networks can be elected browse master.

SAP Browsing

This parameter specifies whether a computer configured with File and Printer Sharing for NetWare Networks uses Service Advertising Protocol (SAP) browsing. Enabling SAP browsing allows a computer with File and Printer Sharing for NetWare Networks to be seen by any NetWare client, but the computer does not appear in a workgroup in Network Neighborhood.

[VRedir]

This section sets parameters for Client for Microsoft Networks. For more information about these values, see Chapter 16, "Windows 98 on Microsoft Networks."

Validated Logon

This parameter specifies whether logons are validated on a Windows NT domain. If you set this value to 1, be sure to specify a value for LogonDomain.

Logon Domain

This parameter specifies the Windows NT domain to use for logon validation. It can be set even if ValidatedLogon=0. If ValidatedLogon=1, you must set a correct value for LogonDomain to ensure that Windows 98 Setup has access to any required files on a protected network resource, and to ensure that the user can log on successfully when installation is completed.

[VServer]

This section sets parameters for File and Printer Sharing for Microsoft Networks. For more information about these values, see Chapter 18, "Logon, Browsing, and Resource Sharing."

Announce

This parameter specifies whether the computer configured with File and Printer Sharing for Microsoft Networks announces its presence to LAN Manager computers on the network. Setting this value to 1 increases network traffic but makes browsing faster.

Browse Master

This parameter specifies how the computer configured with File and Printer Sharing for Microsoft Networks behaves in a browse master election.

[Printers]

This section is used to install one or more printers during Setup by specifying a user-defined name for identifying the printer, the model name, and the printer port. Each printer to be installed has a separate entry in this section using the following syntax:

PrinterName=DriverModel,Port

where Port can be either a local printer name, such as LPT1, or a network path for a network printer, such as \\printserver1\printA.

The following restrictions apply:

• The length of the friendly name for the printer name cannot exceed 32 bytes (31 characters plus a NULL character). If the name specified in the custom setup script is too long, Setup will truncate it to fit the requirement.
• The model name must be recognized by Windows 98. You can see the list of supported printer models in the Add Printers wizard or in the printer INF files.
• No commas or quotation marks can be used in any string.

Note

If the setup script contains a [Printers] section with no entries, you will not be asked to select a printer the first time that Windows 98 runs. If the [Printers] section exists but it does not have any entries under it, you will not be prompted to select a printer. If the script does not contain a [Printers] section, Setup will ask you to install a printer.

Friendly Name

This parameter specifies the friendly name, model, and port for a printer to be installed. The printer’s friendly name is the name that appears in the Printers folder. The model name must be the exact name of a printer driver that is supported under Windows 98; otherwise, Setup skips this entire section.

The following example installs a local printer and a network printer:

[Printers]
My BJC600=Canon Bubble-Jet BJC-600,LPT1
IIIsi Next Door=HP Laserjet IIIsi,\\Server_1\PrtShr_1

[Strings]

The [Strings] section defines one or more string keys that Setup expands to the defined string and uses it for further processing. In other sections, a strings key can be used by enclosing it in percent signs (%).

The following shows three examples of strings keys:

[Strings]
KEY_RUNONCE="SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce"
KEY_INSTALLEDCOMPS="SOFTWARE\Microsoft\Active Setup\Installed Components\BatchRun"
KEY_IEXPLORERMAIN="Software\Microsoft\Internet Explorer\Main"
KEY_INTERNETSETTINGS="Software\Microsoft\Windows\CurrentVersion\Internet Settings"
QuickLaunch_Path="Applic~1\Micros~1\Intern~1\QuickL~1"
CurrentVersion="Software\Microsoft\Windows\CurrentVersion"
PrimaryRec="ProfileReconciliation"
SecondaryRec="SecondaryProfileReconciliation"

[Install]

The [Install] section sets parameters for copying additional files as part of Windows 98 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 98 INF Files."

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

• Installing custom bitmaps and shortcuts.
• Enabling user profiles and remote administration.
• Replacing configuration entries.

[Install] Example: Copying Custom Files

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

[install]
CopyFiles=newfiles.Copy

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

Note 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 8, "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, Reg,User.Box.One, User.Box.Two, Remote.Admin

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

[User.Box.One]
HKCU,"%CurrentVersion%\%PrimaryRec%\Desktop",CentralFile,,"Desktop"
HKCU,"%CurrentVersion%\%PrimaryRec%\Desktop",Default,1,01,00,00,00
HKCU,"%CurrentVersion%\%PrimaryRec%\Desktop",DefaultDir,,"%10%\Desktop"
HKCU,"%CurrentVersion%\%PrimaryRec%\Desktop",LocalFile,,"Desktop"
HKCU,"%CurrentVersion%\%PrimaryRec%\Desktop",MustBeRelative,
    1,01,00,00,00
HKCU,"%CurrentVersion%\%PrimaryRec%\Desktop",Name,,"*.lnk,*.pif"
HKCU,"%CurrentVersion%\%PrimaryRec%\Desktop",RegKey,
    ,"%CurrentVersion%\Explorer\User Shell Folders"
HKCU,"%CurrentVersion%\%PrimaryRec%\Desktop",RegValue,,"Desktop"
HKCU,"%CurrentVersion%\%PrimaryRec%\NetHood",CentralFile,,"NetHood"
HKCU,"%CurrentVersion%\%PrimaryRec%\NetHood",Default,1,01,00,00,00
HKCU,"%CurrentVersion%\%PrimaryRec%\NetHood",DefaultDir,,"%10%\NetHood"
HKCU,"%CurrentVersion%\%PrimaryRec%\NetHood",LocalFile,,"NetHood"
HKCU,"%CurrentVersion%\%PrimaryRec%\NetHood",MustBeRelative,
    1,01,00,00,00
HKCU,"%CurrentVersion%\%PrimaryRec%\NetHood",Name,,"*.lnk,*.pif"
HKCU,"%CurrentVersion%\%PrimaryRec%\NetHood",RegKey,
    ,"%CurrentVersion%\Explorer\User Shell Folders"
HKCU,"%CurrentVersion%\%PrimaryRec%\NetHood",RegValue,,"NetHood"
HKCU,"%CurrentVersion%\%PrimaryRec%\Recent",CentralFile,,"Recent"
HKCU,"%CurrentVersion%\%PrimaryRec%\Recent",Default,1,01,00,00,00
HKCU,"%CurrentVersion%\%PrimaryRec%\Recent",DefaultDir,,"%10%\Recent"
HKCU,"%CurrentVersion%\%PrimaryRec%\Recent",LocalFile,,"Recent"
HKCU,"%CurrentVersion%\%PrimaryRec%\Recent",MustBeRelative,1,01,00,00,00
HKCU,"%CurrentVersion%\%PrimaryRec%\Recent",Name,,"*.lnk,*.pif"
HKCU,"%CurrentVersion%\%PrimaryRec%\Recent",RegKey,
    ,"%CurrentVersion%\Explorer\User Shell Folders"
HKCU,"%CurrentVersion%\%PrimaryRec%\Recent",RegValue,
    ,"Recent"

[User.Box.Two]
HKCU,"%CurrentVersion%\%PrimaryRec%\Start Menu",CentralFile,
    ,"Start Menu"
HKCU,"%CurrentVersion%\%PrimaryRec%\Start Menu",Default,1,01,00,00,00
HKCU,"%CurrentVersion%\%PrimaryRec%\Start Menu",DefaultDir,
    ,"%10%\Start Menu"
HKCU,"%CurrentVersion%\%PrimaryRec%\Start Menu",LocalFile,
    ,"Start Menu"
HKCU,"%CurrentVersion%\%PrimaryRec%\Start Menu",MustBeRelative,1,01,00,00,00
HKCU,"%CurrentVersion%\%PrimaryRec%\Start Menu",Name,,"*.lnk,*.pif"
HKCU,"%CurrentVersion%\%PrimaryRec%\Start Menu",RegKey,
    ,"%CurrentVersion%\Explorer\User Shell Folders"
HKCU,"%CurrentVersion%\%PrimaryRec%\Start Menu",RegValue,,"Start Menu"
HKCU,"%CurrentVersion%\%SecondaryRec%\Programs",CentralFile,,"Programs"
HKCU,"%CurrentVersion%\%SecondaryRec%\Programs",Default,1,01,00,00,00
HKCU,"%CurrentVersion%\%SecondaryRec%\Programs",DefaultDir,
    ,"%10%\Start Menu\Programs"
HKCU,"%CurrentVersion%\%SecondaryRec%\Programs",LocalFile,
    ,"Start Menu\Programs"
HKCU,"%CurrentVersion%\%SecondaryRec%\Programs",MustBeRelative,
    1,01,00,00,00
HKCU,"%CurrentVersion%\%SecondaryRec%\Programs",Name,,"*.lnk,*.pif"
HKCU,"%CurrentVersion%\%SecondaryRec%\Programs",ParentKey,,"Start Menu"
HKCU,"%CurrentVersion%\%SecondaryRec%\Programs",RegKey,
    ,"%CurrentVersion%\Explorer\User Shell Folders"
HKCU,"%CurrentVersion%\%SecondaryRec%\Programs",RegValue,,"Programs"
HKCU,"%CurrentVersion%\%SecondaryRec%\Startup",CentralFile,,"Startup"
HKCU,"%CurrentVersion%\%SecondaryRec%\Startup",Default,1,01,00,00,00
HKCU,"%CurrentVersion%\%SecondaryRec%\Startup",DefaultDir,
    ,"%10%\Start Menu\Programs\Startup"
HKCU,"%CurrentVersion%\%SecondaryRec%\Startup",LocalFile,
    ,"Start Menu\Programs\Startup"
HKCU,"%CurrentVersion%\%SecondaryRec%\Startup",MustBeRelative,
    1,01,00,00,00
HKCU,"%CurrentVersion%\%SecondaryRec%\Startup",Name,,"*.lnk,*.pif"
HKCU,"%CurrentVersion%\%SecondaryRec%\Startup",ParentKey,,"Start Menu"
HKCU,"%CurrentVersion%\%SecondaryRec%\Startup",RegKey,
    ,"%CurrentVersion%\Explorer\User Shell Folders"
HKCU,"%CurrentVersion%\%SecondaryRec%\Startup",RegValue,,"Startup"

[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:

   Security=server
   PassThroughAgent=NWSVR1
   

   On a Windows NT network, if the security provider is a domain named NTDOM1:

   Security=Domain
   PassThroughAgent=NTDOM1
   

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:

   Server_Domain_Username = "NWSVR\HELPDESK"
   

   For a Windows NT network, the following specifies the domain containing the account, plus the account name to be given remote administration capabilities:

   Server_Domain_Username = "NTDOM1\ADMIN"
   

Important

You must also make sure that the related files supporting Microsoft Remote Registry services are installed with the Windows 98 source files. To do this, use INF Installer, as described in Chapter 3, "Custom 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 with Microsoft Batch 98 (User Profiles tab in the General Setup Options dialog box) is equivalent to using the User Profiles options in Control Panel (User Profiles tab in the Passwords Properties dialog box).

There are two ways to enable group policies. One way is by adding a line in the [OptionalComponents] section of a setup script and the other way is by using the Windows Setup tab in Add/Remove Programs.

You can also enable group policies for both the Client for Microsoft Networks and Client for NetWare networks.

To enable group policies by editing a setup script

• In your setup script, add the following line in the [OptionalComponents] section.

  Group Policies=1

To enable group policies using Add/Remove Programs in Control Panel

1. In Control Panel, double-click Add/Remove Programs.
2. Click the Windows Setup tab.
3. Select the System Tools check box and then click Details.
4. Select the Group Policies check box and then click OK.
5. Click OK again in the Windows Setup tab.

To enable group policies for both Client for Microsoft Networks and Client for NetWare networks

• Add the following entries to Msbatch.inf:

  [Install]
  Addreg=User.Profiles.Reg, Group.Policies.Reg
  Copyfiles=Group.Policies.Copy
  
  [User.Profiles.Reg]
  HKLM,Network\Logon,UserProfiles,1,1
  
  [Group.Policies.Reg]
  HKLM,Network\Logon,PolicyHandler,,"GROUPPOL.DLL,ProcessPolicies"
  HKLM,System\CurrentControlSet\Services\MSNP32\NetworkProvider,
  GroupFcn,,"GROUPPOL.DLL,NTGetUserGroups"
  HKLM,System\CurrentControlSet\Services\NWNP32\NetworkProvider,
  GroupFcn,,"GROUPPOL.DLL,NWGetUserGroups"
  
  [Group.Policies.Copy]
  grouppol.dll
  
  [DestinationDirs]
  Group.Policies.Copy = 11
  

For information about user profiles and group policies, see Chapter 8, "System Policies." For information about remote administration of a computer’s registry, see Chapter 23, "System and Remote Administration Tools."

[Install] Example: Replacing Configuration Entries

This section presents some sample entries for replacing entries in configuration files as part of Windows 98 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 98 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 98 on a NetWare network, you should modify the Netdet.ini file rather than making modifications using Msbatch.inf. For information, see Chapter 17, "Windows 98 on Third-Party 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]