Looking for Documentation describing Configuration of SaaSagent32 and Gateway.

Version 1

    Details

    Im looking for docs describing Configuration of SaaSagent32 and Gateway. Where can i find it?


    Resolution

    You can find information in regards to your request at the below link.




    Managing Gateway Settings


    About Managing Gateways

    Viewing and Setting a Central Gateway

    Viewing the List of Agent Tasks

    Updating Administrative Credentials

    Managing the Client Task Subnets

    Deploying the Agent Tab

    Notes for Upgrading the HEAT Discovery Gateway from Earlier Versions

    About Managing Gateways

    Gateways  allow you to scan your network and create records about the devices and  machines. You can install more than one gateway; however, you can only  set one gateway as the central gateway. A central gateway allows you to  have a single machine that communicates with the main server. All other  gateways send information to the central gateway.

    Once  the gateway is successfully installed it sends its own data to the main  server and a configuration item record is created for the gateway  machine. Open the Gateway workspace to find a list of all the gateways.

    The  Data Center Edition Gateway is bundled with Netscan which allows you to  scan within a subnet (IP range), and with VMHA (Virtual Machine Host  Auditor) which discovers virtual machines using a host/guest model.

    HEAT Discovery Managers can manage settings from the Gateway workspace.

    Viewing and Setting a Central Gateway

    From the Gateway workspace,  you can specify a central (or default) gateway computer. If the agent  task of a client cannot be assigned to any gateway, then the system uses  the gateway identified as the central gateway as the fallback.

    The  system selects the closest matching gateway to a client computer based  on the IP address of the client computer. If the subnet of the client  falls within the IP range of a gateway, it is associated with that  gateway. If a client does not match the subnet range of any other  gateway, then the client defaults to the central gateway.


    1.Log into the Service Desk Console as a HEAT Discovery Manager, HEAT Discovery Analyst, or administrator.

    2.Open the Gateway workspace.The system displays a list of gateway computers or displays a default gateway computer record.

    If Central Gateway is checked in the Details tab, the computer is the central gateway.


    3.To make another computer the central gateway, select the record, then click Select/Deselect as Central Gateway icon in the toolbar.

    4.Double-click a computer on the list to view details.
    FieldDescription
    EditionThe computer name registered as the gateway.
    Settings VersionThe number of times that the gateway record has been updated.
    Settings Last Deployed OnThe date and time when the gateway record was updated.
    Central GatewayIf checked, this gateway is a fallback to handle tasks if no other gateway is found.

    5.Click the Computer tab  to view data about the gateway computer. The computer on which the  gateway is installed gets automatically audited after the gateway is  installed. The Computer tab is populated only when auditing is completed.

    6.To open the computer record, select the record and click Go to.

    Viewing the List of Agent Tasks

    Many of the tasks that you perform within the Inventory workspace  are scheduled as agent tasks, for example updating gateway settings.  You can cancel an agent task if it has not yet started or is in pending status.

    Tasks that are in the pending or in progress status are set to expire if they are not processed within the default expiration time, which is seven days.

    Follow these steps to view the list of agent tasks:


    1.Log into the Service Desk Console as a HEAT Discovery Manager.

    2.Open the Gateway workspace. The system displays a list of gateway computers or displays a default gateway computer record.

    3.Open the gateway to manage. The Gateway page appears.

    4.Select the Agent Tasks tab to see the list of tasks.

    Updating Administrative Credentials

    To  scan or deploy agents from the gateway computer to other machines, you  must provide credentials that have administrator privileges on the  client machines.


    1.Log into the Service Desk Console as a HEAT Discovery Manager.

    2.Open the Gateway workspace. The system displays a list of gateway computers or displays a default gateway computer record.

    3.Open the gateway to manage. The Gateway page appears.

    4.From the Administrative Credentials tab, change the user name and password as needed, then click Update.

    5.From the toolbar, click Deploy Settings.

    The system updates the credentials and deploys the settings.

    Managing the Client Task Subnets

    The Client Task Subnets tab  controls which computers the gateway manages. It only handles tasks  such as deploy agent for computers that reside in the specified subnets  (unless it is the central gateway).

    The  specified gateway should have access to the subnets that you specify  here. If there are multiple gateways, the client subnet decides which  gateway handles the task.


    1.Log into the Service Desk Console as a HEAT Discovery Manager.

    2.Open the Gateway workspace. The system displays a list of gateway computers or displays a default gateway computer record.

    3.Double-click to open the gateway to manage. The Gateway page appears.

    4.Select the Client Task Subnets tab  to see the subnet in which the gateway resides. It specifies the range  of IP addresses within the subnet. For example, 192.172.0 covers the  entire subnet 192.172.

    5.Click New Record. The New Gateway Subnet window appears.

    6.Enter information into the fields.
    FieldDescription
    NameThe name of the subnet.
    IP AddressThe IP address in the subnet range. For example, 192.172.0.
    Subnet MaskThe subnet mask that defines the subnet range. For example, 255.255.255.0.

    7.Click Save.

    8.From the toolbar, click Deploy Settings. The system deploys the settings.

    Data center edition gateways have access to Netscan and can scan virtual machines. See Using Netscan.

    Deploying the Agent Tab

    You can select options to deploy agents from the Deploy Client Agent Tab

    The  specified gateway should have access to the selected target types. If  there are multiple gateways, the client subnet decides which gateway  handles the task.


    1.Log into the Service Desk Console as a HEAT Discovery Manager.

    2.Open the Gateway workspace. The system displays a list of gateway computers or displays a default gateway computer record.

    3.Open the gateway to manage. The Gateway page appears.

    4.Click the Deploy Agent tab.

    5.Select a deploy target type from the list.

    6.Enter the appropriate information in the Deploy To field.
    For Target of TypeDescription
    Computer ListThe name or IP address, such as VirtualMachine-002 or 192.168.3.2
    Domain ListDomain names, such as heatsoftware.com or lumension.com
    IP Address Range ListThe IP address range such as 192.168.0.1-192-168.0.254

    7.Enter credential information for the User Name and Password fields.

    8.Click Deploy Settings.

    The system deploys the settings.

    Notes for Upgrading the HEAT Discovery Gateway from Earlier Versions


    Does the HEAT Discovery gateway need to be reinstalled or upgraded?

    Yes. The HEAT Discovery gateway  needs to be reinstalled manually. The newer gateway (version 2.0) is  backward compatible and does support the client version 1.9.

    How does the new agent get deployed via the gateway?

    The current gateway cannot support the newer version of the client agent and must first be upgraded.

    Do I have to uninstall the old agent? Initial testing shows that the old HEAT Discovery agent does not get cleanly removed when manually uninstalled, leaving behind folders and files.

    No,  you do not have to uninstall the existing client prior to installing  version 2.0. The residual folders and files have no side effect when the  newer client agent is installed.

    Do I need to remove the agent via the configuration item object or can this be rolled out via an SCCM package?

    No, you can simply run the new installer and it will upgrade the agent.