Download Controlup Console [EXCLUSIVE]

A graphical display of all the computers currently added to the console, arranged in folders. There are two methods for managing the tree: right-clicking computers or folders, or by using the Folder area of the Home Ribbon.

If you are sure that you won't use any of these features and prefer not to allow log on locally, you can assign Allow Log on as a Service. If you aren't sure, set as recommended or contact support@controlup.com.

Download Controlup Console

Download 🔥 https://tlniurl.com/2y67CY 🔥

The bottom of the Domain Identity page hosts the credentials saved with the monitor instance in order to enable it to connect to your virtualization infrastructure. To monitor virtualization hosts, ControlUp requires consoles and monitors to use the same credentials. Optionally, to enable continuous monitoring of the virtualization hosts using the monitor, use the page to save the same service account credentials used by other ControlUp users in your organization to connect to your hosts.

If your ControlUp Console is already configured to export data on a scheduled basis, the Monitor Configuration Wizard will offer you to move your export rules from your personal settings to the ControlUp Monitor. If you choose to agree, the monitor service starts exporting the data instead of your console, eliminating the need to keep a console open in order to produce data reports. You can configure additional export rules for the monitor.

The monitor is similar to the console, acting like a client that connects to a listening TCP port (40705 by default) on the managed machines. The monitor listens on port 40706 only to allow other installed consoles in your organization to receive status updates and to display the status of the monitor in the Real-Time Console.

You have the option to restrict the display of the ControlUp Real-Time Console user interface components by using the Microsoft Group Policy. You can hide panes, views, actions, columns, and buttons, thus creating a limited view that may be useful for delegated administrators, such as helpdesk personnel. These restrictions are visual only in terms of what is visible in the console. They do not change any permissions the user might have to perform actions in ControlUp.

IT professionals can use the console to observe the health and performance of their organization's systems and take actions such as ending, killing or changing the priority of desktop processes, screenshotting session activity and more.

IT professionals can customize the notifications they receive based on type and urgency. They cannot directly solve a problem with ControlUp Mobile, however. To fix a problem, they must log on to a desktop or laptop and access the ControlUp Real-time console.

1. In the console, go to Settings > Advanced. Here you can modify the data collection interval for windows machines (agent-based collection) or Linux machines (agentless data collection).

When you set up a Hypervisor connection, the console machine is the default data collector. For example, in a large organization with hundreds of consoles connected to hypervisor endpoints, this would greatly impact performance. You can greatly reduce the number of connections to external resources by setting up a dedicated data collector.

You can automate connecting to managed machines from the console by selecting the Show auto-connect state checkbox under the ControlUp organization tree. You can define machines that you want to automatically connect to, either when the console is started and/or after a specific time interval that you need to define in the Agent Settings.

By default, all fields are searched in the search field. By changing the default search option to Name only, the console will use fewer resources since the search is only filtered to the Name column.

You can configure this search behavior in our GPO template. Go to ControlUp > Console > Advanced Settings and configure the Search box behavior settings. To learn more about configuring the console UI with group policies, see here.

By unselecting that option, you take control of the agent deployment. Otherwise, when the console attempts to connect to a monitored computer or endpoint and fails, it will attempt agent deployment. In large environments that may cause degradation in Console performance, try to deploy the agent in the background to all agents which are not connected.

A Data Collector increases the performance capabilities of both your console and monitor when collecting metrics from external sources such as VMware vCenter, Citrix Delivery Controllers, XenServer Pool Masters, AHV Clusters, and ADC appliances.

When using CERTONLY=TRUE, you instruct the agent to only accept connections from the console / monitors that are configured to use the Certificate-based agent authentication if the relevant agent-side registry keys are not configured.

The ControlUp Monitor is a component principally equivalent to ControlUp Real-Time Console but without an interactive user interface. The primary difference between a monitor and a console is the fact that the Monitor runs as a Windows service, requiring no user interaction and allowing for continuous monitoring of your resources.

From version 8.8, you can upgrade and uninstall agents that were installed with the MSI installer from the console. On the agent machine you want to manage from the console, under HKEY_LOCAL_MACHINE\SOFTWARE\Smart-X\ControlUp\Console\EnableAgentManagement set the value to 1.

As in Windows Explorer, Folders in the ControlUp console allow you to organize monitored devices into manageable groups. So far, in this article series, only infrastructure computers exist. Folders allow the grouping of servers by function, action, type, use, or any criteria needed. Folders can mimic an existing AD OU structure or any structure desired.

Advanced Authentication is a security measure used to securely identify and authenticate ControlUp components that access the ControlUp backend, Real-Time consoles, and ControlUp Monitors. The ControlUp organization owner, who is the user that created the organization, is responsible for configuring a certificate within the console. This can be done by generating a self-signed certificate or using a third-party certificate

The certificate that is set up for your organization is unique to it and saved in the local Certificate Store on the console machine where the organization owner has created it. Once you have set up a certificate for your ControlUp organization, the console automatically distributes the private certificate to all the monitors in the ControlUp environment, and sends a public certificate to the ControlUp backend in the cloud.

It's important to understand that if the configured certificate is missing on a console machine, it is not possible to connect to your ControlUp organization from that particular machine. In this case, you have to manually apply the new certificate to this machine to allow the Console to connect to your ControlUp environment. This is explained in the Distribute the New Certificate to Consoles and Assign Read Permissions to Console Users sections.

There are two ways you can distribute the pfx file to other console machines. You can perform the steps manually or you can use our [PowerShell script] attached to this article. If you choose to do it manually, then you have to manually [distribute the certificate to all console machines] and set read permissions for all non-admin users on the console machine. If you want to use our PowerShell script to perform both steps automatically, refer to the Distribution and Permission Setting via PowerShell section.

On each console machine, open the local certificate store on the Console machine. Run mmc > Add/Remove Snap-in > Certificates > Add. In the Certificates snap-in wizard, select Computer account > Next > Local computer: (the computer this console is running on) > Finish.

Open the console as the user you assigned the Read permissions and select the organization in the Select a ControlUp organization list. At this point, the selected organization should be accessible to the user

If you want to distribute the certificate to console machines in your organization and to set the Read permissions for non-admin users on those machines, you can use our PowerShell script to perform both actions automatically.

Create a text file that contains the host name of your console machine to which you want to distribute the certificate. Note that machine names must be line-separated and no space should be left at the end of each line

To access a console machine where you have distributed your certificate, log in and launch the console. Any user, whether local admin or non-admin, who has been granted read permissions as specified in the -allow parameter can now connect to your ControlUp organization.

Users with the Login Access Manager permission can assign any of the login access rights (Login Access Manager, Real-Time DX and Insights) to any other user, and can also revoke any of the login access rights from any other user, except for the organization owner. The organization owner is the only user who is assigned the Login Access Manager permission by default, and for whom it can't be revoked. To change the organization owner, contact support@controlup.com.

Before you start the upgrade, close any ControlUp console instances that might be running and launch the new console executable, enter your login credentials, and log on to your existing organization.

Note that all monitors and consoles in your environment must use the same credentials when connecting to your resources. You can share your credentials in your Monitor Settings so that all ControlUp users can easily connect to your resources without having to know the service account username and password. For more information, see Configuring Shared Credentials. 17dc91bb1f