Copyright: © Copyright FTP Software, Inc. 1997. All rights reserved.
Citation: © Copyright FTP Software, Inc. 1997. All rights reserved.


chaining: The ability to use the functions of one NOS through the interface of another NOS.

The FTP Software Network Driver can chain to any other NOS that supports chaining. For example, if FTP Software Network Driver is “chained” to a Microsoft network driver, you can access the FTP Software driver from a button that is added to the interface to the Microsoft network driver.


client: A computer running Windows 95 or Windows NT.


computer name: The name of a client machine on a network.


customization set: The group of files that includes a Setup information file and a set of Registry edit files, and that controls and defines an OnNet32 installation for a group or client.


group: A set of client machines, or a set of groups, or both. You define a group by whatever criteria you decide to use; you create a group by your actions in the Custom Install Manager program. Compare, however, to workgroup.


object pane: The right pane of the Custom Install Manager window. Displays the elements of a customization set for the group or client selected in the organization pane.


organization pane: The left pane of the Custom Install Manager window. Displays your mapped organization.


root: The top of your organizational structure. By default, this is named DB.


workgroup: The set of client machines that share a groupname as specified in the Network Identification properties of the client machines (not a TCP/IP subnet).


What is the Custom Install Manager
What is Custom Install Manager?

Custom Install Manager is a program that runs on Windows 95 or Windows NT and that lets you create customized installations of FTP Software, Inc. products for specific departments, groups, and individuals in your network. Users run these customized installations from a server on which you have installed an FTP Software product distribution from disks or from a CD-ROM.

Installing product distributions

To install product distributions for Windows 3.1 or Windows for Workgroups 3.11 on a network server, follow the instructions for setting up network installations in the product’s documentation (for example, in the OnNet16 Advanced User’s Guide).

To install product distributions for Windows 95 or Windows NT on a network server, run the product’s Setup program and select the Administrator type of installation. See the installation documentation for instructions about performing this type of installation.

These distributions contain the FTP Software programs and a default set of files required by the Setup (installation) program. The default set of files includes the Setup information file, also known as the installation script file. This file, named Setup.inf, specifies the dialog boxes that appear and the programs that are installed. The Setup information file is unique for each product. Use Custom Install Manager to create customized Setup information files that are not named Setup.inf.

Additional files

When you install Custom Install Manager, you install two additional files, to the folder you specify in the Choose Folder for Data Files dialog box:

The Registry file for the FTP Software TCP/IP stack (also known as the kernel) for Windows 95 systems. This Registry file provides IP, name server, and router configuration information with which the installation program configures a network adapter. Use Custom Install Manager to specify default or specific configuration information for network adapters, thereby creating customized kernel Registry files.

The customization database. The customization database maintains the structure of groups and clients and the related customization sets for your network. You can maintain a single database for your entire network, or you can maintain multiple databases, if you prefer.

When you use Custom Install Manager, you create “customization sets” that contain customized versions of the Setup information file and, for some Windows 95 products, the TCP/IP stack Registry file. You can create any number of customization sets for clients and for groups.

Before you start creating customization sets, print and read The Planning Phase.

Tip

While this release of Custom Install Manager is not optimized to manage a database that supports both OnNet32 and Secure Client distributions, it is possible to do so.

Look for this symbol ∇ in the Help file to view suggestions for managing both products in a single database.

 Related Topics


Using this help file

Because Custom Install Manager supports multiple FTP Software, Inc. products, you might find the program, and using this help file, somewhat complex. Viewing the Table of Contents for this Custom Install Manager online Help might assist you in planning how to read the information.

All users should read the following overview information:

The planning phase

What is Custom Install Manager?

Customization database

Getting ready to create customized installation sets

The Setup information file

If you are customizing installations for the FTP Software products for Windows 95 or Windows NT, you should read the following overview information.

The OnNet32 setup command line

If you are customizing installations for the FTP Software products for Windows 95 that install the FTP Software TCP/IP stack, you should read the following overview information:

Registry files

If you are customizing installations for the FTP Software products for Windows 3.1 and Windows for Workgroups 3.11, you should read the following overview information:

The OnNet16 setup command line

Tips

Many How To... topics apply to all or multiple FTP Software, Inc. products. However, the Table of Contents repeats these topics in each product listing. The only way to be certain that a How To... topic applies to your product is to consult the Table of Contents, with the exception that topic titles that contain the term OnNet16 apply only to that product (or other 16-bit products).

Since this overview information is lengthy, you might prefer to print the topics listed here.


Managing multiple products
∇ Managing multiple products

While this release of Custom Install Manager is not optimized to manage a database that supports more than one product each of the 32-bit type and the 16-bit type, it is possible to do so.

For example, you can use Custom Install Manager to manage Secure Client and OnNet32 installations. With some planning, you can manage both types of client installations in a single database. If you prefer, you can install Custom Install Manager on two different computers and use two different databases; then you can manage Secure Client installations from one computer, and OnNet32 installations from another.

This online Help topic describes how to manage multiple products of the same type in a single database. The procedures describe how to manage both Secure Client and OnNet32 installations, but you can apply the same process to any two products with the same Setup information file structure.

Typically, 32-bit products that succeed OnNet32 will share the same Setup information file structure as OnNet32 and 16-bit products that succeed OnNet16 will share the same Setup information file structure as OnNet16.

If you customize installations for both OnNet32 and OnNet16, the Options properties for each product lets you specify a different setting in the Customization Sets Folder for each product and Custom Install Manager installs customization sets for each product in the specified folder.

However, when you create customized installation sets for still another product, such as Secure Client, you need to associate a separate Setup information file and customization sets folder with each product.

You can associate a Setup information file by creating a true default customization set for each product, as described in the first procedure that follows, and then create further customization sets from that set, as described in the procedures described in this topic.

However, Custom Install Manager can maintain only two default customization sets folder settings: one 32-bit type and one 16-bit type product. It does not maintain a link to the folder in the customization set description. Each time you create a customization set for a product (if you have multiple products of the same type), you need to set the default customization sets folder for that type product.

To manage multiple products in a single database

1	Create two fictional groups, named, for example, Secure Client and OnNet32.

2 	On the Tools menu, click Options and then click the OnNet32 page.

3	In the Setup information template box, specify the Setup information file (Setup.inf) that came with the OnNet32 distribution. You can browse to the file, or type the full pathname.

4	In the organization pane, with the right mouse button, click the OnNet32 group.

5	On the pop-up shortcut menu, point to New and then Customization Set, and click Create from the Default Template.

6 	Again, on the Tools menu, click Options and then click the OnNet32 page.

7	This time, in the Setup information template box, specify the Setup information file (Setup.inf) that came with the Secure Client distribution. You can browse to the file, or type the full pathname.

8	In the organization pane, with the right mouse button, click the Secure Client group.

9	On the pop-up shortcut menu, point to New and then Customization Set, and click Create from the Default Template.

10	Create groups and clients that reflect your network structure.

To assign a Secure Client customization set

1 	On the Tools menu, click Options and then click the OnNet32 page.

2	In the Customization Sets Folder box, specify the folder where you want to keep Secure Client customization sets, typically the same folder that contains the Secure Client distribution. You can browse to the folder, or type the full path.

3	With the right mouse button, click a group or client.

4	On the pop-up shortcut menu, point to New and then Customization Set, and click Create a Copy of an Existing Set.

5	In the Copy Customization Set dialog box, click the Secure Client group you created.

To assign an OnNet32 customization set

1 	On the Tools menu, click Options and then click the OnNet32 page.

2	In the Customization Sets Folder box, specify the folder where you want to keep OnNet32 customization sets, typically the same folder that contains the OnNet32 distribution. You can browse to the folder, or type the full path.

3	With the right mouse button, click a group or client.

