RemoteWare. Guide for Using NetOp with RemoteWare Version 4.3 SP4

Transcription

1 RemoteWare Guide for Using NetOp with RemoteWare Version 4.3 SP4

2 LAST REVISED: September 2013 Copyright 2013 by SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see for additional trademark information and notices.

3 Table of Contents Using this Guide... 4 RemoteWare Support Services... 4 About Remote Control NetOp... 5 Install NetOp Guest on RemoteWare Server... 5 Install NetOp Host on RemoteWare Client... 7 Install NetOp Host using RemoteWare Work Object... 8 Export RemoteWare Client list from RemoteWare Server... 8 Import RemoteWare Client list into NetOp Guest Prepare NetOp Host session Run NetOp Host Installation NetOp and RemoteWare on Vista or later Windows... 13

4 Using this Guide This guide introduces you to installing and using Danware s NetOp product with RemoteWare. Remote Control allows an administrator to view and manipulate a Client s environment, typically for troubleshooting purposes. As of the RemoteWare 4.3 SP4 release, Remote Control NetOp is not going to be distributed with RemoteWare. This guide steps through the installation and setup of NetOp by itself such that it can be used with RemoteWare without being a part of it. RemoteWare Support Services SAP provides industry-leading support and a variety of downloads to help you get the most out of your Sybase products and solutions. If you are a current Sybase customer please use the following sites: 1. For information about Sybase Customer Service and Support, visit 2. If you have a technical support contract, you can locate your local technical support center at 3. For RemoteWare customers with a maintenance agreement, visit METS at If you are a current or new SAP Customer and need to: 1. Log a technical support case. 2. Get updates on a current case. 3. Download the latest RemoteWare enhancements. 4. Get access to the RemoteWare knowledgebase. Please visit the SAP SERVICE MARKETPLACE at

5 About Remote Control NetOp Remote Control NetOp includes the following items: The NetOp product for Servers and Clients. This document describes how to install and setup NetOp to work with your RemoteWare environment. Install NetOp Guest on RemoteWare Server Use your downloaded NetOp files to install NetOp Guest on the RemoteWare Server. 1. Launch NetOp Remote Control Guest Setup Wizard from the NetOp download path. 2. Click Next. 3. Complete the NetOp installation wizard using default settings and choosing a Typical installation.

6 Note: Please be aware of the following items: Refer to the NetOp Remote Control User s Manual for detailed installation instructions. Depending on your computing environment, different installation settings may be required. The maximum supported length for a non-default installation path is 222 characters. The NetOp Remote Control Setup Wizard launches automatically when you complete the NetOp installation. Refer to the NetOp Remote Control User s Manual for detailed instructions about continuing with NetOp setup and operations. You are now ready to export the RemoteWare Client list from the RemoteWare Server.

