Agent Shift Mac OS

broken image


Welcome to vRealize Configuration Manager : Managing Mac OS X Machines : Manually Install the Agent on Mac OS X Machines

Reset SMC: Shut down your Mac, and then press and hold the left-side Shift (⇧)—Control (⌃)—Option keys along with the Power (⎋) button, all at the same time, until the computer turns on. Now release the keys and then turn your Mac back on using the power button. Other keyboard shortcuts are available after your Mac has started up. DarkNight was a launch agent that matched Night Shift and the system appearance: however, with the release of macOS Catalina, this feature has now been Sherlocked. Downloads for Parallels Desktop Run Windows applications on your Mac — without rebooting Try free for 15 days.

Agent

Install the appropriate version of the VCM Agent on each of your licensed target machines to enable communication between the Collector and the managed Mac OS X machines.

Installing the Agent on Mac OS X machines is a manual operation. The Agent is packaged as a Universal Binary Installer. You can run the installation process in silent mode or interactive mode. To run the installation in silent mode, you must edit the configuration options in the csi.config file. The file is edited to accommodate different target machine types.

Prerequisites

  • Verify that the machine on which you intend to install the Agent has enough free disk space. Formore information, see the VCM Installation Guide.
  • If you are installing the Agent on Red Hat Enterprise Linux (RHEL) 7, Oracle Enterprise Linux (OEL) 7, or CentOS 7, verify that the net-tools and redhat-lsb-core packages are installed on the target machine.
  • Identify the Agent binary installation package that you will copy from the Collector to the managed machine. See the VCM Installation Guide.
  • If you run an installation in silent mode, modify the appropriate csi.config file variable options. See Installation Options for Max OS X csi.config .
  • If you select (x)inetd/launchd for CSI_AGENT_RUN_OPTION, verify that (x)inetd/launchd is running on the target machines. On some versions, when (x)inetd/launchd services are not configured, (x)inetd/launchd will not stay running. To ensure the Agent installation completes successfully, pass a - stayalive option to (x)inetd/launchd. See Installation Options for Max OS X csi.config .
  • Log in to the target Mac OS X machine as root, or have sudo as root.
  • Select the method that you want to use to copy files to the target machines. You can use ftp, sftp, or cp using an NFS share. If you use ftp to copy the package to your machine, you must use binary mode.
  • If you are collecting non-ASCII information from the target machines, install a UTF-8 locale. To determine the locales installed on your operating system, use the locale -a command.

