Client 7x24 Lights-out operation
 

The following describes how to setup ASAP Client to run in a 7x24 "lights-out" operation. This configuration is not needed for casual analysis or ad hoc client users of NonStop ASAP. Rather running ASAP Client in this lights-out configuration on one or more independent workstations addresses the issue of how to be notified if the NonStop Server itself is down, or any of it's components go down. One paradox of monitoring software that runs exclusively on a NonStop server is how situations are detected and reported if the NonStop server itself is down, or the server is unable to communicate with the outside world? ASAP includes the ability for independent ASAP Clients on one or more Windows workstations to provide additional monitoring, fault tolerance, detection, and email notifications so in the event that a NonStop server goes down, or its communications are lost, or its components go down, ASAP Client will detect and notify you about such conditions.

Lights-out Setup

The steps below describe how to setup ASAP Client for lights-out operation. This setup includes the ability to auto-startup and auto-connect to the NonStop servers whenever the Client workstation is re-booted. When the environment described below is configured, whenever an ASAP workstation is booted or re-started for any reason, ASAP Client will automatically startup and re-connect to the NonStop servers (as a true lights out configuration, requiring no operator intervention). Also note the configuration below allows ASAP Client to be setup either for an admin or non-admin user, and can be setup on one or more workstations for fault tolerance purposes.

Lights-Out Configuration steps

1) Logon as admin

2) Install ASAP Client from CD or via download.

3) Optional VPN Setup - if you are connecting via a VPN connection, configure the VPN connection, and when you connect select “Anyone who uses this computer” to avoid session loss if multiple users are using the workstation (this step is not needed if on local LAN).

4) Run CSG on the workstation, select File... Start Session...  and when the host logon prompt appears, enter your NonStop userid and password so that CSG will connect to the NonStop server for all future invocations of CSG (you only need to do this once). If you do not wish to use a NonStop userid and password, alternatively you can configure CSG to use one of the procedures described in Configuring Secure CSG.

5) Run ASAP Client, select View... Options... click SSG tab... check the Auto Connect at Startup checkbox... and click Ok. Then shutdown ASAP Client, and run ASAP Client to confirm it automatically connects to the server without any prompts whenever ASAP Client is started.

6) Run each of the following ASAP Client components by double-clicking on the exe while logged on as admin... ASAP, OIL, OEM, CSG, ASAPMAIL, and IconServ. This step allows each ASAP ActiveX server component to be registered for non-admin users (this step is not necessary if you intend to run ASAP Client as admin). The step addresses a known problem with UAC and Windows 7 (and XP) server registration for non-admin users. These files are located at C:\Program Files\Tandem\ASAP\ and related subdirectories, or C:\Program Files (x86)\Tandem\ASAP\ on 64-bit workstations.

7) Using Explorer on 32-bit PCs navigate to the folder C:\Program Files\Tandem\; Or on 64-bit PCs navigate to C:\Program Files (x86)\Tandem\
  a. Select the folder named Tandem, Right mouse on the Tandem folder, and select Properties
  b. Select the Security tab of the Tandem Properties window
  c. Select the Users group
  d. Check the Allow Full Control checkbox (assumes Windows 7 Pro, or Windows XP Pro, or higher).
  e. Click OK
  f. At this point you have registered, setup, and secured all ASAP server components so they can be accessed without the need for admin.

8) To run ASAP Client under a non-admin userid, then logon to the desired non-admin user account, otherwise remain logged on as admin.

9) Setup ASAP Client as desired. This includes possible import of your EDL settings from your master EDL library (for more info on EDL see ASAP 2.0 Intro to EDL). Also you should review your client notifications by selecting View... Options... click the OSC tab... click the Notify button. Then review your ASAP Notify Content, Recipients, and Server settings. Finally check Enable on the Alerts profile and any other profiles for which you wish to receive email notifications and automatic reports.

10) Select Control Panel... System... Advanced ... Environment Variables...
  Create a new user Path variable (or update the existing user Path variable) to include the path:
  C:\Program Files\Tandem\ASAP; on 32-bit PCs, or for 64-bit PCs add the following to the path variable:
  C:\Program Files (x86)\Tandem\ASAP;

11) Copy the contents of RunAsap.txt to your Startup folder as a file named RunAsap.vbs and be sure the extension of the file is .vbs
  a. Default Windows XP Startup folder - C:\Documents and Settings\<pc-userid>\Start Menu\Programs\Startup
  b. Default Windows 7 Startup folder - C:\Users\<pc-userid>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
  c. Test that the startup group is working by shutting down ASAP Client
  d. Log-off from the pc-userid
  e. Logon to the pc-userid account
  f. ASAP should automatically startup and connect to the NonStop server the first time you logon.

12) Run Regedit and navigate to the following key...
  Hkey_local_machine\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\
  Add the following String Values to the registry key above:
  To add new registry values, use right mouse, New... String Value... for registry values not present. For values already present, right mouse, select Modify.
  - AutoAdminLogon = "1"
  - DefaultPassword = "pc-password"
  - DefaultUserName= "pc-userid"
  - if you cannot update the registry values above, and you are not logged on as admin, logon as admin and repeat step 12).

Questions/comments - support
Lastmod: June 14, 2019