How to Move a Proxy Configuration from One Server to Another (295430)

MORE INFORMATION

Moving the Configuration to New Server with a Different Name

To replicate a proxy configuration from your old server to a new one, join the computers together to form an array. When the configuration is replicated across the servers, you can break the array, and then take down the old server.

The following parameters are replicated within an array:

• Domain filters
• Web Proxy service protocol access control information
• Web Proxy service caching options (including advanced caching options such as cache filters)
• Web Proxy service upstream routing options
• Web Proxy service publishing (reverse proxying) information
• WinSock Proxy service protocol definitions
• WinSock Proxy service access control information
• Socks Proxy service permissions
• Logging configuration for each service, including packet filter logging
• Packet filter alerting information
• Local Address Table (LAT) information
• Client configuration information

NOTE: When replication occurs, the array member that you are currently administering is always updated first The following parameters are not replicated in the array:

• Web Proxy service enable caching flag
• Web Proxy cache size
• Web Proxy cache disk location
• Web Proxy service folder information
• Logging folder for each service
• Packet filters
• Microsoft Internet Information Services (IIS) WWW service password authentication settings

Moving a Configuration to a New Server That Has the Same Name

To bring up a server that has the same name as the old proxy server, back up the proxy configuration to an .mpc file, and then import the .mpc file to the new server. You may need to edit the .mpc file before you import it into the new server if the log files or the cache are in different locations, or if local groups do not yet exist on the new server.

The following list describes error messages that may occur when you misconfigure the .mpc file, and the how to resolve the issues that cause the error messages:

• Failed to set Cache Configuration, System Error 21
  To resolve this issue, edit the locations that are specific to the cache to accurately reflect its new settings.
• Failed to set Protocols Configuration, System Error 1332
  To resolve this issue:
  
  
  1. Create a .wpc file, and then copy all the protocols from the [@MSP_WSP Protocols] section to the next [@........] section in the old .mpc file to the new .wpc file.
  2. Open WinSock properties, click the Protocols tab, and then load the new .wpc file.
  If the error message still occurs, verify that there is no reference to a local group on the new server that is not yet created. If there is, you must create that local group on the new server.
• No mapping between account names and security ID was done.
  To resolve this issue, verify that the new server has the same user accounts and local groups as the old server. If the user accounts and local groups are different, open the Winsock Proxy properties, click the Permission tab, and then add user-protocol pairs. You can also remove all Usern= lines under each protocol in the .wpc file, import the .wpc again, and then import the .mpc again.
• Failed to set log configuration for @msp_proxylog, system error 3

  -or-

  Failed to set log configuration for @msp_wsplog, system error 3

  -or-

  Failed to set log configuration for @msp_socklog, system error 3

  -or-

  Failed to set log configuration for @msp_pfdlog, system error 3
  To resolve this issue, change the LogFileDirectory= setting to point to the correct location.
• Failed to set socks configuration, system error 3
  To resolve this issue, verify that the Socks_SocksConfigFile= setting in the [@MSP_RegKeys] section is pointing to the correct location.
• The intra-array IP address of one or more servers in the present array is not correct. Please verify the listed intra-array IP address of each server in the routing properties of the web proxy service:
  To resolve this issue, verify that the Addr1= setting contains the IP address for the new server that is specified, and then verify that the NodeComputerName= setting in the [@MSP_PCM1] setting is correct.