9                   POLYCENTER AssetWORKS T1.0 Field Test 3 ,                                Release Notes-                              October 28, 1994     E Copyright by Digital Equipment Corporation 1994. All Rights Reserved.   I Digital conducts its business in a manner that conserves the environment  H and protects the safety and health of its employees, customers, and the 
 community.  C All trademarks and registered trademarks are the property of their   respective holders.     C The following section contains the T1.0 Field Test 3 Release Notes.     - 1.0 Changes from Field Test 2 to Field Test 3    1.1  Miscellaneous  @     * Various bug fixes from Field Test 1 and 2 problem reports.  <     * The sender/receiver communication protocol used by theE       AssetWORKS server and agents now provides better security.  The D       senders/receivers shipped with FT3 do not support the protocolD       used by the FT2 software.  You will need to upgrade the server       and all agents to FT3.  @       Beginning with the actual release of POLYCENTER AssetWORKSC       Version V1.0, Digital will make every attempt to provide some =       degree of backward compatibility to the sender/receiver        communications protocol.  A     * This field test introduces PC-style "shrinkwrap" licensing. >       LMF license checks have been removed from the POLYCENTERD       Software Distribution (PSD) and POLYCENTER System Census (PSC)B       kits.  This does not relieve any site from its obligation toD       abide by the field test agreement and the Terms and Conditions7       of purchase and use of these Digital products.       1.2  PAW Communications   D     * An AssetWORKS-enabled SMS Site Server will no longer propagate>       changes of the PAW communications password to client PAWB       systems.  If you need to change the password, you must do soC       manually on the server and each client system that reports to D       it.  To improve security, PAW no longer transmits the password!       on the network in any form.   F     * The AssetWORKS communications security mode and password must beJ       identical on both the AssetWORKS-enabled SMS Site Servers and on all       AssetWORKS clients.   + 1.3  POLYCENTER Software Distribution         C     * PSD now installs the PSD server, client and POLYCENTER System >       Census agent automatically.  Please refer to the product?       documentation for instructions and a sample installation.    1.4  POLYCENTER System Census   F     * The PSC installation prompts for a PSC Security Mode and key, in>       addition to the PAW security mode and password.  DigitalF       recommends that you enable PSC "Secure Mode" and supply a randomE       key value.  The PSC Secure Mode setting and key will not affect 5       PSC operation in an AssetWORKS environment.        1.5  UNIX platforms   C     * A beta version of the HP-UX agent is available.  In this beta 7       release we introduce inventory capabilities only.   <     * PAW now reports diagnostic and informational events toD       /paw/debug/event.log on the local Unix machine.  If you defineD       the environment variable PAWEVENT,  PAW will also report theseC       events to your AssetWORKS-enabled SMS Site Server and display        them in the Event Viewer.   C     * /paw/sbin/paw configure  now logs changes locally to the file        /paw/debug/config.log   @     * A new tool, /paw/sbin/pawscript, allows you to write shellC       scripts in a Windows NT editor, such as write or notepad, and 9       sends them to UNIX machines to be executed.  Issue: !          #/paw/sbin/pawscript -H         to view the online help.  4     * For online help on how to install PAW, execute          #install.paw -H  1     * For online help once PAW is installed, type           #/paw/sbin/paw -H  (     * If you encounter problems, issue:           #/paw/sbin/pawbugA       to create a uuencoded snapshot of the state of the PAW Unix D       Agent.  You can send this snapshot to the PAW development team+       through the QAR system for diagnosis.   B     * awcollect: SMS resychronize events must be handled manually.  D       SMS may detect an inconsistancy with its database and the dataB       in a MIF file generated by awcollect on a client.  When thisC       happens SMS generates a synchronize event which indicates the E       client that was inconsistant and caused the event.  In FT3 when ?       a synchronize event occurs, the resynchronization must be C       handled manually by running awcollect with the -r flag on the C       specified client machine.  This will clear the inconsistancy.     % 1.6  PAW Service Manager (Windows NT)   @     * Connect/Exit is the only pulldown menu item that currentlyC       works.  Therefore, the PAW Service Manager works only for the E       local machine, and you can trigger refresh only by selecting an D       item in the list box or changing the state of a selected item.  F     * There is no online help.  A message box pops up to tell you this%       if you press the "Help" button.     % 2.0  Interoperation with PATHWORKS V5   @     * You can set up a PATHWORKS V5 server to serve an SMS LogonF       server and/or an SMS Package Distribution server.  The PATHWORKSB       server must be running version 5 or newer to support the LAND       Manager protocols that the SMS Site Server uses to set up Site       Domains.  A       To add a PATHWORKS server as a domain, follow the steps for F       adding a LAN Manager domain.  It may be best to specify the nodeF       name and device in place of letting the SMS Site Server find allE       the logon servers for the domain.  The PATHWORKS server must be D       running TCP/IP or NetBEUI protocol so that the SMS Site Server       can access it.  E       Normally the SMS Site Server will create the needed directories B       and files on a new Domain logon server.  Because of a bug inE       PATHWORKS V5, you will need to perform some manual steps to set C       up the SMS_SHR share that SMS uses to support clients.  There        are two ways to do this:  B       1) Create a FAT container volume with the name D.DSK with atD       least 20MB of space.  When you enter the PATHWORKS node in theF       SMS Site properties domain dialog box, specify 'D' as the device:       to be used. (See note below about Macintosh support)  C       2) Add the SMS Site domain normally and wait for the SMS Site F       server to attempt to create the SMS_SHR share.  There will be anF       error in the NT event viewer when this step fails. At this pointF       you need to create the SMS_SHR by hand using the ADMIN/PATH userB       interface giving C:[SMS.LOGON__2ESRV] as the directory name.    8     * If the PATHWORKS V5 server you are using as an SMSD       Domain is running on OpenVMS, you will not be able to make useB       of the automatic logon script updates to include commands toF       start the client script.  PATHWORKS V5 for OpenVMS (LAN Manager)@       does not support the needed directory replication feature.  E     * If you need to include Macintosh client support and you plan to F       use a PATHWORKS V5 for OpenVMS server as an SMS domain, you willE       not be able locate the SMS_SHR files on a FAT Volume.  A bug in C       PATHWORKS FAT volumes causes them to lose free space when SMS B       attempts to copy the Macintosh support files to the SMS_SHR.  ?     * The SMS Site Server will put the wrong protections on the F       SMS_SHR DESPOOLR.BOX directory on PATHWORKS 5.0 servers.  Create>       access needs to be added to allow the status of packagesE       installed on DOS client machines to be returned to the SMS Site 
       server.    2.1  PATHWORKS V4.x Clients   D     * PATHWORKS V4.x clients must meet the following requirements inA       order to get a correct inventory and to be supported as SMS        clients.  >       1) There must be one free network drive letter after allD       automatically connected devices are connected to allow for the1       connection to the SMS_SHR during inventory.   B       2) The PC must have an up to date C:\CFGWS.DAT as written byB       NETSETUP.EXE in order to collect some of the inventory data.  F       3) The LAN Manager NETAPI.DLL file must be in the PC's PATH whenE       Windows is started.  This file is copied automatically when the D       enhanced redirector is used.  This file can be copied from the@       \\server\PCSAV41\LMDOS\NETPROG  directory.  It can also beB       copied to the C:\MS\SMS\BIN directory after the client files       have been installed.  F       The DECnet address for these clients will be included in the SMS<       database in the location reserved for the IPX address.   2.2  PATHWORKS V5.x Clients          B     * PATHWORKS V5.x clients that use the Digital Basic RedirectorD       must copy the NETAPI.DLL into one of the PC's PATH directories/       as noted for PATHWORKS 4.x clients above.   ?     * If the PC has more than one CFG????.TPL file in the C:\PW >       directory and does not use SELECT, the inventory may get1       information from the wrong file. Add a 'SET >       PWTPL=c:\dir\CFGxxx.TPL' command pointing to the correctG       template  after STARTNET.BAT but before the logon script is run.  B       You can also delete all unused template files from the C:\PW       directory.  F     * The SMS remote control feature works with PATHWORKS clients thatD       use the enhanced redirector.  If LANA 0 is not assigned to theD       NetBEUI or TCP/IP protocol, it will be necessary to change theD       C:\MS\SMS\BIN\CLIENT.BAT file so that the USERTSR program usesD       LANA 1.  Add '/L1' to the end of the USERTSR line in this file       if it is needed.  @     * When the Network Monitor is started from a node properties?       window it uses the hardware address as one of the default A       address to capture.  If the node uses DECnet, the collected B       hardware address is not the address the node will use on theB       network.  When DECnet is started, it sets the node's station>       address to an address that is based on the node's DECnetE       address.  You can see this address by typing the 'ncp show lineO=       characteristics' command on the PC you wish to monitor.   / 2.3  Inventory via LOGON to the SMS Site ServerO  D     * If you choose to do PC inventory by having the PC logon to the?       SMS Site Server, the PC may have trouble logging on if it D       uses DECnet as the primary network.  The PC client will try toE       logon via LANA 0.  If LANA 0 is connected  to DECnet, the logonrD       will fail.  You can make the PC logon using LANA 1 by changingF       the 'wrknets' line in the PC's LMDOS\LANMAN.INI file to 'wrknets       = 1,0,2'.e    	 3.0  Bugss  F    A number of known bugs exist that are either obscure or unlikely toF    occur in most situations.  The following list represents those bugs+    with a higher likelihood of occurrence. S  D     * Simultaneous installation of the same package will result in a       lost or confused job.o  <     * Installation of the UNIX agent directly from the CDROM       occasionally fails.r  F     * Under certain circumstances, SMS group names ending in "_0" will-       appear: for example, "System Status_0".i  :     * The Sparc collector does not detect removable media.  A     * The UNIX collector may collect nothing if the system has nos%       information for uerf to report.r   sG The following section contains the T1.0 Field Test 2 Release Note itemsm that pertain to Field Test 3.     - 1.0 Changes from Field Test 1 to Field Test 2e  2     * Various bug fixes from Field Test 1 reports.  @     * pawinst. (or paw-install) has been renamed to install.paw.  D     * Questions regarding security setup will be asked.  New options>       have been added to install.paw to support noninteractive       installation.e  .     * A brief note about inventory collection:  E       Your PAW UNIX agent will automatically report your inventory toc6       your host PAW SMS server at the following times:  > 	1. Once, when you first install the package.  The initial MIF= 	   will register your host to SMS server and subsequent jobst( 	   to the client will then be possible.  4 	2. Every 24 hours, at 8 a.m.  Can be configured by 6 	   modifying inventory.ini in /paw/control directory.   	3. Any time you type:              /paw/sbin/pawinv   D     * Communications on OpenVMS systems -- TGV Multinet V3.3 Rev B01D       is a supported TCP/IP stack on OpenVMS systems. There is a bugJ       in other TGV versions which prevent PAW Communications from working.;       Make sure you are running the aforementioned version.      2.0 New Features   2.3 CompressionC: The following "zip" style compression is supported for the
 FT2 release. s   Compressed files:  	NT downloading to UNIX, VMS 	UNIX, VMS uploading to NT. 	VMS transferring to VMS with TCP/IP or DECnet   Compressed directories:c 	NT downloading to UNIX, VMS   3.0 New Programs  6 3.1.2 SMS resychronize events must be handled manually  G SMS may detect an inconsistancy with its database and the data in a MIFi? file generated by awcollect on a client.  When this happens SMSaA generates a synchronize event which indicates the client that was C inconsistant and caused the event.  In FT3 when a synchronize event,F occurs, the resynchronization must be handled manually by running 'paw? inventory' on the specified client machine. This will clear the  inconsistancy.   3.2 pawifile  G This PAW initialization file (PAW.INI) modification program is designed H to ease the PAW installation and modification of PAW.INI.  It is used toB enable and disable debug text output which is used by engineers to diagnose problems.  
 3.3 pawinv  B This new program generates an inventory MIF and delivers it to the/ current defined 'mifDeposit' in inventory.ini. l  
 3.4 pawdeinst   G This new program removes all the PAW files and symbolic links as needed  on UNIX platforms. /  
 3.5 pawconfigf  F This new program alters the UNIX agent to report to 'mynt' rather thanG to its current PAW SMS host server.  Recommended usage is through 'paw'  program with command:    	pawconfig -h mynt  # where 'mynt' is your NT PAW server.d  C This can be used in an SMS job to modify remote client's .ini filesm   4.0 Report Securitya  = Security for POLYCENTER AssetWORKS (PAW) Report generation isn@ provided by the SMS and SQL security mechanism.  The key concept? you need to make use of this is that security is provided based @ on SQL Server users, not SMS users. That is, what matters is who> you are logged into the SQL Server as, not who you are on your individual computer. u  A For example, assume you are logged into your machine as user Doe.l: Now you run SMS.  SMS will ask you for an SQL username and> password.  It is *this* username (which may be something other< than Doe) that will be used for subsequent security checks. @ (This assumes that the necessary account has been created on the? SQL Server.  If not, SMS will not be able to connect to the SQLi database.) x  ? For report generation you need Full permission for Packages andi> Jobs, and at least View permission for the other SMS objects.   @        Note:  permissions may be explicit or default.  Explicit B        permissions can be set on a per SQL user and per SMS objectD        basis.  Default permissions are set on a per SMS object basis        only.    G        If the explicit permissions for a particular user and object arecF        set to the "Default" state, then and only then will the Default        permissions take effect.d   5.0 PAW on Windows NTo   5.1 Installation  A 	1. Switching to another window while waiting at the InstallationdA 	   directory dialog no longer results in an "Invalid Path" error  	   message. (216)  < 	2. Program items are now removed upon deinstallation. (286)   5.2 User Interface  @ 	1.  The icon on the reports toolbar button is now working (240); 	2.  F5/Refresh now works with the Reports MDI window (241)n+ 	3.  Sort and Filter options now work (242)e> 	4.  The UI no longer generates a bugcheck error on exit (213)B 	5.  Help for Report Properties and Report Details now works (243)   5.3 Reports   5 	1.  Wordwrap is now supported in all reports. (246).    5.4 Database  C 	1.  Database security is now supported.  To schedule a report, theuL             user must have write permission on the Packages and Jobs tables.	 	    (33)'  4 6.0 PATHWORKS V5.0 and SMS Integration - Limitations  @ The following are known problems with the data that is collected1 by the PATHWORKS version of the inventory agent. c  ? The Network Type field is not filled in the Network record whenv the network type is PATHWORKS. A  ; The inventory agent uses the IPXAddress field to return theg@ DECnet address for PATHWORKS clients that are running the DECnet8 stack.  This may cause problems with the Network Monitor; application if it is configured to track Novell protocols. S  9 The NIC address in the identification group is the actualg@ hardware address programmed into the client's network card.  The> Network Monitor application may attempt to use this address toA detect activity from a client PC.  This will fail when the cliente@ is running a DECnet protocol stack as DECnet changes the address: that the NIC uses to an address based on the node's DECnet	 address.    @ 7.0 POLYCENTER Software Distribution (PSD) Release Notes for PAW   7.1 PSD Installation Changes  ; In FT1 of PAW, POLYCENTER Software Distribution included ann> installation kit and a configuration procedure.  The specified? method for installing PSD and for incorporating it into the PAWX environment was as follows:   % 	1. Install PSD V3.0 using VMS instala; 	2. Add a proxy for the account to be used when running PSDc< 	3. Run the rsm$configure.com procedure to set up the system  > New for FT2, the POLYCENTER Software Distribution kit has been6 extended to automatically add the proxy account duringA installation and to automatically run the configuration procedure : at the end of the installation. (This is an option you can elect).    RSM$CONFIGURE_CLIENTS.COMi  9 A new command procedure has been included with POLYCENTERM< Software Distribution.  This procedure may be run during PSD7 installation, and it may be run after a successfull PSDr9 installation.  This procedure will install the PSD clientL? software and the POLYCENTER System Census agent software to thei@ clients that you elect to be configured.  You no longer have the: run PSD, issue the INSTALL RSM command, nor do you have to7 install POLYCENTER System Census to your client nodes.   	c The procedure works like this:  % 	$ @sys$manager:rsm$configure_clientsf  K POLYCENTER(TM) AssetWORKS Client Configuration procedure for POLYCENTER(TM)w" Software Distribution V3.0 Server.F Copyright(c) 1994. Digital Equipment Corporation. All rights reserved.  %                                 NOTE:5  J     POLYCENTER(TM) Software Distribution is the new name for Remote SystemH     Manager.  These procedures and the installed product may continue to2     utilize the product's traditional acronym RSM.    = Enter the OpenVMS Client system name to be configured: SAMPLES  ( Is this client running OpenVMS AXP? [NO]  H  Enter the client SYSTEM account password.  As with the DCL SET PASSWORD3  command, your input will not echo on the terminal.N  ) Enter the client SYSTEM account password: ' Re-enter the password for verification:l  7 Client configuration job has been submitted for SAMPLE.   0 You will be notified via MAIL of the job status.1 Would you like to configure another client? [NO]N   B 	You will receive mail with the results of the INSTALL RSM and the= 	INSTALL POLYCENTER System Census commands for client SAMPLE.t     8.0 Documentation Note  F Please note that the PAW FT2 Online Help does not include 2 additionalC appendices.  See the pawaa.ps and pawab.ps files for the additionalm appendices.r  & 9.0 Mounting the CD on OpenVMS systems  H The CD for the FT2 distribution is ISO-9660 Format.  It is only readableG by OpenVMS V6.0 or greater systems.  If you do not have an OpenVMS V6.0wD system, please contact your Field Test Administrator for alternative media.  $ For OpenVMS V6.0 systems or greater:  ' 1. To access the product savesets, use:.  6 	$ mount/media=cdrom/undef=(fixed:cr:9216) <cd_device>  ( 2. To access .PS, .COM, .TXT files, use:  1 	$ mount/media=cdrom/undef=stream=200 <cd_device>                                                                                                                                                                                                                                                                                                                                                                                                       