Sysaid Agent
 
Author
Message
SysAider
20
 
Hi,

Is there any plans to incorporate the agent into CSS? or have I missed it if it is there already?

Also, if we needed Agent, I'm assuming we'd have to move to a dedicated server - is it possible to migrate from CSS to dedicated?

Thanks,
Ori
SysAid Customer Relations
298
 
Hey sthomas,

The Asset Management Module + agent is part of the SysAid It (both in-house and On-demand solution).

If you are interesting in this, you should move to SysAid IT.

If you want to migrate your existing CSS solution to SysAid It, just send us an email to helpdesk@sysaid.comand let us know if you would like to use the in-house edition (installed locally on your servers) or On-Demand edition (we host it for you).

SysAider
20
 
Hi,

Our reason for choosing CSS was that we support external customers IT infrastructure, I'm led to believe that Sysaid IT is aimed at internal helpdesk.

What functionality determines this aim?

Thanks,
Steve
Ori
SysAid Customer Relations
298
 
On of the main differences between the SysAid IT and CSS is the Asset Management module.

Al tough the CSS is designed to support external customers (that's the reason there's no agent), you can use the SysAid IT to support external customer and to use the Asset management module as well.

On the SysAid IT, you can choose the In-house edition (local installation) or On-Demand.

SysAider
2
 
How would you do that? I bought the IT package and have not found a way to do this, but remote control is vital in my organization but all of our customers are external not internal

This message was edited 1 time. Last update was at Feb. 26, 2010 03:27 PM

SysAid Customer Relations
1092
 
Hello Libertas,

If you would like to install the SysAid Agent on machines located in a remote LAN in order to track / remotely control them, please do the following:

1. Your SysAid Server needs to have one of the following:
a. A Public/External IP address.
b. A port forwarded from your external IP address to the internal IP address of the SysAid server. So all requests to https://externalIP:8080 will be forwarded from your firewall/router to https://internalIP:8080.

2. If you have more than a few machines on the remote LAN, it is recommended that you install the Administrator Tools on one of the machines in the remote LAN, and then deploy the agent from that machine to the other machines. Otherwise, you can simply install with the manual install package. On the remote location, you can download the Administrator Tools from the Downloads page by logging in to your SysAid Server as an administrator.


3. When installing the Administrator Tools, you will need to enter the public/external IP address of your SysAid Server in the server URL, in order that this machine will be able to communicate with the server. The serial and account ID can be found on the Downloads page.

4. Once you have correctly installed the Administrator Tools, you can use the Deploy SysAid tool in order to automatically deploy the agents across the LAN at your remote location. After the deployment (several minutes or more, depending on the amount of assets and connection speed to the SysAid server), you should see those assets in your System -> Asset List / My Network Assets page.

5. If you wish to remotely control the assets in the remote LAN, you need to have one of two things:
a. A public IP address assigned to your workstation.
b. A forwarded port from your external (router) IP address to your workstation IP address.
On the assets remote control page, you need to enter the external IP address (which is then forwarded to your internal LAN IP address). You also need to have the Administrator Tools installed on your own workstation as well as have the “Sysaid Remote Control Viewer” running in the your system tray.
Best Regards,
Itay