3	On the pop-up shortcut menu, point to New and then Customization Set, and click Create a Copy of an Existing Set.

4	In the Copy Customization Set dialog box, click the OnNet32 group you created.

Notes

The files and folders you specify in the Options properties are the default settings for the database, one for each type of product (32-bit and 16-bit). The settings for this information are maintained in the Registry. These settings are the templates Custom Install Manager uses when you click Create a Customization Set from the Default OnNet32 Template or Create a Customization Set from the Default OnNet16 Template.

For multiple products of the same type, consider the fictional groups your true default customization sets and choose Create a Copy of an Existing Set. The database maintains the links between a group or client and the Setup information file used by that group or client.

You can  minimize the number of times you need to perform Step 2 of the Assign a customization set procedure by creating all your OnNet32 customization sets, and then creating all your Secure Client customization sets. Once you change the customization sets folder, the database uses the same folder for all subsequent customization sets you create, until you change the folder again.

You can use the same default TCP/IP Registry file for both OnNet32 and Secure Client customization sets.

 Related Topics


The planning phase

In Custom Install Manager you can build a hierarchical structure of groups and clients that reflects your network structure. In this context, a client is an individual PC and a group is a set of clients or a set of other groups, or both. With proper planning, you can use the hierarchical structure to minimize the data entry required to prepare customization sets for the clients on your network.

The planning phase requires that you map your network and determine what installation information you can specify at each level of your organization. For example, you can create a default customization set in which you specify your company name and the serial number and license key that all clients will use. You enter this information once, and Custom Install Manager can copy that information to customization sets that you subsequently create.

Map the network organization

Before you start using Custom Install Manager, you should map the organization of your network in terms of how you plan to distribute FTP Software products. The sample organization plan assumes that the network structure reflects the corporate structure; if your network does not reflect your corporate structure, you should base your organization plan for Custom Install Manager on the network.

Some questions to ask as you plan this organization include:

Will certain departments or groups install the same programs?

Will certain departments, groups, or individual clients share programs from the server (that is, perform a Client installation)?

Will certain departments, groups, or individual clients use the FTP Software TCP/IP protocol stack (while others use the Microsoft TCP/IP protocol stack)?

If so,

— Does any department, group, or client use Dynamic Host Configuration Protocol (DHCP) to provide IP configuration?

— Do any departments, groups, or individual clients, share common elements of an IP configuration, such as name servers or routers, or both?

— Do any departments or groups belong to the same workgroups as specified in the Network Identification properties of the client machines?

Using these principles, and similar guidelines that apply to your organization, plan a “tree” structure that reflects this organization. The tree can have as many levels as you need.

The following example demonstrates the complexity of a sample organization that the installation customization program can help you manage:

When you create a customization set for a group or client, Custom Install Manager names the Setup information file with the same root name as the name you give the group or client. Because Setup searches, by default, for .inf files preceded by the computer name or workgroup (and because Custom Install Manager names .inf files according to the name of the client or group), FTP Software suggests the following:

If any groups in your network have specific workgroup names specified in the Network Identification properties of the client machine, name their lowest level groups according to workgroup name.

Name the clients according to computer name.

Prepare customization sets

You can work from the top of the organization down, specifying a customized installation set, for example, for the Sales department, modifying the set somewhat for Domestic Sales and within it for the Educational Sales group, and further customizing the set for two specific workers, Kim and Leslie. Or, Kim can use the custom installation for the Sales department, or for any group or subgroup, and Leslie can use a specific customized installation. Likewise, the Corporate Sales group might not need a specifically customized installation and can use the Sales custom installation.

In fact, Custom Install Manager does not work strictly hierarchically, since any group or client can derive its customization set from any other customization set. However, after you have established a customization set, you can only modify it directly; changing items in a parent customization set does not change items in sets derived from it, nor do changes to derived sets apply to the parent set.

The following table suggest changes to the customization sets to make at each level of your organization:

Level	Specify this item
Corporate	Company name
Corporate	Serial number
Corporate	License key
Corporate or Group	TCP/IP stack (FTP Software or Microsoft)
Corporate or Group	Time zone
Group	Folders for program files and data files
Group	Dialog boxes displayed
Group	Subnet mask
Group	Domain name
Group	Name servers; whether to use DHCP
Group	NIS name resolution
Group	Routers; whether to use router discovery
Group	Whether program files are shared from a server or installed to the local hard drive
Group	Chaining order for network drivers
Group or User	Type of installation
Group or User	Components; specify programs and groups of programs to install
Group or User	Network card driver and serial protocol
User	User name
User	IP address
Tips

You cannot modify the contents of the default customization set that Custom Install Manager installs and starts using. To create a true default set for your network, create a group and specify settings that apply to the whole network. Then, specify new Setup information and, if applicable, TCP/IP stack Registry file templates in the OnNet32 Options properties. You can then create customization sets for your groups and clients from the default customization set you created for each product. If your network uses multiple products from FTP Software, you will need to create a default customization set for each product.

Ccustomization sets for 16-bit products do not contain a TCP/IP stack Registry file, but do require Netcard.inf and Timezone.ini files. These files are available in the 16-bit distribution. You should keep them in the folder you specify as the Customization Sets Folder in the OnNet16 Options properties.

 Related Topics


The Setup information file

The Setup program operates on the information provided by a Setup information file that, at the time an installation is run, must be in the same folder as the Setup program. The Setup information file provides information to the Setup program that makes one installation distinct from another.

The default Setup information file, installed during an Administrator type of installation or by manually setting up a network installation, is named Setup.inf. However, when you add a customization set to a group or client, Custom Install Manager names the resulting Setup information file with the same name as the group or client. Because of this behavior by Custom Install Manager and because Setup searches, by default, for .inf files preceded by the computer name or workgroup name, you should optimally plan a naming scheme for your groups and clients based on workgroup names and computer names as specified in the Network Identification properties.

Default Setup information files

Setup uses an .inf file that matches one of the following descriptions, listed in the order that Setup searches:

computer_name.inf where computer_name is specified in the Network Identification properties of the client machine

workgroup.inf where workgroup is specified in the Network Identification properties of the client machine

Setup.inf

If you prefer, you or your users can specify the .inf file as an option to the setup command, as follows:

setup /h name.inf

where name.inf is the Setup information file to use.

Types of information

You can use Custom Install Manager to specify the following types of information (not every type applies to every product) in the Setup information file:

The dialog boxes that appear.

The default type of installation. Generally, if you prepare customization sets, this should be the Custom or Custom Install Manager type.

The default folders to use for program files and data files, such as session files and electronic mail messages.

Whether users run program files from a server or from the local hard drive.

User and company information; serial number and license key.

Which programs and sets of programs (components and subcomponents) Setup will install by default.

The default network card drivers and frame-type, and default serial protocol to use.

How FTP Software Network Driver (FTP NFS) and other network operating systems interoperate from File Manager, Print Manager, and Control Panel.

Whether Setup updates system files and whether Setup restarts the computer

Tips

The Setup information files you specify in the Options properties are the default settings for the database, one for each type of product (32-bit and 16-bit). These are the templates Custom Install Manager uses when you click Create a Customization Set from the Default OnNet32 Template or Create a Customization Set from the Default OnNet16 Template.

By default, this file is Setup.inf. However, you cannot make any changes to Setup.inf. You can create another .inf file (by first creating a fictional group) and use that file, which you can modify, as the default for the database. To use this .inf file during an installation, you or your users must specify the new default .inf file (using the setup /h name.inf command).

If you use Custom Install Manager to customize installations for multiple FTP Software products of the same type, you should create fictional groups for each product and assign a customization set to each. Then, consider the fictional groups your true default customization sets; when you create a customization set for a group or client, choose Create a Copy of an Existing Set.

