What is the ZENworks Starter Pack (January 2000)?

  • 10027766
  • 1.0.59972060.2571798
  • 06-Mar-2000
  • 25-Oct-2002

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Goal

Define what is / is not included in the ZENworks for Desktops Starter Pack included with NetWare 5.1 and available on the web as of January 2000.

What NAL features are NOT included in the ZENworks 2.0 Starter Pack?

What ZENworks features are NOT included in the ZENworks 2.0 Starter Pack?

Fact

Novell ZENworks 2 Starter Pack

Fix

Below is the readme.txt included with the ZENworks Starter Pack:

ZENworks Starter Pack (October 1999)
November 16, 1999

Table of Contents

1.0 What Is the ZENworks Starter Pack?
2.0 Installation
   2.1 Error When Installing on a NetWare 4.x Server
   2.2 Installing ZENworks from a Server Image
   2.3 NDS for NT Server System Requirements
   2.3.1 Installing ZENworks Starter Pack on NDS for NT
   2.3.2 Mapping Errors When installing ZENworks Starter Pack on an NT Server
3.0 NetWare Administrator
   3.1 Using ZENworks NetWare Administrator 32
   3.1.1 Policy Objects May Appear in NetWare Administrator 32
   3.1.2 Running Snap-In DLLs Using NetWare Administrator 32
      3.1.3 Running Numerous Snap-Ins with NetWare Administrator 32
      3.1.4 Using NetWare Administrator 32 with the NetWare 5 Client
      3.1.5 Using the Starter Pack on a Non-English Server
   3.2 Using NetWare Administrator 95 or NetWare Administrator NT
   3.3 Authenticating to a New NDS Tree Using NetWare Administrator 95 or NetWare Administrator NT
   3.4 Using FastCache and BorderManager Snap-Ins
   3.5 User Profiles Snap-In
4.0 Application Management
   4.1 General Known Problems and Limitations
      4.1.1 Creating Application Objects with NetWare Administrator for Windows 95
      4.1.2 Creating Application Objects with NetWare Administrator for Windows NT
      4.1.3 Using the Timed Refresh Setting
      4.1.4 Windows 3.1 and UNC
      4.1.5 An Application Object in Tree 1 Cannot Capture a Printer Port to a Server in Tree 2
      4.1.6 Distributing .INI Files
   4.2 Application Launcher 3.0
      4.2.1 Application Launcher Files Installed with the NT Client
      4.2.2 Application Launcher 2.01 and Earlier Files That Can Be Removed after Installation
   4.3 Application Launcher Snap-Ins
   4.4 Application Explorer
      4.4.1 Duplicate Icons in the System Tray
      4.4.2 Creating Application Explorer Desktop Icon for Users Connected to Windows NT Terminal Server or Citrix
   4.5 snAppShot
      4.5.1 DOS Shortcuts (PIF)
      4.5.2 Drive Mappings
      4.5.3 Rights to Destination Directory
      4.5.4 GroupWise Client (32-Bit)
5.0 Workstation Management
   5.1 User Policy Package
      5.1.1 Getting the Correct Paper Size When Distributing Printers
      5.1.2 Troubleshooting the Windows 95 User Policy Package
   5.2 NT User System Printer Policy
   5.3 RAS Configuration Policy
6.0 Novell Client
   6.1 Using an Outdated Novell Client for Windows NT
   6.2 The Primary Network Logon Must be the Novell Client
   6.3 Upgrading the Novell Client without a Full Install
   6.4 Running WM3X.EXE (the DOS/Windows Client) using Windows 3.x
7.0 Interoperability
   7.1 Using ZENworks with NDS for NT 2.0
   7.2 Using the English Version of ZENworks on Double-Byte Machines
8.0 Y2K Readiness
9.0 Product Documentation
   9.1 Installation and Upgrade Guide
   9.2 Online Help
      9.2.1 Error When Clicking Help Button
   9.3 Documentation on the Internet
   9.4 Other Information About the Product
      9.4.1 ZENworks Cool Solutions
10.0 Legal Information
   10.1 Disclaimer and Copyright
   10.2 Trademarks
  

