Agent For Mac Os

Posted onby
You are here: Actions > Agent Software > Installing Mac Agents

The Agent Configuration screen allows you to create or modify agent profiles for Mac Os X agents. Selecting a Mac OS X agent profile from the list will allow you to configure the profile. Changes made to an agent profile can take up to 15 minutes to propagate to active Mac OS X agents.

How to Install OSSEC Agent on Mac OS X. Well as usual, we are going to install OSSEC agent on Mac OS X from the source code. As a result ensure that you have C compiler (gcc) installed. To verify that the the GNU Compiler collection is installed, run the command below; which gcc /usr/bin/gcc. Re: McAfee Agent for Mac OS communication issues In the most recent test the OS version was 10.14.3, however after a closer look I have experienced same bahaviour from a Windows system, so I. To build and deploy Xcode apps or Xamarin.iOS projects, you'll need at least one macOS agent. This agent can also build and deploy Java and Android apps. A centralised way to manage backups of all OS (backup configuration and monitoring). The user must not be able to change backup policy. Plug all agents to a Veeam cloud connect platform. Actually we can't use veeam as desktop backup solution as mac OS x is not supported.

The Mac Agent can monitor local services on a device that uses an Apple Mac OS X operating system. For more information on versions, refer to Supported Operating Systems for Agents.

To install a Mac Agent on a device discovered by a Probe
Note:Depending on the web browser used, the following procedure may differ slightly.
1. Click All Devices view in the navigation pane.
2. Click the Name of the device that you would like to edit.
3. In the Class drop-down menu of the Properties tab, select Workstation – Generic.
4. In the Operating System drop-down menu, select the appropriate Apple Mac OS X operating system.
5. Select Local Agent.
6. Click Save.
7. For the next stage of this process, you will need the Customer/Site ID (also referred to as an Access Code). In the navigation pane, click Administration > Customers/Sites and refer to the Access Code column.
8. In the navigation pane, click Actions > Download Agent/Probe Software.
9. Select Mac OS X Agent in the Download Agent/Probe Software screen.
10. Follow the appropriate instructions in the dialog box that appears and close the dialog box.
11. Navigate to the location where you saved the file.
12. Run the installer by clicking the package file: agent-macosx.tar.gz.
13. Click Continue in the confirmation window that is displayed.
14. Click Continue in the Mac Agent installer window.
15. Select a destination volume to install the software in the Select a Destination screen.
Note:This step is required in order to complete the installation of the Agent.
16. Click Continue.
17. Click Install.
18. If prompted for security credentials, type the appropriate user Name and Password before clicking Install Software.
Agent
19. In the Enter Activation Key screen, configure the following:
a. Customer ID - the Customer/Site ID or Access Code obtained at the beginning of this procedure.
b. Server URL - the URL or FQDN of the N-central server (for example, sedemo1.n-able.com).
Note: You can configure multiple addresses for an Agent to communicate with both a primary and backup N-central server. When typing multiple addresses, they must be separated by a comma but with no spaces between the different addresses and the comma.
c. Protocol - select HTTPS.
20. Click Continue.
21. Click Install Software to begin the installation process.
22. Print or save the readme file if required.
23. Click Continue.
24. Click Close.

After the Mac Agent has been installed, it is recommended that you apply the OS X Service Template to the device. For more information, refer to Service Templates.

To manually add a device with a Mac Agent
Note:Depending on the web browser used, the following procedure may differ slightly.
1. For this process, you will need the Customer/Site ID (also referred to as an Access Code). In the navigation pane, click Administration > Customers/Sites and refer to the Access Code column.
2. In the navigation pane, click Views > All Devices.
3. Click Add.
4. In the Install an Agent on a Single Workstation or Server section of the Add Devices screen, click Select OS.
5. Select Mac OS X.
6. Follow the appropriate instructions in the dialog box that appears and close the dialog box.
7. Navigate to the location where you saved the file.
8. Run the installer by clicking the package file: agent-macosx.tar.gz.
9. Click Continue in the confirmation window that is displayed.
10. Click Continue in the Mac Agent installer window.
11. Select a destination volume to install the software in the Select a Destination screen.
Note:This step is required in order to complete the installation of the Agent.
12. Click Continue.
13. Click Install.
14. If prompted for security credentials, type the appropriate user Name and Password before clicking Install Software.
15. In the Enter Activation Key screen, configure the following:
a. Customer ID - the Customer/Site ID or Access Code obtained at the beginning of this procedure.
b. Server URL - the URL or FQDN of the N-central server (for example, sedemo1.n-able.com).
Note: You can configure multiple addresses for an Agent to communicate with both a primary and backup N-central server. When typing multiple addresses, they must be separated by a comma but with no spaces between the different addresses and the comma.
c. Protocol - select HTTPS.
16. Click Continue.
17. Click Install Software to begin the installation process.
18. Print or save the readme file if required.
19. Click Continue.
20. Click Close.
21. In the navigation pane, click Views > All Devices.
22. Click Add.
23. If discovered assets are available in the Add Devices screen, Click here under the Import Devices heading.
24. In the Discovered Assets screen, select the check box next to the devices you would like to import.
25. Click Import. For more information, refer to Importing Discovered Devices

After the Mac Agent has been installed and the device imported, it is recommended that you apply the OS X Service Template to the device. For more information, refer to Service Templates.

To verify that a Mac Agent is functioning properly
  • At a command prompt, type launchctl list grep com.n-able.agent.macos10_4ppc and press Enter.

If the Mac Agent is functioning properly, the process identifier (PID) will be displayed. If the Mac Agent is not functioning properly, the hyphen character (-) will be displayed.

Starting and Stopping the Mac Agent

The Mac OS X Agent is started automatically during the system boot process. The operating system will ensure that the Agent is restarted automatically in the event that it crashes or stops functioning. If necessary, the Mac Agent can be started and stopped manually using the launchctl utility.

To start the Mac Agent
1. Open a terminal window using administrator credentials.
2. Type sudo launchctl.
3. Press Enter.
4. When prompted, type your login password.
5. Press Enter.
6. Type load /Library/LaunchDaemons/com.n-able.agent-macosx.plist.
7. Press Enter.

Mac Agents Of Shield

8. Press Ctrl-D.
To stop the Mac Agent
1. Open a terminal window using administrator credentials.
2. Type sudo launchctl.
3. Press Enter.
4. When prompted, type your login password.
5. Press Enter.
6. Type unload /Library/LaunchDaemons/com.n-able.agent-macosx.plist.
7. Press Enter.
8. Press Ctrl-D.
Related Topics

For further product information and training, visit the N-able Resource Center.

Copyright © 1990-2013 SolarWinds. All Rights Reserved.

Please click Submit once only after typing your comment. Comments are moderated and there will be a delay before your comment appears.

PST Flight Deck supports migration of files from Mac OS workstations. To support such migrations, the Migration Agent (MA) must be deployed on Mac. This document provides guidance on how to install and set up a migration agent on a Mac workstation. And it explains what steps must be executed on a PST Flight Deck server to make it work.
Note: The PST Flight Deck Migration Agent is compatible with macOS El Capitan 10.11 to Mojave 10.14. Catalina 10.15 and newer require the new Mac Agent installer available in PST Flight Deck 7.2.0.191125 and later.

Installation media for a Mac OS migration agent can be requested from Quadrotech.
Follow these steps to install the migration agent.

  1. Double-click on the installation package and follow the prompts.
  1. You will be prompted to provide Administrator credentials. Enter Administrator credentials to complete the installation.


Installation is now complete.
You should now see the Quadrotech icon in menu bar:
Click on the icon to see options related to the Mac OS migration agent:
Click Show Log to check logs. A Console opens with com.gladwev.flightdec.log, which is the log for the Mac OS migration agent.

Unlike the Windows version of the migration agent, where the destination is set during the installation process, with Mac OS workstations, it must be done after installation. This can be easily done via this command:

  • defaults write com.gladwev.flightdeck apiuri http://YourFDServerName/PSTFlightDeckWS/MacClient.svc
  • restart the application FlightDeck Mac Agent:
    • if you can see the Quadrotech icon in menu bar, choose Exit.
    • if you can’t see it in menu bar, start native the Mac OS application Activity Monitor and search for “FlightDeck Mac Agent”. Select it and quit using the X button.
    • Start it again by double click on FlightDeck Mac Agent in Application