For those products that have a TCP/IP stack Registry file, the Setup information file also specifies which such file to use. Installations that you create from Custom Install Manager use a stack Registry file of the same root name as the Setup information file.

 Related Topics


Registry files

A Registry (.reg) file provides information that Setup must enter in the Windows Registry. A Registry file also moves, deletes, or otherwise processes program data files.

Custom Install Manager lets you create a Registry file for the FTP Software TCP/IP protocol stack for Windows 95. This Registry file specifies the IP configuration for a client. You can specify the use of DHCP (Dynamic Host Configuration Protocol), or set all or part of the IP, DNS, and router configuration.

Tips

The default Registry file template for the FTP Software TCP/IP protocol stack, as specified in the Options properties, is the default template for all products that use a Registry file. This is the template Custom Install Manager uses when you create a customization set for a group or client from the default OnNet32 template.

You can use the same kernel Registry file as the default template for all FTP Software products (for Windows 95) that install the FTP Software TCP/IP stack. You can keep the template file in any folder.

By default, this file is Setup_k.reg, which the Custom Install Manager Setup program installs in the Data Files folder. However, you cannot make any changes to Setup_k.reg. You can create another .reg file (by first creating a group) and specify that file, which you can modify, as the default template for the database.

If you want Setup to use this .reg file, you or your users should specify the corresponding .inf file (using the setup /h name.inf command) and, in this case, you should keep both files in the same folder as the product distribution.

The Setup information file specifies the TCP/IP stack Registry file to use. Installations that you create from Custom Install Manager use a TCP/IP stack Registry file of the same root name as the Setup information file.

 Related Topics


Customization database
The customization database

The customization database contains information for the customized installations you create. It provides information regarding the actual files used in every customization set.

The database maintains the group and client hierarchy that you design and associates the Setup information and, if applicable, the TCP/IP Registry file, that you assign to a group or client.

However, the database does not store specific information for an installation. That information is stored in the Setup information and Registry files.

Tip

To manage large networks you might want to create more than one database. To do so, use Windows Explorer or My Computer to copy an existing database (files with a .mdb extension are database files). Then use the Custom Install Manager General Options properties to open the new database.

 Related Topics


The OnNet32 setup command line

You can use the setup command line with options in batch files to further streamline installations on your network.

To start the Setup program from a command line, enter a setup command with this format:

setup [/f] [/h filename] [/s path] [/u]

where

/f	Runs Setup to add programs to the Start menu for the current user. After the initial installation on a computer, use setup /f for additional users on computers that are set up for multiple users. On Windows NT, you must run the initial installation with administrator privileges.

/h filename.inf	Specifies a file to use as the Setup information file. By default Setup uses an .inf file that matches one of the following descriptions, listed in the order that Setup searches:

computer_name.inf where computer_name is specified in the Network Identification properties of the client machine

workgroup.inf where workgroup is specified in the Network Identification properties of the client machine

Setup.inf

Use /h filename.inf to specify an .inf file that does not match one of the preceding.

/s path	Specifies a folder that contains the distribution. Use setup /s path when the distribution is not in the same folder as the Setup program. For example, the Setup.lst file for the OnNet32 distribution on disks uses this option to run the Setup program from a temporary folder on the local hard drive.

/u	Runs Setup in unattended mode. Setup suppresses all dialog boxes that require user interaction and either exits the Setup program or restarts the computer, depending upon the default behavior specified in the Reboot dialog box.

Tip

You can use Custom Install Manager to suppress the display of specific dialog boxes. The Windows Messaging Setup program, available in some FTP Software Inc. products, cannot be suppressed; if you install Mail OnNet, users will need to provide responses to the Windows Messaging Setup dialog boxes.

 Related Topics


The OnNet16 setup command line

You can use the setup command line with options in batch files to further streamline installations on your network.

To start the Setup program from a command line, enter a setup command with this format:

setup [/d] [/h filename] [/s path]

where

/d	Specifies that Setup not detect network drivers.

/h filename.inf	Specifies a file to use as the Setup information file. By default Setup uses an .inf file that matches one of the following descriptions, listed in the order that Setup searches:

computer_name.inf where computer_name is specified in the Network Identification properties of the client machine

workgroup.inf where workgroup is specified in the Network Identification properties of the client machine

Setup.inf

Use /h filename.inf to specify an .inf file that does not match one of the preceding.

/s path	Specifies a folder that contains the distribution. Use setup /s path when the distribution is not in the same folder as the Setup program. For example, the Setup.lst file for the OnNet16 distribution on disks uses this option to run the Setup program from a temporary folder on the local hard drive.

 Related Topics


Getting ready to create customized installations
To get ready to create customized installations

1	Map the organization of your network in terms of how you plan to distribute the FTP Software, Inc. products.

2	Run the Setup program from a client PC and, when prompted to choose a type of installation, click Administrator. Complete the installation, which creates a distribution on a server (from which clients can install the product).

-or-

For 16-bit products, set up a network installation as described in the product documentation (for example, in the OnNet16 Advanced User’s Guide).

3	Install Custom Install Manager on a PC that is using the Windows 95 or Windows NT operating system and that has network connectivity.

4	In the Choose Folder for Data Files dialog box, choose a folder for Setup to install the database file (and the .reg file for Windows 95 installations that include the FTP Software TCP/IP stack).

5	On the Start menu, click the FTP Custom Install Manager program.

6	In the organization pane, create groups and clients, based on the organization map you have already planned.

If you plan to create a customization set for a Windows 3.1 group or client, limit the name of the group or client to 8 letters. Custom Install Manager creates files based on the name and the 16-bit Setup program does not work with Setup information files that exceed the DOS 8.3 naming conventions.

7	Create true default customization sets for each product and specify the resulting Setup information and, if applicable, TCP/IP stack Registry files in each page of the Options properties.

8	Create customization sets for groups and clients.

9	On the client computer, map the network server to a drive letter and run the Setup program for the FTP Software, Inc. program. Ensure that the Setup information (*.inf) file for the client is in the same folder as the Setup program. Read The OnNet32 setup command line or The OnNet16 setup command line to learn the Setup command line options for the product you are installing.

Notes

By default, Setup installs Custom Install Manager program files to C:\Program Files\FTP Software\CIM.

To most effectively use Custom Install Manager and customization sets, plan a naming scheme for your groups and clients based on workgroup names and computer names as specified in the Network Identification properties of the client machine.

 Related Topics


Creating a new group
To create a new group

1	In the organization pane, click the root or a group to which the new group belongs.

2	On the File menu, point to New, and click Group.

-or-

With the right mouse button, click the root or group; on the pop-up shortcut menu, point to New and click Group.

-or-

On the toolbar, click New Group.

3	Type the name of the group.

Notes

The new group does not yet have a customization set applied to it. Unless you want this group to use the default Setup.inf file on the server, you must create a new customization set.

If you plan to create a customization set for a Windows 3.1 group, limit the name of the group to 8 letters. Custom Install Manager creates files based on the name and the 16-bit Setup program does not work with Setup information files that exceed the DOS 8.3 naming conventions.

To most effectively use Custom Install Manager and customized installation sets, plan a naming scheme for your groups and clients based on group names and computer names as specified in the Network Identification properties of the client machine.

 Related Topics


Creating a new client
To create a new client

1	In the organization pane, click the group to which the client belongs.

2	On the File menu, point to New, and then click Client.

-or-

With the right mouse button, click the group; on the  pop-up shortcut menu, point to New and click Client.

-or-

On the toolbar, click New Client.

3	Type the name of the client.

Notes

The new client does not yet have a customization set applied to it. Unless you want this client to use the default Setup.inf file on the server, you must create a new customization set.

If you plan to create a customization set for a Windows 3.1 client, limit the name of the client to 8 letters. Custom Install Manager creates files based on the name and the 16-bit Setup program does not work with Setup information files that exceed the DOS 8.3 naming conventions.

To most effectively use Custom Install Manager and customized installation sets, plan a naming scheme for your groups and clients based on group names and computer names as specified in the Network Identification properties of the client machine.

 Related Topics


Deleting groups and clients
To delete a group or client

1	In the organization pane, click the group or client.

2	On the File menu, point to Delete, and click Selected Item.

-or-

With the right mouse button, click the root or group; on the pop-up shortcut menu, point to Delete, and click Selected Item.

Note

You should not delete a group whose Setup information and TCP/IP stack Registry files are the templates for your database. If you do, you will not be able to reuse the group name or edit the templates.

 Related Topics


Removing customization sets
To remove a customization set

1	In the organization pane, click the group or client.

2	On the File menu, point to Delete, and click Customization Set.

-or-

With the right mouse button, click the root or group; on the pop-up shortcut menu, point to Delete, and click Customization Set.

 Related Topics


Creating customization sets from a default template
To create a customization set from a default template

1	In the organization pane, click a group or client.

2	On the File menu, point to New, and click Customization Set.

-or-

With the right mouse button, click the group or client; on the pop-up shortcut menu, point to New and click Customization Set.

3	Click Create from the Default OnNet16 Template or Create from the Default OnNet32 Template to copy the default customization set templates (specified by the Setup Information and, if applicable, TCP/IP Stack templates in the Options properties).

4	In the object pane, double-click the Setup information file to modify the Setup information and, if applicable, double-click TCP/IP Protocol Stack to modify the IP configuration.

Tips

You can create true default customization sets for each FTP Software product.

To do so, create fictional groups for each FTP Software product and assign them new customization sets. Then, modify the customization sets with basic information that applies to your whole network.

In the pages of the Options properties, you can set the default Setup information and, if applicable, TCP/IP stack Registry files to those you created for this fictional group. Or you can click Create a Copy of an Existing Set and choose the default customization set you created for the product. In either case, before you create each customization set, ensure that the Customization Sets Folder in the Options properties page for the applicable product type (32-bit or 16-bit) is set to the correct folder for that product.

 Related Topics


Creating customization sets from another customization set
To create a customization set from another customization set

1	In the organization pane, click a group or client.

2	On the File menu, point to New, and click Customization Set.

-or-

With the right mouse button, click the group or client; on the pop-up shortcut menu, point to New and click Customization Set.

3	Click Create a Copy of an Existing Set to copy another customization set.

4	In the Copy Customization Set dialog box, click Select All to view every customization set.

-or-

Click Select OnNet16 Customization Sets or Select OnNet32 Customization Sets to view the customization sets you have created only for that product.

5	Click the customization set to copy.

6	In the object pane, double-click the Setup information file to modify the Setup information and, if applicable, double-click TCP/IP Protocol Stack to modify the IP configuration.

Tips

When you create the customization set from an existing set, be sure to choose a customization set for the appropriate product.

You can create true default customization sets for each FTP Software product.

To do so, create fictional groups for each FTP Software product and assign them new customization sets. Then, modify the customization sets with basic information that applies to your whole network.

In the pages of the Options properties, you can set the default Setup information and, if applicable, TCP/IP stack Registry files to those you created for this fictional group. Or you can click Create a Copy of an Existing Set and choose the default customization set you created for the product. In either case, before you create each customization set, ensure that the setting for the Customization Sets Folder in the Options properties page for the applicable product type (32-bit or 16-bit) is set to the correct folder for that product.

 Related Topics


Specifying the default components to install
To specify the default components to install

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Components Dialog.

4	In the Dialog Properties list, double-click Choose Components.

5	In the Components list of the Choose Components dialog box, click the check box beside a component to select or clear it.

A check mark indicates that the component will be installed.

Tips

To apply the changes to the default list of components, you or users must choose the Custom Install Manager (for 16-bit products, the Custom) type of installation.

Before you create a customization set for a client, configure the components and subcomponents for the parent group. Then create the customization set for the client, based on the customization set of its parent.

To prevent users from changing the default components, clear the Dialog Visible During Install check box, and Setup will not display the Choose Components dialog box. Also, except for 16-bit products, clear the same check box for the Choosing the Installation Type dialog box to prevent users from choosing a Custom type installation that, if selected, displays the Choose Components dialog box.

 Related Topics


Specifying the default subcomponents to install
To specify the default subcomponents to install

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Components Dialog.

4	In the Dialog Properties list, double-click Choose Components.

5	In the Components list of the Choose Components dialog box, click the text of a component to select it.

6	In the same Choose Components dialog box, click View Subcomponents.

7	In the new Choose Components dialog box, click the check box beside a subcomponent to select or clear it.

A check mark indicates that the subcomponent will be installed.

Tips

The Custom Install Manager (for 16-bit products, the Custom) type of installation contains any changes you make to the list of subcomponents selected by default.

Before you create a customization set for a client, configure the components and subcomponents for the parent group. Then create the customization set for the client, based on the customization set of its parent.

 Related Topics


Setting IP configuration values
To set IP configuration values

1	In the organization pane, click a group or client.

2	In the object pane, double-click the TCP/IP stack Registry file.

3	In the Type of Configuration list, click Specify Addresses and type the IP address and subnet mask in the corresponding boxes.

4	Click Next.

5	In the Choose Name Servers dialog box, click DNS (Domain Name System) Servers and type the computer’s hostname and domain name in the corresponding boxes and, for each name server, type its IP address and click Add.

6	Click Next.

7	In the Define Routers dialog box, click I Will Specify Which Routers to Use and, for each router, type its IP address and click Add.

8	Click Finish to complete the configuration.

Tips

Before you create a customization set for a client, configure the subnet mask, routers, and DNS name servers for the parent group. Then create the customization set for the client, based on the customization set of its parent, and specify the client’s IP address.

This version of the Setup program supports only DNS name server configuration. You must enable and configure host table, WINS, and NIS name resolution at individual PCs, in the TCP/IP stack properties.

Whatever values you set for name server configuration and routing apply to all network adapters on a computer.

Any group or client can use a mix of static and dynamic configuration. For example, you can specify the IP addresses of each network adapter, but use DHCP for name resolution.

 Related Topics


Setting IP configuration values for OnNet16
To set IP configuration values for OnNet16

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click IP Configuration Dialog.

4	In the Dialog Properties list, double-click IP Configuration.

5	In the Configure Network Adapters dialog box, type the IP address and subnet mask in the corresponding boxes.

6	Click Next.

7	In the Define Routers dialog box, for each router, type its IP address and click Add. Click Finish.

8	In the Installation Dialogs list of the Setup Process Properties dialog box, click NIS and DNS Configuration.

9	In the Dialog Properties list, double-click NIS and DNS Configuration.

10	In the NIS and DNS Configuration dialog box, click DNS (Domain Name System) or NIS (Network Information Service) and type the computer’s hostname and domain name in the corresponding boxes.

If you are configuring NIS name service, type the NIS domain.

11	For each name server, type its IP address and click Add.

12	Click OK.

Tip

Before you create a customization set for a client, configure the subnet mask, routers, and DNS name servers for the parent group. Then create the customization set for the client, based on the customization set of its parent, and specify the client’s IP address.

 Related Topics


Specifying dynamic IP configuration
To specify dynamic IP configuration

1	In the organization pane, click a group or client.

2	In the object pane, double-click the TCP/IP stack Registry file.

3	In the Type of Configuration list, click Automatic (DHCP). Then click Next.

4	In the Choose Name Servers dialog box, click Use DHCP to Automatically Configure My Name Servers. Then click Next.

5	In the Define Routers dialog box, click Let the TCP/IP Stack Build the List.

6	Click Next to complete the configuration.

Tips

Before you create a customization set for a client, configure the use of DHCP (Dynamic Host Configuration Protocol) and router discovery for the parent group. Then create the customization set for each client, based on the customization set of its parent.

