Using CA ARCserve D2D › How to Deploy CA ARCserve D2D Remotely › Review the Remote Deployment Considerations

Review the Remote Deployment Considerations

Review the following remote deployment considerations before installing CA ARCserve D2D Remotely:

• Ensure that the following ports are available:
  • Port 15011 (used for ADT internal communication)
  • Port 445 (used to access the admin$ and %HOMEDRIVE%$, and remote registry settings)
• Ensure that pinging of the remote machine is enabled.

  To verify if the machine can be pinged, perform the following task:

  1. Access the Firewall advance settings for In-Bound Rule.
  2. For the current network profile:
     • Enable Networking – Echo Request (ICMPv4-In)
     • Enable Networking – Echo Request (ICMPv6-In)

• Allow access to the remote admin$ share.

  If the firewall is turned on from the remote machine, to enable the access to Admin$ on the remote machine, perform the following task:

  1. Access the Firewall advance settings for In-Bound Rule.
  2. For the current network profile:
     • Enable Netlogon Service (NP-In)
     • Enable the in-bound role for the network profile and allow File and Printer Sharing (SMB-In) for port 445

• By default, only the built-in administrator has access rights to admin$ in Windows 7 and Windows 8. To allow non-built-in administrator (users in Administrators group) to access the admin$, perform the following task:
  1. Start edit registry.
  2. Locate key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
  3. Manually create a DWORD value for LocalAccountTokenFilterPolicy = 0x1.
• Allow access to the remote %HOMEDrive%$ (for example, C$) and verify that the share is available from the Computer Management.