Configuring communication settings for a location

Article:HOWTO26969  |  Created: 2010-01-08  |  Updated: 2010-01-15  |  Article URL http://www.symantec.com/docs/HOWTO26969
Article Type
How To


Environment


Configuring communication settings for a location

By default, you configure the same communication settings between the management server and the client for all the locations within a group. However, you can also configure these settings for each location separately. For example, you can use a separate management server for a location where the client computers connect through the VPN. Or, to minimize the number of clients that connect to the management server at the same time, you can specify a different heartbeat for each location.

See Configuring push mode or pull mode to update client policies and content.

You can configure the following communication settings for locations:

The following settings are specific to locations:

  • The control mode that the clients run in.

  • The management server list that the clients use.

  • The download mode that the clients run in.

  • Whether or not you want a list of all the applications that are executed on clients to be collected and sent to the management server.

  • The heartbeat interval that clients use for downloads.

  • Whether or not the management server randomizes content downloads from the default management server or a Group Update Provider.

To configure communication settings for a location

  1. In the console, click Clients.

  2. On the Clients page, select a group.

  3. On the Policies tab, under Location-specific Policies and Settings, under a location, expand Location-specific Settings.

  4. To the right of Communications Settings, click Tasks, and then uncheck Use Group Communications Settings.

  5. Click Tasks again, and then click Edit Settings.

  6. In the Communications Settings for location name dialog box, modify the settings for that location only.

  7. Click OK.


Legacy ID



349326


Article URL http://www.symantec.com/docs/HOWTO26969


Terms of use for this information are found in Legal Notices