Using CA ARCserve D2D › Deploy CA ARCserve D2D Remotely › Remote Deployment Considerations

Remote Deployment Considerations

Before you deploy CA ARCserve D2D remotely to other selected servers, note the following considerations:

1. 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)
2. 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)"
3. 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 inbound role for the network profile and allow "File and Printer Sharing (SMB-In)" for port 445
4. By default, only the build-in "administrator" has access rights to "admin$" in Windows 7. 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.
5. Allow access the remote %HOMEDrive%$ (e.g C$), ensure that the share is available from "Computer Management"