ZENworks Login Panel

AdminStudio 2013 | Legacy Distribution Wizard

This panel is displayed if you selected the ZENworks Desktop Application or ZENworks Server Distribution method from the Distribution Type panel.

Use this panel to login to the server location where you want to create the Distribution Object. Enter the following options:

ZENworks Login Panel Options

Option

Description

Login Name

Enter a valid Login Name for the Novell server where you want to create the Distribution Object. This is a required field. For more information, see Specifying Multiple Parameters in the Login Name and Context Fields.

Password

Enter a valid password for the specified Login Name.

Server

Enter the machine name or IP address of the Novell server where you want to create the Distribution Object.

Context

Enter the Novell environment where you want to create the Distribution Object. Because you can choose to define the context information in the Login Name field, this field is optional. For more information, see Specifying Multiple Parameters in the Login Name and Context Fields.

SSL Port Number

Specify the secure port to connect to ZENworks. The default/recommended port value is 636.

Note: All of these entries except the password are saved and will pre-populate these fields the next time you access this panel.

Specifying Multiple Parameters in the Login Name and Context Fields

The entries that you make in the Login Name and Context fields are concatenated to form the Novell distinguished name. If you enter jsmith in the Login Name field and myorg in the Context field, the login information that AdminStudio would pass to the server would be:

    cn=jsmith, o=myorg

Specifying Multiple Parameters in the Login Name Field

Instead of making entries in both the Login Name and Context fields, you could enter both the login name and the context in the Login Name field (separated by either periods or commas). AdminStudio uses a formula to determine how to pass these parameters to the server:

How to Specify Multiple Parameters in the Login Name Field

If you enter ...

AdminStudio assumes that ...

two unqualified parameters in the Login field, such as:

jsmith, myorg

the first entry identifies the login name (cn)
the second entry identifies the organization parameter (o)

Therefore, the following parameters are passed to the server:

cn=jsmith, o=myorg

more than two unqualified parameters in the Login field, such as:

jsmith, dept01, office03, myorg

the first entry identifies the login name (cn)
the last entry identifies the organization parameter (o)
all entries in between the first and the last entry are assumed to be identifying organizational units (ou)

Therefore, the following parameters are passed to the server:

cn=jsmith, ou=dept01, ou=office03, o=myorg

In this instance, you would leave the Context field blank.

Specifying Multiple Parameters in the Context Field

If you would like to enter multiple parameters in the Context field, you would enter the login name in the Login Name field without parameters (jsmith, for example), and then specify all of the context parameters in the Context field. You can enter multiple qualified parameters in any order:

    ou=dept01, o=myorg, ou=office03

However, if you enter multiple unqualified parameters in the Context field, AdminStudio uses a formula to determine how to pass these parameters to the server:

How to Specify Multiple Parameters in the Context Field

If you enter ...

AdminStudio assumes that ...

one unqualified parameter in the Context field, such as:

myorg

The following parameter is passed to the server:

o=myorg

two unqualified parameters in the Context field, such as:

dept01, myorg

the first entry identifies an organizational unit (ou)
the second entry identifies the organization parameter (o)

Therefore, the following parameters are passed to the server:

ou=dept01, o=myorg

more thantwo unqualified parameters in the Context field, such as:

dept01, office03, myorg

the last entry identifies the organization parameter (o)
all previous entries are assumed to be identifying organizational units (ou)

Therefore, the following parameters are passed to the server:

ou=dept01, ou=office03, o=myorg

Caution: If the above formulas do not accommodate your data, always use fully qualified naming.

Caution: The Login Name is a required field; you cannot leave the Login Name field blank and specify the login name in the Context field using the cn parameter.