Updates were made to the following sections. The changes are explained below.
The following changes were made in this section:
The following changes were made in this section:
| Location | Change |
|---|---|
Installing Policy and Distribution Services on NetWare and Windows Servers |
Added the following note: IMPORTANT: To install a portion of Policy and Distribution Services, such as additional Distributors and Subscribers, or to install only Subscriber software to a server, see Reinstalling Policy and Distribution Services on NetWare and Windows Servers, where more detailed instructions are provided for each installation page. The instructions in this section are tailored to a first-time installation of ZfS. |
Added this section to indicate where to find installation instructions for NICI 2.4. |
|
Added the following note in Step 5 in this section: IMPORTANT: ZfS does not support running from a server's console an instance of ConsoleOne installed on that NetWare server. To use the server's installation of ConsoleOne, you must map a drive from a workstation to that server and run ConsoleOne from the workstation. |
The following changes were made in this section:
| Location | Change |
|---|---|
Added the following note in Step 12.c in this section: IMPORTANT: ZfS does not support running from a server's console an instance of ConsoleOne installed on that NetWare server. To use the server's installation of ConsoleOne, you must map a drive from a workstation to that server and run ConsoleOne from the workstation. |
The following changes were made in this section:
| Location | Change |
|---|---|
Added the following note in Step 11.c in this section: IMPORTANT: ZfS does not support running from a server's console an instance of ConsoleOne installed on that NetWare server. To use the server's installation of ConsoleOne, you must map a drive from a workstation to that server and run ConsoleOne from the workstation. |
The following changes were made in this section:
The following changes were made in this section:
| Location | Change |
|---|---|
Added the following bullet for reasons to reinstall ZfS:
The reinstallation steps are more detailed than the first-time installation steps. Therefore, information needed for installing specific components, such as a Subscriber, is better covered in the reinstallation steps. |
|
Rewrote the bullets under Step 7a to expand on the purposes for checking or unchecking the Create eDirectory Objects check box. Added the following paragraph under Step 8: This will automatically become the trusted tree for all Subscriber servers selected in the next installation page. The trusted tree is where the Subscriber receives its configuration updates. Added the following note under Step 9: IMPORTANT: If you checked the Create eDirectory Objects check box on the Installation Options page (see Step 7), both NetWare and Windows servers will have eDirectory Subscriber objects created in the tree that you identified in the eDirectory Tree for Creating Objects page (see Step 8). However, if you unchecked this box, you should identify a trusted tree for each Subscriber in the File Installation Paths and Options page (see Step 12). Added the following paragraph in Step 10: On the File Installation Paths and Options page (see Step 12), you can create different configurations for different sets of objects. Therefore, you can select objects that might have different installation paths and different trusted trees. Added the following note in Step 12: HINT: For all of the configuration options on this page, if you have multiple objects to select from, you can select some of them, fill in the fields, then select another set of objects, and fill in the fields for them. In other words, you can create different configurations for different sets of objects. Added the following paragraphs to Step 12b: If you are reinstalling software for a Subscriber server, this would be the tree where you originally installed its Subscriber object. The trusted tree has two purposes:
When you install the Subscriber software to a server in another tree or in a Microsoft domain, and you do not want to create a Subscriber object in your Distributor's tree, you should identify the trusted tree for the Subscriber server. If you do not select a tree to be recognized as the Subscriber server's trusted tree during installation of only the Subscriber software (no object), your Policy Package Distributions will not extract on that Subscriber server, because policies often point to objects in a tree. |
The following changes were made in this section:
| Location | Change |
|---|---|
Added the following bullet:
|
The following changes were made in this section: