1 / 54

Chapter Nine

Chapter Nine. Managing Applications. Chapter Objectives. Identify the benefits of Zero Effort Networks (Z.E.N.works) as well as its software and hardware requirements Install Z.E.N.works on servers and clients

hedva
Télécharger la présentation

Chapter Nine

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter Nine Managing Applications

  2. Chapter Objectives • Identify the benefits of Zero Effort Networks (Z.E.N.works) as well as its software and hardware requirements • Install Z.E.N.works on servers and clients • Use the Application Launcher to automate installation and access to software over the network • Use Z.E.N.Works to create workstation objects

  3. Chapter Objectives • Use Z.E.N.Works to manage user desktop environments • Understand how to use Z.E.N.Works to manage workstations remotely

  4. Benefits • Application Management • Application Launcher allows you to distribute, upgrade, and manage applications. • Workstation Management • Store user and desktop configurations in NDS. • Import workstations into NDS tree. • Workstation Inventory • Remote control

  5. Requirements • 486/33 or higher processor • 16 MB RAM for Windows 95 • 24 MB RAM for NT • Hard disk space: • 4 MB workstation • 24 MB full installation • New Novell NetWare Client • 32-bit NetWare Administrator

  6. Installing Z.E.N.works • Log in using the Admin user. • Insert the Novell Client CD-ROM to run the WinSetup program. • Select the option to Install Z.E.N.works.

  7. Install Z.E.N.works (2) • A license agreement windows will be displayed. • Click Yes to confirm license agreement and display the Setup Type window. • Verify that the Typical option is selected and click Next to display a list of servers.

  8. Install Z.E.N.works (3) • Verify that the correct server and tree are checked and then click Next to display a language selection window. • Verify that the English language is checked and then click Next to display the installation summary window.

  9. Install Z.E.N.works (4) • Verify that the options you want are selected and click Next to copy files to the server and workstation. • The Context selection screen allows you to select the context where workstation auto-registration will start.

  10. Install Z.E.N.works (5) • Select [Root] to allow workstations to be registered throughout the entire tree. Users will then be given rights to register workstations in any container. • Click Next to select the [Root] context and display the completion window.

  11. Z.E.N.works Client • After Z.E.N.works is installed on the server each client should be updated. Z.E.N.works can run on the following clients. • Windows 3.x (limited feature support) • Windows 95/98 • Windows NT

  12. Installing Z.E.N.works Client (1) • Browse to the Public directory. Browse to \Client\Win95\ibm_enu and run the Setup program. • Click Yes to agree to the license agreement. • Click the Custom option and click Install to display the Protocol Preference window.

  13. Installing Z.E.N.works Client (2) • Select the protocol to be used. At this time use IPX only as TCP/IP will be added in chapter 10. • Click Next to display the Login Authentication options window. • Select the NDS log in option and click Yes.

  14. Installing Z.E.N.works Client (3) • At a minimum click: • Novell Workstation Manager. • Novell Distributed Print Services • Network Management Responder • If you have the full version of Z.E.N you can also select the Remote Control option.

  15. Activity - Install Z.E.N.works Client • After Z.E.N.works is installed on the server, each client should be updated. Z.E.N.works can be installed manually or by using Novell’s Automatic Client Update. In this activity you will manually install the Z.E.N.works client on your workstation.

  16. Managing Applications • Windows Environment • Dynamic Link Library (DLL) • Part of the program files copied to the workstation during installation of a software package. Certain DLL may be required to run an application. • Registry • Database of Windows configuration information.. • Often modified during application installation to meet the configuration of the application software.

  17. Application Launcher Components • NetWare Administrator Snap-in • Provides logic to manage application objects. • Snapshot Utility • Used to determine the DLLs and Registry changes needed by an application. • Application Object • Contains information on an application. • Application Launcher utilities

  18. NetWare Administrator SnapIn • Extends the capability of the 32-bit NetWare Administrator program through the APPSNP32.DLL. • The APSND32.DLL is located in the SYS:PUBLIC\WIN32\SNAPINS directory. • Necessary to create, modify, and display application object details and new container and user property pages.

  19. The SnapShot Utility • Certain applications require workstation Registry changes and DLLs in order to run. • The SnapShot utility is used to take a “picture” of the workstation before and after the installation of an application. • SnapShot uses the before and after shots to create an Application Object Template (AOT) file that is needed by Application Launcher to automatically update other computers to run the applications.

  20. Using SnapShot (1) • Start the SnapShot program. • Browse to: F:\Public\Snapshot • Run SnapShot.exe • Select Standard to display the application object name window.

  21. Using SnapShot (2) • Type in the Application name and then click in the Application icon title. By default the application title will be the same as the application name. • Click Next to display the AOT File location window.

  22. Using SnapShot (3) • Use this window to specify where the Application software files will be stored. • All the application files used during the installation will be copied to this directory and given a special AOT extension. • Click Next to continue.

  23. Using SnapShot (4) • In this window you need to specify the location where SnapShot will store your AOT files. • By default select the same location as you used for your installation files. • Click Next to continue.

  24. Using SnapShot (5) • In the drive scan window specify which drives SnapShot should scan to any installation changes. • In addition to drive C: specify any other drive letters where the software will be installed. • Click Next to continue.

  25. Using SnapShot (6) • After drives have been selected the SnapShot utility takes a snapshot of the current computer configuration. This may take several minutes. After the snapshot is complete the Run Application window will be displayed. • Click the Run Application button and install your software.

  26. Using SnapShot (7) • During application installation record the application’s directory. • After the installation is complete click Next in the Run Application window. • In the Application Installation window enter the path to the application files and click Next to continue.

  27. Using SnapShot (8) • The SnapShot utility will now scan the drives and take a snapshot of the Registry after the installation. It will then use this information to create an AOT file in the directory you specified. • This process will take several minutes and then a completion window will be displayed showing the name and location of the AOT files. • Click Finish to exit the SnapShot utility.

  28. Activity - Using SnapShot • In this activity you will use the SnapShot utility to install a copy of the NetScape software and create the installation and AOT files that can be used to distribute the application to other workstations.

  29. Application Objects • Application objects store configuration and user access information. • Path to executable files. • Required workstation operation system and hardware requirements. • Required drive letter mappings. • Users, groups, or containers • Registry Settings.

  30. Creating Application Objects (1) • Launch NetWare Administrator • Highlight a container. • Press [Ins] and select Application Object type. • Select how the application object is to be created. • Simple (no AOT file). • From AOT file. • Duplicate object.

  31. Creating Application Objects (2) • If creating from a AOT file, enter the path to the directory where the AOT file is located and click next.

  32. Creating Application Objects (3) • Verify that the Customize Application window contains the path to the installation and target file. • The installation files were copied by SnapShot with an AOT extension. • The target path is where the executable files will be placed.

  33. Creating Application Objects (4) • Click Finish to create the application object. • Double-click the application object to view and customize its properties. • Identification • Path to Executable • System Requirements • Associations • Select users, groups, containers

  34. Activities - Application Objects • In the first activity you will create an application object for Netscape from the AOT file. • In the second activity you will configure the application object for its system requirement, valid users, and executable path.

  35. Delivering the Application • Application Launcher software runs on user workstation and displays application icons. • Wrapper - determines which launcher to run • NAL.EXE • Launcher - displays launcher window with icons for the client • NALW31 - Windows 3.x • NALWIN32 - Windows 95/98 and NT

  36. Starting Application Launcher • Place NAL.Exe command in login script. • Use scheduler on Z.E.N.works clients. • Double-click clock and notepad icon in status bar. • Place NAL.Exe command in the workstation property package associated with the workstations.

  37. Activity - Delivering Applications • In this activity you first simulate installing installing Netscape on another computer by removing the Netscape applications from your computer. • Next you will modify your container login script to run the wrapper software. • To test application delivery you will need to log in as Kellie and then verify that NetScape is automatically re-installed on your computer.

  38. Managing Workstations • Windows Policies • Policies contain configuration information that is placed in the Registry of a workstation at login. • NDS Policy Package Objects • Workstation Policy Packages • User Policy Packages

  39. Workstation Policy Package • Computer Policies • Path to Windows Setup files • Run options (start Application Launcher) • Restrictions • Printer Policies • Inventory • Automatically update hardware information on workstation • Remote Control Policies • Enable or disable remote control • Set user associations and alert options

  40. User Policy Package • Computer system policies • Set restrictions on options such as using Network Neighborhood • Desktop Preferences • Set default wall paper, screen saver, etc • Workstation Import Policy • Enable importing of workstations • Set location and name information

  41. Activity - Create User Policy Package • In this activity you will use NetWare Administrator to create a user policy package that you will use in the next activity to import your workstation into the NDS tree.

  42. Importing a Workstation • Benefits: • Allows inventory information about the computer’s configuration and hardware to be stored in NDS. • Allows workstation packages to be applied to an individual workstation or all workstations in a container. • Allows use of the remote control feature to be used to manage a workstations.

  43. Steps to Import a Workstation • Workstation Import Policy is enabled • Workstation is registered when a user logs in. • WSREG32.EXE run from login script • WSREG32.DLL run from Z.E.N.works scheduler. • Workstation is imported using NetWare Administrator. • Workstation is re-registered in the tree the next time a user logs in.

  44. Enable Workstation Policy

  45. Import Workstation

  46. Activity - Importing a Workstation • In this activity you will perform the following steps: • Enable the Workstation Import policy. • Register your workstation. • Import the workstation. • Re-register your workstation and verify that it exists in the tree.

  47. Activity - Standard User Desktop • In this activity you will use the Computer System policy along with the Desktop Preferences policy to setup a desktop environment that will restrict certain Windows features and provide a standard look to all workstations.

  48. Remote Management Features • Reduces the number of trips to user workstations. • View workstation screen in a window of your computer. • Use your keyboard and mouse to operate the remote computer. • Provides security • Allows only designated users to control specific computers. • Provides notification to user of remote workstation.

  49. Remote Control Requirements • Requires full version of Z.E.N.works • Remote workstation must run the Wuser.exe program. (Wuser for Windows 3.x) • Can be enabled through: • User Policy package • Workstation Policy package (overrides user policy) • Directly through the workstation object (overrides both workstation and user policies)

  50. Chapter Summary • Z.E.N.works functions: • Application Management • Workstation Management • Remote Control • Implementation of Z.E.N.works. • Install on Server. • Update workstation to new Z.E.N.works client.

More Related