Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2012-11-16

Use the Set-ResourceConfig cmdlet to set resource property schema and resource locations on the Resource Config object in Active Directory.

Syntax

Set-ResourceConfig [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-ResourcePropertySchema <MultiValuedProperty>] [-WhatIf [<SwitchParameter>]]

Detailed Description

Custom resource properties are features for room or equipment mailboxes. Administrators can indicate that a resource has a specific feature by assigning the corresponding custom resource property to that resource mailbox.

Important:
Custom resource properties can't include spaces.

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Resource mailbox schema configuration" entry in the Mailbox Permissions topic.

Parameters

Parameter Required Type Description

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory.

ResourcePropertySchema

Optional

Microsoft.Exchange.Data.MultiValuedProperty

The ResourcePropertySchema parameter specifies a list of custom strings that you can use to tag resources.

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch.

Input Types

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

Return Types

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

Examples

EXAMPLE 1

This example adds equipment and room resources to the custom Resource Config list in Active Directory.

Note:
All entries must start with either Room/ or Equipment/. Setting a new entry using the Set-ResourceConfig cmdlet overwrites all existing entries; it doesn't add a new entry to the list. Use the Get-ResourceConfig cmdlet to query the existing entries, and then append to the list. To add or remove entries without overwriting the current entries, see "EXAMPLE 2" and "EXAMPLE 3" later in this topic.
Copy Code 
Set-ResourceConfig -DomainController server1.contoso.com -ResourcePropertySchema ("Room/16Seats","Equipment/Projector","Room/8Seats","Equipment/Whiteboard")

EXAMPLE 2

This example creates three custom resource properties for room mailboxes and two custom resource properties for equipment mailboxes. This example also demonstrates two methods for adding new custom resource properties. The syntax of both commands can be used interchangeably. Perform the following steps:

  1. Read the current resource configuration and store it in a temporary variable called $ResourceConfiguration.

    Copy Code 
    $ResourceConfiguration = Get-ResourceConfig
  2. Create the custom properties AV, TV, and Whiteboard for room mailboxes.

    Note:
    This example assumes that some of the meeting rooms in your organization have audio-visual equipment, TV, or whiteboards. It also assumes that you want to differentiate the rooms that have the specified features from others that don't have these features.
    Copy Code 
    $ResourceConfiguration.ResourcePropertySchema+=("Room/AV")
$ResourceConfiguration.ResourcePropertySchema.Add("Room/TV")
$ResourceConfiguration.ResourcePropertySchema+=("Room/Whiteboard")
  3. Create the custom properties Car and Van for equipment mailboxes by running the following commands.

    Note:
    This example assumes that your organization uses equipment mailboxes to track the scheduling of company vehicles, and you plan to use the custom resource properties to specify the vehicle type.
    Copy Code 
    $ResourceConfiguration.ResourcePropertySchema.Add("Equipment/Car")
$ResourceConfiguration.ResourcePropertySchema+=("Equipment/Van")
  4. Update the resource configuration of your organization by using the modified resource property schema.

    Copy Code 
    Set-ResourceConfig -ResourcePropertySchema $ResourceConfiguration.ResourcePropertySchema

EXAMPLE 3

This example removes two of the custom resource properties for room mailboxes that were created in the previous example. The commands also demonstrate two methods for removing a custom resource property. The syntax of both commands can be used interchangeably.

  1. Read the current resource configuration and store it in a temporary variable called $ResourceConfiguration.

    Copy Code 
    $ResourceConfiguration = Get-ResourceConfig
  2. Remove the custom properties AV and TV for room mailboxes.

    Copy Code 
    $ResourceConfiguration.ResourcePropertySchema-=("Room/AV")
$ResourceConfiguration.ResourcePropertySchema.Remove("Room/TV")
  3. Update the resource configuration of your organization by using the modified resource property schema.

    Copy Code 
    Set-ResourceConfig -ResourcePropertySchema $ResourceConfiguration.ResourcePropertySchema