Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Appendixes

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

This portion of the guide contains valuable information for using Systems Management Server (SMS) in specific cases. Appendix A describes additional steps you must take if you are using SMS to deploy Windows 95 and Office for Windows 95 on an SMS site that includes NetWare logon and distribution servers. Appendix B lists deployment files. Appendix C explains how to create database devices with SQL Server 6.0. Appendix D explains how the files provided with this document enable the retail CD-ROM version of Microsoft Plus! to be installed using unattended setup (Batch Mode Setup).

On This Page

Appendix A: Special Instructions for Sites Using Novell NetWare
Appendix B: Deployment Files
Appendix C: Creating Database Devices with SQL Server 6.0
Appendix D: Microsoft Plus! Batch Mode Setup

Appendix A: Special Instructions for Sites Using Novell NetWare

This appendix describes additional steps you must take if you are using Systems Management Server (SMS) to deploy Windows 95 and Office for Windows 95 on an SMS site that includes NetWare logon and distribution servers.

Special Considerations

When installing SMS to support a Novell NetWare File Server environment, consider the following:

  • SMS Version 1.1 supports NetWare 4.x File Servers in bindery-emulation mode only.

  • File Servers running NetWare 4.x must be running version 4.02 or later.

  • NetWare servers are used as logon and distribution servers in the (passive) SMS model. They should have no executable code running NLMs.

  • NetWare 4.x logon servers require additional modifications to the System Login Script. Refer to the README.HLP file for detailed instructions.

  • Clients using NetWare 4.x must log on with the /b switch for the Program Group Controller to work correctly.

  • You must add the SMS Service Account (SMSADMIN) user account to each NetWare File Server.

  • You must assign supervisor privileges to the SMS Service Account.

  • When creating the SMS Service Account on the NetWare File Server, DO NOT enable the connection limit feature. SMS initiates and uses multiple NetWare logons during the normal course of operations.

Installing the Windows NT Gateway Service for NetWare

The Windows NT Gateway Service acts as the communication layer between the SMS Site Server and each NetWare server to be managed by SMS. Instructions for installation are detailed in this appendix. For more information about this service, see the Windows NT Server documentation.

The Gateway Service for NetWare installs two additional networking components: the NWLink IPX/SPX Compatible Transport and the NWLink NetBIOS interface. All three of these components are needed for SMS to communicate with the NetWare servers.

To install Windows NT Gateway Service for NetWare

  1. From the Control Panel on the Windows NT Server, select the Network icon.

  2. In the Network Settings dialog box, click Add Software.

  3. In the Network Software field, scroll down and highlight Gateway Service for NetWare.

  4. Click Continue.

Cc723700.abk0f(en-us,TechNet.10).gif

The Gateway Service for NetWare is added to the Installed Network Software list in the Network Settings dialog box. Click OK to exit the network section of the Control panel. When prompted, restart your computer to invoke the configuration changes.

Preparing the NetWare Servers

SMS has been designed to make its implementation within a NetWare environment as easy as possible. On the NetWare File Server, create a group called NTGATEWAY; create an account with the same name as the SMS service account; and then configure the Windows NT Gateway Service for NetWare to allow communication to each NetWare File Server to be managed. The administrator can then have SMS attach to each server in turn and install the SMS logon server components onto the selected volume, all from one central location.

Several administrative steps must be taken before SMS can manage the NetWare servers and workstations. These steps are detailed in the following section and need only be performed once at each NetWare server that is to be managed by SMS. To create both the group and user accounts you must use Novell's system console utility, SYSCON.EXE, which is found on the SYS volume in the public directory.

Note: As with many of the Novell tools, this utility may be run from the Windows NT Server computer if the Gateway Service is installed.

Adding the Windows NT Gateway Group to NetWare Servers

A group called NTGATEWAY must be created on each NetWare server that you want to be managed by SMS.

To add the NTGATEWAY group on a NetWare server

  1. From Syscon, in the Available Topics list, select Group Information, and press Enter.

  2. To add a new group, press Insert.

  3. In the New Group Name dialog box, type NTGATEWAY, as shown in the following illustration, and press Enter.

  4. Press Escape.

  5. The NTGATEWAY group is added to the Group Names list.

Cc723700.abk1f(en-us,TechNet.10).gif

Adding the SMSADMIN User Account

The SMS service account, SMSADMIN, must be created on each NetWare server to be managed. This account must have the same name and password as the account you created when you first installed SMS. The account must have SUPERVISOR permissions so that it can install the SMS logon server components and then distribute the application software to the NetWare computers.

To install the SMS service account on a NetWare server

  1. From SYSCON, in the Available Topics list, select User Information, and press Enter.

  2. To add a new user, press Insert. The User Name dialog box appears.

  3. In the User Name dialog box, type SMSADMIN, and press Enter.

  4. Press Escape.

  5. SMSADMIN is added to the User Names list.

Cc723700.abk2f(en-us,TechNet.10).gif

Setting the Password

Next, set the password for the SMSADMIN account. Remember to make the account name and the password different.

To set the password for the SMSADMIN account

  1. From SYSCON, in the User Names list, select the SMSADMIN account, and press Enter.

  2. In the User Information list, select Change Password, and press Enter.

  3. Type the same password assigned to SMSADMIN on the SMS Central Site Server, and press Enter.

  4. When prompted, retype the same password, and press Enter.

  5. Press Escape to close the dialog boxes.

Updating the Group Information

You must add the SMSADMIN account to the NTGATEWAY group so that it can use the Gateway Service.

To add the SMSADMIN account to the NTGATEWAY group

  1. From SYSCON, in the User Information list, select Groups Belonged To, and press Enter.

  2. Press Insert.

  3. In the Groups Not Belonged To list, select NTGATEWAY, and press Enter. NTGATEWAY will appear in the Groups Belonged To dialog box.

Cc723700.abk3f(en-us,TechNet.10).gif

Setting Security on the Account

The last step in this process is to assign SUPERVISOR security privileges so that SMS can distribute software for the users to install.

To assign SUPERVISOR security privileges

  1. In the User Information list, select Security Equivalencies, and press Enter.

  2. Press Insert.

  3. Select SUPERVISOR, and press Enter.

  4. Press Escape to exit.

Cc723700.abk4f(en-us,TechNet.10).gif

This completes the administration tasks on the NetWare server. Remember that each NetWare server has a separate user account database; therefore, these tasks need to be performed on each server that is to be managed by SMS.

Setting the Domain and Server Properties

abk5f

Note: Sites button

After SMS has been installed, and during SMS site configuration, you need to take special steps so that SMS uses the NetWare server as a logon and distribution server. Begin by choosing the Sites button from the SMS Administrator toolbar.

The Sites Properties dialog box appears.

