Intel NetportExpressTM XL Print Server Netport Manager Version 2.5 Extract from Release Notes README.WRI New features and important information about this release Contents 1. About Netport Manager **2. New: Novell* NetWare* Directory Services (NDS) Support **3. New: LANDeskT Management System SnapIn **4. New: LANDesk Alert Management System (AMS) Support **5. New: DMI and MIF Setup Support 6. Upgrading the Application Code for an XL 1 About Netport Manager Netport Manager is the Windows* application that you use to configure the NetportExpress XL print server. You can use Netport Manager to configure all other models of Netport print servers, including the NetportExpress EL, Netport II and the original Netport print server. You can run Netport Manager with Windows 3.1, but Netport Manager currently does not run under OS/2*. This release of Netport Manager includes: - Support for Novell NetWare Directory Services (NDS). You can load Netport Manager on an NDS workstation to configure the XL for either NDS printing or bindery printing. - Support for the LANDesk Alert Management System. You can be notified about and respond to print server events such as "printer offline" from the LANDesk system. - "SnapIn" of the NetportExpress print server, so that you can "see" the NetportExpress XL from the LANDesk system. - Support for DMI and MIF Setup. 6 Upgrading the Application Code for an XL There are two choices: - You can save the new Application Code on a different RBL server than the current one. This choice allows you to gradually introduce Netports with NDS support into your environment. - You can save the new Application Code on the current RBL server. This choice requires you to update all Netport XL and EL print servers, both Ethernet and Token Ring, even if you use the new software on only one XL or EL. To verify that your Netport has the correct RBL and Application Code, check the status from Netport Manager. The software uses Flash memory, allowing Intel to provide you with enhanced functionality while preserving your hardware investment. See the product documentation and online Help for information about installing and configuring your XL or EL, and how to update the Flash memory and the Application Code on the RBL file server. Novell NetWare: The Application Code is stored in the SYS:LOGIN directory of the RBL file server. After you install a new version of Netport Manager, it then copies the new Application Code to the SYS:LOGIN directory of the RBL file server(s) you specify as part of the XL configuration. To upgrade the Application Code for a configured XL 1 Start Netport Manager and select the Netport you want to upgrade. 2 Choose Configure. 3 Choose Netport Hardware. Click Change RBL. The Remote Boot Load (RBL) Server field shows the current RBL file server. You can update the Application Code on this RBL server or select another. 4 Choose OK. Netport Manager copies the latest version of the Application Code to the RBL server. Other XLs that use the same RBL file server will be upgraded when you reset them. To update the RBL Flash for a configured XL 1 Start Netport Manager and select the Netport print server you want to upgrade. 2 From the Utilities Menu, choose the Update RBL Flash option. 3 Select the new NFLASH.NET file that you want to use to update the Netport print server. To update LAN Manager installations This update is necessary for you to use a NetBIOS server as an RBL server. To do this, you'll have to stop and restart the NetBIOS Monitor. 1 From the Netport Manager Manage menu, choose NetBIOS Monitor. You see the Netport Print Monitor Shutdown window. 2 Select the Monitor Server you want to shut down. Click OK. 3 From the LAN Manager server, run the INSTALL.CMD file from Disk #2 of the Netport Manager installation disks. This updates the LMNPMON.EXE program. Note: .CMD only runs in OS/2 environments. _____________________________________________ Copyright O 1994 - 1995 Intel Corporation. All rights reserved. Intel Corporation 5200 NE Elam Young Parkway Hillsboro, OR 97124 * All brand and product names are trademarks of their respective owners. ** See README.WRI for details