Patch Name: PHSS_8606 Patch Description: s700_800 10.01-[12]0 ITO Agent for Windows NT 4.0 Creation Date: 96/10/01 Post Date: 96/11/29 Hardware Platforms - OS Releases: s700: 10.01 10.10 10.20 s800: 10.01 10.10 10.20 Products: ITO 3.00 and ITO 3.01 Filesets: OVOPC-CLT.OVOPC-NT-CLT OVOPC-CLT-ENG.OVOPC-NT-CLT OVOPC.OVOPC-UX-MGR78 Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_8606 Symptoms: PHSS_8606: previous ITO A.03.01 supported NT 3.51 only Defect Description: PHSS_8606: no defect - just enhanced functionality SR: B700027441 Patch Files: /opt/OV/bin/OpC/agtinstall/opcwntinst /opt/OV/bin/OpC/agtinstall/opcwntping /opt/OV/bin/OpC/agtinstall/opcwntprlg /opt/OV/bin/OpC/agtinstall/opcwntprocs /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/opc_pkg.Z /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/unzip.exe /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/unzip.txt /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/opc_inst.bat /opt/OV/bin/OpC/opcvterm /opt/OV/bin/OpC/utils/nthost.exe /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/monitor/itoprocs.exe /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itodiag.exe /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itokill.exe /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itomserv.exe /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itoreg.cfg /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itoreg.exe /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itosdown.exe /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itouser.exe /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/opcprfls.exe /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/opcdf.bat /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/opcps.bat /opt/OV/OpC/examples/progs/opcapint.mak /opt/OV/OpC/examples/progs/opcmpint.mak /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ AgentPlatform /opt/OV/lib/nls/C/opcinst.cat what(1) Output: /opt/OV/bin/OpC/agtinstall/opcwntinst: HP OpenView IT/Operations A.03.03 (11/11/96) OpC A.03.03 (11/11/96) /opt/OV/bin/OpC/agtinstall/opcwntping: HP OpenView IT/Operations A.03.03 (11/11/96) OpC A.03.03 (11/11/96) /opt/OV/bin/OpC/agtinstall/opcwntprlg: HP OpenView IT/Operations A.03.03 (11/11/96) OpC A.03.03 (11/11/96) /opt/OV/bin/OpC/agtinstall/opcwntprocs: OpC A.03.03 (11/11/96) /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/opc_pkg.Z: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/unzip.exe: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/unzip.txt: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/opc_inst.bat: None /opt/OV/bin/OpC/opcvterm: HP OpenView IT/Operations A.03.03 PHSS_8606 (11/11/9 6) /opt/OV/bin/OpC/utils/nthost.exe: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/monitor/itoprocs.exe: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itodiag.exe: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itokill.exe: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itomserv.exe: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itoreg.cfg: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itoreg.exe: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itosdown.exe: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/itouser.exe: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/opcprfls.exe: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/opcdf.bat: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03/cmds/opcps.bat: None /opt/OV/OpC/examples/progs/opcapint.mak: None /opt/OV/OpC/examples/progs/opcmpint.mak: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ AgentPlatform: None /opt/OV/lib/nls/C/opcinst.cat: None cksum(1) Output: 2229075555 3246 /opt/OV/OpC/examples/progs/opcapint.mak 1229167631 3278 /opt/OV/OpC/examples/progs/opcmpint.mak 777197468 22410 /opt/OV/bin/OpC/agtinstall/opcwntinst 739928198 10437 /opt/OV/bin/OpC/agtinstall/opcwntping 580343341 16827 /opt/OV/bin/OpC/agtinstall/opcwntprlg 3374156216 7805 /opt/OV/bin/OpC/agtinstall/opcwntprocs 163652430 637294 /opt/OV/bin/OpC/opcvterm 3136038379 37076 /opt/OV/bin/OpC/utils/nthost.exe 3711463791 47203 /opt/OV/lib/nls/C/opcinst.cat 3562195761 94068 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/cmds/itodiag.exe 1793803163 48952 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/cmds/itokill.exe 2366988102 50856 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/cmds/itomserv.exe 3904447237 216 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/cmds/itoreg.cfg 362999512 78908 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/cmds/itoreg.exe 89232574 42892 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/cmds/itosdown.exe 3798226940 47844 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/cmds/itouser.exe 1031538823 32 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/cmds/opcdf.bat 4069510168 39964 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/cmds/opcprfls.exe 4219242959 35 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/cmds/opcps.bat 4281357319 30780 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/monitor/itoprocs.exe 362315805 1039 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/opc_inst.bat 3619666015 927083 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/opc_pkg.Z 3162183940 113152 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/unzip.exe 1939298735 508 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.03.03/unzip.txt 2749337469 4867 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/AgentPlatform Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: None Equivalent Patches: None Patch Package Size: 2300 Kbytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_8606 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_8606.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHSS_8606.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_8606. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_8606.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_8606.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: Note: - You may use this patch with the following official ITO releases: A.03.00 for HP-UX systems (English version) A.03.01 for HP-UX systems (English version), A.03.01 for HP-UX systems (Japanese version), no matter whether you run your OpC Management Server system with Oracle or Ingres database. - DO NOT use this patch with previous releases of OpC, for example versions A.01.X A.02.X - All functionality contained in this patch will be included in the next official release of HP OpenView IT/Operations (ITO) release. - It provides support for ITO 3.0 intelligent agents running on MS Windows NT 4.0. - This patch must be installed on the ITO Management Server system, NOT on an ITO Managed Node directly. Changes will take effect on Managed Nodes by means of ITO Software Distribution. - Distributing the patched ITO Managed Node Software up- grades the ITO intelligent agents to version A.03.03. - Depending on your SD version: If you can't swinstall from the patch depot, you may need the swinstall option "-x source_type=tape" After successful installation you have to propagate the new supported agent version to the ITO server. Run as root: # opcagtdbcfg -p ms/intel/nt -dbupdate -f And restart the server processes with: # opcsv -start KNOWN PROBLEMS WITH THE ITO A.03.03 AGENT FOR MS WIN NT: Symptom 1: Applications started on NT under a different user account from "HP ITO Account" do not receive the environment settings of this user. Solution 1: All applications inherit the environment settings of the NT system and the ITO account, not those of the different users. If an application requires a specific environment variable setting, this variable must be added to the NT System Environment Variables (Control Panel/System) or to the User Environment Variables of the HP ITO Account. Symptom 2 (this problem occurs on NT 3.51 only and is fixed with NT 4.0): Applications started on Windows NT that need to display a GUI on the local machine should be started only under a user account that is a member of the Administrator group, for example, the ITO account. For all other user accounts, NT denies access to the display causing the applications either to fail or to run on an invisible desktop. Solution 2: Run the applications in the previously mentioned administrative accounts or manually allow the required users to access the local desktop using nthost.exe. Symptom 3 (this problem occurs on NT 3.51 only and is fixed with NT 4.0): If the Reboot application is started on an NT server when the screen saver is running on that system, you will see a message telling you that the system is about to be shutdown. If you now use the "Cancel Reboot" application, it correctly terminates the reboot process, but when the system is used again locally, the desktop is empty. Solution 3: Press Ctrl-Alt-Del to display the Windows NT Security Box, then press Cancel. This displays the local users desktop. Symptom 4: The NT Agent fails to start an application executed from the Application Desktop with an error message saying that it can't log on using the specified user account. Solution 4: Check that the user account exists on the system or domain controller. Make sure that ITO A.03.03 version was properly installed on the system's primary and backup domain controllers. Symptom 5: Applications started on NT under a specific user account return the message "Access Denied" even if the user is correctly included in the access control list of the application. Solution 5: If the application calls a batch file, the user must have "Read" access to the file. If the application calls an executable file, Win NT checks erroneously for the access rights of the "HP ITO account" and not the access rights of the specified user. To overcome this, the "HP ITO account" must also have Execute access rights to the file. You can use the Security Permissions dialog box of the NT file manager to view/change the access control list of the file. Symptom 6: On HP-UX 9.x ITO management servers only: The heartbeat polling for DCE-based agents (currently Windows NT) takes more than 8 minutes to time-out if the node is switched off, or the network connection from the server to the node is broken. During this time the ITO server cannot perform heartbeat polling of any other machines. Solution 6: This problem only occurs if the managed node is configured to use "DCE TCP/IP" communication: [Add/Modify Node: Advanced Options: Communication Type: DCE RPC (TCP)]. This is related to a problem in HP-UX 9.x networking. You need to install the PHNE_6707 or later cumulative patch, for example, PHNE_7252. If your system includes managed nodes that are often unreachable, increase the heartbeat polling interval, or disable it completely on affected machines. In LAN environments with no bandwidth problems, it is recommended to configure the agents to use DCE RPC (UDP). In low bandwidth environments, for example between WANs, it is recommended that you use the DCE RPC (TCP) communication type to avoid reliability problems. Symptom 7: You cannot specify the command name directly for commands that use the internal NT command interpreter, for example, dir, del, type, etc. Solution 7: Internal command interpreter commands that cannot be started from another process without starting a new command interpreter to execute them. Run these commands as follows: cmd.exe /c "dir c:\temp" cmd.exe /c "type c:\temp\inst.log" This starts a new command interpreter with the option to execute the command and then terminate. Symptom 8: Difficulties when matching message conditions from the Windows NT event logs. Solution 8: The Event messages created on the NT system can be multilined, so the end of line character must be considered when creating the "MATCH CONDITIONS - Message Text", to match the end of line character you should define <2*> in the text. It is useful to check the message once it arrives on the message manager, by looking at the original message it is possible to see where the spaces and end of line characters are. Symptom 9: Piping of input/output fails in monitor batch files. If the pipe ( | ) is used before a right angle bracket ( > ) the standard input is an invalid handle. This can cause problems in certain cases, for example, with some grep functions. Solution 9: Enter the following as the first line of the batch file: @ECHO OFF >NUL After this point, standard input is a valid handle. Symptom 10: When de-installing the NT agent software, the file opcauth.dll in the directory :\\system32 is not automatically removed. Solution 10: Remove the file opcauth.dll manually. Symptom 11: The command itokill.exe does not always kill a process completely on the Selected Windows NT node, although it appears to have done so. Solution 11: Always use the /f option (forced kill without notification) with the itokill.exe command in an NT environment. Symptom 12: CPU usage of the ntvdm process goes to 99% if the server side of the Virtual Terminal (PC) is terminated with CTRL-C while the agent side is running a program like EDIT that cannot be displayed. Solution 12: Kill the ntvdm process that consumes all the processor time. itokill /f /name ntvdm Symptom 13: The agent does not start up if the registry entries for ITO are deleted. Solution 13: If one of the registry entries (Agent Version, Hostname, Installation Drive) is missing in the registry at the address HKEY_LOCAL_MACHINE\ SOFTWARE\Hewlett-Packard\OpenView\ITO the agent on that system has to be reinstalled. Symptom 14: opcdcode does not find the message catalog if it is started from a different drive than the drive holding the agent. The error message is Internal error: Can not open message catalog .\opc.cat No such file or directory Solution 14: Start the opcdcode tools only on the drive that holds the agent software. Symptom 15: de-install and re-install of the agent on an NT 4.0 system leave a user profile consuming 138 KB of space on the disk. This happens if the agent is installed without the correct password for the HP ITO Account so that the account is deleted and newly created. Solution 15: Delete the old user profile in the Control Panel/ System/ User profiles. Symptom 16: Installation on PDC does not always find that there exists a BDC in the domain though there is one. This can be seen in the installation logfile. The result may be that the installation process creates a new user account for the HP ITO Account that cannot be used by the BDC and so the agent on the BDC does not come up the next time. A de-installation of the PDC may result in a deletion of the HP ITO Account that also disables the agent on the BDC. Solution 16: This is caused by a badly syncronized NT domain. Mostly it can be fixed by resyncing the domain (sometimes it is needed to do it more than once) Symptom 17: Manager of Manager config file does not work if the IP address 0.0.0.0 is given. i.e. the following line on the MoM config file is invalid for NT: NODE IP 0.0.0.0 "mumpitz.bbn.hp.com" Solution 17: for NT the correct IP address has to be given in the config file. Symptom 18: removal of the patch PHSS_8605 on 9.x mgmt server leaves empty A.03.03/* subdirectories in the databases directory tree. Solution 18: the directory tree /usr/OV/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.03.03 can be deleted after the agent was deinstalled. Symptom 19: If the NT system is member of a workgroup instead of a domain it may find a machine in the workgroup as a primary domain controller. If this machine is unavailable the installation does not work. Solution 19: If the installation aborts because it cannot contact the PDC make sure that this machine is running and try again. Symptom 20: There may be the requirement to install a Backup Domain Controller (BDC) without having the Primary Domain Controller (PDC) installed. This normally aborts because of the missing installation of the agent on the PDC. Solution 20: The BDC installation checks for the existence of the domain global HP ITO account account. This is normally created during the installation of the agents on the PDC. To install the agents to the BDC the HP ITO account and the opc_op account can be created manually. These must have the following attributes: Username: HP ITO account Full Name: HP ITO account Description: HP ITO agent account Password: _ User Must Change Password at Next Logon _ User Cannot Change Password X Password Never Expires _ Account Disabled _ Account Locked Out Member of the following groups: Administrators Domain Admins Domain Users Username: opc_op Full Name: opc_op Description: HP ITO operator account Password: _ User Must Change Password at Next Logon X User Cannot Change Password X Password Never Expires _ Account Disabled _ Account Locked Out Member of the following groups: Domain Users Users Then the BDC can be installed and can also be used as the installation server for that domain.