04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 91 CHAPTER 3 Novell Management Tools Using ConsoleOne ConsoleOne is a Java-based tool for managing your network and its resources. It can be launched by running CONSOLEONE.EXE from where it was installed (default: SYS:PUBLIC\MGMT\CONSOLEONE\1.2\BIN). By default, it lets you manage Novell eDirectory objects, schema, parti- tions, and replicas and NetWare server resources. If you install other Novell products, the appropriate management capabil- ities are automatically snapped into the version of ConsoleOne installed on that server. ConsoleOne is installed during the NetWare 6.5 installation, but can also be re-installed or installed locally from the Novell client’s CD. ConsoleOne also supports remote server console access through a Java applet called RConsoleJ. To access the NetWare 6.5 server console remotely, launch ConsoleOne and browse to the desired server. Select Tools, and then Remote Console. Accessing Web Manager Web Manager is a Web-based “home page” for accessing most of the NetWare 6.5 Web-based tools and services. To access Web Manager, open your Web browser and enter your Web server’s domain name or IP address, followed by a colon and the Web Manager port, which by default is 2200. For example: 04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 92 92 PART I Getting Started https://www.quills.com:2200 or https://137.65.192.1:2200 Accessing iManager iManager provides role-based management of your NetWare network, together with a nearly comprehensive set of administrative tools. You can use either a secure (HTTPS) or unsecure (HTTP) connec- tion to access iManager. However, a secure connection is recom- mended. Once configured, you can access the iManager Web page by appending the iManager path (/nps/iManager.html) to the IP address or DNS name of the server running iManager. For example: https://www.quills.com/nps/iManager.html or https://137.65.192.1/nps/iManager.html . To force iManager into Simple mode to support Federal accessibili- ty guidelines, use the Simple mode path (/nps/Simple.html). For example: https://www.quills.com/nps/Simple.html or https://137.65.192.1/nps/Simple.html . You will be prompted to authenticate using a valid eDirectory user- name. Users can access iManager features only for which they have been assigned rights. Once loaded, you will use iManager to perform most of the day-to-day administrative tasks in your NetWare environment, including manage- ment of most additional services that are available with NetWare 6.5. 04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 93 93 Novell Management Tools CHAPTER 3 Using NetWare Remote Manager NetWare Remote Manager (NoRM) is used for remote management of NetWare 6.5 servers. You can launch NoRM from Web Manager, or you can launch NoRM directly by the NetWare 6.5 server’s domain name or IP address, followed by a colon and the port number, which by default is 8009. For example: https://www.quills.com:8009 or https://137.65.192.1:8009 . You can also launch NoRM directly from the graphical server con- sole by clicking the red N icon on the icon bar at the bottom of the GUI. You will be prompted to authenticate. If your user object is in the same context as the server object, you can authenticate by common name only. Otherwise, you need to specify a full eDirectory user- name, including the leading dot. For access to all NoRM features, the user should have supervisory rights to the NetWare server. Working with iMonitor iMonitor is used for Web-based management of Novell eDirectory in your NetWare 6.5 network. Launch iMonitor from NoRM by selecting NDS iMonitor from the Managing eDirectory section in the left side navigation frame. Alternatively, you go straight to iMonitor by appending the iMonitor path (/nds) to the NoRM URL. For example: https://www.quills.com:8009/nds or https://137.65.192.1:8009/nds NOTE You can also launch iMonitor directly by appending :8008/nds to the end of your server’s IP address or URL. 04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 94 94 PART I Getting Started Introduction to Novell Management Since the release of NetWare 4 in the early 1990s, Novell has been work- ing toward a consolidated management interface from which all adminis- trative tasks can be performed. In that time, the primary issue hampering this effort has been how to deliver that management interface. From NWAdmin and ConsoleOne The first version of a centralized management interface was NWAdmin. NWAdmin was a Windows-based utility that delivered a graphical interface that allowed administrators to see the whole network from a directory- centric perspective rather than a server-centric perspective. It relied on the Novell client to provide network communications and access. NWAdmin also defined the standard look and feel for graphical management utilities that is still largely adhered to today. NWAdmin supported an extendable plug-in architecture so new func- tionality could be added as necessary to manage new features and new products. This was accomplished through Windows-based programming techniques common at the time. However, NWAdmin ran only on Windows and used a proprietary archi- tecture. Rather than try to support multiple versions of NWAdmin, Novell moved toward a more open and standards-based management architecture based on Java programming techniques. Java promised the capability to “write once, run anywhere,” which was critical to Novell’s management plans. In 1998, with the release of NetWare 5, Novell introduces its second- generation administrative utility known as ConsoleOne. Similar to NWAdmin, ConsoleOne is an extendable management architecture that supports snap-ins to extend its capabilities. Its Java-based design allows it to run on both workstations and the NetWare server itself, providing the first-ever graphical server console. However, it still required some type of Novell client support for network communications and access. In the years since its release, ConsoleOne has achieved respectable performance, a major deficiency in its early versions, and still serves as the preferred tool for managing Novell and third-party products and services. 04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 95 95 Novell Management Tools CHAPTER 3 To iManager With the release of NetWare 6, Novell started making the final manage- ment interface transition necessary to support its One Net initiative by introducing a set of Web-based management tools. Just as ConsoleOne untied the management console from Windows, iManager is untying the management console from the Novell client. iManager promises a true platform-independent management interface that can be used from any workstation at any location to perform network management and mainte- nance of any kind. NetWare 6.5 introduces a greatly enhanced set of tools in iManager, near- ly equaling that available from ConsoleOne. However, because every fea- ture is not yet available in iManager, you will need to be familiar with the capabilities of each management interface. This chapter provides an introduction to the primary Novell management utilities, from ConsoleOne to iManager. It provides requirements and installation infor- mation for each utility, as well as an overview of its features and cap- abilities. First, the chapter presents ConsoleOne, which is still the most compre- hensive management interface for NetWare 6.5. We show how ConsoleOne can be used for both local and remote server administration as well as full eDirectory management. Next, a new generation of Web-based management tools is presented, starting with iManager and its closely related sister utilities—NetWare Remote Manager (NoRM) and iMonitor. These browser-based utilities are close to eclipsing ConsoleOne for feature completeness and promise much more flexibility for network administrators looking to get their jobs done from any place at any time. ConsoleOne NetWare 6.5 includes ConsoleOne v1.3.6. ConsoleOne is a Java-based tool for managing your network and its resources. By default, it lets you manage . Novell eDirectory objects, schema, partitions, and replicas . NetWare server resources If you install other Novell products, additional capabilities are snapped in to ConsoleOne automatically. For example, if you install Novell 04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 96 96 PART I Getting Started eDirectory, the capability to configure the LDAP interface to eDirectory is snapped in to ConsoleOne automatically. Because ConsoleOne is a Java-based application, it has a similar look and feel across all platforms, as shown in Figure 3.1. FIGURE 3.1 Novell ConsoleOne v1.3.6. ConsoleOne Basics Before looking at specific administrative tasks that are described through- out this book, it’s a good idea to get a feel for the basics of ConsoleOne administration. If you need a more detailed introduction to ConsoleOne, see the NetWare 6.5 online documentation. Organizing Objects into Containers The whole purpose of using eDirectory to manage your network is that it allows you to organize network resources so they can be managed more easily. A principal way of doing this is to organize objects into logical groupings known as containers. Because of inheritance rules, objects in a container are security-equivalent to the container itself; so, general object rights can be managed at the container level rather than the individual 04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 97 97 Novell Management Tools CHAPTER 3 object level. For more information on eDirectory tree design, see Chapter 5. For information on network security with eDirectory, see Chapter 6. Creating and Manipulating Objects Once you have located the objects you want to manage, you can change their behavior by modifying their properties.