Novell Home

Upgrading from NAL 2.x to ZENworks 1.0

Novell Cool Solutions: Tip

Digg This - Slashdot This

Posted: 4 May 1999
 

If you've been administering a network with the NAL 2.0 or NAL 2.01 snap-in, and are planning to upgrade to the new NAL 2.5 included in Z.E.N.works, one of your concerns might be ?What about all those snAppShots...do I have to do them again?? or ?Are new 2.5 snAppShots backwards compatible??

NAL 2.5 introduces several new macros and new .AOT entry types. If you create an .AOT with NAL 2.5 and use that .AOT in NAL 2.01, the older version will not recognize the new macros and, therefore, they won't do what macros are supposed to do: substitute data. The same thing happens to newer .AOT entries: They are ignored because 2.01 does not know what to do with them. In short, NAL 2.5 is backward compatible with 2.01 data; however, NAL 2.01 is NOT forward compatible with 2.5 data.

NOTE: Before you install Z.E.N.works, be sure to read the NDS Design document we have. It has some good pointers that could save you a lot of headaches.

Now that we've cleared the air, let's get that system of yours upgraded! To upgrade from NAL 2.0 to Z.E.N.works 1.0,  follow these steps:

1. Because the Z.E.N.works installation process overwrites NAL 2.01 snap-ins with NAL 2.5 snapins, make a backup copy of the NetWare Administrator (NWAdmin) software you are currently using.

For example, if you use NWAdmin95, copy the SYS:Public\Win95 directory to a safe place other than SYS:Public. If you use NWAdminNT, copy the SYS:Public\WinNT directory to a safe place other than SYS:Public.

2. Install Z.E.N.works to SYS:Public, which includes NWAdmin32 as one of the components in the installation.

NOTE: If you intend to use NAL 2.01 with the new Windows NT Client that comes with Z.E.N.works, disable the installation of the NAL NT Service, which might cause conflicts when NAL 2.01 runs. By default, the new Windows NT Client installs the NAL NT Service, which consists of three files in the System32 directory: NALNTSRV.EXE, NALNTRES.DLL and NWAPP32.DLL. You can disable the NT Service installation while installing the new Windows NT Client.

3. Use the old NWAdmin you saved in Step 1 to manage your network as you transition from NAL 2.01 to NAL 2.5.

NOTE: The ?transition? includes the period of time it takes you to update NAL.EXE and NALEXPLD.EXE, the executables that enable users to access Application Launcher and Application Explorer at their workstations. It's possible that some users will be running the new NAL and others will be running the old NAL. Hence, it's best to administer the network with the older NWAdmin because NAL 2.01 does not recognize the new features in NAL 2.5.

4. When you are sure all users are running NAL 2.5 software at their workstations, delete the copy of NWAdmin you created in Step 1.

5. Start the new NWAdmin32 (found in SYS:Public\Win32).

6. OPTIONAL: Open the Launcher Configuration property page of each User, Organization, and Organizational Unit object where you previously set launcher configurations and uncheck the Backwards Compatible option so that NAL 2.01 data is not saved anymore.

7. Open the Launcher Configuration property page on the parent container that you've previously set as the ?top? of the configuration inheritance tree. On that page, check the Use As Top of Configuration Tree option.

NOTE: When Application Launcher searches the NDS tree for configuration settings, it starts at the lowest possible leaf object (a User or container object) and works up the inheritance tree. It continues walking up this tree searching for custom settings until it reaches a container object that has been designated as the ?top? of the inheritance tree. If it finds custom configurations in any of the objects along the way, those are the configurations that are applied. If it doesn't find any custom configurations, then the configuration is considered ?unset? and the default configuration is applied. This method of inheritance lets you control when and where custom configurations are applied instead of the defaults.

8. In addition to the changes to the Launcher Configuration property page, notice the new or changed property pages in the Application object.

For example, check out the new Order Icon feature on the Identification property page, which lets you order the application icons on the desktop as well as order how applications are forced to run.

The Registry Settings, Application Files, Text Files, Icons/Shortcuts, and INI Settings property pages have some great new stuff, including a Find option and a bevy of distribution options that let you control how specific settings are distributed.

Speaking of distribution, the global distribution options (those that affect the entire Application object) have been moved to a new property page called ?Distribution.? Look at it and you'll see some familiar faces and some new bells and whistles.

Lest we forget, you can also create Application folder objects to help you set up multi-level foldering at the workstation, and also an Application Launcher Tools menu (off of the main Tools menu). Of course, to really get to know all of these new features, the best thing to do is click that Help button on the dialog box. We'll also be posting Feature Articles and Tips in the future that illuminate even more.
 


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell