To stop, start, or restart the Management Console for Unix service (mcu_service) on a Windows machine
This is handy on Windows 7+ because you can use the <windows_key> to search for it quickly.
Use the Start, Stop, or Restart commands from the Action menu or right-click context menu.
You use the toolbar buttons across the top of the All Hosts view to perform individual tasks against one or more managed host systems. If the toolbar buttons are not active, it might be due to
If you select multiple hosts, they all must be in the same state (added, profiled, or joined) to perform the desired task. If they are not all in the same state, the toolbar button for that task will be disabled.
For example, if you select all hosts, but one or more of them are not profiled, the Install Software toolbar button will not be available for the whole group. If you deselect the hosts that are not profiled, the Install Software toolbar button becomes active. Also, if one of the selected hosts is currently being profiled by auto-profile, the web services, or by another console user, the Profile button will be disabled. You can either wait for the profile task to complete, or deselect the host to activate the Profile button.
Another reason for a disabled toolbar button might be your user account role. You may only have read-only access to the view and are not allowed to perform the desired task. For example, if your user account is not in the Manage Hosts role, then you cannot make changes to hosts.
Other tasks, such as Clear column filters have nothing to do with host state or user roles. That toolbar button is only enabled if you have column filters set. If there are no column filters set, then the option to Clear column filters is disabled. When one or more filters are set, then the option is enabled.
Management Console for Unix does not automatically pick up changes to the host made externally to the console unless you configure the host for auto-profiling.
For example, when you install Privilege Manager software on a remote host, it creates a new user and group named pmclient, assigning a UID and GID accordingly. If you do not profile the host after installing the Privilege Manager packages, the mangement console will not recognize the new user name and group name. If you attempt to configure that host for auto-profiling or automatic QAS status updates without profiling, you might encounter a UID conflict, such as this:
Or, if you attempt to add a new local group to that host without profiling, you might encounter a GID error like this:
If you encounter a UID or GID conflict, profile the host and try the action again before you troubleshoot the problem further.
It is important to safeguard your data. One Identity recommends that you maintain copies of the most important files so you're always prepared for the worst.
This appendix provides general information and guidelines for maintaining or backing up your data.