Procedure

  1. Copy the appropriate Agent binary installation package from the Collector to the machine on which you will install the Agent.

    The Agent packagesare located on the Collector in Program Files (x86)VMwareVCMInstallerPackages.

  2. On the target machine, run chmod u+x to set the execute permission for the file owner on the Agent binary file.
  3. In the directory to which you copied the file, run ./CMAgent.. to create the necessary directory structure and extract the files.

    To force an overwrite of any existing files, include the -o option.For example: /CMAgent..Darwin -o.

    The command and output is similar to the following example, but with different file names depending on the operating system.

    # ./CMAgent..Darwin
    UnZipSFX 5.51 of 22 May 2004, by Info-ZIP (http://www.info-zip.org).
    creating: CSIInstall/
    inflating: CSIInstall/CMAgent.5.1.0.Darwin.i386
    inflating: CSIInstall/CMAgent.5.1.0.Darwin.ppc
    inflating: CSIInstall/csi.config
    inflating: CSIInstall/InstallCMAgent

  4. Run cd /CSIInstall to change the directory to the location where the InstallCMAgent executable file was extracted.
  5. Run ls -la to validate that the correct files are in the /CSIInstall directory.

    FileDescription
    InstallCMAgentInstallation script.
    csi.configConfiguration file for the installation. This is the file you can modify to include installation options for silent rather than interactive installation processes.
    packagesInstallation packages.
    scriptsScripts required for the installation.
  6. (Optional) Edit the csi.config file to customize the installation variables and save your changes.

    1. Run the chmod u+x csi.config command to add write file permissions if the file has only read permissions set.
    2. Modify the csi.config file options based on your local requirements and save the file.
    3. Where is joann? (devy_games) mac os. Copy the modified and saved csi.config file to the extracted location.

      For example, # cp //csi.config //CSIInstall/csi.config.

  7. Run InstallCMAgent in either silent mode or interactive mode.

    OptionAction

    Silent mode

    Run the # ./CSIInstall/InstallCMAgent -s command.

    Install the Agent using the silent mode if you manually edited the csi.config file, if you modifiedthe csi.config file using the interactive method, or if you are using a custom configuration file thatyou saved from a previous Agent installation. This mode uses the valuesspecified in csi.config without prompting for input.

    When the silent installation finishes, a summary of the installation process and status appears.Verify that the installation finished without errors.

    Interactive mode

    Run the # ./CSIInstall/InstallCMAgent command.

    Install the Agent using the interactive mode if you did not modify the csi.config and to respond to each prompt toaccept or change each parameter in the csi.config file as it runs. As a result of your responses, the csi.config is modified.

    The preinstallation stage of interactive mode checks for a valid user, CSI_USER. If the user exists, you are not prompted for these configuration values.

    • CSI_USER_NO_LOGIN_SHELL
    • CSI_USER_PRIMARY_GROUP
    • CSI_USER_PRIMARY_GID
    • CSI_USER_USE_NEXT_AVAILABLE_LOCAL_GID

    You are prompted for these values only when the CSI_USER user account is not found.

    The User and the Group are created in the local directory service storage.

    You can check the installation status in the installation log file. The file is located in /log/install.log.

  8. Street crossing mac os. Run ls –la /CSI_PARENT_DIRECTORY/CMAgent Death metal mac os. to verify that all the required files and directories were installed.

    /CSI_PARENT_DIRECTORY/CMAgent is the default directory. If you changed the directory name during installation, modify the ls -la command to display the custom directory name.

    drwxr-x--- 3 root cfgsoft 4096 Jul 2 17:34 Agent
    drwxr-x--- 3 root cfgsoft 4096 Jul 2 17:34 CFC
    -rw-rw---- 1 root cfgsoft 49993 Jul 2 17:34 CSIRegistry
    -rw-rw---- 1 root cfgsoft 0 Jul 2 17:34 .CSIRegistry.lck
    drwxrwx--- 3 csi_acct cfgsoft 4096 Jul 2 17:34 data
    drwxrwx--- 3 root cfgsoft 4096 Jul 2 17:34 ECMu
    drwxr-x--- 6 root cfgsoft 4096 Jul 2 17:34 install
    lrwxrwxrwx 1 root root 20 Jul 2 17:34 log -> /var/log/CMAgent/log
    dr-xr-x--x 3 root cfgsoft 4096 Jul 2 17:34 ThirdParty
    drwxr-xr-x 2 root root 4096 Jul 2 17:34 uninstall

  9. Run # netstat -na | grep to verify that the Agent is installed correctly, listening on the assigned port, and ready to collect data.

    The default is 26542 for VCM installations.

What to do next

Run a collection for Mac OS X data. See Collect Mac OS X Data.

Agent shift mac os download

Install the appropriate version of the VCM Agent on each of your licensed target machines to enable communication between the Collector and the managed Mac OS X machines.

Installing the Agent on Mac OS X machines is a manual operation. The Agent is packaged as a Universal Binary Installer. You can run the installation process in silent mode or interactive mode. To run the installation in silent mode, you must edit the configuration options in the csi.config file. The file is edited to accommodate different target machine types.

Prerequisites

  • Verify that the machine on which you intend to install the Agent has enough free disk space. Formore information, see the VCM Installation Guide.
  • If you are installing the Agent on Red Hat Enterprise Linux (RHEL) 7, Oracle Enterprise Linux (OEL) 7, or CentOS 7, verify that the net-tools and redhat-lsb-core packages are installed on the target machine.
  • Identify the Agent binary installation package that you will copy from the Collector to the managed machine. See the VCM Installation Guide.
  • If you run an installation in silent mode, modify the appropriate csi.config file variable options. See Installation Options for Max OS X csi.config .
  • If you select (x)inetd/launchd for CSI_AGENT_RUN_OPTION, verify that (x)inetd/launchd is running on the target machines. On some versions, when (x)inetd/launchd services are not configured, (x)inetd/launchd will not stay running. To ensure the Agent installation completes successfully, pass a - stayalive option to (x)inetd/launchd. See Installation Options for Max OS X csi.config .
  • Log in to the target Mac OS X machine as root, or have sudo as root.
  • Select the method that you want to use to copy files to the target machines. You can use ftp, sftp, or cp using an NFS share. If you use ftp to copy the package to your machine, you must use binary mode.
  • If you are collecting non-ASCII information from the target machines, install a UTF-8 locale. To determine the locales installed on your operating system, use the locale -a command.

Procedure

  1. Copy the appropriate Agent binary installation package from the Collector to the machine on which you will install the Agent.

    The Agent packagesare located on the Collector in Program Files (x86)VMwareVCMInstallerPackages.

  2. On the target machine, run chmod u+x to set the execute permission for the file owner on the Agent binary file.
  3. In the directory to which you copied the file, run ./CMAgent.. to create the necessary directory structure and extract the files.

    To force an overwrite of any existing files, include the -o option.For example: /CMAgent..Darwin -o.

    The command and output is similar to the following example, but with different file names depending on the operating system.

    # ./CMAgent..Darwin
    UnZipSFX 5.51 of 22 May 2004, by Info-ZIP (http://www.info-zip.org).
    creating: CSIInstall/
    inflating: CSIInstall/CMAgent.5.1.0.Darwin.i386
    inflating: CSIInstall/CMAgent.5.1.0.Darwin.ppc
    inflating: CSIInstall/csi.config
    inflating: CSIInstall/InstallCMAgent

  4. Run cd /CSIInstall to change the directory to the location where the InstallCMAgent executable file was extracted.
  5. Run ls -la to validate that the correct files are in the /CSIInstall directory.

    FileDescription
    InstallCMAgentInstallation script.
    csi.configConfiguration file for the installation. This is the file you can modify to include installation options for silent rather than interactive installation processes.
    packagesInstallation packages.
    scriptsScripts required for the installation.
  6. (Optional) Edit the csi.config file to customize the installation variables and save your changes.

    1. Run the chmod u+x csi.config command to add write file permissions if the file has only read permissions set.
    2. Modify the csi.config file options based on your local requirements and save the file.
    3. Where is joann? (devy_games) mac os. Copy the modified and saved csi.config file to the extracted location.

      For example, # cp //csi.config //CSIInstall/csi.config.

  7. Run InstallCMAgent in either silent mode or interactive mode.

    OptionAction

    Silent mode

    Run the # ./CSIInstall/InstallCMAgent -s command.

    Install the Agent using the silent mode if you manually edited the csi.config file, if you modifiedthe csi.config file using the interactive method, or if you are using a custom configuration file thatyou saved from a previous Agent installation. This mode uses the valuesspecified in csi.config without prompting for input.

    When the silent installation finishes, a summary of the installation process and status appears.Verify that the installation finished without errors.

    Interactive mode

    Run the # ./CSIInstall/InstallCMAgent command.

    Install the Agent using the interactive mode if you did not modify the csi.config and to respond to each prompt toaccept or change each parameter in the csi.config file as it runs. As a result of your responses, the csi.config is modified.

    The preinstallation stage of interactive mode checks for a valid user, CSI_USER. If the user exists, you are not prompted for these configuration values.

    • CSI_USER_NO_LOGIN_SHELL
    • CSI_USER_PRIMARY_GROUP
    • CSI_USER_PRIMARY_GID
    • CSI_USER_USE_NEXT_AVAILABLE_LOCAL_GID

    You are prompted for these values only when the CSI_USER user account is not found.

    The User and the Group are created in the local directory service storage.

    You can check the installation status in the installation log file. The file is located in /log/install.log.

  8. Street crossing mac os. Run ls –la /CSI_PARENT_DIRECTORY/CMAgent Death metal mac os. to verify that all the required files and directories were installed.

    /CSI_PARENT_DIRECTORY/CMAgent is the default directory. If you changed the directory name during installation, modify the ls -la command to display the custom directory name.

    drwxr-x--- 3 root cfgsoft 4096 Jul 2 17:34 Agent
    drwxr-x--- 3 root cfgsoft 4096 Jul 2 17:34 CFC
    -rw-rw---- 1 root cfgsoft 49993 Jul 2 17:34 CSIRegistry
    -rw-rw---- 1 root cfgsoft 0 Jul 2 17:34 .CSIRegistry.lck
    drwxrwx--- 3 csi_acct cfgsoft 4096 Jul 2 17:34 data
    drwxrwx--- 3 root cfgsoft 4096 Jul 2 17:34 ECMu
    drwxr-x--- 6 root cfgsoft 4096 Jul 2 17:34 install
    lrwxrwxrwx 1 root root 20 Jul 2 17:34 log -> /var/log/CMAgent/log
    dr-xr-x--x 3 root cfgsoft 4096 Jul 2 17:34 ThirdParty
    drwxr-xr-x 2 root root 4096 Jul 2 17:34 uninstall

  9. Run # netstat -na | grep to verify that the Agent is installed correctly, listening on the assigned port, and ready to collect data.

    The default is 26542 for VCM installations.

What to do next

Run a collection for Mac OS X data. See Collect Mac OS X Data.

See Also

Manually Uninstalling the Mac OS X Agent

Help us improve this topic. Send feedback to . | Technical Support | © 2006–2015 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.

Frequently Asked Questions

  1. 1. Customers who purchased and registered a copy of Parallels Desktop 15 for Mac from the Parallels Online Store or an authorized reseller on or after August 1, 2020 through September 30, 2020, are eligible for an upgrade to the next version of Parallels Desktop for Mac at no charge, subject to certain conditions. For details on the Tech Guarantee 2020, please visit the Tech Guarantee page.
    Note: : If you have a subscription for Parallels Desktop for Mac, Parallels Desktop for Mac Pro Edition, or Parallels Desktop for Mac Business Edition, you can upgrade Parallels Desktop to the latest version with the license you own. Download and install Parallels Desktop 16 and use your subscription license for activation.
  2. You should receive your upgrade key within 7 days after the new version of Parallels Desktop for Mac becomes available. The upgrade key will be sent to the email that was used for registration of your Parallels Desktop 15 for Mac license.
    If you have not yet registered your copy of Parallels Desktop 15 for Mac, please register it in your Parallels account.
  1. I have already purchased a Parallels Desktop 16 license, can I use Parallels Desktop 16.5 update on Mac with M1?
    Yes, any license you purchased to use with Parallels Desktop 16 is valid with a Parallels Desktop 16.5 update.
  2. I have an existing Windows 10 virtual machine on an Intel-based Mac. Can I continue using it on a Mac with Apple M1 chip?
    No, you will need to create a new ARM-based virtual machine. Running VMs on a Mac with Apple M1 chip in Parallels Desktop 16.5 requires ARM-based operating systems (OSes). Learn about installing ARM-based OSes here.
  3. I want to know how to install a new ARM-based virtual machine with Parallels Desktop on Mac with M1 chip.
    Please visit KB 125375 for instructions.
  4. I want to transfer my data from an existing virtual machine to a new one on Mac with M1 chip
    For complete instructions on how to transfer your data from an existing virtual machine to a new one on Mac with M1 chip, visit KB 125344.
  5. I have installed the Technical Preview of Parallels Desktop for Mac with M1. Can I download Parallels Desktop 16.5 for free?
    Parallels team provided Technical Preview builds for free. Parallels Desktop 16.5 is an update to Parallels Desktop 16 and requires a license. The license can be purchased either online at parallels.com/desktop (which also offers free full-featured 14-day trials) or from retail and online stores worldwide.
  1. Does Windows come pre-installed with Parallels Desktop for Mac?
    Windows is not included with your purchase of Parallels Desktop for Mac. Windows can be purchased directly from Microsoft or retail stores. Please visit KB 9003 for additional information.
  2. Will Parallels run on my current Mac hardware?
    A full list of system and hardware requirements can be found here.
  3. What is the difference between Standard and Pro Editions?
    Visit KB 123296.
  4. What is the difference between a permanent license and a subscription?
    Visit KB 122929.
  5. Can I use my license on multiple Mac computers?
    Parallels licenses are valid only on one Mac per license. For more information, please reference www.parallels.com/about/eula/.
  6. Do you have discounts for Students/Education Staff/offer academic licenses?
    Yes. For more information on Education licenses, visit KB 113630.
  7. Is there a trial version of Parallels Desktop for Mac I can evaluate before purchasing?
    Yes, Parallels offers a free 14 day trial at www.parallels.com/products/desktop/trial/
  1. Install or upgrade to the latest version of Parallels Desktop for Mac.
    Visit KB 124250.
  2. Install Windows in Parallels Desktop for Mac.
    Visit KB 4729.
  3. Migrate my current Windows PC to a Parallels Desktop for Mac virtual machine.
    For instructions, visit KB 123929.
  4. Register and activate Parallels Desktop for Mac.
    Visit KB 124225.
  5. Launch Windows from Parallels Desktop for Mac.
    Visit KB 115170.
  6. Upgrade my license to Pro Edition
    Visit KB 123159.
  7. Install Quicken, MS Office or other software in Windows virtual machine.
    Visit KB 119310.
  8. Learn how to use the Coherence mode.
    Visit KB 4670.
  9. Learn how to use the Parallels Desktop sharing tools.
    Visit KB 122567.

Agent Shift Mac Os X

  1. What is Parallels Toolbox?
    Visit KB 123903 and KB 124200 to learn about Parallels Toolbox for Mac and for Windows.
  2. How can I get Parallels Toolbox?
    See KB 123902 about Parallels Toolbox for Mac and KB 124202 about the Windows version.
  3. How do I install Parallels Toolbox?
    Visit KB 123904 for information on the Mac version, and KB 124183 to learn how to install the Windows one.

Agent Shift Mac Os 11

  1. How to give more hard disk space to a Windows virtual machine?
    Visit KB 113972.
  2. How can I improve virtual machine performance on my Mac?
    Visit KB 112091.
  3. How to reinstall Parallels Tools in Windows Guest OS?
    Visit KB 4841.
  4. Fix network issues in a Windows virtual machine.
    Visit KB 8978.
  5. Free up disk space on Mac.
    Visit KB 123553.
  6. Fix 'There's not enough disk space available to start the Windows virtual machine.'
    Visit KB 10117.
  7. Fix 'Unable to connect USB device to virtual machine now. Try to connect this USB device later.'
    Visit KB 10136.




broken image