This version of the 32-bit Setup program supports only DNS name server configuration. You must enable and configure host table, WINS, and NIS name resolution at individual PCs, in the TCP/IP Stack properties.

Whatever values you set for name server configuration and routing apply to all network adapters on a computer.

Any group or client can use a mix of static and dynamic configuration. For example, you can specify the IP addresses of each network adapter, but use DHCP for name resolution.

 Related Topics


Specifying dynamic IP configuration for OnNet16
To specify dynamic IP configuration for OnNet16

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click IP Configuration  Dialog.

4	In the Dialog Properties list, double-click IP Configuration.

5	In the Type of Configuration box of the Configure Network Adapters dialog box, click Automatic (DHCP).

Tips

If you specify dynamic IP configuration, Setup does not display the Name Server Configuration dialog box.

Before you create a customization set for a client, configure the use of DHCP (Dynamic Host Configuration Protocol) for the parent group. Then create the customization set for the clients, based on the customization set of its parent.

 Related Topics


Searching for groups or clients
To search for a group or client

1	In the organization pane, click the root or a group.

2	On the Tools menu, click Find.

3	Type the client or group name.

4	Click Find.

Note

Find searches the organization from the top of the selected group down; it does not wrap to the top of the organization.

 Related Topics


Specifying the name of a user
To specify the name of a user

1	In the organization pane, click a client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click User Information Dialog.

4	In the Dialog Properties list, double-click Name.

5	In the Value Label box of the User Information Dialog: Name dialog box, type the name of the user.

 Related Topics


Specifying the username of an OnNet16 client
To specify the username of an OnNet16 client

1	In the organization pane, click a client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Username.

4	In the Dialog Properties list, double-click Name.

5	In the Value Label box of the User Name: Name dialog box, type the client’s username as recognized by network hosts.

 Related Topics


Specifying the company name
To specify the company name

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click User Information Dialog.

4	In the Dialog Properties list, double-click Company.

5	In the Value Label box of the User Information Dialog: Company dialog box, type the company name.

Tip

Before you create a customization set for a client, specify the company name for the root or parent group. Then create the customization set for the client, based on the customization set of its parent.

 Related Topics


Specifying the serial number
To specify the serial number

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click User Information Dialog.

4	In the Dialog Properties list, double-click Serial Number.

5	In the Value Label box of the User Information Dialog: Serial Number dialog box, type the serial number.

Tip

Before you create a customization set for a client, specify the serial number for the root or parent group. Then create the customization set for the client, based on the customization set of its parent.

 Related Topics


Specifying the license key
To specify the license key

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click User Information Dialog.

4	In the Dialog Properties list, double-click License Key.

5	In the Value Label box of the User Information Dialog: License Key dialog box, type the license key.

Tip

Before you create a customization set for a client, specify the license key for the root or parent group. Then create the customization set for the client, based on the customization set of its parent.

 Related Topics


Specifying the OnNet16 serial number
To specify the OnNet16 serial number

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Serial Number and License Key.

4	In the Dialog Properties list, double-click Serial Number.

5	In the Value Label box of the User Information Dialog: Serial Number dialog box, type the serial number.

Tip

Before you create a customization set for a client, specify the serial number for the root or parent group. Then create the customization set for the client, based on the customization set of its parent.

 Related Topics


Specifying the OnNet16 license key
To specify the OnNet16 license key

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Serial Number and License Key.

4	In the Dialog Properties list, double-click License Key.

5	In the Value Label box of the User Information Dialog: License Key dialog box, type the license key.

Tip

Before you create a customization set for a client, specify the license key for the root or parent group. Then create the customization set for the client, based on the customization set of its parent.

 Related Topics


Opening another database
To open another database

1	On the Tools menu, click Options.

2	In the Database File box, type the pathname of, or browse to, another database file.

Tip

∇	Creating multiple databases is one way to support both Secure Client and OnNet32 client installations. If you do this, be sure to set the default setup information file, in the OnNet32 Options properties, to that of the appropriate product when you open the other database.

 Related Topics


Specifying the Setup information file template
To specify a Setup information file template

1	Create a fictional group or client and assign a new customization set to it. Specify default Setup information file settings for your network.

2	On the Tools menu, click Options.

3	Click the product page.

4	In the Setup Information Template box, type the filename of, or browse to, the Setup information file you created in step 1.

Notes

If you use Custom Install Manager to customize installations for multiple FTP Software, Inc. products, you should create fictional groups or clients for each and assign applicable customization sets to each.

The Setup information file template for 16-bit products cannot be used for 32-bit products, nor can the Setup information file template for 32-bit products be used for 16-bit installations.

The Setup information file templates are used by all databases you open.

∇	If you use separate databases for Secure Client and OnNet32 client installations, be sure to set the default setup information file, in the OnNet32 Options properties, to that of the appropriate product when you open another database.

 Related Topics


Specifying the TCP/IP stack Registry file template
To specify the TCP/IP stack Registry file template

1	Create a fictional group or client and assign a new customization set to it. Specify default IP configuration settings for your network.

2	On the Tools menu, click Options.

3	Click the product page.

4	In the TCP/IP Stack Registry file box, type the filename of, or browse to, the TCP/IP stack Registry file you created in step 1.

Note

The TCP/IP stack Registry file template is used by all databases you open.

 Related Topics


Specifying the customizations sets folder
To specify the customization sets folder

1	On the Tools menu, click Options.

2	Click the product page.

3	In the Customization Sets Folder box, type the pathname of, or browse to, the folder you want to use.

Tips

If you customize installations for OnNet32 and OnNet16, the Customization Sets Folder for each product lets you specify a different folder for each and Custom Install Manager adds customization sets for each product to the specified folder.

However, to create customization sets for Secure Client, you need to set the Customization Sets Folder on the OnNet32 Options page to the folder that contains the Secure Client distribution. The database can only associate a default customization sets folder for one 32-bit and one 16-bit product.

Since, at the time the Setup program is run, the customization sets must be in the same folder as the product distribution, you should set the Customization Sets Folder to the same folder as the product distribution.

If you do not keep your customization sets in the same folder as the product distribution, you should copy the Netcard.inf and Timezone.ini files from the product distribution to the customization sets folder for any 16-bit product. Both the 16-bit Setup program and Custom Install Manager need the Netcard.inf file to configure the TCP/IP stack and the Timezone.ini file to set a default time zone for the Network Time program.


Specifying the dialog or message boxes to display
To specify the dialog or message boxes to display

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click the name of a dialog or message box.

4	In the Dialog Properties list, double-click Dialog Visible During Install to select or clear it.

A check mark indicates that Setup will display the dialog box during the installation.

5	Repeat steps 3 and 4 for each dialog or message box.

Tip

To suppress all dialog boxes (except in the case of 16-bit installations), run the setup command with the /u option. However, the Windows Messaging Setup program cannot be suppressed; if you install Mail OnNet, users will need to provide responses to the Windows Messaging Setup dialog boxes.

 Related Topics


Setting computer or workgroup names
To set a computer or workgroup name

In Windows 95 or Windows NT

1	On the Start menu, point to Settings and click Control Panel.

2	Double-click the Network icon.

3	Click the Identification page.

4	Type a computer name or workgroup name, or both, in the text boxes.

In Windows for Workgroups

1	In Program Manager, generally in the Main program group, double-click Control Panel.

2	In the Control Panel program group, double-click Network.

3	If the InterDrive Options dialog box appears, click Cancel.

4	In the Microsoft Windows Network dialog box, type a computer name or workgroup name, or both, in the text boxes.

Note

You can perform these steps at each computer, or, for Windows 95 or Windows NT, you can use Windows system policy editor and user profiles.


Specifying the default installation type
To specify the default installation type

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Install Type Dialog.

