Chip 1998 January

home *** CD-ROM | disk | FTP | other *** search

/ Chip 1998 January / CHIPCD1_98.iso / software / testsoft / nds / i386 / goodies / nal / nls / english / readnal.txt

Wrap

Text File | 1997-07-30 | 21.0 KB | 514 lines

NOVELL(R) APPLICATION LAUNCHER(tm) 2.01 GETTING STARTED GUIDE OVERVIEW Novell(R) Application Launcher(tm) 2.0 software ("NAL") lets you work with applications as objects in the Novell Directory Services(tm) (NDS(tm)) tree. This lets you manage applications centrally, making it easy to deliver new and updated network applications and data to your users. Using the product's features, which are integrated with NetWare(R) Administrator, you set up each application, and then set up the users you want to access it. Users can then launch the application from Windows*. NOTE: In July 1997, NAL 2.0 was updated to NAL 2.01 to address some issues. See the Appendix for more details. SPECIAL NOTE: In order to support roaming profiles in NAL 2.01, all existing NAL 2.0 applications on Windows 95 and NT workstations will be re-distributed to the workstation when the user double-clicks on the application icon or the application is force-run. Re-distribution or "Verify" can take a long time depending on the size of the application. See the Appendix for more details. Product Components NAL 2.0 consists of four components, two for administrator functions and two for end user functions: -- Novell Application Launcher Snap-In ("NAL" Snap-In), a Windows DLL that extends NetWare Administrator to make it possible to create Application objects in NDS. NAL Snap-In adds an Application object class to the NDS tree and adds new NetWare Administrator property pages for the Application object, Organization object, Organizational Unit object, Group object, and User object. -- Novell Application Launcher snAppShot ("NAL" snAppShot) which, when used with NAL Snap-In, provides a means to simplify managing complex application installations. NAL snAppShot detects changes that an application Setup program makes to a workstation's configuration and stores this information in an Application Object Template (.AOT) file. NAL snAppShot also keeps track of all the files that an application Setup program installs to the workstation, copies these files, and stores them as a series of .FIL files. You use the information gathered by NAL snAppShot when you create and set up Application objects. -- Novell Application Launcher Window ("NAL" Window), the user workstation component that displays the icons of the Application objects that you set up. NAL Window lets users create personal folders (with your permission), refresh applications, change views, and get information about folders and applications. Because you centrally manage the applications, users cannot change any icons or captions or disturb the drive paths of the applications. -- Novell Application Launcher Explorer ("NAL" Explorer), which lets you deliver applications into the Windows Explorer on Windows 95* and Windows NT* workstations. Users can see the applications you have assigned them in an Explorer window, the Start Menu, the System Tray, the Desktop, or any combination of these. Setup Files in This Release This release contains two software setup files: SETUPNAL.EXE, which installs all the files for NAL Snap-In, NAL snAppShot, NAL Window, and NAL Explorer into a network location you specify. You must run SETUPNAL.EXE at a Windows 95 or Windows NT workstation. It does not run on Windows 3.1x. SETUPSNP.EXE, an additional, separate Setup program for NAL snAppShot, which lets you also install NAL snAppShot directly on workstations, if you want to. You can run SETUPSNP.EXE on a Windows 3.1x, Windows 95, or Windows NT workstation. SETUPSNP.EXE creates a NAL snAppShot program group or folder. Product Documentation This Getting Started Guide contains information to help you get the software installed and operating. An appendix provides information about caveats, limitations, and known problems. See the NAL online Help for complete information about the features and use of NAL 2.0. SYSTEM REQUIREMENTS To use NAL 2.0, your system must have the following software: Novell Software NetWare 4.1 or later NetWare Administrator 4.11 (If needed, you can download this from http://www.novell.com/managewise/NAL/nal2.html [The URL is case-sensitive.]) Released versions of Client 32(tm) software or Windows NT Client 4.0 (If needed, you can download these from http://www.novell.com/managewise/NAL/nal2.html)[The URL is case-sensitive.]) Or Workstation Manager 1.0 (download from http://support.novell.com) Workstation Platforms For administrators: Windows 95 or Windows NT Client 32, Windows NT Client 4.0, or Workstation Manager For end users: Windows 3.1x, Windows 95, or Windows NT Virtual Loadable Module(tm) (VLM(tm)) 1.21 software, Client 32 for DOS/Windows, Client 32 for Windows 95, or Windows NT Client 4.0 or later NAL Explorer requires Windows 95 or Windows NT Before you install NAL 2.0, also make sure that -- You have Supervisor rights to the [ROOT] of the NDS tree in which you will install the NAL 2.0 software. -- Your users have rights to the directory in which you will install NAL 2.0, and have rights to the directories in which you will install the applications they can access. NOTE: If you have NAL 1.0 installed and want to use existing NAL 1.0 Application objects, NAL 2.0 offers a migration utility that creates NAL 2.0 Application objects based on existing NAL 1.0x Application objects. The migration utility is available from the NetWare Administrator Tools menu. For more information, see the online Help. INSTALLING NAL 2.0 1. Log in to the NDS tree where you will install the NAL 2.0 software. 2. Close all applications (including NetWare Administrator) on the workstation you are using. NOTE: If you have NAL 1.1 already installed, make sure you close it and that your users are not running it. 3. Determine the network directory in which you will install the software and the directory in which you will install the applications that you will distribute. We recommend installing files to the default Z:\PUBLIC directory. 4. Run SETUPNAL.EXE and respond to the screen prompts. One prompt asks "Do you want to extend the NDS Schema?" You must extend the schema to use NAL 2.0 software. You can do it now, during Setup, or wait until after NAL 2.0 is installed. If you click Yes, to extend the schema now, -- Setup extends the schema in the NDS tree that contains the directory in which you are installing the NAL 2.0 software. -- Another prompt asks "Do you want Setup to create sample Application objects?" We recommend you click Yes, so that, after you install NAL 2.0, you can explore the characteristics of the sample Application objects to quickly get familiar with many of the features that NAL Snap-In adds to NetWare Administrator. If you click No, to extend the schema later, -- The first time you open NetWare Administrator after NAL 2.0 is installed, a prompt appears, asking you on which NDS tree you want to extend the schema. Select the appropriate NDS tree and then click Modify. -- You cannot install sample Application objects. At the end of Setup, a prompt asks whether you want to display READNAL.TXT (this Getting Started Guide). By default, the check box in the prompt box is selected. If you do not want to review READNAL.TXT, click the check box to deselect it. SETUPNAL.EXE installs all product files in the directory you specified (default: Z:\PUBLIC). NAL snAppShot is installed in a Snapshot subdirectory. 5. After Setup is complete, open NetWare Administrator. 6. Notice the changes that NAL Snap-In makes to NetWare Administrator: -- An object--Application--is added to the new object list. -- The Tools menu shows three new options: Export Application Object Migrate Application Objects Show Inherited Applications -- An Applications property page and a Launcher Configuration property page are added to each Organization object, Organizational Unit object, and any User object that exists in the NDS tree. An Applications property page is added to any Group object that exists. -- If you chose to have sample Application objects installed, the NetWare Administrator 95, NetWare Administrator NT, and snAppShot sample Application objects appear in the NDS tree. Double-click a sample Application object to access and explore that object's property pages. Notice that you can use the Page Options feature to select and sort the property pages in the order you like. USING NAL 2.0 To use NAL 2.0 to distribute an application, you first set up the application as an Application object in the NDS tree, and then set up users so they can access the application. Setting Up the Application as an Application Object For a simple application installation, you can create an Application object directly in the NDS tree and then make any optional configuration entries in the Application object's property pages. However, for a more complex application installation that modifies .INI settings, Registry settings, etc., use NAL snAppShot to first create the .AOT file and .FIL files used by NAL to create the Application object. Use the following procedure to set up the application as an Application object: 1. If appropriate, use NAL snAppShot to create a .AOT file and .FIL files: (If you don't need to use NAL snAppShot, go to Step 2.) a. Select a workstation that has a representative configuration, that does not already have the application you want to distribute installed, and is not currently running any application. b. At the selected workstation, run NAL snAppShot. Run SETUPSNP.EXE and then click the NAL snAppShot icon. Or Run SNAPSHOT.EXE from the Snapshot subdirectory in the network directory where NAL 2.0 is installed. c. Respond to the prompts that appear. For information about using the fields on each screen, click the Help button. 2. Create an Application object in the NDS tree. a. In NetWare Administrator, highlight the container object in which you want to create the Application object, and then choose Object > Create > Application. The Application Object Creation wizard is displayed. b. If you used NAL snAppShot to create a .AOT file and .FIL files, select the Use This Wizard with an Application Object Template check box. c. Respond to the prompts from the wizard to create the Application object. The Application object is displayed in the NDS tree. d. To specify any special requirements or configurations, make entries in the Application object's property pages. Double-click the Application object to access its property pages. Click the Help button on each property page for information about the options available. Setting Up Users to Access the Application 1. Open the Application object's Associations property page, and associate the User, Group, Organizational Unit, or Organization objects that can access the application. 2. Double-click the associated User, Group, Organizational Unit, or Organization object, and use its Applications property page to specify how you want the application to appear on the user's desktop. 3. Use the User, Organizational Unit, or Organization object's Launcher Configuration property page to specify characteristics of NAL Window and NAL Explorer. 4. Make NAL Window and NAL Explorer available to users. To do this, you can Place NAL.EXE, NALEXPLD. EXE, or ADDICON.EXE in user login scripts. (See the online Help for details.) Or Let users know how to find and run these executables. ================================================================================ APPENDIX: CAVEATS, LIMITATIONS, AND KNOWN PROBLEMS RE-DISTRIBUTION OF APPLICATIONS BECAUSE OF ROAMING PROFILES (2.01) Problem: Users with roaming profiles on Windows 95 and NT run into a problem when the distribution flag was stamped in HKEY_CURRENT_USER and the user logs in at another workstation. When attempting to run an application that previously recorded that the distribution had been done, the application will likely not run. The user needed to 'verify' the application to have the distribution occur at a new machine. Solution: Stamp HKEY_CURRENT_USER when HKEY_CURRENT_USER registry changes are made. Stamp HKEY_LOCAL_MACHINE when the Application files, INI files, Text files, and Shortcuts are made. Caveats: All existing v2.0 applications on Windows 95 and NT will be re-distributed so they are recorded in KHEY_LOCAL_MACHINE. GENERAL * If you install NAL in a directory other than SYS:\PUBLIC, you must copy NWAPP32.DLL, APPSNP95.DLL, and SNAPIN32.DLL to the directory where NWADMN95.EXE resides and APPRES32.DLL, APPSNAP.HLP, and APPSNAP.CNT to the NLS\(LANGUAGE) directory below NWADMN95.EXE. You must also copy NWAPP32.DLL and APPSNPNT.DLL to the directory where NWADMNNT.EXE resides and APPRES32.DLL, APPSNAP.HLP, APPSNAP.CNT to the NLS\(LANGUAGE) directory below NWADMNNT.EXE. * If NetWare Administrator for Windows 95 does not allow you to create Application objects, verify that NWAPP32.DLL, APPSNP95.DLL, SNAPIN32.DLL are located in the same directory as NWADMN95.EXE and that APPRES32.DLL, APPSNAP.HLP, and APPSNAP.CNT are in the NLS\(LANGUAGE) directory. Also make sure that the dates of the files are the same as those shipped in the product. Make sure that the registry key for NAL Snap-In is set to either the hex or string value of "APPSNP95.DLL", but not to both. HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator\ KEY: Snapin Object DLLs WIN95 VALUE: APPSNP95.DLL = "APPSNP95.DLL" --OR-- VALUE: APPSNP95.DLL = 41 50 50 53 4E 50 39 35 2E 44 4C 4C * If NetWare Administrator for Windows NT does not allow you to create Application objects, verify that NWAPP32.DLL and that APPSNPNT.DLL are located in the same directory as NWADMNNT.EXE and APPRES32.DLL, APPSNAP.HLP, and APPSNAP.CNT are in the NLS\(LANGUAGE) directory. Also make sure that the dates of the files are the same as those shipped in the product. Make sure that the registry key for NAL Snap-In is set to either the hex or string value of "APPSNPNT.DLL", but not to both. HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator\ KEY: Snapin Object DLLs WINNT VALUE: APPSNPNT.DLL = "APPSNPNT.DLL" --OR-- VALUE: APPSNPNT.DLL = 41 50 50 53 4E 50 4E 54 2E 44 4C 4C * If a drive mapping exists, applications that need that drive letter with a different mapping do not execute. * File system rights are not automatically granted when the Application object is assigned to a User, Group, Organization, or Organizational Unit object. You must explicitly grant these file system rights. * Use caution when specifying the timed refresh setting. Frequent refreshes of large numbers of users can adversely impact network traffic. The default setting for timed refresh is Off. * You must explicitly grant your users rights to NRD: REGISTRY DATA and NRD: REGISTRY INDEX if you want them to be able to store personal folders in their User object. * The Auto Run associations from previous versions of NAL are not retained after migrating Application objects to NAL 2.0. NAL snAppShot * NAL snAppShot does not correctly discover shortcuts to DOS executable files; they are discovered as new files. * The location where NAL snAppShot places the .FIL files defaults to a drive letter. After importing the Template (.AOT) file into an Application object, go to the Macros page and change the SOURCE_PATH to a UNC path. (G:\PUBLIC\AOT\NETSCAPE to \\SERVERNAME\SYS\PUBLIC\AOT\NETSCAPE) This allows users to run the program without mapping to the G drive. * When you run NAL snAppShot, make sure you have rights to the destination directory or directories you specify for the .AOT file and .FIL files. (You enter these on the Template and Configuration Information page in the fields labeled Directory and File Name for the Template You will Create, and Directory for Application Files [Network Directory Recommended].) If you enter a path to which you do not have rights, NAL snAppShot will not create valid "snapshots." NAL EXPLORER * To run NAL Explorer, you must have a newer version of SHELL32.DLL. This file is part of the Microsoft* Windows 95 Service Pack 1 Update. Download this from http://www.microsoft.com/kb/softlib/mslfiles/setup.exe Or http://www.microsoft.com/windows/software/servpak1/sphome.htm * Changes in the icon are not reflected in any opened window until you close the browser and Explorer windows. * Microsoft* Windows 95 password screen causes problems when loading the NAL Explorer from a login script. Since the desktop (explorer) is not loaded at that time the NAL Explorer times out and can't load. This means forced-run applications will not launch immediately. They will launch after the user double-clicks on the NAL Explorer folder. A workaround until next release is to put a shortcut in the startup group to the NALEXPLD.EXE. The NAL can be used to distribute this shortcut to users. * Some settings in the Launcher Configuration property page do not apply to NAL Explorer: - In NAL Window, selecting the Exit the Launcher check box disables the Exit menu item. However, in NAL Explorer, the menu item is not disabled. A user can exit by selecting File > Close. - The Log In check box applies only to NAL Window. There is no option to log in from within NAL Explorer. - Save Window Size and Position on Local Drive applies only to NAL Window; it does not apply to NAL Explorer. NAL 2.01 FIXES THE FOLLOWING IMPORTANT PROBLEMS: snAppShot * Update of existing files were not discovered * Registry corruption on Windows 3.x * Problem scanning HKEY_LOCAL_MACHINE\SYSTEM on Windows NT * Double-byte language problems NAL Window * Distribution fails if TEMP variable is not set on Windows 3.x NAL Explorer * Lock up when putting two application icons with the same title on the desktop Distribution * Distribution does not work correctly using roaming profiles Documentation * If running VLMs, Must use VLM 1.21 or higher -------------------------------------------------------------------------------- Copyright 1994-1997, Novell, Inc. All rights reserved. Novell Trademarks NetWare is a registered trademark of Novell, Inc. in the United States and other countries. Novell is a registered trademark of Novell, Inc. in the United States and other countries. Client 32 is a trademark of Novell, Inc. Novell Application Launcher is a trademark of Novell, Inc. Novell Directory Services and NDS are trademarks of Novell, Inc. Virtual Loadable Module and VLM are trademarks of Novell, Inc. Third-Party Trademarks Microsoft, Windows, and Windows NT are registered trademarks and Windows 95 is a trademark of Microsoft Corporation. -------- Novell, Inc. makes no representation or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell.