Attachmate Worldwide  |   Contact Us  |   NetIQ.com
Home » Support » Solution Library

Technical Support

Using Winboot to install NetWizard agents


Technical Note USA9203
Created 17-Sep-2003

Applies To
NetWizard Professional

NetWizard 5.0

Goal

Using Winboot to install NetWizard agents

Fix

Winboot is a utility that is included with Attachmate's NetWizard product. Winboot's sole purpose is to ensure that the NetWizard service/agent in installed properly on the particular computer. If the agent has not been installed or has been corrupted, the agent will automatically (re)install itself at Windows boot time.

Winboot is usually placed within a network login script. This login script will execute the Winboot utility every time the user logs into the network server.  Most, if not all network operating systems have a facility to force execution of programs at login.

Winboot can use the same command line parameters as for Setup.EXE:
-C, -D, -G, -N, -O, -P, -Q, -R.

Execute Winboot /? from Dos command line and -X is presented as an option to allow the name to be extracted from an INI file. It is suggested that further information is available in the manual. This information is not in the Netwizard Manual (Netwizard Installation and Administration Guide).


Use of WINBOOT -X and other options
The -X Option allows you to extract a "USER NAME" from a INI file.

The syntax is as follows:
WINBOOT.EXE -X INIFILE,SECTION,KEYNAME where INIFILE, SECTION and KEYNAME have the following meanings.

INIFILE - The name of the INI file that the information will be obtained from.

SECTION - The Section name contained in the INI file.

KEYNAME - The Keyname that is contained in the Section area of the INI file.

e.g. WINBOOT.EXE -X Agent.ini,WindowAgent,PC0001

Agent.INI - INI file name
[WindowAgent] - Section Name

PC0001=NetWiz001 - Keyname
This will install an agent with the user name equal to NETWIZ001.


How WINBOOT works:
1. Query the registry(Win32) or win.ini(Win3.x) for the location of the service/agent.
Win95 agent running as a service looks for the following keys:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\RunServices
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run
Non-service agents look for:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run
NT agent running as a service looks for the following keys:
HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services
HKEY_LOCAL_MACHINE\\ Software\\Microsoft\\Windows NT\\CurrentVersion\\WinLogon
Non-service agents look for:
HKEY_CURRENT_USER\\ SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Windows

Ensure the service or agent executable file is present on the system.
Both operating systems use the path from the key(s) above to look for remote32.dll

Ensure that other files necessary for execution of service/agent are present on the system.
Both operating systems look for remote32.dll and wsagent.ini.

Ensure that agent has not instructed the winboot facility to reinstall.
Both operating systems read wsagent.ini for section [Variables], key ReInstall= to determine if setup.exe needs to be launched.

If any of the above procedures fail, Winboot will cause the (re)installation of the service/agent.


Did this technical note answer your question?

Yes    No    Somewhat     Not sure yet

Additional comments about this tech note:

Need further help? For technical support, please contact Support.