Cc723700.abk6f(en-us,TechNet.10).gif

To set the domain properties

  1. From the Sites Properties dialog box, click Domains. The Proposed Properties dialog box appears.

    Cc723700.abk7f(en-us,TechNet.10).gif

  2. Choose Proposed Properties, and then click Add. The Domains Properties dialog box appears.

  3. Enter the domain name in the Name text box. Do not choose a name that is the same as the name of any Windows NT or LAN Manager domain in your organization.

  4. Select Novell NetWare from the Type list box.

  5. Type name of your NetWare server in the New Logon Server text box, and click Add. Repeat for each NetWare logon server in your domain, until they all appear in the Use These Logon Servers list box.

Setting the Server Properties

To set the server properties

  1. From the Sites Properties dialog box, click Servers. The Servers dialog box appears.

    Cc723700.abk8f(en-us,TechNet.10).gif

  2. Choose Proposed properties, and then click Add. The Server Properties dialog box appears.

    Cc723700.abk9f(en-us,TechNet.10).gif

  3. Enter the name of the NetWare server in the Server Name text box.

  4. Select Default Package Server from the Server Type list box.

Appendix B: Deployment Files

CD Directory Structure

root directory\ Doc

Contains the entire deployment guide on-line.

root directory\ pdf&inf

Contains the following files:

  • WIN95.INF — Standard auto-install of Windows 95.

  • WINOFC95.INF — Combined Windows 95 and Office for Windows 95 setup.

  • WIN95TCP.INF — Auto-install of Windows 95 using Microsoft TCP/IP and DHCP protocol settings.

  • WIN95NW.INF — Auto-install of Windows 95 using Microsoft client for Netware networks.

  • WINOFC95.PDF — PDF For combined Windows 95 and Office for Windows 95 setup.

  • OFF95STD.PDF — PDF for auto-install of Office for Windows 95.

  • SCANDISK.PDF — PDF for scandisk used to check disks prior to upgrades.

root directory\ plus

Contains all the necessary files for auto-installing the Microsoft Plus! pack.

WINOFC95.INF

;
;Windows 95 and Office 95 installation using Runonce functionality.
;
;  --- WINOFC95.INF ---
;
;  Automated Windows 95 Batch Setup Information File 
;  (for use with Microsoft System Management Server) 
; 
;  IMPORTANT **********************************************
;  This inf file includes the use of the Runonce facility to
;  install Office 95 - please refer to comments below !
;
;  For the purposes of demonstration this automated installation
;  uses the Vredir and Netbeui protocol. see Appendix D MSBatch.inf paramters
;  for more details.
;
;  Refer to the Windows 95 resource kit for information about
;  section entries and setup installation options.
[Setup]
;  Remove ";" and set this value to your 10-digit Windows 95 product ID,
;  which is printed on the Windows 95 CD or your Certification of Authenticity.
;ProductID=9999999999 
ProductType=1
;  0 = stop for user input, 1 = do not stop for user input
Express=1
;  0 = Compact, 1 = Typical, 2 = Portable, 3 = Custom
InstallType=1
;  The location of the Windows Directory
;  If blank, default directory will be used.
InstallDir=""
;  1 = Allow user to change the installation directory 
;  0 = don't allow user to change installation directory
ChangeDir=0
;  1 = Allow selection of optional components 
;  0 = Don't allow selection of optional components. 
;  Should be 1 unless all defaults are desired.
OptionalComponents=0
;  0 = Don't search; 1 = Search source directory for INF's
DevicePath=1
;  0 = Do not allow user to choose Uninstall and do not back up existing Windows
;  1 = Show Uninstall options for user to choose
;  5 = Automatically create backup files for uninstalling Windows 95
Uninstall=0
;  0 = Do not create startup disk, 1 = Create startup disk
EBD=0
;  1 = Reboot after setup, 
;  0 = Don't reboot (user will have to manually restart system).
Reboot=1
;  Some Win95 installs will require a second reboot...
;  1 = Don't display prompt before second reboot 
;  0 = Display prompt for second reboot
NoPrompt2Boot=1
;  1 = Force Compliance Upgrade Check
;  0 = Don't force Compliance Upgrade check
CCP=0
;  1 = Display all dialogs during setup, 0 = don't display all dialogs during setup
Display=0
;  0 = Prompt user to confirm before overwriting more recent files
;  1 = Overwrite all without prompting for confirmation
VRC=1
;  1 = Warn user when an unknown version of Pen Windows is installed
;  0 = Do not display warning. 
PenWinWarning=0
;  Remove ";" from the value for your timezone
;  (file shipped with TimeZone="Pacific" selected)
;TimeZone="Afghanistan"
;TimeZone="Alaskan"
;TimeZone="Arabian"
;TimeZone="Atlantic"
;TimeZone="AUS Central"
;TimeZone="Azores"
;TimeZone="Bangkok"
;TimeZone="Canada Central"
;TimeZone="Cen. Australia"
;TimeZone="Central"
;TimeZone="Central Asia"
;TimeZone="Central Pacific"
;TimeZone="China"
;TimeZone="Czech"
;TimeZone="Dateline"
;TimeZone="E. Europe"
;TimeZone="E. South America"
;TimeZone="Eastern"
;TimeZone="Egypt"
;TimeZone="Fiji"
;TimeZone="GFT"
;TimeZone="GMT"
;TimeZone="Greenwich"
;TimeZone="Hawaiian"
;TimeZone="India"
;TimeZone="Iran"
;TimeZone="Israel"
;TimeZone="Lisbon Warsaw"
;TimeZone="Mexico"
;TimeZone="Mid-Atlantic"
;TimeZone="Mountain"
;TimeZone="New Zealand"
;TimeZone="Newfoundland"
TimeZone="Pacific"
;TimeZone="Romance"
;TimeZone="Russian"
;TimeZone="SA Eastern"
;TimeZone="SA Pacific"
;TimeZone="SA Western"
;TimeZone="Samoa"
;TimeZone="Saudi Arabia"
;TimeZone="South Africa"
;TimeZone="Sydney"
;TimeZone="Taipei"
;TimeZone="Tasmania"
;TimeZone="Tokyo"
;TimeZone="US Eastern"
;TimeZone="US Mountain"
;TimeZone="W. Europe"
;TimeZone="West Asia"
;TimeZone="West Pacific"
[Install]
Addreg=Runonce.reg
[Runonce.Reg]

HKLM,Software\Microsoft\Windows\CurrentVersion\RunOnce,Office,,"\\SMS_CENTRAL\Þ Products\office95\setup.exe /Q1 /B2"

;
; The string "UNC\share\" must point to a path that has the Office 95 code.
: This path must be available to the client PC.
; 

; MS Office uses "setup.exe /Q1 /B2", please see Office 95 Resource Kit for

Þ further information

;
; This is an example of an automated (Q1), minimal (B1) install.
; The off95std.pdf file can be viewed by a text editor for other options.
;
[NameAndOrg]
;  Name of registered user
;  If left blank, a default value for this key will be determined.
Name=""
;  Organization 
;  If left blank, a default value for this key will be determined.
Org=""
;  1 = Display name and organization dialog during setup
;  0 = Don't display name and organization dialog during setup
Display=0
[Network]
;  Default to Client for Microsoft Networks (VREDIR) and 
;  Microsoft client for Netware Networks (NWREDIR).
;  Refer to the Win95 resource guide for valid values.
;  If this key does not specify VREDIR, the [VREDIR] section
;  will be ignored.
Clients=VREDIR
;  0 = Do not prompt for network components during Custom setup type,
;      so Setup will only use detection to install networking
;  1 = Prompt for network components
Display=0
;  Computer name (must be unique identifier on network)
;  If left blank, a default value for this key will be determined.
ComputerName=""
;  Computer workgroup (also used for domain default)
;  If left blank, a default value for this key will be determined.
Workgroup=""
;  Computer description
;  If left blank, a default value for this key will be determined.
Description=""
;  User Security
;  share = share level security
;  nwserver = user level security, validated by a NetWare server
;  domain = user level security, validated by a Windows NT domain
;  msserver = user level security, validated by a computer running 
Þ Windows NT Workstation
Security=share
[VRedir]
;  This section is used if the client is to be configured as
;  a Client for Microsoft Networks (ie: [Network] Clients
;  key specifies VREDIR).  
;  0 = Don't validate logons
;  1 = Validate logon to NT domain
ValidatedLogon=1
;  Windows NT Domain to use for logon validation.
;  If left blank, a default value for this key will be determined.
LogonDomain=
[Printers]
;  This section is used to install one or more printers during Windows 
;  95 setup.  If the [Printers] section contains no entries, the user
;  will not be prompted to select a printer.  The entry syntax is:
;
;  "Printer Name"="driver name", port or network print queue UNC
; 
;  eg: "First floor printer"="HP Laserjet IIIsi",\\Server_1\PrtShr_1

WIN95TCP.INF

;
;  --- WIN95tcp.INF ---
;
;  Automated Windows 95 Batch Setup Information File 
;  (for use with Microsoft System Management Server) 
; 
;  This is an example of setting up a Windows 95 client to use
;  the TCP/IP protocol(using DHCP), supplied with Windows 95.
; 
;  Refer to the Windows 95 resource kit for information about
;  section entries and setup installation options.
[Setup]
;  Remove ";" and set this value to your 10-digit Windows 95 product ID,
;  which is printed on the Windows 95 CD or your Certification of Authenticity.
;ProductID=9999999999 
ProductType=1
;  0 = stop for user input, 1 = do not stop for user input
Express=1
;  0 = Compact, 1 = Typical, 2 = Portable, 3 = Custom
InstallType=1
;  The location of the Windows Directory
;  If blank, default directory will be used.
InstallDir=""
;  1 = Allow user to change the installation directory 
;  0 = don't allow user to change installation directory
ChangeDir=0
;  1 = Allow selection of optional components 
;  0 = Don't allow selection of optional components. 
;  Should be 1 unless all defaults are desired.
OptionalComponents=0
;  0 = Don't search; 1 = Search source directory for INF's
DevicePath=1
;  0 = Do not allow user to choose Uninstall and do not back up existing Windows
;  1 = Show Uninstall options for user to choose
;  5 = Automatically create backup files for uninstalling Windows 95
Uninstall=0
;  0 = Do not create startup disk, 1 = Create startup disk
EBD=0
;  1 = Reboot after setup, 
;  0 = Don't reboot (user will have to manually restart system).
Reboot=1
;  Some Win95 installs will require a second reboot...
;  1 = Don't display prompt before second reboot 
;  0 = Display prompt for second reboot
NoPrompt2Boot=1
;  1 = Force Compliance Upgrade Check
;  0 = Don't force Compliance Upgrade check
CCP=0
;  1 = Display all dialogs during setup, 0 = don't display all dialogs during setup
Display=0
;  0 = Prompt user to confirm before overwriting more recent files
;  1 = Overwrite all without prompting for confirmation
VRC=1
;  1 = Warn user when an unknown version of Pen Windows is installed
;  0 = Do not display warning. 
PenWinWarning=0
;  Remove ";" from the value for your timezone
;  (file shipped with TimeZone="Pacific" selected)
;TimeZone="Afghanistan"
;TimeZone="Alaskan"
;TimeZone="Arabian"
;TimeZone="Atlantic"
;TimeZone="AUS Central"
;TimeZone="Azores"
;TimeZone="Bangkok"
;TimeZone="Canada Central"
;TimeZone="Cen. Australia"
;TimeZone="Central"
;TimeZone="Central Asia"
;TimeZone="Central Pacific"
;TimeZone="China"
;TimeZone="Czech"
;TimeZone="Dateline"
;TimeZone="E. Europe"
;TimeZone="E. South America"
;TimeZone="Eastern"
;TimeZone="Egypt"
;TimeZone="Fiji"
;TimeZone="GFT"
;TimeZone="GMT"
;TimeZone="Greenwich"
;TimeZone="Hawaiian"
;TimeZone="India"
;TimeZone="Iran"
;TimeZone="Israel"
;TimeZone="Lisbon Warsaw"
;TimeZone="Mexico"
;TimeZone="Mid-Atlantic"
;TimeZone="Mountain"
;TimeZone="New Zealand"
;TimeZone="Newfoundland"
TimeZone="Pacific"
;TimeZone="Romance"
;TimeZone="Russian"
;TimeZone="SA Eastern"
;TimeZone="SA Pacific"
;TimeZone="SA Western"
;TimeZone="Samoa"
;TimeZone="Saudi Arabia"
;TimeZone="South Africa"
;TimeZone="Sydney"
;TimeZone="Taipei"
;TimeZone="Tasmania"
;TimeZone="Tokyo"
;TimeZone="US Eastern"
;TimeZone="US Mountain"
;TimeZone="W. Europe"
;TimeZone="West Asia"
;TimeZone="West Pacific"
[NameAndOrg]
;  Name of registered user
;  If left blank, a default value for this key will be determined.
Name=""
;  Organization 
;  If left blank, a default value for this key will be determined.
Org=""
;  1 = Display name and organization dialog during setup
;  0 = Don't display name and organization dialog during setup
Display=0
[Network]
;  Default to Client for Microsoft Networks (VREDIR) and 
;  Microsoft client for Netware Networks (NWREDIR).
;  Refer to the Win95 resource guide for valid values.
;  If this key does not specify VREDIR, the [VREDIR] section
;  will be ignored.
Clients=VREDIR
Protocols=MSTCP
;  0 = Do not prompt for network components during Custom setup type,
;      so Setup will only use detection to install networking
;  1 = Prompt for network components
Display=0
;  Computer name (must be unique identifier on network)
;  If left blank, a default value for this key will be determined.
ComputerName=""
;  Computer workgroup (also used for domain default)
;  If left blank, a default value for this key will be determined.
Workgroup=""
;  Computer description
;  If left blank, a default value for this key will be determined.
Description=""
;  User Security
;  share = share level security
;  nwserver = user level security, validated by a NetWare server
;  domain = user level security, validated by a Windows NT domain
;  msserver = user level security, validated by a computer running 
Þ Windows NT Workstation
;Security=share
Security=domain
PassThroughAgent="MSTVDOM_NT"
[MSTCP]
DHCP=1
DNS=0
WINS=DHCP
[Printers]
;  This section is used to install one or more printers during Windows 
;  95 setup.  If the [Printers] section contains no entries, the user
;  will not be prompted to select a printer.  The entry syntax is:
;
;  "Printer Name"="driver name", port or network print queue UNC
; 
;  eg: "First floor printer"="HP Laserjet IIIsi",\\Server_1\PrtShr_1