4	In the Dialog Properties list, double-click Choose Install Type.

5	In the Choose Default Installation Type list box, click an installation type.

Tips

The Custom Install Manager type of installation contains any changes you make to the list of components selected by default.

The default type becomes the first type in the list; you can view the result by clicking OK to close the Choose Installation Type dialog box, OK again to close the Setup Process Properties dialog box, and then reopening the Choose Installation Type dialog box.

To enforce this type of installation, suppress the display of this dialog box during installation.

 Related Topics


Specifying the default OnNet16 installation type
To specify the default OnNet16 installation type

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Install Type Dialog.

4	In the Dialog Properties list, double-click New, Upgrade, or Reinstallation.

5	In the Choose Default Installation Type list box, click an installation type.

Tips

The Custom type of installation contains any changes you make to the list of components selected by default.

To enforce this type of installation, suppress the display of this dialog box during installation.

 Related Topics


Specifing the program files folder
To specify the program files folder

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Install Type Dialog.

4	In the Dialog Properties list, double-click Choose Install Type.

5	In the Choose Install Type dialog box, in the Copy Program Files to Folder box, click Change.

6	In the Choose a Folder list, click [Program Files] to install the programs to the folder specified by the ProgramFilesDir entry in the Registry.

-or-

Click [Windows Drive] to install the programs to the drive that contains the Windows installation.

-or-

Click Custom to specify another pathname.

7	Click Apply and type the name of the subfolder.

Tip

To enforce the default folder, suppress the display of this dialog box during installation.

 Related Topics


Specifying the OnNet16 destination directory
To specify the OnNet16 destination directory

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Destination Directory.

4	In the Dialog Properties list, double-click Destination Directory.

5	To use the FTP Software default, click c:\pctcp in the Choose a Folder list, then click Apply and OK.

To install the product to the drive that contains the Windows installation, click [Windows Drive] in the Choose a Folder list, click Apply, and type a folder name in the Destination Path box.

To specify both a specific drive and folder, click [Custom], click Apply, type the folder name, and click OK.

Tip

To enforce the default folder, suppress the display of this dialog box during installation.

 Related Topics


Sharing program files
To share program files

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Install Type Dialog.

4	In the Dialog Properties list, double-click Share Program Files.

5	In the Share Program Files dialog box, click Yes.

Notes

This setting applies only to the Custom Install Manager installation type (and not to the 16-bit product).

To enforce sharing of program files, set the Custom Install Manager to be the default type of installation and suppress the display of the Choose Installation Type dialog box during installation.


Specifying the data files folder
To specify the data files folder

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Data File Folder.

4	In the Dialog Properties list, double-click Choose Data Files Location.

5	In the Choose a Folder list, click [Program Files] to install the data files to the folder specified by the ProgramFilesDir entry in the Registry.

-or-

Click [Windows Drive] to install data files to the drive that contains the Windows installation.

-or-

Click Custom to specify another pathname.

6	Click Apply and type the name of the subfolder.

Tip

To enforce the data files folder, suppress the display of the Choose Folder for Data Files dialog box during installation.


Setting the default exit behavior
To set the default exit behavior

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Reboot Dialog.

4	In the Dialog Properties list, double-click Restart the Computer After the Installation.

5	Click Yes to restart the computer after the installation.

-or-

Click No to exit the setup program without restarting the computer.

Tip

To enforce the default behavior, suppress the display of this dialog box during installation.


Enforcing the installation of the FTP Software TCP/IP stack
To enforce installation of the TCP/IP protocol stack

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Components Dialog.

4	In the Dialog Properties list, double-click Choose Components.

5	Verify that a check mark appears beside TCP/IP and Accessories. If it does not appear, click the check box and close the Choose Components dialog box.

6	In the Installation Dialogs list of the Setup Process Properties dialog box, click NDI Foreign Dialog.

7	In the Dialog Properties list, double-click Specify the Default Choice.

8	In the NDI Foreign Dialog: Replace dialog box, click Yes.

Tip

To prevent users from changing the components, for both the Choose Components Dialog and the NDI Foreign Dialog boxes, in the Dialog Properties list, clear the Dialog Visible During Install check box.

 Related Topics


Specifying the default TCP/IP stack to use
To specify the default TCP/IP stack to use

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click NDI Foreign Dialog.

4	In the Dialog Properties list, double-click Specify the Default Choice.

5	In the NDI Foreign Dialog: Replace dialog box, click Yes to use the FTP Software stack.

-or-

Click No to use the Microsoft stack.

 Related Topics


Reorganizing groups and clients
To reorganize groups and clients

Use drag and drop.

Note

The state of the customization set does not change when you move a group or client; it does not acquire any settings from its new parent.


Viewing group or client properties
To view group or client properties

1	In the organization pane, click a group or client.

2	On the File menu, click Properties.

-or-

With the right mouse button, click the group or client; on the pop-up shortcut menu, point to New and click Properties.

-or-

On the toolbar, click Properties.


Renaming groups or clients
To rename a group or client

1	In the organization pane, click a group or client.

2	On the File menu, click Rename.

-or-

With the right mouse button, click the group or client; on the pop-up shortcut menu, point to New and click Rename.

-or-

Click the group or client then click it a second time. (Do not double-click it.)

3	Type the new name.


Renaming the database root
To rename the database root

1	Click the database root and, on the File menu, click Rename.

-or-

With the right mouse button, click the database root; on the pop-up shortcut menu, point to New and click Rename.

-or-

Click the database root then click it a second time. (Do not double-click it.)

2	Type the new name.

 Related Topics


Configuring a Network Card
To configure a network card

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click Network Card.

4	In the Dialog Properties list, double-click Configuration.

5	In the Network Card: Configuration dialog box, click the name of a network card; then click OK. In the next dialog box, which is specific to the network card, specify new default card settings or accept the defaults. You can click Additional to specify other settings, generally the software interrupt to the kernel.

-or-

Click Serial Port Using Slip or PPP; then click OK. In the Serial Port Using SLIP or PPP dialog box, click OK.

-or-

Click None so that the Setup program prompts the user for the information. Be sure to set the dialog box visible.

6	In the Dialog Properties list, double-click Show Driver Configuration? and specify whether Setup should prompt the user to configure the network card.

Tip

If network cards are already installed and configured on the computers, you do not need to repeat that configuration process in Setup. Setup detects the existing card and can use the existing configuration.

 Related Topics


The Install Type dialog box

The Install Type dialog box lets you specify the default type of installation and the folder where Setup will install the programs.

Installation types

When you create customization sets, you also create an additional installation type, Custom Install Manager. This type contains all the choices you make about the components to install and specifies whether the installation copies program files to the local hard drive or sets up the sharing of program files on a server. If you allow your users to view the Installation Type dialog box, they will see this choice listed, in addition to the choices normally provided by the installation program. You should instruct your users to choose the Custom Install Manager type, if you want them to install only the set of programs you have specified.

To specify the default installation type

In the Choose the Default Installation Type list box, click an installation type.

Tips

To verify the default installation type, click OK twice to exit the Install Type and Setup Process Properties dialog boxes. Then, reopen the Install Type dialog box. The new default installation type is the first type listed.

You can specify that, when users install a Custom Install Manager type, they share program files from a server by setting the Share Program Files property of the Install Type dialog box.

 Related Topics


The Data Files Destination dialog box

1	To install the data files to the folder specified by the ProgramFilesDir entry in the Registry, click [Program Files] in the Choose a Folder list.

-or-

To install the data files to the drive that contains the Windows installation, click [Windows Drive] in the Choose a Folder list.

-or-

To specify another pathname, click Custom.

2	Click Apply and type the name of the subfolder.


The Program Files Folder dialog box

1	In the Choose a Folder list, click [Program Files] to install the data files to the folder specified by the ProgramFilesDir entry in the Registry.

