Udostępnij za pośrednictwem

Pre-requisites for remote push install of Mobility Service (guest agents)

  • Artykuł

From the Migration Accelerator portal you can remotely push Mobility Service (guest agents) on to the source server. You can remotely deploy agents on multiple servers without relying on another deployment technology or worry about installing it manually.  Follow the pre-requisites recommend in this article to successfully push install your agents from the MA portal.

Push Install pre-requisites for Windows

  • Add Windows Management Instrumentation (WMI) and File and Printer Sharing to Windows firewall exception for all 3 profiles (Domain, Private and Public).
  • Ensure the domain\username (or local account) and password entered in MA portal for push installation is part of Local Administrators group .
  • For local user account, make sure the Remote UAC is disabled.

Steps to configure the pre-requisites:

Windows Firewall settings

  • Open Windows firewall from Control Panel.

  • Click on “Allow a program or feature through Windows firewall”.

  • Check “File and Printer Sharing” for all 3 profiles (Domain, Private and Public).

  • Check “Windows Management Instrumentation (WMI) ” for all 3 profiles (Domain, Private and Public).Click OK.

  • User account:

  • Using local user account:
    • Create local user.
      • Open Local Users and Groups. Click Start, click Run, type lusrmgr.msc, and then press ENTER.
      • Right-click on Users and select New User.
      • Enter user name and password.
      • Uncheck User must change password at next logon and check Password never expires.
      • Click Create and Close.
    • Add local user to Administrators group
      • Open Local Users and Groups. Click Start, click Run, type lusrmgr.msc, and then press ENTER.
    • Double-click the Groups folder.
    • Right-click the Administrators group and then click Add to Group.
    • Click Add, and then type the name of the user account created in step (1.a).
      • Click Check Names, click OK, and then click OK again.

    • Disable Remote UAC using registry key.

      • Click Start, click Run, type regedit, and then press ENTER
      • Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

      • If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:
        • On the Edit menu, point to New, and then click DWORD Value.
        • Type LocalAccountTokenFilterPolicy, and then press ENTER.

      • Right-click LocalAccountTokenFilterPolicy, and then click Modify.

      • In the Value data box, type 1, and then click OK.

      • Exit Registry Editor.

  • Using domain user account:

    • Create domain user

      • Logon to domain or DC machine.
      • Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
      • In the Active Directory Users and Computers window, expand <domain name.com>
      • Right-click Users, point to New, and then click User.
      • In the New Object - User dialog box, enter First name and User logon name and then click Next.
      • In the Password box, type a password for the account, and then in the Confirm password box, type the password again.
      • Select User cannot change password and Password never expires, and then click Next.
      • Click Finish.

    • Add domain user to Administrators group

        • Logon to remote target machine where you want to install UA agents.
        • Open Local Users and Groups. Click Start, click Run, type lusrmgr.msc, and then press ENTER.
        • Double-click the Groups folder.
        • Right-click the Administrators group and then click Add to Group.
        • Click Add, and then type the name of the user account created in step (2.a).
        • Click Check Names, click OK, and then click OK again.

Additional Trouble Shooting References:

Push Install pre-requisites for Linux:

  • Connection to the source machine should be with root user account.
  • Port number 22 should be opened on the source machine to allow for ssh connections.
  • Source machine should have openssh, openssh-askpass, openssh-server, openssh-clients and openssl packages installed. On Cent OS, the package can be installed with the following command:

yum install openssh*

  • The source machine should allow enabling of Password Authentication over SSH channel. The following steps are required to enable it.
    • Login under the root user account
    • Edit the file /etc/ssh/sshd_config
    • Find the line that begins with “PasswordAuthentication”
    • Change the value from “no” to “yes”
    • Save the changes and restart the sshd service.

Comments

  • Anonymous
    February 18, 2015
    Microsoft Migration Accelerator (MA) enables you to migrate workloads running in your enterprise to Azure
  • Anonymous
    February 18, 2015
    This page will be updated periodically with frequently asked questions, common Issues and their solutions