13.13 EnableSiteComm

Use this Knowledge Script to resume regular ongoing network communication from a managed client to the management server. Network communication may be disabled because you have run the DisableSiteComm script to disable network communication between the managed client and management server.

As soon as network communication is restored, any information temporarily stored in the local repository of the managed client while communication was disabled is transferred to the management server, either immediately or in the next scheduled upload if the managed client is configured to transfer events or data according to a schedule.

If a managed client is managed by more than one site (that is, if information for the managed client is stored in more than one repository) you can set the Enable communications for all sites parameter to y to enable communication from the managed client to all management sites with which the managed client communicates.

In this simplified example, MC 2 normally sends data and events to both ORLANDO and MIAMI, but communication with these sites has been temporarily disabled for this managed client.

If you run this script on MC 2 and enable the Enable communications for all sites parameter, communication to both ORLANDO (Repository 1) and MIAMI (Repository 2) is re-enabled for MC 2.

You can set Enable communications for all sites to n to enable communication from the managed client only for the repository you are currently logged onto.

For example, if you have logged onto Repository 1 in AppManager (in the Login dialog box), and run this script on MC 2 with Enable communications for all sites Select n, communication between MC 2 and Repository 1 is enabled, but communication between MC 2 and Repository 2 remains disabled.

13.13.1 Resource Objects

Windows 2003 Server or later

13.13.2 Default Schedule

The default interval for this script is Run once.

13.13.3 Setting Parameter Values

Set the following parameters as needed:

Parameter	How to Set It
Enable communications for all sites?	Set to y to enable communication from the managed client to all repositories the managed client communicates with Set to n to enable communication from the managed client to the repository you are logged onto. The default is n.
Raise event when attempt to enable communication succeeds?	Set to y to generate an event indicating the success or failure of the operation. The default is n.
Event severity when attempt to enable communication succeeds	Set the event severity level, from 1 to 40, to reflect the importance when the communication succeeds. The default is 25.
Event severity when attempt to enable communication fail	Set the event severity level, from 1 to 40, to reflect the importance when the job fails. The default is 5.