RemoteScope 2.6 User s Guide

Transcription

1 RemoteScope 2.6 User s Guide Table of Contents Introduction...7 What is RemoteScope?... 7 About Micro2000, Inc... 7 Chapter 1: Quick Tour...8 Console, Client and VIP Client... 8 Primary Functions... 8 Tutorial Videos README File Chapter 2: Installation...11 Pre-Installation System Requirements Console System Requirements Client System Requirements Console Installation Console Activation Logging On Re-Activation Closing the Console Console Uninstall Network Segment Client Installation Installing the Client Module Remote Client Deployment System Requirements Deploy Client Wizard Uninstalling a Client Chapter 3: Getting Started...34 Master Console Interface Tour of the Main Screen Tree View List View Console Activity Log Changing Passwords Changing the Console Password Changing Client Passwords Configuring the Console General Tab Log Tab Network Segment Tab... 43

2 RemoteScope View Settings Tab Managing Profiles Creating a New Profile Editing an Existing Profile Selecting a Profile Configuring the Client Configuring the VIP Client Detecting and Adding Clients Client Status Chapter 4: Managing Clients and Groups...55 The Client/Group Menu Open New Group New Client Add Member Add to Group Connect All Disconnect All Send Message Conference Room File Transfer Remote Control Remote Configure Wake-On-LAN (WOL) Command Inventory Delete Properties View View Menu Context Menus Chapter 5: Remote Control...74 Using Remote Control Control Modes Selecting Clients VIP Clients Full Screen Remote Ctrl Alt Del Fit to Window Clipboard Transferring Remote Shut-down and Restart Ending the Remote Control Session Chapter 6: Inventory...80 Inventory Groups Viewing Inventory Inventory Tab

3 User Guide Monitor Policy Tab Adding a Monitor Policy Changing a Monitor Policy Deleting a Monitor Policy Change History Tab Alarm Information Tab Tabbed View of Inventory Statistic Viewing Statistic Hardware Details User Custom Data License Management Database Maintenance Utility Enterprise Assets Manager Exporting data Opening Enterprise Assets Manager Importing data Configuration Changing the Password Inventory Reports View Version information Chapter 7: File and Folder Operations File Transfer File and Folder Actions VIP Clients File Search File Distribution Setting the Path Selecting the File or Folder VIPs in Distribution Chapter 8: Software Distribution Definitions Product Definition Edit Creating a New Product Product Edit Procedure Creating the ISS File Using an MSI File Creating an MSI Distribution Package Importing/Exporting Products Duplicating a Product/Mode Product Distribution Distribution Tasks Distribution Record Scheduled Distribution

4 RemoteScope More Distribution Examples Example One: Distributing Acrobat Reader 6.0 with ISS Example Two: Distributing Office2k with MSI Chapter 9: Task Management Creating a Task System command Command line Script Refresh Inventory Software distribution Task Properties Executing a Task Stop a Task that is running Scheduling Creating a New Schedule Delayed Distribution Schedule Properties Deleting a Schedule or Task Chapter 10: Scripting What is VBScript? VBScript Data Type VBScript Variables RemoteScope Scripting Creating a Script Writing a Script Saving a Script Checking the Syntax of a Script Running a Script Task and Schedule Chapter 11: IM and Conferencing IM (Instant Messaging) Messages from the Client Sending a Message from the Console Disabling Messaging From Client Conferencing Starting a Conference Room The Conference Room Window Using a Conference Room Creating a new room Inviting members Deleting members Switching to and from Closing a conference room Saving a conference record Chapter 12: System Logs Viewing the System Logs

5 User Guide Clearing the System Logs Configuring the System Logs Record Type Operation Client Logs Viewing the Client Log Configuring Client Logs Chapter 13: Reports Report Templates Creating a New Report Accessing and Using Reports Report Preview Window Printing and Exporting Printing a Report Exporting a Report Other Report Actions Chapter 14: File Backup Creating a Backup Edit the Backup Immediate Back-up Scheduled Backup Get Backup Result File Backup Record Chapter 15: Miscellaneous Security Encryption Client Mapping Activation Control User Control Updates Editing NETSEGMENT.CFG Import File, Creating and Editing Chapter 16: Troubleshooting and Error Messages Symptoms and Causes Error Messages and Codes Security Errors Client/Group Errors Configuration Errors Communication Errors Inventory Errors Remote Control Errors Software Distribution Errors Task Management Errors Database Errors Scripting Errors Report Errors

6 RemoteScope Contacting Micro 2000 Support Feedback Appendix A: EULA Software Product License Limited Warranty Appendix B: Glossary Index

7 User Guide Introduction What is RemoteScope? Basically, RemoteScope is a collection of tools that allow the network administrator, sitting at his or her desk, to manage a network of remote PCs and accomplish those tasks that would otherwise require running from one PC to the next. These tasks include the installation of new applications and updates, remote control or monitoring of network workstations, keeping an inventory of software and hardware installed on those systems, and many other functions that will be described in detail throughout the manual. About Micro2000, Inc Formed in September 1990, Micro 2000 Inc was chartered to provide the personal computer industry with professional-quality diagnostic tools, which at that time were available for mainframes but were virtually non-existent for PCs. As the personal computer evolved into the powerful machines of today and became an indispensable fixture in the corporate world, Micro 2000 has maintained its position of industry leadership through award-winning technical support and by staying consistently on the cutting edge throughout the rapid advances in PC technology. Meanwhile, our basic philosophy has not changed at all. Whether it is diagnostics, network administration tools or educational and certification courses, our goal has always been to provide our customers with the best state-of-the-art products of their kind available in the world, and always at an affordable price. 7

8 RemoteScope Chapter 1: Quick Tour Although you may be eager to begin using RemoteScope, we strongly recommend that you read at least this chapter and Chapter 2 (Installation) before installing the software. You may also want to view the first two tutorial videos on the CD that correspond to these two chapters, and the README file which contains up-to-date information on your version. More information on the tutorials and README file can be found later in this chapter. Console, Client and VIP Client The RemoteScope program is organized in two modules, called Console and Client. The Console module is the control point, and will be installed on whichever system(s) the network administrator will use to manage the network. There are also Sub-consoles that can be used to simplify administration of large or dispersed networks Note: The administrator should log on the Console with Admin credential to enable all functions. The Client module is installed on each of the PCs that will be managed from the Console. The Client is a passive module that normally runs in the background and is not accessed by the user on that system except for instant messaging to the Console. It cannot be turned off, uninstalled or tampered with in any way without the administrator s password. Its purpose is to communicate with the Console and to carry out instructions that are issued by the network administrator via the Console module. There is also a version of the Client module called the VIP Client that allows the user at the Client machine to accept or deny a request from the Console to remote-control, browse or distribute files to the Client system. Primary Functions There are six basic tasks that RemoteScope is designed to do. These are remote control, file transfer, software deployment, inventory, messaging/ conferencing, license management and reports. Most of the features described in this manual are for the purpose of supporting one or more of these basic functions. Remote Control From the Console, the administrator can take control of a remote machine. A copy of the remote system s desktop display will appear on the Console s monitor, and keyboard and mouse actions at the Console will be carried out at the remote system just as if the administrator was sitting at that computer. There are also modes that allow shared control or passive monitoring 8

9 User Guide of the remote system. These functions are described more completely in Chapter 5. File Transfer Files can be transferred between the Console and a Client with drag-and-drop simplicity or distributed from the Console to a group of Clients simultaneously. File Transfer and Distribution is covered in Chapter 7. Software Deployment Considered by many to be the greatest laborsaving feature of RemoteScope, the deployment utility allows new applications or updates to be pushed out and installed on selected PCs across the network, all without leaving the Console workstation. Deployment, also referred to as software distribution, can be done in real-time or in many cases scheduled for a later unattended install. All the ins and outs of deployment will be found in Chapter 8. Inventory One of the more difficult tasks in a widespread network is keeping track of what is installed and where. RemoteScope maintains a database of all of the hardware and software installed in each system, along with relevant information about each, such as version and install date. This database is maintained on the Console, which allows instant access even in the case of hard drive crash or other failure on a remote system. Alarms can be set to notify the administrator of specific changes. A complete description of the inventory function appears in Chapter 6. License management This is an extension of the inventory function. Enter the number of licenses owned for any software and the expiration date. The program will compare the values to the installed base and the current date, and flag any overages in color. Reports A flexible reporting function has templates for the most common internal reports, and can export data to a variety of destinations in different formats, all available with point-and-click simplicity. Reports are based on the inventory database in the main Console, and are covered in Chapter 14. Other Supporting the primary functions listed above are a variety of other features such as messaging, conferencing, and security measures. Messaging and conferencing are covered in Chapter 12, while security and a grab-bag of other features appear in Chapter 16. Problems If you have any questions or difficulties with RemoteScope, there is an index in the back of the manual to help in locating specific features and information. On-line Help files can be accessed with the F1 key from any point in the program. In Chapter 17 of the manual you will find a troubleshooting guide and a list of all of the error codes that you may encounter. Information for contacting Micro 2000 support is there as well, including details on a feedback feature that simplifies sending an to our technical support department. 9

10 RemoteScope We also recommend that you view the tutorial videos on the CD, which cover all of the major functions of RemoteScope and most of the minor ones. Tutorial Videos The RemoteScope CD contains a number of tutorial clips that take the viewer step-by-step through the basic operations of the program. Each of these tutorials covers a specific topic and lasts for only a couple of minutes. Accessing the CD will normally present the RemoteScope Start-up screen shown here. Start-up Screen To view the tutorials, click on the bottom choice, labeled appropriately enough RemoteScope Tutorials. Then click on the tutorial title of your choice. The selected tutorial will run in the browser, so the system used to view the tutorials must have Internet Explorer (4.0 SP1 or later) and speakers. Note: If the access screen does not appear, you can still reach the tutorials by opening the folder on the CD labeled Tutorials and double-clicking on any of the individual lessons. However, in that case the lessons will be listed only by number and not by title. README File While you are in the Start-up screen, click on View Documentation and then on View README File. The README file will give you the latest tips on avoiding problems and getting the best use from RemoteScope. 10

11 User Guide Chapter 2: Installation We recommend reading this chapter through entirely before installing RemoteScope. Be aware that the Master Console must be installed first. Installation and activation of the Master Console must be complete before the Sub-consoles or Client modules can be installed. The Client is not installed from the CD but from a package created during the Master Console installation. Pre-Installation There are several steps to take before starting the installation of RemoteScope that will help to ensure a smooth, trouble-free install. 1. Determine which system will be the Master Console and which if any will be Sub-consoles. 2. Jot down the IP address range of the systems on the LAN that will use the program. It does not matter if the LAN uses static or dynamic IP addressing, as long as the starting and ending IP addresses of the range are known. These values will be needed to configure the Network Segment (described in Chapter 3) the first time the RemoteScope Console is opened. Chapter 3 will also cover accessing Clients outside of the LAN. 3. Make sure that the systems receiving the Console and Sub-console modules have an active Internet connection. A Console must be activated before it can be used. This is a simple procedure if done on-line during the installation. activation is available within the program where you will be ed the activation code. If Internet access is not available, it will be necessary to contact Micro 2000 technical support to activate the program. However, activation is not required if this is a demo CD or Academic version of RemoteScope. 4. Have the PCPK product serial number handy. This is found on the CD case, and will be needed during installation. 5. You will also need to log in at the completion of installation. The default values are: User Name: Remote Password: Scope Be aware that the password is case sensitive. 6. See that the systems meet the minimum hardware and software requirements. These are slightly different for the Console and Client, and are listed on the following page. 11

12 RemoteScope System Requirements Console System Requirements Hardware: Pentium (recommended Pentium 4 or higher) 16MB SVGA card 256MB memory + RAM 40MB available on local hard drive 4X CDROM drive 10/100 Mbps NIC card Software: Windows 98/SE, Windows NT 4 SP6, Windows ME, Windows 2000, Windows XP, Windows 2003 Internet Explorer 5.0 or better WinZip or WinRAR installed Video card capable of 16 bit, 800 by 600 pixels Internet connection Client System Requirements Hardware: Pentium (recommended P3-500), 16 MB SVGA card 128MB (recommended 256 MB or higher) 10 MB available local hard drive 10/100 mbps NIC card Software: Windows 95B, Windows 98/SE, Windows NT SP6, Windows ME, Windows 2000, Windows XP, Windows 2003 Tip: Windows 95 is no longer supported. Internet Explorer 5.0 or better Video card capable of 16 bit, 800 by 600 pixels WinZip or WinRAR installed 12

13 User Guide Console Installation 1. Choose the system that is most convenient as the control point for the managing the network. This can be a desktop workstation rather than a server as long as it meets the minimum requirements listed in the previous section. Switching the Master Console to another system after installation will require reactivation of the Console. 2. It is recommended you close all applications on the system selected as the Console. 3. Insert the RemoteScope CD into the CD-ROM drive. If the system has autoplay capability, the RemoteScope start-up window will appear. Start-up Screen 4. Click on the CD icon to the left of Install RemoteScope. Note: If the Start-up screen does not appear, use Windows Explorer to find the setup.exe file on the CD and double-click it, or go to the command line and type run D:\setup.exe, where D is the drive letter for the CD-ROM drive. 13

14 RemoteScope Welcome Screen 5. After the Install Shield Wizard has been prepared you will see the Welcome screen. Click Next. EULA screen 6. Read the End User License Agreement (EULA) and click YES to accept the terms and proceed with the installation. If you do not agree, click NO. RemoteScope will not be installed and you will be directed to exit from the install program. If you wish to study the EULA outside of the installation procedure, a copy of it is available in Appendix A of this manual or in the EULA.TXT file on the CD. 14

15 User Guide Customer Information screen 7. In the Customer Information screen, type in your User Name, Company Name and the PCPK serial number from the RemoteScope CD case. Click Next. Master-Sub Screen 8. Designate whether this installation is for the Master Console or a Sub- Console. Remember that only one Master Console is allowed in any given network (or subnet, as long as the IP addresses have no overlap with those of any other Master Console). The Demo and Academic versions allow only one Console, so it must be the Master Console. 9. The default destination path for the RemoteScope program files is C:\Program Files\RemoteScope. Normally you will accept the default, but you may also 15

16 RemoteScope browse to select another path. Click Next. The next screen, Select Folder, will create the RemoteScope Program folder. Here again you can accept the default or change it, then click Next. 10. In the Setup Information screen, inspect the data to make sure everything is OK, then click Next. Note: If any data in Step 10 is incorrect, instead of Next click the Back button until you reach the screen where that data was entered. Correct the data and then come forward again to this step. 11. At this point, the program will copy the RemoteScope files to the hard drive, which will take a minute or two. When copying is complete, the Setup Finish screen will appear. Finish screen 12. If you would like to review the README file or the What s New file at this time, check the appropriate boxes. If not, leave the boxes blank. These files can be accessed later from the CD. Click Finish. Installation of the Console is now complete. You will find that a new RemoteScope group has been created in the Windows Program Bar. This group will contain icons for the RemoteScope Console, Uninstall RemoteScope Console, Database Maintenance Utility, On-line Help, and Client Package. The desktop will also have a new shortcut icon to launch the Console. Before running the RemoteScope Console or installing the Client modules, RemoteScope needs to be activated, as described on the next page. 16

