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

Creates a new device update management test device. Test devices provide a way for administrators to test firmware updates before those updates are distributed to all the devices in an organization.

Syntax


New-CsTestDevice -Identity <XdsIdentity> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Identifier <String>] [-IdentifierType <MACAddress \| SerialNumber>] [-InMemory <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

New-CsTestDevice -Identity <XdsIdentity> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Identifier <String>] [-IdentifierType <MACAddress | SerialNumber>] [-InMemory <SwitchParameter>] [-WhatIf [<SwitchParameter>]]


New-CsTestDevice -Name <String> -Parent <String> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Identifier <String>] [-IdentifierType <MACAddress \| SerialNumber>] [-InMemory <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

New-CsTestDevice -Name <String> -Parent <String> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Identifier <String>] [-IdentifierType <MACAddress | SerialNumber>] [-InMemory <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

Parameters

Parameter	Required	Type	Description
Identity	Required	XdsIdentity	Indicates the Identity for the new test device. An Identity consists of both the scope where the test device is to be assigned (e.g., site:Redmond) and the name for the new device (for example, UCPhone). To assign a test device named UCPhone to the Redmond site your Identity parameter must look like this: -Identity "site:Redmond/UCPhone".
IdentifierType	Required	String	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.
Identifier	Required	String	Based on the IdentifierType, indicates the MAC address or serial number of the new test device.
Parent	Optional	String	Name of the scope (for example, site:Redmond) where the new test device is to be assigned. If you use the –Parent parameter then you must also use the –Name parameter; for example: -Parent site:Redmond –Name UCPhone. If you use –Parent then you should not use –Identity, and vice-versa.
Name	Optional	String	Name for the new test device (names must be unique within a given scope). The –Name parameter should be used only when using the –Parent parameter.
InMemory	Optional	Switch Parameter	Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet’s matching Set- cmdlet.
Force	Optional	Switch Parameter	Suppresses the display of any non-fatal error message that might arise when running the command.
WhatIf	Optional	Switch parameter	Describes what would happen if you executed the command without actually executing the command.
Confirm	Optional	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.

Test devices are created by using the New-CsTestDevice cmdlet. These devices can be configured at either the global scope or the site scope.

Return Types

Creates new instances of the Microsoft.Rtc.Management.WriteableConfig.Settings.DeviceUpdate.TestDevice object.

Examples

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

	Copy Code
New-CsTestDevice -Identity site:Redmond/UCPhone -IdentifierType -SerialNumber -Identifier "07823-A345"

The preceding command creates a new test device (named UCPhone) for the Redmond site. Note the syntax used to specify the device Identity: the device scope (site:Redmond) followed by the / character followed by the device Name (UCPhone). This device uses the serial number as the IdentifierType, and has a serial number of 07823-A345.

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

	Copy Code
New-CsTestDevice -Parent Redmond -Name UCPhone -IdentifierType -SerialNumber -Identifier "07823-A345"

The command shown in Example 2 is a variation of the command shown in Example 1. In Example 2, however, the –Identity parameter is not used. Instead, the –Parent parameter is used to specify the scope for the new test device (site:Redmond) and the –Name parameter is used to indicate the name for the new device (UCPhone). The New-CsTestDevice cmdlet will take those two parameter values and construct the test device Identity (site:Redmond/UCPhone) for you.