1.0 What Is the ZENworks Starter Pack (October 1999)?

     The ZENworks Starter Pack includes many of the
     Workstation Management and Application Management
     functions that are part of the full version of ZENworks
     2.

     If you are currently using the full version of ZENworks
     2, the ZENworks Starter Pack installation program notifies
     you that continuing may disable some features that you are
     currently using (such as Software Metering). If you are
     already running a Starter Pack, the install will proceed
     without notifications.
     
     The following new features in Application Launcher 3.0
     (that is, the Application Launcher in the full version
     of ZENworks 2) are not included in the ZENworks Starter
     Pack:
     
       - Pre-install
       - System Requirements (Applications, Files, Environment
         Variables & Registry)
       - Run as system user
       - Workstation associated applications
       - Force Run Wait
       - Distribution Scripts
       - SNMP Reporting
       - Prompted Macros

     Other ZENworks 2 features not included in the Starter
     Pack are
     
       - Software Metering
       - Hardware and Software Inventory in Sybase or NDS
       - Inventory Reporting
       - Help Requester
       - Remote Control
       - Other Remote Management features, including
          - Remote View
          - Remote Execute
          - Chat
          - File Transfer
          - Remote Diagnostics
       - Third-Party Tools, including
          - GMT Check 2000 for ZENworks
          - NAI VirusScan

2.0 Installation

  
  2.1 Error When Installing on a NetWare 4.x Server

       The following error may occur while you are
       installing ZENworks Starter Pack on a NetWare 4.x
       server:

          "this server cannot resolve its own hostname
          please configure DNS hostname resolution" hit any
          key

       To resolve the error, edit the SYS:\ETC\HOSTS file
       to include the IP address and the name of the file
       server. For example:

       137.65.254.254 <Server Name>

       Failure to add this information may result in a
       server abend displaying the following text:

          abend: Free called with a memory block that has a
          null resource tag.
  
  2.2 Installing ZENworks Starter Pack from a Server Image

       If you copy the downloaded ZENworks Starter Pack
       software onto a server, you will need to map root to
       the directory from where you run WINSETUP.EXE.
       Otherwise, the installation program might not be able
       to locate certain .HLP files.
  
  2.3 NDS for NT Server System Requirements

       If you will be installing ZENworks on an NT Server
       whose NT domains are managed by NDS for NT, the
       server should meet the following minimum
       requirements:

          - Windows NT Server 4.0 with Service Pack 1, 3, 4, or 5.
            The NT server must be running on an NT file system (NTFS) in
            order to create a replica.
          - 64 MB RAM.
          - 175 MB of available disk space.
          - Administrative rights to the container where you install
            ZENworks.
          - Administrative rights to the NT server and to all
            portions of the NDS tree that will contain User objects that
            are domain-enabled.
          - Administrative rights to the root of the NDS tree to
            extend the schema.
     
     2.3.1 Installing ZENworks Starter Pack on NDS for NT

            When installing ZENworks in directory trees
            containing NDS for NT local replicas, be sure
            to wait until the ZENworks schema extensions
            have synchronized completely before starting
            any NDS partition operations involving the
            replicas. Preferably, you should perform the
            partition operations prior to the installation
            of ZENworks.
     
     2.3.2 Mapping Errors When installing ZENworks Starter Pack
            on an NT Server

            If you see the following mapping error when
            installing ZENworks to the NT server, map a
            drive to "SYS" share on the NT server and then
            rerun the ZENworks installation program.

               "Setup was unable to allocate a drive to use
               for transferring files. Please verify that
               you are using an authenticated connection,
               and there is a drive available. The
               installation will now exit."

            To map a drive, use the GUI utility or the NET
            USE command. For example, type

               NET USE * \\NTSERVER-NT\SYS

3.0 NetWare Administrator
  
  3.1 Using ZENworks NetWare Administrator 32

       The ZENworks Starter Pack supports NetWare
       Administrator 95 and NetWare Administrator NT.
       However, to take full advantage of the new features
       included in ZENworks, you should use NetWare
       Administrator 32, which ships with ZENworks. The
       ZENworks Starter Pack does not support ConsoleOne.

     
     3.1.1 Policy Objects May Appear in NetWare Administrator
            32

            If you run NetWare Administrator 95 or NetWare
            Administrator NT, save settings, and then run
            NetWare Administrator 32, you will see all the
            Policy objects in the browser window.

            To hide the Policy objects in NetWare
            Administrator 32, you can close all browser
            windows and open new browser windows, or you
            can remove the registry key for NetWare
            Administrator:

            HKEY_CURRENT_USER\Software\NetWare\Parameters\N
            etWare Administrator

            You can also hide Policy objects in NetWare
            Administrator 95, NetWare Administrator NT, and
            NetWare Administrator 32 if you use the
            View-Sort and Include dialog box to remove
            individual policies from the current browser
            window and save your settings.
     
     3.1.2 Running Snap-In DLLs Using NetWare Administrator 32

            NetWare Administrator 32 has support for old
            snap-in DLLs (those compiled with SNAPIN95.LIB
            or SNAPINNT.LIB) as well as new Snap-in DLLs
            (those compiled with SNAPIN32.LIB). NetWare
            Administrator 32 includes the following shim
            DLLs in the SYS:PUBLIC\WIN32 directory that
            support the old snap-ins:

              - NWCORE95.DLL
              - NWCOMN95.DLL
              - NWVCTL95.DLL
              - NWCORENT.DLL
              - NWCOMNNT.DLL
              - NWVCTLNT.DLL

            These DLLs make calls into the corresponding
            NetWare Administrator 32 DLLs (NWCORE32.DLL,
            NWCOMN32.DLL, and NWVCTL32.DLL.

            To run a snap-in DLL that has been installed
            with NetWare Administrator 95 or NetWare
            Administrator NT, copy the snap-in DLL to the
            SYS:PUBLIC\WIN32\SNAPINS directory and any
            supporting DLLs to the SYS:PUBLIC\WIN32
            directory. The snap-in directory is different
            if the snap-in runs only under Windows NT
            (SYS:PUBLIC\WIN32\SNAPINS\NTONLY) or Windows 95
            (SYS:PUBLIC\WIN32\SNAPINS\95ONLY). You can get
            a list of the current snap-in DLLs by viewing
            two registry keys under the NetWare
            Administrator key:

            HKEY_CURRENT_USER\Software\NetWare\Parameters\N
            etWare Administrator

            For NetWare Administrator 95:

               - Snap-in Object DLLs WIN95
               - Snap-in View DLLs WIN95

            For NetWare Administrator NT:

               - Snap-in Object DLLs WINNT
               - Snap-in View DLLs WINNT

            If the snap-in DLL loads resource DLLs or help
            files relative to NetWare Administrator (using
            NWAGetNLSFilePath), copy the resource DLLs and
            help files relative to the SYS:PUBLIC\WIN32
            directory. If the snap-in DLL loads resource
            DLLs or help files relative to the snap-in DLL,
            copy the resource DLLs and help files relative
            to the SYS:PUBLIC\WIN32\SNAPINS directory.

            Contact your vendor for a list of files and for
            the latest version of the snap-in DLL.
     
     3.1.3 Running Numerous Snap-Ins with NetWare Administrator
            32

            If you have configured the registry for
            numerous snap-ins to load for NetWare
            Administrator 95 or NetWare Administrator NT,
            adding the ZENworks snap-ins will cause the
            NetWare Administrator process to run out of
            Thread Local Storage handles. Windows 95 and
            Windows NT allocate 64 handles for the NetWare
            Administrator 95 or NetWare Administrator NT
            process. NetWare Administrator requires 17
            handles. Each Snap-in DLL can require from zero
            to four or more Thread Local Storage handles.

            The ZENworks snap-ins require four handles in
            all. If other snap-ins don't load or crash
            after adding the ZENworks snap-ins, you have
            likely exceeded the 64-handle limit on your
            workstation.

            Novell snap-ins that consume multiple handles
            will be fixed in future releases. In the
            meantime, you can remove unnecessary snap-ins
            from the registry so that your necessary
            snap-ins will load. The NetWare Administrator
            snap-in registry keys are:

            For NetWare Administrator 95

            HKEY_CURRENT_USER\Software\NetWare\Parameters\N
            etWare Administrator\Snapin Object DLLs WIN95

            For NetWare Administrator NT

            HKEY_CURRENT_USER\Software\NetWare\Parameters\N
            etWare Administrator\Snapin Object DLLs WINNT
     
     3.1.4 Using NetWare Administrator 32 with the NetWare 5
            Client

            Creating the Workstation Manager Client
            Configuration (WMCC) in NetWare Administrator
            32 requires that the Novell Client for Windows
            95 (v2.5 or higher) or Windows NT (v4.3 or
            higher) be installed on the workstation being
            used to create the policy. The snap-in depends
            on accessibility to the GUI Login Active-X
            controls to configure the WMCC policy for login
            settings.

     
     3.1.5 Using the Starter Pack on a Non-English Server

            Running the ZENworks Starter Pack on a server
            with a non-English OS could cause DLL version
            mismatch errors. These errors may occur if the
            version of NWADMN32.EXE you are running does
            not match the language-specific DLLs located on
            the server.

            To correct the problem, copy the NWADMR32.DLL
            and NWADLG32.DLL resource DLLs from
            \PRODUCTS\ZENWORKS\PUBLIC\WIN32\NLS\<LANGUAGE>
            on the ZENworks CD to
            \SYS:\PUBLIC\WIN32\<LANGUAGE> on the server.
  
  3.2 Using NetWare Administrator 95 or NetWare Administrator
       NT

       ZENworks requires that the DMPOLICY.DLL snap-in is
       the first ZENworks snap-in to be loaded by NetWare
       Administrator 95 or NetWare Administrator NT (this
       does not apply if you are using NetWare
       Administrator 32).

       In some instances, NetWare Administrator 95 and
       NetWare Administrator NT do not read these DLLs out
       of the Registry in order. In these scenarios, the
       DMPOLICY.DLL snap-in detects the problem and
       displays a warning message recommending that you fix
       the problem.

       Note that NetWare Administrator 95 and NetWare
       Administrator NT are not available with NetWare 5.

       The solution to this problem is to remove all
       ZENworks snap-ins from the snap-in object registry
       for NetWare Administrator and then re-enter them so
       that they are loaded in the correct order.

       This process is simplified by a .REG file, which is
       installed to the SYS:\PUBLIC\WIN95 and
       SYS:\PUBLIC\WINNT server directories during ZENworks
       installation. The file lists all registry keys
       needed for the ZENworks snap-ins to work.

       Depending on your version of ZENworks, this .REG
       file might be named ZENSTART.REG or ZENFULL.REG.

       To fix the problem

       1)Open the .REG file (either ZENSTART.REG or ZENFULL.REG)
          in Notepad or another ASCII text editor.
       2)Open Regedit and manually delete the keys found in the
          .REG file.
       3)Run Regedit ZENSTART.REG or Regedit ZENFULL.REG to reload
          the registry.
  
  3.3 Authenticating to a New NDS Tree Using NetWare
       Administrator 95 or NetWare Administrator NT

       When running on the ZENworks Client, NetWare
       Administrator 95 and NetWare Administrator NT might
       be unable to launch the NetWare Login dialog box
       when you try to browse to a tree to which you are
       not currently authenticated.

       However, you can task-switch to Windows Explorer,
       browse to the Network Neighborhood, and authenticate
       to the new tree without shutting down NetWare
       Administrator NT or NetWare Administrator 95. When
       you return to NetWare Administrator NT or NetWare
       Administrator 95, you should be able to browse to
       the new tree. This problem does not occur with
       NetWare Administrator 32.
  
  3.4 Using FastCache and BorderManager Snap-Ins

       FastCache and BorderManager currently require
       NetWare Administrator NT in order to install the NT
       snap-ins for these products. NetWare Administrator
       NT does not ship with ZENworks. If you don't have
       this file and you want to install one of these
       snap-ins, download it from the following address:

       www.novell.com/download
  
  3.5 User Profiles Snap-In

       In the User Profiles snap-in in NetWare
       Administrator 32, when you choose desktop
       preferences/display options and browse to a filename
       for either the screen saver or wallpaper, the
       snap-in converts your local drive mappings to a UNC
       mapping. When you type a path, make sure the mapping
       corresponds to the correct UNC path on the local
       machine making the changes, not to the user's
       workstation. The program uses the current
       workstation mappings for the conversion.

