ConvertFrom-FIMResource

ConvertFrom-FIMResource

Serializes FIMResource objects and stores them in the given file.

Syntax

ConvertFrom-FIMResource [-objects] <ImportObject[] | ExportObject[] | MatchObject[]> [-file] <string> [<CommonParameters>]

Detailed Description

The ConvertFrom-FIMResource in the Windows PowerShell™ command-line interface serializes into XML resources used elsewhere in the Forefront Identity Manager (FIM) Automation snap-in. The cmdlet takes ExportObject, ImportObject, or MatchObject instances as input. With this cmdlet, you can save intermediate work and transfer it among computers.

The cmdlet serializes the resources by using XmlObjectSerializer in Microsoft .NET. You must use this cmdlet instead of Export-Clixml because Export-Clixml does not preserve nested and complex types.

To help distinguish ConvertTo-FIMResource from ConvertFrom-FIMResource, remember that you are converting from FIM resources to a file.

For more information about the Microsoft® Forefront Identity Manager (FIM) 2010 Windows PowerShell™ cmdlet set see Forefront Identity Manager Configuration with Windows PowerShell.

Parameters

--Objects <ImportObject[] | ExportObject[] | MatchObject[]>

Specifies the objects to serialize as a set of ImportObject, ExportObject, or MatchObject instances. The following is an example use of this parameter:

-objects $exports

Attributes

--File <string>

Specifies the file in which to store the converted FIM resource resources. The following is an example of how to use this parameter:

-file “C:\Fabrikam FIM Configuration\config002.xml”

Attributes

--CommonParameters

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see about_CommonParameters.

-CommonParameter

This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, and OutVariable. For more information, see about_CommonParameters.

Input and Return Types

The input type is the type of the objects that you can pipe to the cmdlet. The return type is the type of the objects that the cmdlet emits.

Examples

EXAMPLE 1

Command prompt:

 
          $pilot = Export-FIMConfig -uri https://localhost:5725/ResourceManagementService -policyConfig 
          $pilot | ConvertFrom-FIMResource -file pilot.xml 
        

This is a simple example of how you can serialize ExportObject objects to transport across a firewall.

See Also

Reference

Export-FIMConfig
Join-FIMConfig
Compare-FIMConfig
Import-FIMConfig
ConvertTo-FIMResource