WIN95NW.INF

;
;  --- WIN95nw.INF ---
;
;  Automated Windows 95 Batch Setup Information File 
;  (for use with Microsoft System Management Server) 
; 
;  This is an example of setting up a Windows 95 client to use 
;  the Netware redir, supplied with Windows 95.
;
;  Refer to the Windows 95 resource kit for information about
;  section entries and setup installation options.
[Setup]
;  Remove ";" and set this value to your 10-digit Windows 95 product ID,
;  which is printed on the Windows 95 CD or your Certification of Authenticity.
;ProductID=9999999999 
ProductType=1
;  0 = stop for user input, 1 = do not stop for user input
Express=1
;  0 = Compact, 1 = Typical, 2 = Portable, 3 = Custom
InstallType=1
;  The location of the Windows Directory
;  If blank, default directory will be used.
InstallDir=""
;  1 = Allow user to change the installation directory 
;  0 = don't allow user to change installation directory
ChangeDir=0
;  1 = Allow selection of optional components 
;  0 = Don't allow selection of optional components. 
;  Should be 1 unless all defaults are desired.
OptionalComponents=0
;  0 = Don't search; 1 = Search source directory for INF's
DevicePath=1
;  0 = Do not allow user to choose Uninstall and do not back up existing Windows
;  1 = Show Uninstall options for user to choose
;  5 = Automatically create backup files for uninstalling Windows 95
Uninstall=0
;  0 = Do not create startup disk, 1 = Create startup disk
EBD=0
;  1 = Reboot after setup, 
;  0 = Don't reboot (user will have to manually restart system).
Reboot=1
;  Some Win95 installs will require a second reboot...
;  1 = Don't display prompt before second reboot 
;  0 = Display prompt for second reboot
NoPrompt2Boot=1
;  1 = Force Compliance Upgrade Check
;  0 = Don't force Compliance Upgrade check
CCP=0
;  1 = Display all dialogs during setup, 0 = don't display all dialogs during setup
Display=0
;  0 = Prompt user to confirm before overwriting more recent files
;  1 = Overwrite all without prompting for confirmation
VRC=1
;  1 = Warn user when an unknown version of Pen Windows is installed
;  0 = Do not display warning. 
PenWinWarning=0
;  Remove ";" from the value for your timezone
;  (file shipped with TimeZone="Pacific" selected)
;TimeZone="Afghanistan"
;TimeZone="Alaskan"
;TimeZone="Arabian"
;TimeZone="Atlantic"
;TimeZone="AUS Central"
;TimeZone="Azores"
;TimeZone="Bangkok"
;TimeZone="Canada Central"
;TimeZone="Cen. Australia"
;TimeZone="Central"
;TimeZone="Central Asia"
;TimeZone="Central Pacific"
;TimeZone="China"
;TimeZone="Czech"
;TimeZone="Dateline"
;TimeZone="E. Europe"
;TimeZone="E. South America"
;TimeZone="Eastern"
;TimeZone="Egypt"
;TimeZone="Fiji"
;TimeZone="GFT"
;TimeZone="GMT"
;TimeZone="Greenwich"
;TimeZone="Hawaiian"
;TimeZone="India"
;TimeZone="Iran"
;TimeZone="Israel"
;TimeZone="Lisbon Warsaw"
;TimeZone="Mexico"
;TimeZone="Mid-Atlantic"
;TimeZone="Mountain"
;TimeZone="New Zealand"
;TimeZone="Newfoundland"
TimeZone="Pacific"
;TimeZone="Romance"
;TimeZone="Russian"
;TimeZone="SA Eastern"
;TimeZone="SA Pacific"
;TimeZone="SA Western"
;TimeZone="Samoa"
;TimeZone="Saudi Arabia"
;TimeZone="South Africa"
;TimeZone="Sydney"
;TimeZone="Taipei"
;TimeZone="Tasmania"
;TimeZone="Tokyo"
;TimeZone="US Eastern"
;TimeZone="US Mountain"
;TimeZone="W. Europe"
;TimeZone="West Asia"
;TimeZone="West Pacific"
[NameAndOrg]
;  Name of registered user
;  If left blank, a default value for this key will be determined.
Name=""
;  Organization 
;  If left blank, a default value for this key will be determined.
Org=""
;  1 = Display name and organization dialog during setup
;  0 = Don't display name and organization dialog during setup
Display=0
[Network]
;  Default to Client for Microsoft Networks (VREDIR) and 
;  Microsoft client for Netware Networks (NWREDIR).
;  Refer to the Win95 resource guide for valid values.
;  If this key does not specify VREDIR, the [VREDIR] section
;  will be ignored.
Clients=NWREDIR
Protocols=NWLINK
[NWLINK]
FrameType=4
NetBIOS=0
[NWREDIR]
FirstNetDrive=F:
PreferredServer=MSTV
ProcessLoginScript=1
;  0 = Do not prompt for network components during Custom setup type,
;      so Setup will only use detection to install networking
;  1 = Prompt for network components
Display=0
;  Computer name (must be unique identifier on network)
;  If left blank, a default value for this key will be determined.
ComputerName=""
;  Computer workgroup (also used for domain default)
;  If left blank, a default value for this key will be determined.
Workgroup=""
;  Computer description
;  If left blank, a default value for this key will be determined.
Description=""
;  User Security
;  share = share level security
;  nwserver = user level security, validated by a NetWare server
;  domain = user level security, validated by a Windows NT domain
;  msserver = user level security, validated by a computer running 
Þ Windows NT Workstation
Security=share
[Printers]
;  This section is used to install one or more printers during Windows 
;  95 setup.  If the [Printers] section contains no entries, the user
;  will not be prompted to select a printer.  The entry syntax is:
;
;  "Printer Name"="driver name", port or network print queue UNC
; 
;  eg: "First floor printer"="HP Laserjet IIIsi",\\Server_1\PrtShr_1

WINOFC95.PDF

[PDF]
Version=1.0
[Win95 Automated Setup]
CommandLine=w95tow95.exe setup.exe win95.inf Win95_to_Win95 /IS /IW
CommandName= Automated Windows 95 Upgrade
UserInputRequired=FALSE
SynchronousSystemExitRequired=TRUE
SupportedPlatforms=Windows95
[Win TCP Automated Setup]
CommandLine=win2w95.exe setup.exe win95tcp.inf Win_to_Win95 /IS /IW
CommandName= Automated Setup for WfW Client-TCP
UserInputRequired=FALSE
SynchronousSystemExitRequired=TRUE
SupportedPlatforms=Windows 3.1
[WINOFC95 Automated Setup]
CommandLine=win2w95.exe setup.exe winofc95.inf Win_to_Win95 /IS /IW
CommandName= Automated Setup to Win95 & Office95 
UserInputRequired=FALSE
SynchronousSystemExitRequired=TRUE
SupportedPlatforms=Windows 3.1
[WinNW Automated Setup]
CommandLine=win2w95.exe setup.exe win95nw.inf Win_to_Win95 /IS /IW
CommandName= Automated Setup for WindowsNW Client
UserInputRequired=FALSE
SynchronousSystemExitRequired=TRUE
SupportedPlatforms=Windows 3.1
[DOS Automated Setup]
CommandLine=dos2w95.exe setup.exe win95.inf Dos_to_Win95 /IS /IW /D
CommandName= Automated Setup for DOS Client
UserInputRequired=FALSE
SynchronousSystemExitRequired=TRUE
SupportedPlatforms=MS-DOS 5.0, MS-DOS 6.0, MS-DOS 6.2, MS-DOS 6.21, MS-DOS 6.22
[Win95 Manual Setup]
CommandLine=w95tow95.exe setup.exe win95min.inf Win95_to_Win95 
CommandName=Manual Windows 95 Upgrade
UserInputRequired=TRUE
SynchronousSystemExitRequired=TRUE
SupportedPlatforms=Windows95
[Win Manual Setup]
CommandLine=win2w95.exe setup.exe win95min.inf Win_to_Win95 
CommandName=Manual Setup for Windows/WfW Client
UserInputRequired=TRUE
SynchronousSystemExitRequired=TRUE
SupportedPlatforms=Windows 3.1
[DOS Manual Setup]
CommandLine=dos2w95.exe setup.exe win95min.inf Dos_to_Win95 /D
CommandName=Manual Setup for DOS Client
UserInputRequired=TRUE
SynchronousSystemExitRequired=TRUE
SupportedPlatforms=MS-DOS 5.0, MS-DOS 6.0, MS-DOS 6.2, MS-DOS 6.21, MS-DOS 6.22
[Package Definition]
Product=Deployment Guide
Version=Windows 95 & Office 95 
Comment=Deployment guide PDF - various options

SetupVariations=Win95 Automated, Win TCP Automated, WINOFC95 Automated,

Þ WinNW Automated, DOS Automated, Win95 Manual, Win Manual, DOS Manual

[Setup Package for Inventory]
InventoryThisPackage=TRUE
Detection Rule Part 1=File 1
[File 1]
FILE=SETUPLOG.TXT
COLLECT=TRUE
Checksum=
DATE=
SIZE=
TIME=

OFF95STD.PDF

[PDF]
Version=1.0
[Package Definition]
Product=Microsoft Office 95
Version=7.0
Comment=Microsoft Office 95 Standard
SetupVariations=Compact, Typical, Complete, Custom, Uninstall
[Compact Setup]
CommandLine=setup.exe /q1 /B2
CommandName=Compact
UserInputRequired=FALSE
SupportedPlatforms=Windows95, Windows NT 3.1 (x86)
[Typical Setup]
CommandLine=setup.exe /Q1 /B1
CommandName=Typical
UserInputRequired=FALSE
SupportedPlatforms=Windows95, Windows NT 3.1 (x86)
[Complete Setup]
CommandLine=setup.exe /Q1 /B3
CommandName=Complete
UserInputRequired=FALSE
SupportedPlatforms=Windows95, Windows NT 3.1 (x86)
[Custom Setup]
CommandLine=setup.exe
CommandName=Custom
UserInputRequired=TRUE
SupportedPlatforms=Windows95, Windows NT 3.1 (x86)
[Uninstall Setup]
CommandLine=setup.exe /Q1 /U
CommandName=Uninstall
UserInputRequired=TRUE
SupportedPlatforms=Windows95, Windows NT 3.1 (x86)
[Setup Package for Sharing]
ShareName=ofs95ash
ShareAccess=UserRead, , GuestRead,
[Program Item Properties 1]
CommandLine=MSOFFICE.EXE
Description=Microsoft Office95a Std Install
ConfigurationScript=smsacme.exe ofs95a+install
RegistryName=ofs95a+install
DefaultINIFile=
RunMinimized=FALSE
RunLocalCopyIfPresent=FALSE
DriveMode=UNC
SupportedPlatforms=Windows95, Windows NT 3.1 (x86)
SetupIcon=OFS95A01.ICO
DisplayIconInProgGroup=TRUE
[Setup Package for Inventory]
InventoryThisPackage=TRUE
Detection Rule Part 1=File 1
[File 1]
FILE=MSOFFICE.EXE
COLLECT=FALSE
Checksum=
DATE=7, 20, 95
SIZE=365056
TIME=00, 00

SCANDISK.PDF

[PDF]
Version=1.0
[Package Definition]
Product=Scandisk
Version=6.22	 
Comment=Scandisk test for Windows 95 Upgrade
SetupVariations=Automatic MS DOS Disk check, Automatic Windows Disk check
[Automatic MS DOS Disk check Setup]
CommandLine=scandisk c: /checkonly /nosummary
CommandName=Automated Disk check for MS DOS
UserInputRequired=FALSE
SupportedPlatforms=MS-DOS 5.0, MS-DOS 6.0, MS-DOS 6.2, MS-DOS 6.21, MS-DOS 6.22
[Automatic Windows Disk check Setup]
CommandLine=scandisk c: /checkonly /nosummary
CommandName=Automated Disk check for Windows
UserInputRequired=FALSE
SupportedPlatforms=Windows 3.1
[Setup Package for Inventory]
InventoryThisPackage=TRUE
Detection Rule Part 1=File 1
[File 1]
FILE=SCANDISK.LOG
COLLECT=TRUE
Checksum=
DATE=
SIZE=
TIME=

Appendix C: Creating Database Devices with SQL Server 6.0

When Systems Management Server (SMS) is installed, the setup program automatically creates the devices and databases required if SMS and SQL Server are running on the same server. However, you might want to run SQL Server on a different computer running Windows NT Server in order to move the processing of the database onto a computer other than the primary site server. In this case, there are a few extra steps that need to be completed using the SQL Server tools.

Creating Database Devices

From the SQL Enterprise Manager, log on using the sa account (or a Windows NT Administrator account, if you are using integrated security). The account you use must have the ability to create SQL devices. The sa account is the default account for SQL administration.

From the main screen, select the Database Devices Icon. Click the right mouse button, and select New Device, as shown in the following illustration.

Cc723700.abk10f(en-us,TechNet.10).gif

From the New Database Device menu, enter in the details of the first device (typically SMSData), as shown in the following illustration.

Cc723700.abk11f(en-us,TechNet.10).gif

If the device were created on the computer used for the SMS primary site, the Name would default to SMSData, and the Path would default to \win32app\SQL60\DATA\SMS.DB. You might choose to use these values in creating the database on a separate computer. The Size for SMSData should generally be set at 45 MB. See SMS online Help for additional information on setting the Size.

Once the first device has been created, do the same for the second device (SMSLog). For the log device, the recommended size is 8 MB.

When you are installing SMS and the following screen appears, enter the details of the remote SQL Server that you just worked with and the name of the database that you would like SMS to create.

Cc723700.abk12f(en-us,TechNet.10).gif

For more information about working with Microsoft SQL Server, please refer to the SQL Server documentation.

Note: For each additional SMS administrator account, a separate SQL Server client license is required. The first comes with the SQL Server license itself, but additional licenses must be purchased if more than one SMS administrator account is to be used.

Appendix D: Microsoft Plus! Batch Mode Setup

The files provided with this document enable the retail CD-ROM version of Microsoft Plus! to be installed using unattended setup (Batch Mode Setup). This appendix explains how to configure and use Batch Mode Setup.

For information on using Microsoft Plus!, see the Microsoft Plus! User's Guide and online Help. To print Batch.doc, open it in WordPad or another word processor, and then use the Print command on the File menu.

Before You Start

This section discusses some things you should know before you start the preinstallation process.

Some components of Microsoft Plus! require certain Windows 95 components to work properly. However, a typical Windows 95 Setup does not install all the Windows 95 components that Microsoft Plus! needs. If Microsoft Plus! Setup doesn't find the Windows 95 components it needs, it automatically has Windows 95 Setup install them. If at that time the Windows 95 setup files are not located where they were during Windows 95 Setup, then Microsoft Plus! Batch Mode Setup halts with a request for the original Windows 95 Setup disk(s). (This is why retail Microsoft Plus! Setup from CD-ROM often requires the Windows 95 CD-ROM as well as the Microsoft Plus! CD-ROM.)

For more information on which Microsoft Plus! components require Windows 95 components, see the section, "Customizing Individual Components," later in this appendix.

To determine where a particular system will expect the Windows 95 installation files to be located

  1. On the target system, click the Start button, click Run, and then type REGEDIT.EXE.

  2. In the Registry Editor, change to the following registry folder:

    [HKEY_LOCAL_MACHINE \Software \Microsoft \Windows
    Þ CurrentVersion\Setup]
    

    The SourcePath string value contains the drive or network path that specifies the location of the Windows 95 Setup files.

Planning for Disk Space Requirements

Microsoft Plus! Setup requires 40 to 55 MB of disk space. If there is not enough disk space, Setup displays an error message and stops.

By default, Microsoft Plus! is installed on the local Windows drive, in the \Program Files\Plus! folder. If you choose to install Microsoft Plus! on a different local hard drive, Setup still requires up to 20 MB of space on the Windows drive. This is for the Microsoft Plus! files that Windows 95 uses only if they are installed to the Windows or Program Files folders.

Important: Microsoft Plus! cannot be installed on a system if Windows 95 is not installed on a local drive. If the system uses a Windows directory on a network server (Shared Windows), do not attempt to install Microsoft Plus!

If Microsoft Plus! Is Already Installed

Batch Mode Setup might display an error and refuse to install if Microsoft Plus! has already been installed via batch mode or if it was preinstalled by the hardware manufacturer.

Getting Ready to Use Batch Mode Setup

Before using Batch Mode Setup to install Microsoft Plus!, you must copy the necessary files to a local or network location that is accessible from the workstation on which Microsoft Plus! will be installed.

To enable Batch Mode Setup

  1. Copy the files from the root of your retail Microsoft Plus! CD-ROM to a local or network location.

    Be sure to copy the \Win95 directory as well as the files in the root directory. This directory is used by Windows 95 and the DriveSpace 3 utility to create Windows Startup disks able to access and fix damaged DriveSpace 3 drives. (The \MMCAT directory is not required.)

  2. Copy the files provided with this appendix to the same location. Doing so replaces some of the PLUS.INF and SETUP.LST files that you copied from the compact disc.

  3. To install Microsoft Plus! on a system with no user interaction, use the command line:

    Setup /Q1 /K"xxxxxxxxxx"
    

    Where xxxxxxxxxx is the 10-digit CD Key located on the back of your Microsoft Plus! compact disc.

  4. Edit the Plus!.pdf file to incorporate the following line:

    [Batch Setup]
    CommandLine = setup.exe /Q1
    

    to read

    [Batch Setup]
    CommandLine = setup.exe /Q1/K"xxxxxxxxxx"
    

    Where xxxxxxxxxx is the 10-digit CD Key located on the back of yourMicrosoft Plus! CD. Then copy the edited Plus!.PDF to:

    root directory\SMS\PRIMSITE.SRV\IMPORT.SRC\ENU\ directory.

Batch Mode will now install all Microsoft Plus! components with the default options. You can specify that Batch Mode not install a component, or you can customize how a component is to be installed. Instructions on how to do so are included under "Customizing Individual Components," later in this appendix. Once Batch Mode has been enabled, you can still use Setup in the normal interactive mode.

Using and Customizing Batch Mode Setup

This section explains how to use Batch Mode Setup to install Microsoft Plus! and also explains how to customize Batch Mode Setup. By default, all of the following components are installed by Setup:

  • DriveSpace3

  • System Agent

  • Internet Tools

  • Desktop Themes

  • Dial-Up Server

  • 3D Pinball

  • Visual Enhancements

For more information, see the individual discussion of each component in the sections that follow.

General Guidelines for Customizing Batch Mode Setup

Microsoft Plus! Batch Mode Setup can be modified to fit your needs. To do this, you edit certain text files. When customizing Batch Mode Setup, be sure to follow these guidelines:

  • Never edit your only copy of a file.

  • Do not change tabs when editing the PLUS.STF file. Setup regards a tab in the .STF file as a special character; tabs and spaces are not interchangeable.

  • Always use Windows 95 WordPad (NOT Edit) or another editor that will leave tabs in place when making changes. Microsoft Write and Microsoft Word for Windows also are acceptable.

  • When editing the PLUS.INF file, be sure all filenames are in uppercase. Setup regards these filenames as case-sensitive; for example, Setup treats SETUP.INF and setup.inf as two different files.

Some of the changes described in the sections that follow only apply to Batch Mode Setup; other changes also affect interactive setup. To provide access to an unaltered interactive setup, do so in a separate location from the customized Batch Mode Setup.

General Setup Options

You can modify the following general options for Microsoft Plus! Batch Mode Setup:

  • Changing The Default Installation Directory

  • Predefining The Microsoft Plus! Setup SourcePath

  • Disabling System Restart After Setup Is Completed

The following sections describe how to modify these options.

Changing the Default Installation Directory

This changes the location where most of Microsoft Plus! will be installed. (Some files must be installed to the Windows 95 directory and are not affected by this change.)

To change the default installation directory

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #1 by changing the %P\Plus! to the desired default target. Include both the long filename and short filename for the directory. For example, to install the Plus! files in the C:\Customized directory, which has a short filename of C:\CUSTOM~1, you would specify:

    1 Microsoft Plus! for Windows 95 AppSearch 
    Þ C:\CUSTOM~1<c:\Customized>,.….
    

Predefining the Microsoft Plus! Setup SourcePath

You can force Microsoft Plus! Setup to use Microsoft Plus! Setup files from a specific location. This is useful if the location of the Microsoft Plus! Setup files during the initial installation will not be available in the future, but a specific, known location will be available in the future.