4.0 Application Management
  
  4.1 General Known Problems and Limitations
     
     4.1.1 Creating Application Objects with NetWare
            Administrator for Windows 95

            If NetWare Administrator for Windows 95 does
            not allow you to create Application objects,
            verify that ZENAPP32.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 with the product. Make sure that the
            registry key for Application Launcher Snap-In
            is set to either the hex or string value of
            "APPSNP95.DLL," but not to both.

            HKEY_CURRENT_USER\Software\NetWare\Parameters\N
            etWare Administrator\Snapin Object DLLs WIN95

            Or

            VALUE: APPSNP95.DLL = 41 50 50 53 4E 50 39 35
            2E 44 4C 4C
     
     4.1.2 Creating Application Objects with NetWare
            Administrator for Windows NT

            If NetWare Administrator for Windows NT does
            not allow you to create Application objects,
            verify ZENAPP32.DLL and that APPSNPNT.DLL are
            located in the same directory as NWADMNNT.EXE.
            You should also verify that APPRES32.DLL,
            APPSNAP.HLP, ZENWORKS.HLP, and ZENWORKS.CNT are
            in the NLS\<LANGUAGE> directory. Make sure that
            the dates of the files are the same as those
            shipped with the product. Make sure that the
            registry key for Application Launcher snap-in
            is set to either the hex or string value of
            "APPSNPNT.DLL," but not to both.

            HKEY_CURRENT_USER\Software\NetWare\Parameters\N
            etWare Administrator\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
     
     4.1.3 Using the Timed Refresh Setting

            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.
     
     4.1.4 Windows 3.1 and UNC

            In Windows 3.1, Application Launcher does not
            support UNC paths in the distribution part of
            an Application object (for example, path to a
            file to be copied) that has a server name
            greater than 11 characters or a volume name
            greater than eight characters. Use a drive
            letter path in place of the UNC path or upgrade
            to Windows for Workgroups 3.11.
     
     4.1.5 An Application Object in Tree 1 Cannot Capture a
            Printer Port to a Server in Tree 2

            Defining printer port captures within an
            application object must be restricted to
            servers within the tree in which the
            Application object is defined.
  
     4.1.6 Distributing .INI Files

            Windows purposely sets a 64K size limitation on
            .INI files called by the standard Windows APIs. This
            limitation directly affects the distribution of .INI
            files in a ZENworks Application object, deleting data
            above the 64K limit.

            You can work around this limitation by letting the
            Application Launcher distribute the large .INI file
            instead of trying to generate a new .INI from scratch.
            Add the file to the Application Files tab (like any
            other file that is being distributed) and make any
            changes as necessary (such as "Copy if Newer",
            "Distribute Always", etc).

            For more information about managing Application files,
            click the ZENworks 2 documentation link at the ZENworks
            Starter Pack documentation web site at

            www.novell.com/documentation/lg/zenstp/docui/index.html

            then click Application Management > Application
            Distribution > Managing > Application files.

  4.2 Application Launcher 3.0

       Application Launcher 3.0 is a collection of
       primarily 32-bit applications. It will not work on a
       16-bit platform (that is, Windows 3.1). The
       NALW31.EXE and accompanying files shipping with
       Application Launcher 3.0 are the same as those
       shipped with version 2.7.
     
     4.2.1 Application Launcher Files Installed with the NT
            Client

            As part of the NT Client install, you can
            install the Application Launcher NT Service. If
            this component is installed to the workstation,
            the following files that are copied (assume
            Windows NT is located in C:\WINNT):

               - C:\WINNT\SYSTEM32\NALNTSRV.EXE (Application Launcher NT
                 Service)
               - C:\WINNT\SYSTEM32\ZENAPP32.DLL (32-bit Application
                 Launcher library)
               - C:\WINNT\SYSTEM32\NALSRVLD.EXE (Load/Unload for NT
                 Client)
               - C:\WINNT\SYSTEM32\NLS\ENGLISH\NALNTRES.DLL (App
                 Launcher NT Service resource)

            If you plan to continue using Application
            Launcher 2.0 or Application Launcher 2.01,
            Novell recommends that you do not install
            Application Launcher NT Service as part of the
            NT Client install.
     
     4.2.2 Application Launcher 2.01 and Earlier Files That Can
            Be Removed after Installation

               - SYS:PUBLIC\NALW95.EXE (NALWIN32.EXE is now used)
               - SYS:PUBLIC\NLS\ENGLISH\APPRES3X.DLL (APPRES16.DLL is
                 now used)
               - SYS:PUBLIC\NLS\ENGLISH\APPSNAP.CNT (ZENWORKS.CNT is now
                 used)
               - SYS:PUBLIC\SNAPSHOT\NLS\ENGLISH\DVJRES16.DLL (This file
                 has been changed to SNPRES16.DLL)
               - SYS:PUBLIC\SNAPSHOT\NLS\ENGLISH\DVJRES32.DLL (This file
                 has been changed to SNPRES32.DLL)
               - SYS:PUBLIC\SNAPSHOT\NLS\ENGLISH\SNAPSHOT.CNT
                 (APPSNAP.CNT is now used)
               - SYS:PUBLIC\SNAPSHOT\NLS\ENGLISH\SNAPSHOT.HLP
                 (APPSNAP.HLP is now used)

            The following subdirectories contained the
            client login files for Application Launcher to
            update the user's workstation. Application
            Launcher 3.0 no longer updates client login
            files.

               - SYS:PUBLIC\NALLIB\WIN31
               - SYS:PUBLIC\NALLIB\WIN95
               - SYS:PUBLIC\NALLIB\WINNT
  
  4.3 Application Launcher Snap-Ins

       If the version of MSVCRT.DLL in the Windows System
       directory (that is, the C:\WINDOWS\SYSTEM on Windows
       95/98 or C:\WINNT\SYSTEM32 for Windows NT), is not
       at least version 6.0, the Application Launcher
       snap-ins (APPSNP32.DLL and APPSNPEX.DLL) may fail to
       load when NetWare Administrator runs. The snap-ins
       are dependent on MSVCRT.DLL version 6.0 or higher.

       If you installed the Novell Clients that ship with
       ZENworks 2, the Client install program adds
       MSVCRT.DLL (version 6.00.8337.0; 1/5/1999) to the
       files copied.

       To check the version of MSVCRT.DLL you have
       installed

       1) From the Windows System directory, right-click
          MSCVRT.DLL.
       2) Click Properties > Version.

       If you chose not to upgrade the clients during the
       ZENworks 2 install, you can use any of the following
       options to update a MSVCRT.DLL already in use:

       Option 1: Install the Novell Client that ships with
                 ZENworks. Client installs are augmented with version
                 6.0 of MSVCRT.DLL.

       Option 2: Run NAL.EXE or NALEXPLD.EXE from SYS:\PUBLIC to
                 check and update files on the local drive as needed
                 (including MSVCRT.DLL from SYS:\PUBLIC\WIN32). If
                 MSVCRT.DLL is updated, you will be prompted to restart
                 Windows.

                 Note that you may optionally include the /i
                 command line option when you run NAL.EXE or
                 NALEXPLD.EXE. This does not launch the
                 Application Launcher window, but it will
                 update files on the local drive.

       Option 3: This option is less desirable because of the
                 increased chance of making mistakes.
                 1) Copy MSVCRT.DLL from SYS:\PUBLIC\WIN32 to a
                    temporary directory on the local drive.
                 2) Exit Windows to a DOS prompt.
                 3) Copy MSVCRT.DLL from the temporary location to the
                    Windows System directory.
  
  4.4 Application Explorer
     
     4.4.1 Duplicate Icons in the System Tray

            If more than one icon for the same application
            displays in the system tray, two NALDESK.EXE
            programs may be running. Check the Startup
            folder, registry, login scripts, and policies
            for multiple loads.
     
     4.4.2 Creating Application Explorer Desktop Icon for Users
            Connected to Windows NT Terminal Server or Citrix

            If you run ZENworks on a Windows Terminal
            Server or Citrix, users connected to this type
            of server will not have an Application Explorer
            icon on their desktops unless you manually
            create and distribute it.

            Use the Create Applications Wizard to create a
            simple Application object, pointing to the
            Application Explorer executable at
            \\<SERVER>\SYS\PUBLIC\NAL.EXE. Assign a name
            and icon to this object and associate it with
            the desktop of the User, Workstation, Group,
            Organization, Organizational Unit, or Country
            object that need will to use it.

            When the associated users reboot their
            workstations, the icon representing NAL.EXE is
            displayed on their desktops. When double-
            clicked, this icon launches the Application
            Launcher and users will have access to all of
            their distributed applications.
  
  4.5 snAppShot
     
     4.5.1 DOS Shortcuts (PIF)

            snAppShot does not correctly discover shortcuts
            to DOS executable files; they are discovered as
            new files.
     
     4.5.2 Drive Mappings

            The location where snAppShot places the .FIL
            files defaults to a drive letter. After you
            import the Template (.AOT) file into an
            Application object, go to the Macros page and
            change the SOURCE_PATH to a UNC path. For
            example, G:\PUBLIC\AOT\NETSCAPE

            changes to

            \\<SERVERNAME>\SYS\PUBLIC\AOT\NETSCAPE

            This allows users to run the program without
            mapping to a drive.
     
     4.5.3 Rights to Destination Directory

            When you run snAppShot, make sure you have
            rights to the destination directory or to
            directories you specify for the .AOT file and
            .FIL files. (You enter these in the fields
            labeled "Application files(s) location" and
            "Application object template (.AOT) filename
            and location.") If you enter a path to which
            you do not have rights, snAppShot will not
            create valid "snapshots."
     
     4.5.4 GroupWise Client (32-Bit)

            snAppShot may encounter a conflict when running
            at the same time as the GroupWise Client
            (32-bit) installation. If you encounter this
            problem, cancel snAppShot after the first
            picture of the workstation has been taken and
            before you install the GroupWise Client.
            Because the first picture is stored in files,
            cancelling snAppShot will work. After you
            install the GroupWise Client, you can restart
            snAppShot and it will start again where it
            ended.

5.0 Workstation Management
  
  5.1 User Policy Package
     
     5.1.1 Getting the Correct Paper Size When Distributing
            Printers

            When distributing a printer with a User Policy
            Package, the printer may prompt to insert
            Letter paper size although all printer settings
            at the workstation refer to A4. This occurs
            when the Regional Settings of the workstation
            and the user are not set properly.

            To correct the setting if your location is
            Germany, Denmark, Sweden, or another European
            country, click the Start menu > Settings >
            Control Panel > double-click Regional Settings
            > make sure the paper size defaults are set to
            A4 > make sure the Regional Settings of the
            users match your country.

            When the Regional Settings is set to US, the
            paper size setting will default to Letter.
     
     5.1.2 Troubleshooting the Windows 95 User Policy Package

            In the 95 Desktop Preferences Policy, if you
            configure a Serial Key Device in Accessibility
            Options but do not have a physical device
            connected to your computer, you may receive a
            general fault protection error in Windows 95/98
            the next time you restart the workstation.
  
  5.2 NT User System Printer Policy

       If you set up the NT User System printer policy and
       then log in to an NT workstation as a user who is
       set up to use that Policy Package, you may receive a
       Dr. Watson error message pointing to WMRUNDLL.EXE.
       This is a Windows NT problem that will be fixed in
       Support Pack 5. To work around the problem, select a
       default printer in the Policy.
  
  5.3 RAS Configuration Policy

       A Windows 95 RAS policy can be safely edited only
       from a Windows 95 or Windows 98 workstation. A
       Windows NT RAS policy can be safely edited only from
       a Windows NT workstation.

6.0 Novell Client
  
  6.1 Using an Outdated Novell Client for Windows NT
       In NetWare Administrator, after you create a Policy
       Package object and modify a policy on the Policies
       page, you can use the Reset button on the Policies
       page to reset the selected policy to the default
       settings. After clicking Reset, if you receive a
       -601 error ("Object not found"), you are probably
       running an old version of the Novell Client for
       Windows NT.

       To resolve this, update your client to the one that
       ships with the ZENworks Starter Pack.

       Similarly, after you add a scheduled action to a
       Policy Package, if you receive an "Object not found"
       error, you are probably running an old version of
       the Novell Client for Windows NT. To resolve this,
       update your client to the one that ships with the
       ZENworks Starter Pack.
  
  6.2 The Primary Network Logon Must be the Novell Client

       Desktop preferences and user system policies are
       only processed when the primary network logon is the
       Novell Client.
  
  6.3 Upgrading the Novell Client without a Full Install

       If you have previously installed the WIN95 version
       3.1 or WINNT version 4.6 clients and you want to
       upgrade to the ZENworks 2 clients without having to
       run through a full client install, run SETUPSP.EXE
       found in the \PRODUCTS\WIN95 directory or the
       \PRODUCTS\WINNT directory. This program installs the
       Client Service Pack 1 for the WIN95 version 3.1 or
       WINNT version 4.6 clients.
  
  6.4 Running WM3X.EXE (the DOS/Windows Client) using Windows
       3.x

       The DOS/Windows Client, WM3X.EXE, is intended to run
       at the end of STARTNET.BAT (or before Windows 3.x
       loads). Running WM3X.EXE after Windows is loaded
       (from a DOS box) could result in a general fault
       protection error.

7.0 Interoperability
  
  7.1 Using ZENworks with NDS for NT 2.0

       ZENworks is not compatible with the Novell Windows
       NT 4.12 Client that is installed to the Domain
       Controller with NDS for NT 2.0.

       ZENworks requires a Novell Client for NT version 4.3
       or greater. The current release of NDS for NT
       version 2.01 includes a Novell Client for the domain
       controller that is compatible with ZENworks.
  
  7.2 Using the English Version of ZENworks on Double-Byte
       Machines

       You may experience certain errors if you use the
       English version of ZENworks on a double-byte-enabled
       machine using the 1.1.5 Java Virtual Machine (JVM).

       A newer version of the JVM, version 1.1.7, helps to
       eliminate the double-byte errors. A self-extracting
       zip file, JVM117B.EXE, located in the \PRODUCTS\JVM
       folder of the ZENworks product CD, launches
       InstallShield and installs a new version of the JVM
       on your ZENworks server.

       Note that you should run this install after you
       install ZENworks; otherwise, certain parts of
       ZENworks will not perform correctly.

8.0 Y2K Readiness

     Novell has made a diligent effort to assure than
     ZENworks technology is Y2K ready. You should be aware,
     however, that one of the Windows 95 common control
     files used by ZENworks and shipped on the ZENworks 2
     CD, COMCTL32.DLL, is not Y2K ready.

     Although Novell does not have the rights to
     redistribute an updated version of COMCTL32.DLL,
     Microsoft has released a Common Controls update
     (401COMUPD.EXE) to update the COMCTL32.DLL on your
     workstation. The update is available on the Microsoft
     web site at

     www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp

     Follow the instructions at the web site to update the
     file.

     The following text is an excerpt from the Microsoft
     TechNet web site dedicated to Year 2000 issues. The
     text explains additional steps you should take to
     ensure Y2K readiness with COMCTL32.DLL:

       "When Regional Settings from Control Panel is set to
       use two digits for years, the Date/Time Picker
       function may not return the proper date. To ensure
       proper handling of dates, set Regional Settings to
       4-digit date handling."

     The Microsoft TechNet web site can be accessed at

     www.microsoft.com/technet/year2k/product/user_view68383EN.htm

9.0 Product Documentation
  
  9.1 Installation and Upgrade Guide

       This guide provides users with a quick solution for
       installing the ZENworks Starter Pack and configuring
       some of its basic and most popular functionality.
       The audience for the guide is the network
       administrator who is performing an installation for
       the first time on a test system. The guide is
       printed and included in the product box. It is also
       available in .PDF file format and is viewable from
       an Adobe Acrobat viewer. The .PDF file can be
       accessed during the ZENworks Starter Pack
       installation or by browsing the Starter Pack CD.

       The Upgrade chapter provides information that
       administrators may be interested in when upgrading
       from an older version of the ZENworks Starter Pack.
  
  9.2 Online Help

       Help is available from the workstation or from the
       desktop for the administrator or a user whenever a
       Help button is accessible from a ZENworks, Novell
       Client, or Application Launcher interface.

       Critical tasks are documented in online help while
       more detailed, conceptual documentation can be found
       on the Internet. This information is referenced with
       active links from help that launch a web browser to
       access the contents page of that information.
     
     9.2.1 Error When Clicking Help Button

            After the initial installation of the Starter
            Pack, Windows Help may fail to properly open a
            help file when you click a Help button on a
            ZENworks snap-in properties page. In this
            situation, you may see a Windows Help error
            similar to the following:

            "Unable to open the file
            \public\win32\nls\english\Zenworks.cnt"

            To correct the problem, browse to
            \PUBLIC\WIN32\NLS\ENGLISH with Windows Explorer
            and open ZENWORKS.HLP manually. After the file
            is opened initially, Help buttons in the
            NetWare Administrator should function normally.
  
  9.3 Documentation on the Internet

       The most current ZENworks documentation is found at
       the ZENworks Starter Pack documentation web site at

       www.novell.com/documentation/lg/zenstp/docui/index.html

       This URL has a link to a web site that displays the
       contents of the full version of ZENworks 2. Here you
       can study the detail and conceptual information
       about the components in the full product, as well as
       learn about the components that are included with
       the ZENworks Starter Pack.
  
  9.4 Other Information About the Product
     
     9.4.1 ZENworks Cool Solutions

            You will find feature articles, questions and
            answers, tips of the week, links to specific
            Novell Support Technical Information Documents
            (TIDs) and more about ZENworks and the ZENworks
            Starter Pack on the Internet at the ZENworks
            Cool Solutions web site maintained by the Novell
            Content & Community Web Group at

            www.novell.com/coolsolutions/zenworks

            The site is periodically updated with current
            product issues. It also provides a searchable
            archive that contains information for making
            the most of ZENworks.

10.0 Legal Information
  
  10.1 Disclaimer and Copyright

       Novell, Inc. makes no representations or warranties
       with respect to the contents or use of this
       documentation, and specifically disclaims any
       express or implied warranties of merchantability or
       fitness for any particular purpose. Further, Novell,
       Inc. reserves the right to revise this publication
       and to make changes to its content, at any time,
       without obligation to notify any person or entity of
       such revisions or changes.

       Further, Novell, Inc. makes no representations or
       warranties with respect to any software, and
       specifically disclaims any express or implied
       warranties of merchantability or fitness for any
       particular purpose. Further, Novell, Inc. reserves
       the right to make changes to any and all parts of
       Novell software, at any time, without any obligation
       to notify any person or entity of such changes.

       Copyright (C) 1999 Novell, Inc. All rights reserved.
       No part of this publication may be reproduced,
       photocopied, stored on a retrieval system, or
       transmitted without the express written consent of
       the publisher.
  
  10.2 Trademarks

       Novell, NetWare, and GroupWise are registered trademarks of
       Novell, Inc. in the United States and other countries.

       BorderManager, BorderManager FastCache, NDS,
       NetWare, Novell Client, and ZENworks are trademarks
       of Novell, Inc.

       All third-party trademarks are the property of their
       respective owners..

Feedback service temporarily unavailable. For content questions or problems, please contact Support.