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

Imports a set of device update rules downloaded from Microsoft.com. Device update rules associate firmware version updates with hardware devices; that is, with telephones and other devices running Microsoft Communicator “14” Phone Edition.

Syntax


Import-CsDeviceUpdate -Identity <XdsIdentity> [-Confirm [<SwitchParameter>]] [-FileName <String>] [-Force <SwitchParameter>] [-LocalStore <SwitchParameter>] [-WhatIf [<SwitchParameter>]]


Import-CsDeviceUpdate -Identity <XdsIdentity> [-ByteInput <Byte[]>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-LocalStore <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

Parameters

Parameter	Required	Type	Description
Identity	Required	XdsIdentity	Indicates the service instance where the new update rules will be applied. For example: service:WebServer:atl-cs-001.litwareinc.com.
FileName	Optional	String	Path to the update file (e.g., C:\Updates\UCUpdates.cab). The -FileName parameter is used when the .CAB file is on the same computer as the service being updated.
ByteInput	Optional	String	Path to the update file (e.g., C:\Updates\UCUpdates.cab). The -ByteInput parameter is used when the .CAB file is on a different computer than the service being updated.
Force	Optional	Switch Parameter	Suppresses the display of any non-fatal error message that might arise when running the command.
LocalStore	Optional	Switch Parameter
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

Periodically, Microsoft releases a new set of device update rules for Communicator “14” Phone Edition. These rules represent firmware updates for devices (such as Tanjay telephones and the Roundtable conferencing station) that run Communicator “14” Phone Edition. After these rules have been imported administrators can test the firmware updates and then, assuming the tests succeed, can make the updates available to all the relevant devices used in the organization.

The only way to create new update rules is to download update packs from Microsoft; you cannot create your own device update rules. To obtain the latest set of device update rules, go to the Help and Support page on Microsoft.com and search for "Phone Edition". Download the update package and extract the files to a folder. (The folder can be on any computer that has access to Microsoft Communications Server 2010.) After the files have been extracted, you then use the Import-CsDeviceUpdate cmdlet to import the device update rules found in the extracted .CAB file (which will have a name similar to UCUpdates.cab).

Note that the syntax used to import the device update rules varies depending on the location of the .CAB file. For example, suppose you have extracted the file to a Communications Server Web Services server. In that case, you use the -FileName parameter to specify the file location; this parameter is used when the .CAB file is located on the same computer as the service where the update rules will be imported. Conversely, suppose you have extracted the .CAB file to your local workstation. In that case you use the -ByteInput parameter; that parameter is used when the .CAB file is located on a computer other than the one running the service to be updated.

Update rules can only be imported to services; they are not applicable at the global, site, or per-user scopes.

Input Types

Return Types

The Import-CsDeviceUpdate cmdlet imports instances of the Microsoft.Rtc.Management.WriteableConfig.Settings.DeviceUpdate.Rule class.

Examples

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

	Copy Code
Import-CsDeviceUpdate -Identity "service:WebServer:atl-cs-001.litwareinc.com" -FileName C:\Updates\UCUpdates.cab

The command shown in Example 1 imports device update rules from the file C:\Updates\UCUpdates.cab. Because the .CAB file is located on the same computer as the one running the service to be updated (service:WebServer:atl-cs-001.litwareinc.com) the -FileName parameter is used to indicate the file path.

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

	Copy Code
Import-CsDeviceUpdate -Identity "service:WebServer:atl-cs-001.litwareinc.com" -ByteInput \\atl-fs-001\Updates\UCUpdates.cab

The command shown in Example 2 imports device update rules from the file \\atl-fs-001\Updates\UCUpdates.cab. Because the .CAB file is located a different computer that the one running the service to be updated (service:WebServer:atl-cs-001.litwareinc.com) the -ByteInput parameter is used to indicate the file path.