When the migration agent is installed on a Mac OS workstation and the PST Flight Deck core address is set to “apiuri”, you can see in the Administration Console how the Mac OS migration agent presents itself and how to troubleshoot basic issues.

License

You must request Mac OS workstation licenses to be part of PST Flight Deck licensing. The About window shows how many Mac licenses are available. Take a look:
You can see which Mac OS workstations have licenses via Settings > Mac OS Migration Agent > User Licenses button. Take a look:
In order for the Mac OS migration agent to work, you must have a valid registration key.
If you don’t have a valid registration key, you’ll see this message in the migration agent’s logs:
info 1 MacClient GetWorkItems : WorkHandler is not initialized, product not registered.

Configuration settings

Similar to the Windows migration agent, the Mac OS migration agent can be customized to meet customer needs. All settings for the Mac OS migration agent are in Settings > Mac OS Migration Agent.
Use the Path Excludes and Search Paths field to indicate what should be scanned and what should be excluded.

Show/Hide PST Flight Deck icon in Mac OS agent menu bar

If you want to show/hide the PST Flight Deck icon from the Mac OS menu/task bar, follow these steps:

  1. Select Mac OS Migration Agent from the left menu bar.
  2. Select Edit Xml in the top menu bar.
  3. In the Config window, locate this line: <Item Name = “ShowMenu” >true</Item>
  4. Change the line to: <Item Name = “ShowMenu” >false</Item>
  5. Save your changes.

Here’s how it looks:

This section can be used to help troubleshoot issues.

Checking to see if the Mac OS migration agent is reaching the PST Flight Deck core


Mac OS workstations should be listed in Settings > Computers. To view them, in the Computer Type column, filter by Mac OS Computer. If you can’t see you Mac OS workstation, go back to the workstation and check:

  • if you are able ping your PST Flight Deck core server
  • if you are able to reach the PST Flight Deck webservice (http://YourFDServerName/PSTFlightDeckWS/MacClient.svc) in a web browser, you will see a screen similar to this:
  • if logs on the Mac OS workstation show that you have a valid license (see above for more information)

Mac OS migration agent should report Outlook profile to PST Flight Deck core

To see if the migration agent is reporting to the PST Flight Deck core:

  1. In core, go to Manage > Files.
  2. Add the File Type column and filter for Mac Profile 2016 or 2013.

This is the basic identity that must be met before any processing can occur.
When the profile does not appear after some time, try restarting the Mac OS migration agent.
Note that the Path is different for Mac OS files, starting with MAC Workstation followed by : and then ~/ or ~//. Please be aware that this ~ is not equivalent to the “current user” shortcut used in Mac OS workstations. Rather, it indicates in PST Flight Deck that files are from a different file system.

Logs

Logs can be accessed from menu in Task Bar, by choosing Show Log option. This will open log file in Console.
If you need to access log file on you file system, logs are stored in a file com.gladwev.flightdeck.log. Location of that file:

  • Library/Logs/com.gladwev.flightdeck.log

User from Mac OS in Manage > Users


When a Mac OS migration agent reports files for a Mac OS user, it uses the username of the Mac OS user. In many cases, this is not an Active Directory account. To be able to migrate files from a Mac OS workstation to a target (for example, Office 365 cloud), the Mac OS user must be matched with an Active Directory account. This is explained in the next section.
Mac OS users can be identified by User Type = Mac OS user on the Manage > Users screen.

Mac OS users are often not Active Directory users. To be able to migrate files from a Mac OS user/workstation to a target, this account must be matched with an Active Directory account.
Be aware that a user with the type Mac OS user should NOT be enabled. If you try to enable it, you will see the following warning:
Matching can be done in two ways:

Automatically

PST Flight Deck can uniquely and reliably match a Mac OS user with an Active Directory account. In such case, no action is required. The Mac OS user is “blended” with an Active Directory account. The original Mac OS user will not be visible anymore and all files for the “blended” user will appear there (there can be both Windows and Mac OS files under one user).

Manually

When there are circumstances preventing PST Flight Deck from doing automatic matching, it must be done manually. For example:

  • There might be multiple Outlook profiles on a Mac OS workstation
  • The Mac OS user’s name might not match any names in Active Directory
  • The Mac OS user’s name might match more than one Active Directory account.
  • And so forth

Go to Manage > Events to see information about unsuccessful matching. For example:

PST Flight Deck offers a wizard that can be used to manually match Mac OS users and Active Directory accounts.
You can find it by going to Settings > Mac OS Migration Agent > Manage users. Take a look:
Step 1: The wizard shows only users with the type Mac OS user if they have an uploaded Outlook profile. If the Outlook profile is not yet uploaded you won’t see the Mac OS user here.
Note: The following filter is preset and can’t be deleted:
Step 2: In the AD Users section, select the Active Directory account to which it should be matched.
Step 3: If you are OK with your selection, click Confirm.
The Mac OS user is now “blended” with an Active Directory account and you’ll not be able to find it on the Manage > User screen with the original Mac OS username. Mac OS files now appear under the matched Active Directory account instead.

When the Mac OS migration agent is not needed anymore or must be replaced with a newer version, you can uninstall the older version and remove all records related to it.
Uninstalling the Mac OS migration agent is simple. To do it, right-click on the application and choose Move to Trash (shown below).
The Mac OS migration agent stores some of its settings in the Mac OS “defaults” mechanism. When the migration agent is removed/uninstalled these settings are left intact. This could cause confusion when installing newer version of the migration agent.

There are two locations on the Mac OS system where migration agent files are stored: global and local (user related). Installation in administrative/root locations are not likely, but could occur. Therefore, check these locations when you’re cleaning the Mac OS migration agent. For global settings and files, an administrative/root account is required.

User (local)

Defaults

To check default Mac OS migration agent settings, use this command:

  • defaults read com.gladwev.flightdeck

If you want to read only a specific parameter and you know its name use it in “”:

  • defaults read com.gladwev.flightdeck “apiuri”

To delete values from defaults and completely remove migration agent records from the system, use these commands:

  • defaults delete com.gladwev.flightedeck “apiuri” – this deletes just apiuri
  • defaults delete com.gladwev.flightdeck – this deletes all settings for the Mac OS migration agent

Logs

Logs are stored in a file named com.gladwev.flightdeck.log

  • Library/Logs/com.gladwev.flightdeck.log

If you want to delete log, remove it via:

  • rm Library/Logs/com.gladwev.flightdeck.log

Data

The Mac OS migration agent stores its data in Library/Application Support/com.gladwev.flightdeck. Remove this directory and its content to wipe all migration history from the Mac OS workstation. For example:

  • rm -r ~/Library/Application Support/com.gladwev.flightdeck/

Global (root/admin)

Some information might be stored globally. To wipe this data, you’ll need root/administrative access to be able to execute elevated commands via sudo

Defaults

  • sudo defaults delete /Library/Preference/com.gladwev.flightdeck “apiuri” – use this command if you want to delete just apiuri
  • sudo defaults delete /Library/Preference/com.gladwev.flightdeck – use this command delete all settings for Mac OS migration agent

Logs

This log is not usual, but just in case check this location for log:

  • /Library/Logs/com.gladwev.flightdeck.log

And, if the log exists, remove it via:

  • sudo rm /Library/Logs/com.gladwev.flightdeck.log

Photos Agent Mac

Note

Snow Inventory Agent For Macos

  • Please be aware of difference between /Library (absolute path) and Library (user path relative to logged user also known as ~ path in *nix systems) directories.
  • There is a difference between global (root) and user (local) access to resources.
  • In Mac OS ~ is translated to /Users/CurrentUser.
  • in a path is “escape character” for space.
  • You can enclose a path with special characters like space into ” “

Veeam Agent For Mac Os

Please be careful with sudo and rm commands as they can harm your Mac OS installation if they’re used improperly.