Set-CsHealthMonitoringConfiguration [-Identity <XdsGlobalRelativeIdentity>] [-Confirm [<SwitchParameter>]] [-FirstTestSamAccountName <String>] [-FirstTestUserSipUri <String>] [-Force <SwitchParameter>] [-SecondTestSamAccountName <String>] [-SecondTestUserSipUri <String>] [-WhatIf [<SwitchParameter>]]

Set-CsHealthMonitoringConfiguration [-Confirm [<SwitchParameter>]] [-FirstTestSamAccountName <String>] [-FirstTestUserSipUri <String>] [-Force <SwitchParameter>] [-Instance <PSObject>] [-SecondTestSamAccountName <String>] [-SecondTestUserSipUri <String>] [-WhatIf [<SwitchParameter>]]

Parameters

Synthetic transactions are used in Microsoft Communications Server to verify that users are able to successfully complete common tasks such as logging on to the system, exchanging instant messages, or making calls to a phone located on the Public Switched Telephone Network (PSTN). These tests can be conducted "manually" by an administrator, or they can be automatically run by an application such as Microsoft System Center Operations Manager.

Synthetic transactions can be conducted in two different ways. Many administrators will use the CsHealthMonitoringConfiguration cmdlets to set up a "health monitoring registrar" for each of their registrar pools. A health monitoring registrar is nothing more than a pair of users that have been preconfigured for use with synthetic transactions. (Typically these are test accounts and not accounts belonging to actual users.) When a health monitoring registrar is configured for a pool, administrators can run a synthetic transaction against that pool without having to specify the identities of (and supply the credentials for) the user accounts involved in the test. Instead, the synthetic transaction will automatically use the preconfigured test accounts when performing its checks.

Alternatively, administrators can run a synthetic transaction using actual user accounts. For example, if two users are unable to exchange instant messages, an administrator can run a synthetic transaction using the two user accounts in question (as opposed to a pair of test accounts). If you decide to conduct a synthetic transaction using actual user accounts keep in mind that you will have to supply the logon names and passwords for each user.

After you have configured a health monitoring registrar you can modify that registrar at any time by using the Set-CsHealthMonitoringConfiguration cmdlet. This cmdlet provides a way for you to change either (or both) of the test accounts configured for use with the registrar.

Set-CsHealthMonitoringConfiguration modifies existing instances of the Microsoft.Rtc.Management.WritableConfig.Settings.HealthMonitoring.HealthMonitoringSettings object.

-------------------------- Example 1 ------------------------

	Copy Code
Set-CsHealthMonitoringConfiguration -Identity atl-cs-001.litwareinc.com -FirstTestUserSipUri "sip:kenmyer@litwareinc.com" -FirstTestSamAccountName "kenmyer"

The command shown in Example 1 modifies the first test user assigned to the health monitoring configuration settings for the pool atl-cs-001.litwareinc.com. In this example, the SIP address for the new test user is set to sip:kenmyer@litwareinc.com and the SamAccountName for this test user is set to kenmyer.

-------------------------- Example 2 ------------------------

	Copy Code
Get-CsHealthMonitoringConfiguration | Set-CsHealthMonitoringConfiguration -FirstTestUserSipUri "sip:kenmyer@litwareinc.com" -FirstTestSamAccountName "kenmyer"

The preceding command is a variation of the command shown in Example 1. In this case, however, the same new test user is assigned to each collection of health monitoring configuration settings in use in the organization. To carry out this task, the command first uses Get-CsHealthMonitoringConfiguration to return a collection of all the health monitoring configuration settings. This collection is then piped to Set-CsHealthMonitoringConfiguration, which assigns the same first test user SIP address and SamAccountName to each item in the collection.

-------------------------- Example 3 ------------------------

	Copy Code
Get-CsHealthMonitoringConfiguration | Where-Object {$_.FirstTestUserSipUri -eq "sip:jhaas@litwareinc.com"} | Set-CsHealthMonitoringConfiguration -FirstTestUserSipUri "sip:kenmyer@litwareinc.com" -FirstTestSamAccountName "kenmyer"

Example 3 shows how you can do a search-and-replace for the first test user assigned to a collection of health configuration settings; in this example, the user with the SIP address sip:jhaas@litwareinc.com is replaced any time that user appears as the first test user in a collection.

To do this, the command first calls Get-CsHealthMonitoringConfiguration without any additional parameters; that returns a collection of all the health monitoring configuration settings currently in use in the organization. This collection is then piped to the Where-Object cmdlet, which picks out only those items where the FirstTestUserSipUri property is equal to (-eq) sip:jhaas@litwareinc.com. That filtered collection is , in turn, piped to Set-CsHealthMonitoringConfiguration, which takes each item in the collection and sets the value of the FirstTestUserSipUri property to sip:kenmyer@litwareinc.com and the value of the FirstTestSamAccountName property to kenmyer.