The Multi-User Impact Analysis graph is very useful to determine how Citrix and MS Terminal Servers are running out of capacity as user load grows. The graph to the right collects the last 7 days of concurrent usage data along with how key system metrics change as user load grows. This server is at 80% of physical memory at 23 concurrent users.
Additional users on this server would not be a good idea.
XIII. Updating Agents and Gateways to Future Versions
Your subscription to ProactiveWatch includes automatic access and upgrades to all future hot fixes, patches, updates, and major versions. ProactiveWatch also includes an incredibly easy process to distribute these new versions of the product to your internal and customer systems. In the cases where future versions include updates to the Gateway or the Agent components, you use the SettingsManage Updates feature of the Explorer to distribute and install the new versions. Manage Updates allows you to control which servers and workstations get updated, and you have this control on a per customer or per server/workstation basis. To use Manage Updates, take the steps below:
1. Go to SettingsManage Updates.
2. The Express tab will tell you how many of each type of agent and gateway components need to be updated.
3. If you would like to update all of your workstations and servers at one time, hit the Schedule All Updates button.
4. If you would like individual control over which customers and serves to upgrade, select the Advanced Tab. This will bring up the
dialog to the right.
5. You can choose to only display the computers at one customer site in the
Customer pull down.
6. The Status pull down allows you to display All Computer, Computers for which an Update is Available, and Computers for which the Update has been scheduled.
7. To update a set of computers, multi-select them in the table and then hit the Schedule Updates button.
8. If you like to track the progress of the update, go to SettingsManage Columns and add Agent Version as a column in the Grid View. This will give you a real time display of the progress of the updates as you will see the version numbers of the components change as they are updated.
V120322 39
XIV. Integration with LogMeIn IT Reach and the LogMeIn Network Console
ProactiveWatch includes integration with the LogMeIn IT Reach Remote Control Service. You can buy LogMeIn agent licenses and LogMeIn Network Console licenses on the Price Plans page of the
ProactiveWatch Manage Site. The process of buying LogMeIn licenses, setting up your account, and installing LogMeIn agents is documented in ProactiveWatch Quick Start Guide.
Once your LogMeIn account is set up, and you have installed your purchased licenses, you can launch the LogMeIn multi-server Network Console from the ProactiveWatch Explorer by selecting ToolsLaunch Network Console from the ProactiveWatch Explorer. The multi-server network console allows you to start a remote control session with any server or workstation upon which you have installed LogMeIn agents.
If you wish to directly launch a remote control session on one server or workstation, select that computer in the ProactiveWatch Explorer, right-click and choose Remote Control. This will launch the single session version of the LMI Network Console directly into a remote control session for that computer.
V120322 41
XV. Using A Different Remote Control Method than LogMeIN
LogMeIn is the default remote control method for ProactiveWatch. If you wish to use a different method, you can still launch the method of your choice. To configure a different remote control method than LogMeIn, take the following steps:
1. Use SettingsManage Columns to add the Remote Control column to the grid view of your Explorer as shown below (this is not essential, but it lets you see what you are doing).
2. Highlight the row containing the server that you would like to set up your own remote control session to.
3. Right-click and select Properties
4. Find the remote control field and put the launch string for your remote control method into the blank field for remote control.
5. Note you can use the data in any column as input to your remote control launch string. In the example below, Microsoft Terminal Services (MSTSC) is used being launched to the IP address of the
ProactiveWatch Gateway for that site. Since Gateway IP is an Explorer field, you can put it into the remote control launch string bracketed by “$” (mstsc /v:$Gateway IP$). You can also create custom fields and put custom data in those fields if you like.
6. Once you get a general remote control launch string that will work for more than one computer, go back to properties and copy the string into the clipboard. Then select the rows that you would like to apply this string to, right click, select Fill Cells, choose Remote Control as the field to fill, and then paste your string into the data field.
XVI. Autotask Integration
ProactiveWatch can easily be seamlessly integrated with Autotask. In order to integrate the two products, configuration must be done on both ends. Autotask must be set up to recognize ProactiveWatch, and vice-versa.