[This is preliminary documentation and is subject to change. Blank topics are included as placeholders.]

Modifies one or more of the device update management test devices that have been configured for use in your organization. Test devices provide a way for administrators to test firmware updates before those updates are distributed to all the devices in an organization.


Set-CsTestDevice [-Identity <XdsIdentity>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Identifier <String>] [-IdentifierType <MACAddress | SerialNumber>] [-WhatIf [<SwitchParameter>]]
Set-CsTestDevice [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Identifier <String>] [-IdentifierType <MACAddress | SerialNumber>] [-Instance <PSObject>] [-WhatIf [<SwitchParameter>]]


Parameter Required Type Description




Indicates the Identity of the test device to be modified. For example: -Identity site:Redmond/UCPhoneTestDevice. Note that you cannot use wildcards when specifying an Identity.



Test device object

Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values.




Indicates whether the test device will be uniquely identified by its MAC address or by its serial number. To identify a device by its MAC address set the IdentifierType to MACAddress. To identify a device by its serial number set the IdentifierType to SerialNumber. MACAddress and SerialNumber are the only allowed values.




Based on the IdentifierType, indicates the MAC address or serial number of the new test device.



Switch Parameter

Suppresses the display of any non-fatal error message that might arise when running the command.



Switch Parameter

Describes what would happen if you executed the command without actually executing the command.



Switch Parameter

Prompts you for confirmation before executing the command.

Detailed Description

By identifying specific Microsoft Communicator “14” Phone Edition phones or other devices as test devices, administrators can verify and approve firmware updates before those updates are rolled out to all the relevant devices in the organization. When device update rules are imported to Microsoft Communications Server 2010, those rules are marked as "pending;" that means that the updates corresponding to these rules will not automatically be downloaded and installed by the affected devices.

Instead, these pending rules will be downloaded and installed by any relevant test devices. That’s the whole idea behind test devices: new device update rules are automatically applied to test devices, giving administrators the opportunity to very that the firmware updates work as expected. If they do, those administrators can then mark the rules as approved; approved rules are then downloaded and installed by all the relevant devices in the organization.

To identify the phones and other hardware devices that will act as your test devices you must create test device objects using the New-CsTestDevice cmdlet. After a test device has been created you can then use the Set-CsTestDevice cmdlet to change the Identifier and/or the IdentifierType of any existing device.

Return Types

Set-CsTestDevice does not return a value or object. Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.WriteableConfig.Settings.DeviceUpdate.TestDevice object.


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

Copy Code
Set-CsTestDevice -Identity site:Redmond/UCPhone -Identifier "09768-ABDR-83295"

The preceding command modifies the Identifier property for the test device named UCPhone assigned to the Redmond site.

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

Copy Code
Set-CsTestDevice -Identity site:Redmond/UCPhone -IdentifierType SerialNumber -Identifier "09768-ABDR-83295"

The command shown in Example 2 also modifies the test device named UCPhone assigned to the Redmond site. In this case, however, the command not only specifies a new Identifier but also assigns a new IdentifierType: SerialNumber.