7 Install NetOp Host on RemoteWare Client You must install NetOp Host on the RemoteWare Client. You can choose to use the Work Object available in the install, or you can install it using the basic NetOp installation program. The following table compares the differences in functionality that result from the two installation types. Basic Installation ASYNC: After host is loaded, Information window pops up alerting that a Communication profile needs to be created. IP: Communication profile gets created by default. ASYNC: When guest attempts to connect the first time, a security warning is seen on the Host alerting the user that any guest could access the computer and that a password should be set. The warning goes away on clicking OK and no password actually needs to be set. Start/programs has an entry for NetOp Host. NetOp Host icon is seen in systray when launched. TCPIP: NetOp host: NHSTW32.exe is launched and the host is seen. TCPIP Host: when client is loaded and NHSTW32.exe is launched, the Host application is started and connections from Guest to the host made without additional work (i.e.: showhost.exe doesn't need to be executed and the Host program does not need to be started) Work object installation ASYNC: No windows pop up. IP: Communication profile gets created by default. Not seen with WorkObject install. Start/programs has NO entry for NetOp Host. NetOp Host icon is NOT seen in systray when launched (stealth mode setting). TCPIP: NetOp host: NHSTW32.exe is launched but the host is not seen. TCPIP Host: after client is loaded, the showhost.exe app must be executed to unhide the Host app and then the Host must be started before connections can be made (stealth mode setting). To execute a basic installation: You can do a basic installation by executing the.msi file from the NetOp download files.

8 Install NetOp Host using RemoteWare Work Object Installing Remote Control NetOp Host using a RemoteWare work object is a multi-step process. The process is summarized by the following general steps: 1. Export RemoteWare Client list from RemoteWare Server 2. Import RemoteWare Client list into NetOp Guest 3. Prepare NetOp Host session 4. Run NetOp Host installation Export RemoteWare Client list from RemoteWare Server Use RemoteWare to export a NetOp Client list for RemoteWare Clients that you want to run NetOp Host. To export the RemoteWare Client list from the RemoteWare Server: 1. Open the RemoteWare Server Menu. 2. Open the Client profile and select the Client List tab. 3. Open the Command menu and select Export NetOp Client List. 4. Select the Clients from list that will be using NetOp and choose OK to open the Save As dialog.

9 5. Navigate to a save location and choose OK. 6. You are prompted for a profile name if your export list includes asynchronous Clients. You are now ready to import your RemoteWare Client list into NetOp Guest. Alternative export using command line 1. Open a command line for the following path: <RemoteWareServerInstall>\System 2. Run NetOpClientExport. The utility supports using the following switches. Switch Description -a All nodes. Returns all nodes in all Client groups. Use without the group or node switches. -g Group. Returns all nodes in a Client group. May be used with the node name switch for further definition. -n Node. Returns a single node, i.e. Client. -c Communications device. Identifies the name of an asynchronous node s communication device, as defined by NetOp Guest. -f File name. Save as file name. Example: NetOpClientExport -F[FileName] -G[GroupName] -N[NodeName]

10 Import RemoteWare Client list into NetOp Guest Use NetOp Guest to import your RemoteWare Server s exported NetOp Client list. Refer to NetOp Remote Control User Manual for detailed import instructions and definitions of NetOp terminology. To import the RemoteWare Client list: 1. Start NetOp Guest from the Remote Control menu to open the NetOp Guest window. 2. Select Import to Phonebook from the File menu to open the Import to Phonebook dialog.

11 3. Choose Browse to navigate to the NetOp Client list that you exported from the RemoteWare Server and choose OK. 4. Verify that the import was successful by viewing the new Client entries in the Phonebook page of the NetOp Guest window. You are now ready to create a NetOp worklist object and session to deliver NetOp Host files to RemoteWare Clients. Prepare NetOp Host session Use RemoteWare to create a NetOp worklist object and session that can deliver NetOp Host files to the RemoteWare Clients. The RemoteWare Clients you select are the Clients that you want to run the NetOp Host application. To create and enable a NetOp Host worklist object: 1. Open the RemoteWare Server menu. 2. Open Work Object Editor and create a new worklist object with a name of your choice. 3. Open the Events page and import the following NetOp sample event file available in the downloaded zip file from SAP support website : <NetOpInstallSample.evf> 4. Save the event page changes. 5. Open the Objects page and enable the object. 6. Close Work Object Editor. To create and enable a NetOp Host session: 1. Open Session Editor and create a new session with a name of your choice. 2. Open the Schedule page and establish an outbound schedule for the session. 3. Open the Objects tab and assign your NetOp Host worklist object to the session. 4. Open the Client tab and assign the Clients that you want to run the NetOp Host application. These should be the same Clients that you imported into the NetOp Guest console. 5. Open the Sessions tab and enable the session.

12 6. Close Session Editor. Run NetOp Host Installation You can choose to use RemoteWare to run the NetOp Host installation on RemoteWare Clients. These should be the same Clients that you imported into the NetOp Guest console. Allow the NetOp Host installation session to run according to the outbound schedule you defined, or run it manually. Consider the following items about the delivery of the installation files: The delivery of the installation files runs silently without interaction from the Client user. When delivery of the files is complete, you can view the event details in the RemoteWare Log Viewer if a Remoteware work object is used for delivering the NetOp files to the RemoteWare client. The NetOp Host installation launches after the files are delivered to the Client. Consider the following items about the installation process: Like the delivery of the NetOp Host installation files, the installation process runs silently without requiring interaction from the Client user. However, the user may witness brief interruptions to their monitor s image as the installation process runs. The installation may take several minutes to run, and the time required to complete the installation process is partly dependant upon the host computer s available resources. You can verify NetOp Host installation by searching for the following installation path: C:\Program files\danware data\netopremotecontrol\host.

13 NetOp and RemoteWare on Vista or later Windows If running under Vista or later and the RemoteWare kernel is running as a service, the NetOp host runs in the console session, which is typically session 1. If the host does not run in session 1, the NetOp host may not run correctly. Under XP, everything runs in session 0. The kernel only starts and stops NetOp for IP connections if the kernel is listening for a TCP connection; if the kernel is running async-only it ignores NetOp at startup and shutdown. A registry key has been added to allow disabling the kernel starting and stopping NetOp. At startup the kernel looks for a DWORD value named "NetOpStrategy" under the client key: HKEY_LOCAL_MACHINE\software\remoteware\client\<clientname> If there is a nonzero value, the kernel won't start or stop NetOp for IP connections. With the addition of this registry key, when the kernel starts up, it now checks to see whether NetOp is installed and whether the NetOp service and host are running. If the NetOp service is not running the kernel starts it, then if the NetOp host is not running the kernel starts it. The NetOp host requires the NetOp service to be running before it starts. The kernel remembers which of these it started. When the kernel shuts down it stops the NetOp service or host it started.