-or-

Click [Windows Drive] to install data files to the drive that contains the Windows installation.

-or-

Click Custom to specify another pathname.

2	Click Apply and type the name of the subfolder.


The Options properties

The following describes the entries you can make in the Options properties:

Option	Description
Database File	Specifies the filename of the database you are using. To open another database, click Browse.
Setup Information Template	Specifies the default Setup information file for the product and for related products. When you create a customization set from the default OnNet32 template, Custom Install Manager bases the resultant Setup information file on the Setup Information template you specify on the OnNet32 page. And when you create a customization set from the default OnNet16 template, Custom Install Manager bases the resultant Setup information file on the Setup Information template you specify on the OnNet16 page.
	By default, this file is Setup.inf. However, you cannot make any changes to Setup.inf. You can create another .inf file (by first creating a group) and use that file, which you can modify, as the default for the database. To use this .inf file during an installation, you or your users must specify the new default .inf file (using the setup /h name.inf command). To specify the new .inf file as the template for your database, click Browse.
TCP/IP Stack Registry edit file	Specifies the default TCP/IP Registry file for the OnNet32 product and for related products such as Secure Client. When you create a customization set from the default OnNet32 template, Custom Install Manager bases the resultant TCP/IP stack Registry file on the TCP/IP stack Registry edit file you specify on the OnNet32 page.
	By default, this file is Setup_k.reg. However, you cannot make any changes to Setup_k.reg. You can create another .reg file (by first creating a group) and use that file, which you can modify, as the default for the database. To use this .reg file during an installation, you or your users must specify the corresponding default .inf file (using the setup /h name.inf command). To specify the new .reg file as the template for your database, click Browse.
Customization Set Folder	Specifies the folder where Custom Install Manager stores the customization sets you create. To specify another folder in which to save the customization sets, click Browse.  When you create a customization set from the default OnNet32 template (or from any customization set based on the 32-bit type Setup information template), Custom Install Manager adds the files to the folder you specify on the OnNet32 page. When you create a customization set from the default OnNet16 template, Custom Install Manager adds the files to the folder you specify on the OnNet16 page. Since, at the time the Setup program is run, the customization sets must be in the same folder as the product distribution, you should set the Customization Set Folder to the same folder as the product distribution.
Save Window Positions When Exiting	Saves the current window size and the sizes of each pane, and restores the program with these settings.


The Setup Process Properties dialog box

The following describes the installation dialog boxes:

Dialog Box	Description
Welcome Dialog	Briefly explains the installation program and lets users view the installation notes.
License Dialog	Displays the license agreement between the user and FTP Software, Inc. and prompts users to accept the terms before proceeding with the installation.
Install Type Dialog	Prompts users to select a type of installation and to specify a path for the program files.
Reinstall Dialog	When a product is already installed, replaces the Install Type dialog box. Lets users choose whether to reinstall the same components, add new components, remove the product, or perform an Administrator type of installation.
User Information Dialog	Prompts users to enter their name, the company name, and the serial number and license key.
Data Files Folder Dialog	Prompts users to specify the folder for data files, such as mail messages and session files.
WinSock2 Dialog	Informs users that WinSock2 is installed and that the FTP Software TCP/IP stack (which does not provide WinSock2 or WinSock2 support) will not be installed. Advises users to contact FTP Software, Inc. for a version of the FTP Software TCP/IP stack that does support WinSock2.
Components Dialog	Lets users choose which programs are installed.
NDI Conflicts Dialog	When the Microsoft TCP/IP protocol stack is installed and users choose to install the FTP Software TCP/IP protocol stack (in the Choose Components dialog box), this dialog box advises users that Setup will replace the Microsoft stack with the FTP Software stack.
NDI Foreign Dialog	When the Microsoft TCP/IP protocol stack is installed and users choose an installation type that installs the FTP Software TCP/IP protocol stack by default, this message box prompts users to confirm the replacement of the Microsoft stack with the FTP Software stack.
Copyfiles Dialog	Displays the components that will be installed and prompts for final confirmation of the installation.
Configure Message Box	Informs users that the next step is to configure a modem, if installed, and network adapter(s).
Adapters Dialog	Prompts users to configure an IP address and subnet mask for each network adapter.
Define Routers Dialog	Prompts users to choose router discovery or to specify a default router.
Reboot Dialog	Prompts users to decide if they want to restart the computer immediately. If they do not do so, they cannot use the programs until they restart the computer.
Choose Name Servers Dialog	Prompts users to choose to obtain DNS (Domain Name Server) configuration from DHCP (Dynamic Host Configuration Protocol) servers or to specify DNS configuration.


The OnNet16 Setup Process Properties dialog box

The following describes the installation dialog boxes:

Dialog Box	Description
Welcome	Briefly explains the installation program and lets users view the installation notes.
License Notice	Displays the license agreement between the user and FTP Software, Inc. and prompts users to accept the terms before proceeding with the installation.
Installation Method	Prompts users to select a type of installation. You can set the default for the following dialog boxes: New Installation Method: Lets users choose between an Express installation that prompts for a limited set of information and a Custom installation that is the installation program you define using the Custom Install Manager. Update Installation Method: Lets users choose between an Express installation, a Custom installation, and a New Installation that does not display or use any configuration information from a previous version of the product. This dialog box appears if an earlier version of the product is installed on the computer. Reinstallation Method: Lets users choose whether to reinstall the same components or add new components. This dialog box appears if this version of the product is already installed on the computer.
WINSOCK.DLL	Warns the user that Setup has detected another WINSOCK.DLL file (TCP/IP stack) and that the programs in the product do not run over this stack. Prompts the user to choose between exiting the installation program (and not installing the product) and replacing the stack with the FTP Software TCP/IP stack.
Serial Number and  License Key	Prompts users to enter their product serial number, if applicable, and license key.
Destination Directory	Prompts users to specify the folder for the product programs and data files.
Reference Desk	Prompts users to decide if they want Reference Desk documentation files installed on their hard drive, or if they want to use the files from the CD-ROM or network.
Components	Lets users choose which programs are installed.
MAPI.DLL	Warns the user that, if they want to use Mail OnNet, they might not be able to use other, installed, mail programs that use a different Mapi.dll file.
Existing Driver	Displays the name of a network card driver that is in use on the computer and prompts the user to choose between using the current driver and choosing a new driver for Setup to install.
Network Card	Lets the user select a network card and specify its configuration.
Network Type	Prompts the user to specify the type of network the computer is connected to, for example, DIX-Ethernet.
IP Configuration	Prompts users to configure an IP address, subnet mask, and router.
Default Serial Protocol	Prompts the user to choose a default serial protocol.
Summary	Displays a list of configured interfaces and prompts the user to select the default interface to use.
NIS and DNS Configuration	Prompts users to choose to obtain NIS (Network Information Service) or DNS (Domain Name Server) configuration from DHCP (Dynamic Host Configuration Protocol) servers or to specify NIS or DNS configuration.
WINS Configuration	Prompts the user to configure WINS name service and servers.
Username	Prompts the user to type a username, as recognized by remote computers that run server programs, such as FTP and Telnet.
Time Zone	Prompts the user to choose a geographic time zone which is used by the Network Time application.
Stack Vendor	When the Microsoft TCP/IP protocol stack (“wolverine”) is installed, this message box prompts users to choose whether to replace the Microsoft stack with the FTP Software stack.
Network Access	Prompts the user to decide whether the FTP Software Network Driver (FTP NFS) is available from File Manager and Print Manager, and if so, whether to chain it to another network driver.
Firewall Server	Prompts the user to enter the IP address of a firewall server.
Copy Files	Prompts for final confirmation of the installation.
DOS System Files	Prompts the user to decide whether Setup should update the Autoexec.bat and, if appropriate, Config.sys files.
Setup Completion Behavior	Prompts users to decide if they want to restart the computer immediately. If they do not do so, they cannot use the programs until they restart the computer.
DLLs in Use	Warns the user that, because Setup is not restarting the computer, the user must run the Ftpclean batch file before they restart Windows.


