Topic Last Modified: 2015-03-09

Deletes any rejected device update files that are no longer associated with a device. This cmdlet was introduced in Lync Server 2010.

Clear-CsDeviceUpdateFile -Identity <XdsIdentity> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

The command shown in Example 1 deletes all the device update files from the service that are no longer associated with a device.

Clear-CsDeviceUpdateFile -Identity ""

Each time new device updates are uploaded to the system, a corresponding device update rule is created. By default, these new device update rules are assigned to the Pending state; that means that the rules can be downloaded and installed on test devices, but not on production devices. In turn, this gives you an opportunity to test the updates before making them available to users. If testing is successful, you can then run the Approve-CsDeviceUpdateRule cmdlet to make these device updates available to users.

If testing is not successful then you can use the Reset-CsDeviceUpdateRule cmdlet or the Restore-CsDeviceUpdateRule cmdlet to reject an update. When these cmdlets are run, the device update is disassociated from its device update rule. At that point, administrators can then use the Clear-CsDeviceUpdateFile cmdlet to remove the disassociated updates from the server.


Parameter Required Type Description




Unique identifier of the service hosting the device update files. For example, this syntax clears device update files from the Web Services service for the pool -Identity "".




Prompts you for confirmation before executing the command.




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




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

None. The Clear-CsDeviceUpdateFile cmdlet does not accept pipelined input.

None. The Clear-CsDeviceUpdateFile cmdlet does not return any values.