To specify the location of Microsoft Plus! Setup files

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #2572 by specifying the path to the Microsoft Plus! files in the Title field. Add the path to the Title field; precede it with a semicolon. The following line is an example:

    2572 yes Remove stf if cancel;c:\pluspath\ CustomAction...
    
  3. Modify object line #2514 by replacing the %s\ with the path to the Microsoft Plus! files, followed by a backslash. The following line is an example:

    2514 GenInstall RegEntry ... ""SourcePath"",""c:\pluspath\""" 
    Þ yes %S
    

Disabling System Restart After Setup Is Completed

Normally, Microsoft Plus! restarts the system after it completes Setup. You should restart the system before using any Microsoft Plus! components. However, you might want to prevent Plus! Setup from rebooting the system if you are running several setup programs and want to restart only after the last one is completed.

To control whether Microsoft Plus! Setup restarts the system after it completes Setup

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #2563 by changing the batch field to YES (to restart) or NO (not to restart).

Customizing Individual Components

This section describes how you can customize installation of specific components.

The following table briefly describes the default batch mode settings.

Microsoft Plus! component

Windows 95 component(s) required

Notes

DriveSpace3

Requires Windows 95 Disk Defragmenter

Will not be installed if Stacker, SuperStor, or other non-Microsoft disk compression is already in use.

System Agent

Requires Windows 95 Disk Defragmenter

Will be installed with default task list set to run ScanDisk and Defrag when the system is not in use during the day.

Internet Tools

Requires various Windows 95 files when the Internet Setup Wizard is run

Unlike interactive setup, the Wizard is not run during Batch Mode Setup.

Desktop Themes

The Windows 95 theme is applied automatically

Sound files will not be installed if no sound card is in use.

Dial-Up Server

Requires Windows 95 Dial-Up Networking Client and a modem

 

3D Pinball

Automatically installed

 

Visual Enhancements

Automatically installed as appropriate for system's video settings

 

DriveSpace 3

DriveSpace 3 is an enhanced disk-compression alternative to Windows 95 DriveSpace. Its features include offline compression, variable compression (including no on-the-fly compression), more efficient space usage, and support for drives up to 2 GB.

Even if Setup is configured to install DriveSpace 3, it will not be installed if Stacker, SuperStor, or another non-Microsoft disk compression is in use.

To enable or disable DriveSpace 3 installation

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #31 by changing the batch field to YES (to install DriveSpace 3) or NO (not to install DriveSpace 3).

There are no other installation options for DriveSpace 3.

Required Windows 95 Components

DriveSpace 3 requires the Windows 95 Disk Defragmenter. Disk Defragmenter is installed during a typical Windows 95 Setup. To install Microsoft Plus! without user intervention, do one of the following:

  • Ensure that the Windows 95 installation files are accessible during Microsoft Plus! Setup.

  • Ensure that Disk Defragmenter (one of the Disk Tools options) is installed during Windows 95 Setup.

  • Disable DriveSpace 3 installation during Batch Mode Setup.

System Agent

By default, System Agent is configured to run system-maintenance tasks (such as ScanDisk for Windows and Disk Defragmenter) and other programs at specific times or whenever the system is not in use. System Agent is also useful for scheduling offline compression with DriveSpace 3.

To enable or disable System Agent installation

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #32 by changing the batch field to YES (to install System Agent) or NO (not to install System Agent).

Scheduled Tasks

You can customize System Agent's scheduled tasks by using the Install Daytime or Nighttime System Agent Task List option. You can preconfigure System Agent to run ScanDisk for Windows and Disk Defragmenter when the system is idle at night or during the day. By default, System Agent runs these tasks when the system is idle during the day.

To configure System Agent to run tasks during the day or night

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object lines #255 and #257 by changing the batch field to YES (to run the preconfigured tasks at night) or NO (to run the tasks during the day).

Customized System Agent Tasks (SAGE.DAT file)

By default, System Agent is configured to run ScanDisk for Windows and Disk Defragmenter. You can preconfigure System Agent to run other tasks or to configure the default tasks differently.

To configure System Agent to run custom tasks

  1. Extract the SAGE.DAT file from the PLUS_2.CAB file.

  2. Copy the SAGE.DAT file to a system that has Microsoft Plus! already installed. Place the file in the Program Files\Plus!\System folder.

  3. Use the System Agent to add, modify, or delete tasks until the task list looks the way you want it to. (This modifies the SAGE.DAT file.)

  4. Copy the modified SAGE.DAT back to the local or network location containing the Microsoft Plus! Batch Mode Setup files.

  5. Open the PLUS.INF file in Windows 95 WordPad.

  6. In the [SystemAgent] section, change all instances of DS3UPGRD.DAT, SAGE24.DAT, and DS3UPG24.DAT to SAGE.DAT.

  7. Add !DECOMPRESS to the seventh comma-delimited field of each of the SAGE.DAT lines in the [SystemAgent] section. There are eight such lines; the following is an example:

    "cdt" = 2,SAGE.DAT,,,,1995-07014,!DECOMPRESS,,,,,
    Þ SAGE.DAT,6858,,6858
    

Registry Information for System Agent

You can add registry information for System Agent about any other System Agent-aware applications. This can be useful if you use or have created such applications.

To add registry information for System Agent

  1. Create a Windows 95 registry file containing the Sage-Aware setting the application needs.

  2. Rename that registry file to ADMIN.REG, and then copy it to the local or network location containing the Microsoft Plus! Batch Mode Setup files.

  3. Open the PLUS.STF file in Windows 95 WordPad.

  4. Modify object line #270 by adding 361 to the Group references, such as the following example:

    270 *** Sage Awareness *** Group 271 291 321 351 361
    

Required Windows 95 Components

System Agent requires the Windows 95 Disk Defragmenter, which is installed during a typical Windows 95 Setup. To install Microsoft Plus! without user intervention, do one of the following:

  • Ensure that the Windows 95 installation files are accessible during Microsoft Plus! Setup.

  • Ensure that Disk Defragmenter (one of the Disk Tools options) is installed during Windows 95 Setup.

  • Disable System Agent installation during Batch Mode Setup.

Internet Jumpstart Kit

The Internet Jumpstart Kit includes the following:

  • Internet Explorer World Wide Web browser

  • Internet e-mail option for Microsoft Exchange

  • Version 1.05 of the Microsoft Network (MSN), which includes access to Usenet Newsgroups

This section is applicable if you are installing Microsoft Plus! over the retail version of Windows 95. If Windows 95 was installed by the hardware manufacturer, Microsoft Plus! Setup does not install the Internet Jumpstart Kit. The version of Windows 95 licensed to hardware manufacturers already includes the same Internet Explorer components as Microsoft Plus!

If you are using an Internet proxy server, you can arrange for the Internet Explorer to use it automatically. See the Proxy.txt file for more information.

To enable or disable Internet Jumpstart Kit installation

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #33 changing the batch field to YES (to install) or NO (not to install).

Enabling or Disabling the Internet Desktop Icon

Microsoft Plus! Setup usually adds an icon to the desktop titled "The Internet." This is a shortcut to the Internet Explorer, which also is located on the Start Menu.

To prevent the icon "The Internet" from being added to the desktop

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #1410 by removing the group reference to object line #1436, as indicated in the following example:

    1410 Shortcut Group 1411 1412…1434 1435
    

Enabling/Disabling Internet Setup Wizard (INETWIZ) During Setup

The Internet Setup Wizard tool configures the Internet Jumpstart Kit. It is normally run during Microsoft Plus! Setup and can also be run from the Start Menu.

To run the Internet Setup Wizard during Batch Mode Setup

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #1620 by changing the batch field to YES (to launch the Internet Setup Wizard during Setup) or NO (not to launch the Internet Setup Wizard during Setup).

Note: The Internet Setup Wizard does NOT have an unattended mode. Therefore, user input is required if it is run during Setup.

Required Windows 95 Components and Other Prerequisites

The Internet Jumpstart Kit component is different from the other Microsoft Plus! components that require Windows 95 files, in that the Windows 95 Setup files might not be required during Setup itself.

The Windows 95 Setup files, and sometimes the Microsoft Plus! Setup files, are required to configure the Internet Tools using the Internet Setup Wizard. Whenever the Wizard is run, the Windows 95 Setup files are accessed and/or requested. The specific Windows 95 components required varies depending on the user's choices in the Internet Setup Wizard and the current configuration. By default, Batch Mode Setup does not run the Internet Setup Wizard.

Prerequisites also can include one or more of the following:

  • Modem and Internet account information

  • Modem and willingness to enroll in the MSN

  • Network connection using TCP/IP

  • A network proxy server and connection information

Desktop Themes

Each of the 12 Desktop Themes coordinate a wallpaper, system icons, sounds, mouse cursors, and a screen saver for a particular theme. A Desktop Theme can be a useful medium for creating a corporate look for your brand of computers. Desktop Themes do not require any additional Windows 95 components.

To control whether or not Microsoft Plus! Setup installs Desktop Themes

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #34 by changing the batch field to YES (to install Desktop Themes) or NO (not to install Desktop Themes).

Specifying the Desktop Theme to Be Applied by Setup

By default, if you specify that a Desktop Theme be installed, the Windows 95 theme is installed. You can specify a different theme if you want.

To specify that Setup should apply a theme other than the default

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #2007 by changing the Title field to specify the Desktop Theme you want. The name must be the long filename (as it appears on object lines 81-92), plus the filename extension. For example, to have Setup install the Inside Your Computer theme, you would change the Title field to the following:

    2007 yes Inside Your Computer (high color).theme 
    Þ CustomAction…
    

Enabling/Disabling Installation of Sound Files

If the system has no sound card, you can control whether Setup installs the sound files.

To control whether Setup installs the sound files

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object lines #2025 and #2026 by changing the batch field to YES (to install sound files) or NO (not to install them).

Dial-Up Networking Server

The Dial-Up Networking server allows a system to accept incoming calls from other computers and then allows the calling computer to connect to shared directories and other shared resources.

To control whether Setup installs the Dial-Up Networking server

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #35 by changing the batch field to YES (to install the Dial-Up Networking server) or NO (not to install the Dial-Up Networking server).

Required Windows 95 Components and Other Prerequisites

Dial-Up Networking Server is an extension of the Windows 95 Dial-Up Networking component. Dial-Up Networking is not installed during a typical Windows 95 setup. To install Microsoft Plus! Dial-Up Networking Server without user intervention, do one of the following:

  • Ensure that the Windows 95 installation files are accessible during Microsoft Plus! Setup.

  • Ensure that Dial-Up Networking Client is installed during Windows 95 Setup.

  • Disable Dial-Up Networking Server installation.

A modem (and Windows 95 modem drivers) are required to use Dial-Up Networking.

3-D Pinball

Unlike the Desktop Themes sounds, the sound files for 3D Pinball are always installed whether or not you have a sound card.

To control whether Setup installs 3-D Pinball

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #36 by changing the batch field to YES (to install 3D Pinball) or NO (not to install 3D Pinball).

Visual Enhancements

If you install Desktop Themes but not Visual Enhancements, then some Visual Enhancements are installed anyway, but they might not be activated. To ensure that Setup does not install any visual enhancements, disable installing both Visual Enhancements and Desktop Themes.

To control whether Setup installs the Microsoft Plus! Visual

  1. Open the PLUS.STF file in Windows 95 WordPad.

  2. Modify object line #37 by changing the batch field to YES (to install visual enhancements) or NO (not to install them).

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.