17 User Guide Console Activation 1. Once the RemoteScope Master Console or Sub-console has been installed, open the RemoteScope group in the Windows program bar and click on RemoteScope Console. The first time you do this, you should see the RemoteScope Activation Wizard screen. Note: If you have a demo or Academic version of RemoteScope, activation is not required and the Activation Wizard will not appear. Proceed directly to the next section of the manual: Logging On. Activation Wizard 2. Click Next to proceed to the Activation Information screen. 17

18 RemoteScope Activation Information Screen 3. Fill in the Information screen that appears and click Next again to proceed to the Connect screen shown below. Connect Screen 4. If the Console system accesses the Internet through a proxy server, the proxy s parameters must be entered here. If the Console does not use a proxy server, or if the proxy server allows all ports, uncheck the box and proceed to Step 7. 18

19 User Guide 5. Fill in the blanks with the correct information for your proxy server s Type, its IP address, and the proxy port used by the Console system. 6. If the proxy requires authentication, check that box and type in the appropriate user name and password. 7. Make sure the Console system has an active Internet connection. Click on the Connect button. This will connect the Console system to Micro 2000 s Activation Server, which will validate the information from Step 2 and the number of Client modules included in the license, and will activate the Console. If this is the Master Console, it will also validate the number of Client Modules included in the license. While the information is being transferred, this prompt will appear: Tip: If there is a firewall preventing activation, make sure port 3333 is allowed and routed to this Console PC. 8. Go to the next section: Logging On. Note: If the Console system is unable to connect to the activation server or cannot get the activation code for any reason, you can activate the console by . Click Next to proceed to the Activation Code screen and complete steps 9-11 to do this. Activation Code screen 19

20 RemoteScope 9. Click the Send button to get the SMTP Server Settings window. SMTP Server Settings window To send an using your own account, choose the Use my own mailbox to send the option and set the corresponding SMTP server information. Then click Send. You can also use the RemoteScope default account by choosing Use RemoteScope default mailbox to send the . This option will automatically send an with the user information previously entered into the Micro 2000 activation server account. If you cannot send the using either of those two methods, click the Create File button in the Activation Code window. Save the activation.txt file to a desired location and send the activation.txt file to RemoteScope@micro2000.com using your own . When the activation server administrator receives your he will promptly reply and send you the activation code. 10. Copy the activation code into the appropriate box on the Activation Code screen and click the Activate button. You will be prompted for a successful activation. 11. Click Finish to close the wizard. The RemoteScope Console will open, ready for logon. Note: For activation by authentication, only one Console can be activated with a single activation code. If you have Sub-consoles aside from the master Console in the network, you should activate each Console with a different activation code. 20

21 User Guide Logging On Once the Console has been activated by the Activation Server, the Log On window will appear. The default User name is Remote and the password is Scope. This first time, you will be logged in automatically, but on subsequent uses you will need to enter these values, with the S capitalized because login is case-sensitive. Each time you log on with these defaults, you will be prompted to change the default values and should do this at the first opportunity, as described in Chapter 3. Logon Re-Activation RemoteScope will automatically reconnect to the Activation Server at 15 days and 45 days after installation to confirm current activation status and check for updates, so it is important for the Console system to have a functioning Internet connection at those times. If for any reason the Console is unable to connect, it will display a prompt and will continue to attempt activation at each logon for three consecutive days. If the Console is unable to connect after 3 days, the Console will not allow logon. Instead, it will open the Activation Wizard and the activation code must be entered as shown in the previous section before continuing to use RemoteScope. It is also possible to re-activate the program at any time (provided activation has not expired) by using the Re-Activate System command on the Console s Tools menu. This method is used to get program updates and to confirm the addition of more Client seats or Sub-consoles. Note: Re-activating or updating RemoteScope will not change the user name and password you have set, unlike re-installing the program which will restore the default values. 21

