Approves a device update rule that has been imported to the system. After a device update rule has been approved, the corresponding update will automatically be downloaded and installed by client devices affected by the update.
Syntax
Approve-CsDeviceUpdateRule [-Identity <XdsIdentity>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-WhatIf [<SwitchParameter>]] |
Approve-CsDeviceUpdateRule [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Instance <PSObject>] [-WhatIf [<SwitchParameter>]] |
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
|
Identity |
Optional |
String |
Unique identifier for the device update rule being approved. The Identity for a device update rule consists of two parts: the service where the device update rule has been assigned (for example, service:WebServer:atl-cs-001.litwareinc.com) and a GUID (globally unique identifier). Consequently, a device update rule configured for the Redmond site will have an Identity similar to this: service:WebServer:atl-cs-001.litwareinc.com /d5ce3c10-2588-420a-82ac-dc2d9b1222ff9. |
|
Instance |
Optional |
DeviceUpdate.Rule object |
Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. |
|
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
Microsoft Communications Server 2010 uses "device update rules" as a way to provide firmware updates to devices (such as Tanjay telephones and the RoundTable conferencing station) that run Communicator “14” Phone Edition. Periodically, administrators upload a set of device update rules to Communications Server 2010; after those rules have been tested and approved, they are then automatically downloaded and applied to the appropriate devices as those devices connect to the system. By default, devices check for new update rules each time they turn on and connect to Communications Server 2010; devices also check for updates every 24 hours after that initial sign-on.
Each new device update rule added to the system is marked as "Pending." That means that the update will be downloaded and installed by the appropriate test devices; however, it will not be downloaded and installed by client devices in general. This gives you an opportunity to test the updates and ensure that there are no adverse effects before you make this update widely available. As soon as you are convinced that the update is "safe," you can then use the Approve-CsDeviceUpdateRule to approve the update.
When you approve an update, the PendingVersion of the associated update rule is assigned to the ApprovedVersion, and the PendingVersion property is cleared. For example, suppose the PendingVersion of a new update rule is version 1.0.0.1. After you run Approve-CsDeviceUpdateRule, the PendingVersion will be set to a null value, and the ApprovedVersion will be set to 1.0.0.1. The next time a client device logs on, the device will automatically check to see if there are any newly-approved updates applicable for that device. If so, the update will automatically be downloaded and installed.
Return Types
Approve-CsDeviceUpdateRule approves instances of the Microsoft.Rtc.Management.WriteableConfig.Settings.DeviceUpdate.DeviceUpdate.Rule object.
Examples
-------------------------- Example 1 ------------------------
 Copy Code |
|
|---|---|
Approve-CsDeviceUpdateRule -Identity service:WebServer:atl-cs-001.litwareinc.com/d5ce3c10-2588-420a-82ac-dc2d9b1222ff9 |
|
The command shown in Example 1 approves the device update rule d5ce3c10-2588-420a-82ac-dc2d9b1222ff9 found on the service WebServer:atl-cs-001.litwareinc.com.
-------------------------- Example 2 ------------------------
| Copy Code |
|
|---|---|
Get-CsDeviceUpdateRule -Filter service:WebServer:atl-cs-001.litwareinc.com* | Approve-CsDeviceUpdateRule |
|
The preceding command approves all the device update rules that have been configured for the service WebServer:atl-cs-001.litwareinc.com. To carry out this task, the command first calls Get-CsDeviceUpdateRule along with the –Filter parameter; the filter value "service:WebServer:atl-cs-001.litwareinc.com*" ensures that only those rules that have an Identity that begins with the string value "service:WebServer:atl-cs-001.litwareinc.com" will be returned. (By definition, these are all the device update rules that have been assigned to the service WebServer:atl-cs-001.litwareinc.com.) This filtered collection is then piped to the Approve-CsDeviceUpdateRule cmdlet, which, in turn, approves each rule in the collection.
-------------------------- Example 3 ------------------------
| Copy Code |
|
|---|---|
Get-CsDeviceUpdateRule | Where-Object {$_.Brand -eq "LG-Nortel"} | Approve-CsDeviceUpdateRule
|
|
The command shown in Example 3 approves all the device update rules for the specified brand (LG-Nortel). To do this, the command first calls Get-CsDeviceUpdateRule to return a collection of all the device update rules currently in use in the organization. This collection is then piped to the Where-Object cmdlet, which picks out only those rules where the Brand property is equal to (-eq) LG-Nortel. This filtered collection is then piped to Restore-CsDeviceUpdateRule, which proceeds to approve each rule in the collection.