Saving window positions
To save window positions

On the Tools menu, click Options, and on the General page, select the Save Window Positions When Exiting check box.


Custom Install Manager Accelerator Keys

The following accelerator keys are unique to the Custom Install Manager program:

Behavior	Action
Create a new group	Ctrl + G
Create a new client	Ctrl + L
Edit Setup information file	Spacebar
Edit TCP/IP Registry file	Spacebar


The Select Customization Set File for OnNet32 dialog box

Type the pathname of, or browse to, the Setup information file that ends with a .inf extension and that you want to use as a template for your database.

When you create a customization set from the default OnNet32 template, Custom Install Manager bases it on this file.

Note

Typically, this file is Setup.inf and is in the folder where you installed the product distribution during an Administrator installation.

 Related Topics


The Select Customization Set File for OnNet16 dialog box

Type the pathname of, or browse to, the Setup information file that ends with a .inf extension and that you want to use as a template for your database.

When you create a customization set from the default OnNet16 template, Custom Install Manager bases it on this file.

Note

By default, this file is Setup.inf and is in the folder where you created the product distribution.

 Related Topics


The Open Database dialog box
The Select Database File dialog box

Type the pathname of, or browse to, the database file that ends with a .mdb extension.

Note

By default, this file is Ftpcim32.mdb and is in the folder you specified for data files during the Custom Install Manager installation.


The Open Customization Sets Folder for OnNet32 dialog box
The Select Customization Sets Folder for OnNet32 dialog box

Type the pathname of, or browse to, the folder that contains your customization sets (or where you want to store your customization sets).

When you create a customization set from the default OnNet32 template (or from any customization set based on the 32-bit style Setup information template), Custom Install Manager adds the files to this folder.

Notes

By default, this is the folder you specified for the default Setup information file.

During an installation, the customization sets must be in the same folder as the setup command and the product distribution.

 Related Topics


The Open Customization Sets Folder for OnNet16 dialog box
The Select Customization Sets Folder for OnNet16 dialog box

Type the pathname of, or browse to, the folder that contains your customization sets (or where you want to store your customization sets).

Notes

By default, this is the folder you specified for the default Setup information file.

During an installation, the customization sets must be in the same folder as the setup command and the product distribution.

 Related Topics


The Open TCP/IP Stack Template dialog box
The Select Kernel Template File dialog box

Type the pathname of, or browse to, the FTP Software, Inc. TCP/IP protocol stack Registry file that ends with a .reg extension and that you want to use as a template for your database.

Note

By default, this file is Setup_k.reg and is in the folder you specified for data files during the Custom Install Manager installation.

 Related Topics


The Use Current Configuration dialog box

Setup obtains the following default answers from the previous configuration:

Destination Directory

Network card configuration and network frame type

IP address, subnet mask, and router address

DNS, NIS, and WINS configuration

Username and time zone

Socks firewall server


The Destination Directory dialog box

The first choice in the Choose a Folder list, c:\pctcp, is the FTP Software default. To use that folder, click it, then click Apply and OK.

The second choice in the list, [Windows Drive], only defines a drive letter. To install the product to the drive that contains the Windows installation, click [Windows Drive], click Apply, and type a folder name in the Destination Path box.

The third choice, Custom, lets you specify both a specific drive and folder. To do so, click [Custom], click Apply, type the drive letter and folder name, and click OK.


The Existing Driver: Use dialog box

If you know that the computers in your network are already working on the network (for example, if they are all using another NOS), then click Yes in this Existing Driver dialog box. If the network card drivers in use on your network support more than one type of network, you need to specify the type of network also.

If you click No, you must configure a network card.

 Related Topics


The Network Card: Choose Type dialog box

If you select NONE, Setup prompts the user for this information.

If you select Serial Port Using SLIP or PPP, you can use Custom Install Manager to also configure a default serial protocol; or you can let Setup prompt the user for that information.

If you select a network card and then click OK, Custom Install Manager prompts you to configure the network card. After you complete the configuration, or accept the default configuration for the card, click OK. Then, in the Dialog Properties list, click Show Driver Configuration? to specify whether Setup displays the Driver Configuration dialog box. If you click No, then Setup never displays the Driver Configuration dialog box, even if you let the user choose a network card.

Tip

Type the initial letters or numbers of the network card name to quickly find it in the list.

 Related Topics


The Network Card: Configuration dialog box

The information you can set depends upon the type of card. For some cards, you do not configure any of the hardware settings; for other cards, you configure all or some of the hardware settings.

Click Additional to set the software interrupt for the driver to use to communicate with the TCP/IP protocol stack, and in some cases, other hardware settings for the network card.

 Related Topics


The Time Zone dialog box

If you click None and if the user is upgrading from a previous version of the product, Setup uses the time zone in the PCTCP.INI file as the default. Otherwise, Setup uses us-est as the default.

Tip

Type the initial letters of the time zone to quickly find it in the list.


The DOS System Files dialog box

Generally the changes to DOS system files are limited to the Autoexec.bat file and consist of the following entries:

set pctcp=c:\pctcp\pctcp.inic:\pctcp\vxdinitset path=c:\pctcp;%path%

Some network configurations might require other entries in other files. The product documentation (for example, the OnNet16 Advanced User’s Guide) documents these entries in detail.


The WINS Configuration dialog box

You can enable the use of Windows Internet Naming Service (WINS), alone or together with the use of a broadcast file, to resolve NetBIOS names to IP addresses. If you enable WINS, you can also specify WINS name servers.

To enable WINS

1	Click Use WINS and a Broadcast File to set the NetBIOS node type to H, which means that NetBIOS resolves hostnames primarily by using a WINS server, but uses broadcasts if the name cannot be resolved by a WINS server.

-or-

 	Click Use WINS Resolution Only to set the NetBIOS node type to P, which means that NetBIOS resolves hostnames by using only WINS servers and does not use broadcasts.

2	For each name server, type its IP address and click Add.

3	If your network uses scope ids, type a scope id.

Note

If you do not enable WINS name resolution, Setup sets the NetBIOS node type to B, which means that NetBIOS resolves hostnames by using the following three resources, in this order:

Name cache on the local computer

Broadcasted request

NAMES or LMHOSTS file on the local computer


Configuring WINS name resolution
To configure WINS name resolution

1	In the organization pane, click a group or client.

2	In the object pane, double-click the Setup information file.

3	In the Installation Dialogs list of the Setup Process Properties dialog box, click WINS configuration.

4	In the Dialog Properties list, double-click Configuration.

5	Click Use WINS and a Broadcast File to set the NetBIOS node type to H, which means that NetBIOS resolves hostnames primarily by using a WINS server, but uses broadcasts if the name cannot be resolved by a WINS server.

-or-

 	Click Use WINS Resolution Only to set the NetBIOS node type to P, which means that NetBIOS resolves hostnames by using only WINS servers and does not use broadcasts.

6	For each name server, type its IP address and click Add.

7	If your network uses scope ids, type a scope id.

Note

Be sure to specify a DNS domain if you enable WINS name resolution.

If you do not enable WINS name resolution, Setup sets the NetBIOS node type to B, which means that NetBIOS resolves hostnames by using the following three resources, in this order:

Name cache on the local computer

Broadcasted request

NAMES or LMHOSTS file on the local computer

 Related Topics


The Setup Completion Behavior dialog box

To ensure a clean installation, FTP Software, Inc. recommends that you let the Setup program restart the computer.

If you choose No, Setup cannot automatically update .DLL files that are in use. To update these files, you or the user must run the FTPCLEAN batch file before restarting Windows.