22 RemoteScope Closing the Console Click the x in the upper right corner of the Console main window to exit. The Console will take a few moments to release its Client connections and close the program, and will display a prompt while this is occurring. You will not be able to restart RemoteScope until this process is complete and the prompt disappears. Console Uninstall The RemoteScope Console can be uninstalled in either of two ways. One is the traditional Add/Remove Programs feature in the Windows Control Panel. For the other method, go to the RemoteScope group of the Windows Program bar and find the last item: Uninstall RemoteScope. This is the recommended method because if any files cannot be removed (for instance, because they are open at the time), the RemoteScope Uninstall window will list them and they can then be removed manually. Network Segment The program contains a feature called a Network Segment that allows the Console to see and interact with only the PCs within a certain range of IP addresses at any given time. There can be many network segments organized into groups called Profiles. The first time you log into a RemoteScope Console, it will ask you to set the Network Segment. Chapter 3 contains more information about network segments and profiles, but at this time it is necessary to create only one profile with a single network segment. For simplicity, this network segment should contain the entire range of addresses that the Console will be concerned with. It can be edited later if needed Click OK and the program will take you to the Network Segment tab of the Console Configuration window. 22

23 User Guide Network Segment tab Click on the button that says Create. This will bring up the Create a Profile window. Create a Profile window Configuring a network segment is just a matter of entering the starting and ending IP addresses of the range. With static IP addressing these would be the highest and lowest IP addresses used by any of the Clients. With dynamic addressing, this network segment will use the same starting and ending addresses as the DHCP server. In the left-hand IP Range box, enter the 4 octets of the starting IP address of this network segment. In the right-hand box, put the ending IP address. Then click the Add button. The new addresses will be transferred to the lower pane. 23

24 RemoteScope Note 1: This first network segment of the Master Console should include the IP addresses of all Clients in its domain. Each Sub- Console might connect to all of these or only a portion of them, and its first network segment would need to include only those Clients to which it will connect. Note 2: Each octet must be between 1 and 255 (253 for the first octet). The ending address of a network segment must have a higher value than the starting address. Note 3: The first octet must be the same for both the starting and ending IP address, and it is strongly recommended that the second octet is the same as well. This will normally be a concern only for WAN connections and the small handful of Class A domains. Since there is only one network segment in this first profile, you are done. Click OK to close the Create a Profile window, and click OK again to close the Configuration window. Client Installation Installing the Client module takes only a double mouse click, and may be the simplest application installation you will ever see. First though, it must be distributed to the Client system. For security reasons, the module must be installed from the system where it will reside. After that, the Console is able to install software on the Client remotely, or take complete remote control of the Client. Deploying the Client At the Master Console, in the RemoteScope group of the Windows programs menu, locate and click on the Client Package. The setupclient window will open, showing two files called setup.exe and vipsetup.exe. These are the Client setup and VIP Client setup programs. More information on VIP Clients can be found in Chapter 3 in the section: Configuring the VIP Client. In most cases, the setup.exe file will be used. 24

25 User Guide Setupclient window There are several options for easily distributing these files to the Client nodes. Option 1 the file to the user at each of the Client systems. Option 2 Transfer the file to a server or shared resource that each of the Clients can access. Option 3 Share the folder at C:\Program Files\RemoteScope\ Console Main\setupclient. Option 4 For Windows NT/2000, XP, and 2003 it is possible to remotely deploy the Clients. That procedure is described in a later section of this chapter, called Deploy Clients Remotely. Option 5 (Not recommended) Transfer the file to a floppy diskette and carry it around to each system. Note: Any one system will have either the Client module or the VIP Client module, but not both. Normally the VIP module is used for top executives. It requires the user to respond with permission before the Console can remote-control, browse or transfer files to the Client system. 25